Hitachi Vantara Pentaho Community Forums
Results 1 to 5 of 5

Thread: Action Item: Pentaho Repository

  1. #1

    Default Action Item: Pentaho Repository

    Taking a quick look around, it looks like the only thing really missing is a remotely-accessible repository to access the compiled .jars.

    A simple Apache filesystem sharing will work with jar submittal through a local process, or you can have an Apache-WebDAV enabled approach to submit and retrieve through the same location.

    Either way, a repository is needed for at least SNAPSHOT builds.

    As for production jars (version 1.6.0, 1.6.1 finalized jars), either it can be hosted at Pentaho, or the maven community usually utilizes

    my two coppers,

  2. #2


    Posting a second thread to keep a seperation-of-concern, but also maintain the same concept of the thread.

    If you use a continuous integration system, the continuous integration can/should handle the actual deployments to the SNAPSHOT repositories.

    Unfortunately, this setup requires intimacy with the internals of the Pentaho development environment, so community can not help too much ;-)

  3. #3


    I have not seen any references to a maven2 repository for pentaho jars. Is this something that looks like might happen?

    similar request from Reporting side:

  4. #4

    Default Pentaho Maven Repository

    Hello Maven guys:

    I realize I am bumping an old thread here, but due to its popularity I thought it was worth a response. We (Pentaho) have stood up an Artifactory instance where we are deploying SNAPSHOTS. You can take a browse to see what we have on it so far. This is a work in progress, so by no means to we have everthing getting deployed to it from the CI process we have in place. Currently we have little more than the 2.0 BI Platform getting deployed regularly.

    There is a guest login to our public Artifactory instance @ User: guest, Passwd: guest.

    There is a little more background on what triggered the presence of this repo on another Maven thread here:
    We are forming documentation on our improved build process on the Wiki here.


  5. #5


    excellent, thank you!

    Artifactory is pretty well recognized, so good choice. If Artifactory starts becoming problematic, recommend also looking at Nexus (, especially for the downloadable index abilities that can be used within the Eclipse environment to quickly search for libraries (m2eclipse, q4e plugins).

    The only reason I switched was for that indexing ability, so not saying one is 'better' than the other, just the feature set with Nexus was found more useful in my environment.
    Last edited by dhartford; 11-05-2008 at 10:55 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.