Pentaho

 View Only

 Problem in accessing pnt-mvn repo

Harikrishna Ezhumalai's profile image
Harikrishna Ezhumalai posted 09-27-2024 05:59

Hi, 

I have a Java Maven application (Java 7), and we are triggering Pentaho job from Java code that connects to Postgres 9.x, using Pentaho-kettle version 5.0.7.

I am working on a stack upgrade from Java 7 to Java 8 and Postgres 9.x to 15.x—Seems the kettle 5.0.7 does not support Postgres 15.x and that leads me to upgrade pentaho-kettle mvn libraries 

And I am looking to have a Pentaho kettle  9.x version and am unable to get the libs in the below repos,

1. https://repo.orl.eng.hitachivantara.com/ui/native/pnt-mvn/  -- > It routing me to https://repo.orl.eng.hitachivantara.com/ui/login/

2. https://repo.orl.eng.hitachivantara.com/artifactory/pnt-mvn/ -- > It routing me to https://hitachiedge1.jfrog.io/ui/login/

Where to create the login?  a few years back I accessed it without login.

3. https://public.nexus.pentaho.org/content/groups/omni/ --> Site Unavailable.

Someone, please help me with how I can get pentaho-kettle 9.x mvn libs refs?

Thanks & Regards

Harikrishna E

Mladen Milev's profile image
Mladen Milev

Hi @Harikrishna Ezhumalai,

Pentaho supports Postgres 15 since version 10.1, where the current Pentaho Developer Edition is 10.2.

Please consult our matrix of supported databases.

We recommend you use our official compiled software.

If you have further questions, reach out to our sales team, that will guide you on the freely use of Pentaho Developer Edition under BSL, and the transition path to Pentaho Enterprise Edition. 

Hope this helps you.

Steven Maring's profile image
Steven Maring

The repo at https://repo.orl.eng.hitachivantara.com/artifactory/pnt-mvn is setup to be a proxy that serves Maven artifacts from an internal repo.  Browsing or curling is unlikely to work and as you've noticed will prompt for a login.  You will have much better luck trying to resolve with Maven.

If you are just trying to download artifacts up to the 9.4 release you can use commands like:

$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.8.0:get \
-DgroupId=org.pentaho.di \
-DartifactId=pdi-ce \
-Dversion=9.0.0.0-423 \
-Dpackaging=zip \
-Dtransitive=false \
-DremoteRepositories=https://repo.orl.eng.hitachivantara.com/artifactory/pnt-mvn

and then copy from your local Maven repo to your local directory with:

$ cp ~/.m2/repository/org/pentaho/di/pdi-ce/9.0.0.0-423/pdi-ce-9.0.0.0-423.zip .

Here are the groupIds and artifactIds of some of the common end artifacts:

groupId artifactId package (extension)
pentaho pad-ce zip
org.pentaho.di pdi-ce zip
pentaho pentaho-big-data-plugin zip
pentaho pme-ce zip
org.pentaho.reporting prd-ce zip
pentaho psw-ce zip
org.pentaho.reporting pre-classic-sdk zip
pentaho pentaho-server-ce zip
pentaho pentaho-server-manual-ce zip
pentaho-kettle kettle-sdk-plugin-assembly zip

If you are trying to build from an OSS project you will likely want to create a settings.xml to use while issuing mvn commands that tries to find all artifacts at the remote.

  <mirrors>
    <mirror>
      <id>pentaho-public</id>
      <url>https://repo.orl.eng.hitachivantara.com/artifactory/pnt-mvn/</url>
      <mirrorOf>*</mirrorOf>
    </mirror>
  </mirrors>

Then you can grab the project and kick off a build locally:

user@computer:~/github$ git clone -b 9.4.0.0-343 --single-branch --depth 1 \
                           https://github.com/pentaho/pentaho-kettle.git

user@computer:~/github$ cd pentaho-kettle

user@computer:~/github/pentaho-kettle$ git checkout -b 9.4-ga 9.4.0.0-343

user@computer:~/github/pentaho-kettle$ mvn -s ~/pentaho-settings.xml clean install

The repo contains artifact dependencies that make building all OSS projects up to and including 9.4 pretty easy.  Starting with 9.5, the Community Edition (now called Developer Edition) artifacts are only available to customers.  However, you CAN still build even the master branches of all OSS projects using this repo.  You will just need to go through a rather painful discovery process of finding the projects to build upstream in Github, build those, and try to cure your failed dependencies.  This repo does still come in handy for that as there are other dependencies that will be found there that are not part of the regular "suite build".