search

OSBI / saiku

Saiku Analytics - The Worlds Greatest Open Source OLAP Browser
http://community.meteorite.bi
Apache License 2.0
1.31k stars 664 forks source link

Cannot build code cloned from master. #615

Closed vesselink closed 6 years ago

vesselink commented 6 years ago

After cloning the repository a mvn clean install -DskipTests produces errors with resolving maven dependencies. The first one is easy to fix - the Pentaho maven repository URLs are wrong (f.e. http://nexus.pentaho.org/content/repositories/proxied-3rd-party-releases/ should be really https://nexus.pentaho.org/content/repositories/proxy-public-3rd-party-release/, pentaho-release should be https://nexus.pentaho.org/content/repositories/proxy-public-release/, etc.). After fixing these however it seems the Analytical Labs Repo (http://repo.meteorite.bi/repository/alabs-release-local/) cannot be resolved.

lizihanglove commented 6 years ago

I got this problem either, did you fix this at present?I appreciate it if fixed and do let me know.Thanks a lot.

vesselink commented 6 years ago

Situation is still the same - I've abandoned Saiku for now and I'm trying to find alternatives.

buggtb commented 6 years ago

Well, it works for me and I'm busy with the day job. I'll take a look when I get time, but you could always tinker with the maven pom files and figure it out

buggtb commented 6 years ago

[INFO] Building jar: /root/saiku/saiku-bi-platform-plugin-p7.1/target/saiku-bi-platform-plugin-p7.1-3.16-javadoc.jar [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Saiku Module Project ............................... SUCCESS [ 3.412 s] [INFO] saiku - core libraries ............................. SUCCESS [ 1.265 s] [INFO] saiku olap util .................................... SUCCESS [ 20.198 s] [INFO] saiku - services ................................... SUCCESS [12:44 min] [INFO] saiku - web ........................................ SUCCESS [03:39 min] [INFO] saiku-ui ........................................... SUCCESS [ 30.180 s] [INFO] saiku - webapp ..................................... SUCCESS [07:39 min] [INFO] saiku-server ....................................... SUCCESS [ 16.994 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 40.126 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 47.192 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 22.658 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 12.172 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 27:18 min [INFO] Finished at: 2018-01-19T11:21:02+00:00 [INFO] Final Memory: 204M/1699M [INFO] ------------------------------------------------------------------------ root@adapted-toucan:~/saiku# git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean root@adapted-toucan:~/saiku#

clean clone clean master branch

scottcame commented 6 years ago

I am running into the same problem. @buggtb your build might be working because Maven is finding the necessary jars in your local Maven repo and doesn't need to hit the remote repo.

It looks like there are no repositories defined at repo.meteorite.bi, which is apparently where a lot of the pentaho/mondrian/etc jars needed in the build are pulled from.

buggtb commented 6 years ago

Hi Scott

That had crossed my mind prior to that so for that test I deliberately launched a clean LXD image with nothing on it and install java and maven from the ubuntu repos, so I can't have got the dependencies from anywhere else.

On 19/01/18 16:25, Scott Came wrote:

I am running into the same problem. @buggtb https://github.com/buggtb your build might be working because Maven is finding the necessary jars in your local Maven repo and doesn't need to hit the remote repo.

It looks like there are no repositories defined at repo.meteorite.bi, which is apparently where a lot of the pentaho/mondrian/etc jars needed in the build are pulled from.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSBI/saiku/issues/615#issuecomment-359016127, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGUeFSLpiPTsB8ldBXzngXz46MMAPNfks5tMMHpgaJpZM4RSuZb.

--

Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891.

All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.

scottcame commented 6 years ago

Very odd. I did exactly the same thing in a docker container with Java 8 and Maven 3.5. Then cloned master and did mvn install -DskipTests. No joy. Is it possible that there is a nexus repo defined somewhere in these poms that is accessible to you but not the Internet?

I am also getting certificate validation warnings, which don't prevent the build from completing, but are perhaps a hint to what's wrong?

Also, the olap-util module refers to a Mondrian jar that does not exist in the Pentaho repos (It's version 4.3.0.1.1-SPARK I believe). I just changed that to 4.3.0.1-130 (which is the latest 4.3.0.x in the pentaho public repo) and I got past that, but it's failing on finding the licenseserver-core jar.

buggtb commented 6 years ago

nope, i've not got a direct connect to the repo or anything, I have got another fresh build running now just to triple check i'm not making it up.

I am curious to know why its only just started appearing in the last few months because we've not changed anything in the repo or pom files.

Just out of curiosity can you just hand over your java and maven versions?

scottcame commented 6 years ago

Sure: Java 1.8.0_66 Maven 3.5.2

buggtb commented 6 years ago

Thanks scott I've kicked off a build with that maven version as well, I was testing with 3.3.9 which is in the ubuntu apt repo, we'll see if it makes a difference.

scottcame commented 6 years ago

I am doing the same. By the way, as another data point, I successfully built master about two weeks ago. Then tried again yesterday and had the issues. I looked at the commits to master since and didn't see anything in there that I'd expect to cause the issues, so that's what led me to suspect an issue in your repos.

Results:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Saiku Module Project ............................... SUCCESS [04:07 min]
[INFO] saiku - core libraries ............................. SUCCESS [  2.974 s]
[INFO] saiku olap util .................................... FAILURE [ 46.183 s]
[INFO] saiku - services ................................... SKIPPED
[INFO] saiku - web ........................................ SKIPPED
[INFO] saiku-ui ........................................... SKIPPED
[INFO] saiku - webapp ..................................... SKIPPED
[INFO] saiku-server ....................................... SKIPPED
[INFO] saiku biserver plugin .............................. SKIPPED
[INFO] saiku biserver plugin .............................. SKIPPED
[INFO] saiku biserver plugin .............................. SKIPPED
[INFO] saiku biserver plugin .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:50 min
[INFO] Finished at: 2018-01-19T17:05:16+00:00
[INFO] Final Memory: 30M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project saiku-olap-util: Could not resolve dependencies for project org.saikuanalytics:saiku-olap-util:jar:3.16: Failed to collect dependencies at pentaho:mondrian:jar:4.3.0.1.1-SPARK: Failed to read artifact descriptor for pentaho:mondrian:jar:4.3.0.1.1-SPARK: Could not transfer artifact pentaho:mondrian:pom:4.3.0.1.1-SPARK from/to Analytical Labs Repo (http://repo.meteorite.bi/repository/alabs-release-local/): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1]
bash-4.3# mvn --version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
Maven home: /opt/apache-maven-3.3.9
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /opt/jdk/jdk1.8.0_66/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "4.9.49-moby", arch: "amd64", family: "unix"
bash-4.3#
buggtb commented 6 years ago

[INFO] Building jar: /root/saiku/saiku-bi-platform-plugin-p7.1/target/saiku-bi-platform-plugin-p7.1-3.16-javadoc.jar [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Saiku Module Project ............................... SUCCESS [02:19 min] [INFO] saiku - core libraries ............................. SUCCESS [ 8.103 s] [INFO] saiku olap util .................................... SUCCESS [ 48.419 s] [INFO] saiku - services ................................... SUCCESS [12:29 min] [INFO] saiku - web ........................................ SUCCESS [03:36 min] [INFO] saiku-ui ........................................... SUCCESS [ 23.440 s] [INFO] saiku - webapp ..................................... SUCCESS [07:48 min] [INFO] saiku-server ....................................... SUCCESS [ 18.831 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 41.832 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 48.569 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 22.758 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 14.665 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 30:16 min [INFO] Finished at: 2018-01-19T17:05:29+00:00 [INFO] Final Memory: 202M/1773M [INFO] ------------------------------------------------------------------------ root@relaxed-gator:~/saiku# mvn -version Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_151, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en, platform encoding: UTF-8 OS name: "linux", version: "4.4.0-109-generic", arch: "amd64", family: "unix"

Thats the first of the 2 builds complete in a completely clean LXC Xenial container

scottcame commented 6 years ago

I can try with openjdk I suppose...

buggtb commented 6 years ago

I don't see the JDK version being a difference maker cause you guys are seeing weird issues with the maven build chain, but on the maven 3.5.2 build i'm halfway through saiku web and its still happy, so I'm not sure I'll find a match here.

scottcame commented 6 years ago

I still suspect some kind of network thing, where for some weird reason you are able to get to a repo and we cannot.

buggtb commented 6 years ago

okay well to that end... does this render an xml blob? https://repo.meteorite.bi/repository/alabs-snapshot-local/org/olap4j/olap4j-xmla/TRUNK-SNAPSHOT/maven-metadata.xml

scottcame commented 6 years ago

Yes it does

If I were to browse to the location where pentaho:mondrian:jar:4.3.0.1.1-SPARK is located, where would that be? What URL?

buggtb commented 6 years ago

yeah so you have access to the repos

Generating /root/saiku/saiku-bi-platform-plugin-p7.1/target/apidocs/index.html... Generating /root/saiku/saiku-bi-platform-plugin-p7.1/target/apidocs/help-doc.html... [INFO] Building jar: /root/saiku/saiku-bi-platform-plugin-p7.1/target/saiku-bi-platform-plugin-p7.1-3.16-javadoc.jar [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Saiku Module Project ............................... SUCCESS [02:20 min] [INFO] saiku - core libraries ............................. SUCCESS [ 7.921 s] [INFO] saiku olap util .................................... SUCCESS [ 51.014 s] [INFO] saiku - services ................................... SUCCESS [12:08 min] [INFO] saiku - web ........................................ SUCCESS [03:42 min] [INFO] saiku-ui ........................................... SUCCESS [ 38.400 s] [INFO] saiku - webapp ..................................... SUCCESS [10:06 min] [INFO] saiku-server ....................................... SUCCESS [ 14.774 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 55.158 s] [INFO] saiku biserver plugin .............................. SUCCESS [01:09 min] [INFO] saiku biserver plugin .............................. SUCCESS [ 25.312 s] [INFO] saiku biserver plugin .............................. SUCCESS [ 11.820 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 33:06 min [INFO] Finished at: 2018-01-19T17:28:42Z [INFO] Final Memory: 203M/1840M [INFO] ------------------------------------------------------------------------ root@logical-earwig:~/saiku#

Thats the version with your maven release... so I'm still stumped

scottcame commented 6 years ago

If you can point me to the url (that I can hit with my browser) where the pentaho:mondrian:jar:4.3.0.1.1-SPARK jar lives, that would help confirm that repo access is working.

buggtb commented 6 years ago

https://repo.meteorite.bi/repository/alabs-release-local/pentaho/mondrian/4.3.0.1.1-SPARK/mondrian-4.3.0.1.1-SPARK.pom and https://repo.meteorite.bi/repository/alabs-release-local/pentaho/mondrian/4.3.0.1.1-SPARK/mondrian-4.3.0.1.1-SPARK.jar for that

scottcame commented 6 years ago

Absolutely baffling...

buggtb commented 6 years ago

you're telling me...

On 19 Jan 2018 5:50 pm, "Scott Came" notifications@github.com wrote:

Absolutely baffling...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSBI/saiku/issues/615#issuecomment-359040300, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGUeF5uNrsdhEEdQOH8Bv3ShxlhcT8fks5tMNXMgaJpZM4RSuZb .

--

Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891.

All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.

scottcame commented 6 years ago

I need to turn to some other things today, but I may come back to this over the weekend and see if I can figure it out.

vesselink commented 6 years ago

Guys, after I did some digging, I found one of the problems with the build. It DOES have everything to do with the Java version. The https://repo.meteorite.bi/repository/alabs-snapshot-local repo uses the Let's Encrypt certificate which IS NOT supported in Java prior to Java 1.8.0_101. I was using Java 1.8.0_66 - exactly the same as Scott was using - serves me right for using an outdated version :) After upgrading it to the latest (1.8.0_161) ALMOST everything builds ok :) Here is the log I get: [INFO] ------------------------------------------------------------------------ [INFO] Building saiku biserver plugin 3.16 [INFO] ------------------------------------------------------------------------ [WARNING] The POM for com.sun.xml.stream.buffer:streambuffer:jar:0.4 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for org.apache.poi:poi-ooxml-schemas:jar:3.8 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/repository/alabs-snapshot-local/pentaho/pentaho-platform-scheduler/7.1.0.0-12/pentaho-platform-scheduler-7.1.0.0-12.jar Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/repository/alabs-snapshot-local/pentaho/pentaho-connections/7.1.0.0-12/pentaho-connections-7.1.0.0-12.jar Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/repository/alabs-snapshot-local/org/json/json/5.0.0/json-5.0.0.jar [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Saiku Module Project ............................... SUCCESS [ 4.417 s] [INFO] saiku - core libraries ............................. SUCCESS [ 1.821 s] [INFO] saiku olap util .................................... SUCCESS [ 7.649 s] [INFO] saiku - services ................................... SUCCESS [ 48.528 s] [INFO] saiku - web ........................................ SUCCESS [ 32.459 s] [INFO] saiku-ui ........................................... SUCCESS [ 30.317 s] [INFO] saiku - webapp ..................................... SUCCESS [01:29 min] [INFO] saiku-server ....................................... SUCCESS [01:37 min] [INFO] saiku biserver plugin .............................. FAILURE [ 7.037 s] [INFO] saiku biserver plugin .............................. SKIPPED [INFO] saiku biserver plugin .............................. SKIPPED [INFO] saiku biserver plugin .............................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 05:19 min [INFO] Finished at: 2018-01-19T20:18:16+02:00 [INFO] Final Memory: 90M/1675M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project saiku-bi-platform-plugin-p5: Could not resolve dependencies for project org.saikuanalytics:saiku-bi-platform-plugin-p5:jar:3.16: The following artifacts could not be resolved: pentaho:pentaho-platform-scheduler:jar:7.1.0.0-12, pentaho:pentaho-connections:jar:7.1.0.0-12, org.json:json:jar:5.0.0: Could not transfer artifact pentaho:pentaho-platform-scheduler:jar:7.1.0.0-12 from/to Analytical Labs snapshots (http://repo.meteorite.bi/repository/alabs-snapshot-local/): Failed to transfer file: http://repo.meteorite.bi/repository/alabs-snapshot-local/pentaho/pentaho-platform-scheduler/7.1.0.0-12/pentaho-platform-scheduler-7.1.0.0-12.jar. Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 7.1.0.0-12. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :saiku-bi-platform-plugin-p5

buggtb commented 6 years ago

oooh can't believe it! I also can't believe you don't get a sane SSL error.... thanks for the update

On 19 Jan 2018 18:20, "vesselink" notifications@github.com wrote:

Guys, after I did some digging, I found one of the problems with the build. It DOES have everything to do with the Java version. The https://repo.meteorite.bi/repository/alabs-snapshot-local repo uses the Let's Encrypt certificate which IS NOT supported in Java prior to Java 1.8.0_101. I was using Java 1.8.0_66 - exactly the same as Scott was using

  • serves me right for using an outdated version :) After upgrading it to the latest (1.8.0_161) ALMOST everything builds ok :) Here is the log I get: [INFO] ------------------------------------------------------------

    [INFO] Building saiku biserver plugin 3.16 [INFO] ------------------------------------------------------------

    [WARNING] The POM for com.sun.xml.stream.buffer:streambuffer:jar:0.4 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for org.apache.poi:poi-ooxml-schemas:jar:3.8 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/ repository/alabs-snapshot-local/pentaho/pentaho- platform-scheduler/7.1.0.0-12/pentaho-platform-scheduler-7.1.0.0-12.jar Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/ repository/alabs-snapshot-local/pentaho/pentaho-connections/7.1.0.0-12/ pentaho-connections-7.1.0.0-12.jar Downloading from Analytical Labs snapshots: http://repo.meteorite.bi/ repository/alabs-snapshot-local/org/json/json/5.0.0/json-5.0.0.jar [INFO] ------------------------------------------------------------

    [INFO] Reactor Summary: [INFO] [INFO] Saiku Module Project ............................... SUCCESS [ 4.417 s] [INFO] saiku - core libraries ............................. SUCCESS [ 1.821 s] [INFO] saiku olap util .................................... SUCCESS [ 7.649 s] [INFO] saiku - services ................................... SUCCESS [ 48.528 s] [INFO] saiku - web ........................................ SUCCESS [ 32.459 s] [INFO] saiku-ui ........................................... SUCCESS [ 30.317 s] [INFO] saiku - webapp ..................................... SUCCESS [01:29 min] [INFO] saiku-server ....................................... SUCCESS [01:37 min] [INFO] saiku biserver plugin .............................. FAILURE [ 7.037 s] [INFO] saiku biserver plugin .............................. SKIPPED [INFO] saiku biserver plugin .............................. SKIPPED [INFO] saiku biserver plugin .............................. SKIPPED [INFO] ------------------------------------------------------------

    [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------

    [INFO] Total time: 05:19 min [INFO] Finished at: 2018-01-19T20:18:16+02:00 [INFO] Final Memory: 90M/1675M [INFO] ------------------------------------------------------------

    [ERROR] Failed to execute goal on project saiku-bi-platform-plugin-p5: Could not resolve dependencies for project org.saikuanalytics:saiku-bi-platform-plugin-p5:jar:3.16: The following artifacts could not be resolved: pentaho:pentaho-platform-scheduler:jar:7.1.0.0-12, pentaho:pentaho-connections:jar:7.1.0.0-12, org.json:json:jar:5.0.0: Could not transfer artifact pentaho:pentaho-platform-scheduler:jar:7.1.0.0-12 from/to Analytical Labs snapshots (http://repo.meteorite.bi/ repository/alabs-snapshot-local/): Failed to transfer file: http://repo.meteorite.bi/repository/alabs-snapshot-local/pentaho/pentaho- platform-scheduler/7.1.0.0-12/pentaho-platform-scheduler-7.1.0.0-12.jar. Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 7.1.0.0-12. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :saiku-bi-platform-plugin-p5

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSBI/saiku/issues/615#issuecomment-359048114, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGUeNXYYYkhudWNoLWqhkEjcysoXOI2ks5tMNzxgaJpZM4RSuZb .

--

Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891.

All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.

scottcame commented 6 years ago

Good find @vesselink . I haven't had a chance to test it out yet, but that makes sense. When I successfully built master 2 weeks ago, it was on a system that was at _151 or _161...

vesselink commented 6 years ago

To be completely honest, there WAS an SSL error - that's how I caught it :) But the problem is the error was hidden under a ton of other messages AND the final error had no mention of the SSL problem. Also, the pom files had a http:// repo url which was redirected automatically to https:// so I didn't think of it initially. Any idea what the other error I see now in the build might be ?

buggtb commented 6 years ago

Are you fully sync'ed? There was some repo ordering stuff I saw the other week and I also forcilbly set the snapshot policies on the repos. But as you can see I've built master a bunch of of times today.

vesselink commented 6 years ago

I did a new clone from master today before I started testing - just to be on the safe side. Anyway, thanks for the help, I'll continue digging after I finish the stuff the client pays for ;)

vesselink commented 6 years ago

Finally was able to make it build but ONLY after fixing the root pom.xml to contain the correct Pentaho repository URLs. Maybe someone should fix this in master ? Here are the changed URLs: pentaho-third-party should be http://nexus.pentaho.org/content/repositories/proxy-public-3rd-party-release/ pentaho-public-release should be http://nexus.pentaho.org/content/repositories/proxy-public-release/ pentaho-snapshot should be http://nexus.pentaho.org/content/repositories/proxy-public-snapshot/ pentaho-releases should be http://nexus.pentaho.org/content/groups/omni/

buggtb commented 6 years ago

Feel free to submit a PR

scottcame commented 6 years ago

I was able to get a successful build in a clean docker container (i.e., no pre-existing .m2 repo) without doctoring the root pom...

poojasaxena commented 6 years ago

Hello, I am receiving the build error as well. I am using the following versions (also settings.xml in /.m2): §§§§§§§§§§§§§§§§§§§§ Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00) Maven home: /usr/local/Cellar/maven/3.5.2/libexec Java version: 1.8.0_152, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre Default locale: en_DE, platform encoding: UTF-8 OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"

Surprisingly the Build worked perfectly good earlier with my DELL laptop using the same versions. If someone see some obvious mistake, please let me know.

Many Thanks,

screen shot 2018-02-08 at 11 54 20
vesselink commented 6 years ago

First of all a little late but I can confirm to confirm I am also able to build if there is no pre-existing .m2 repo as @scottcame suggests. As for the error @poojasaxena sees, this should be either a network configuration problem on the machine or a temporary problem with https://nexus.pentaho.org. I confirm I can download the file mentioned in the error at the moment. To troubleshoot, just try the download in a browser or using wget.

poojasaxena commented 6 years ago

Well, the most funny observation I just made. I tried compiling the package from scratch using the same home network on both laptop (DELL and MAC) at the same time. The DELL managed to Built it successfully, however MAC failed. Would appreciate any suggestion to locate the source of error on MAC? The DELL settings: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00) Maven home: /opt/apache-maven-3.5.2 Java version: 1.8.0_151, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.13.0-32-generic", arch: "amd64", family: "unix"

The MAC settings Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00) Maven home: /usr/local/Cellar/maven/3.5.2/libexec Java version: 1.8.0_152, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre Default locale: en_DE, platform encoding: UTF-8 OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: “mac"

The error on the MAC is: [INFO] PDI Client Community Edition ....................... FAILURE [03:37 min] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 56:03 min [INFO] Finished at: 2018-02-08T17:25:44+01:00 [INFO] Final Memory: 279M/1764M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project pdi-ce: Could not resolve dependencies for project org.pentaho.di:pdi-ce:pom:8.1.0.0-SNAPSHOT: Could not transfer artifact org.pentaho.adaptive:pdi-websocket-daemon-assembly:zip:8.1.0.0-20180208.161827-149 from/to pentaho-public (http://nexus.pentaho.org/content/groups/omni/): Failed to transfer file: http://nexus.pentaho.org/content/groups/omni/org/pentaho/adaptive/pdi-websocket-daemon-assembly/8.1.0.0-SNAPSHOT/pdi-websocket-daemon-assembly-8.1.0.0-20180208.161827-149.zip. Return code is: 502 , ReasonPhrase:Proxy Error. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :pdi-ce

vesselink commented 6 years ago

Well, this means the problem is almost certainly with your Mac network config. Best thing to try is to open https://nexus.pentaho.org/content/groups/omni/org/pentaho/adaptive/pdi-websocket-daemon-assembly/8.1.0.0-SNAPSHOT/pdi-websocket-daemon-assembly-8.1.0.0-20180208.161827-149.zip in Safari and see the response there. I suspect you'll get an error - if you do, try to resolve it. Unfortunately I'm not a Mac expert and can't help you with it.

poojasaxena commented 6 years ago

thanks @vesselink for your suggestion , I installed maven manually on MAC and now try again to build. Lets see..

poojasaxena commented 6 years ago

Yes, it worked and am able to Build it on MAC after Manual installation of maven. thanks again.

Though the Build (mvn clean install) was succesful, but the test (mvn test) failed on my DELL laptop with following error: [INFO] Pentaho Google Cloud Storage VFS ................... SUCCESS [ 0.014 s] [INFO] Pentaho Google Cloud Storage VFS Plugin Core ....... SUCCESS [ 0.285 s] [INFO] Pentaho Google Cloud Storage VFS Assemblies ........ SUCCESS [ 0.006 s] [INFO] Pentaho Google Cloud Storage VFS Plugin Distribution SUCCESS [ 0.017 s] [INFO] PDI Assemblies ..................................... SUCCESS [ 0.010 s] [INFO] PDI Client Static Assets ........................... SUCCESS [ 0.016 s] [INFO] PDI Client Samples ................................. FAILURE [ 0.454 s] [INFO] PDI Client Libraries ............................... SKIPPED [INFO] PDI Client Plugins ................................. SKIPPED [INFO] PDI Client Community Edition ....................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 32:19 min [INFO] Finished at: 2018-02-09T10:30:27+01:00 [INFO] Final Memory: 114M/580M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:sql-maven-plugin:1.5:execute (default) on project pdi-samples: Sequence "SYSTEM_SEQUENCE_B4ADD799_499E_49DC_997F_E4924C2E21EC" already exists; SQL statement: [ERROR] CREATE SEQUENCE PUBLIC.SYSTEM_SEQUENCE_B4ADD799_499E_49DC_997F_E4924C2E21EC START WITH 6 BELONGS_TO_TABLE [90035-131] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :pdi-samples

anyone has the similar experience?

ksice commented 5 years ago

i need mondrian-4.3.0.1.1-SPARK.jar，who can upload the jar，thanks

InnovartJ2 commented 4 years ago

I'm getting a proxy error...

[INFO] Building Saiku Module Project 3.90 [1/9] [INFO] --------------------------------[ pom ]--------------------------------- Downloading from Analytical Labs Plugin Repo: http://repo.meteorite.bi/repository/alabs-release-local/org/codehaus/mojo/license-maven-plugin/maven-metadata.xml [WARNING] Could not transfer metadata org.codehaus.mojo:license-maven-plugin/maven-metadata.xml from/to Analytical Labs Plugin Repo (http://repo.meteorite.bi/repository/alabs-release-local/): Transfer failed for http://repo.meteorite.bi/repository/alabs-release-local/org/codehaus/mojo/license-maven-plugin/maven-metadata.xml 502 Proxy Error [INFO]

Also, when I try this URL... https://repo.meteorite.bi/auth/login/

I got that proxy error

The proxy server received an invalid response from an upstream server. The proxy server could not handle the request

Reason: Error reading from remote server

Apache/2.4.29 (Ubuntu) Server at repo.meteorite.bi Port 443

buggtb commented 4 years ago

Yeah, so in a nutshell folks, the repo went down, its old and has a lot of junk in it, I haven't yet got around on restoring it. @brunogamacatao is working on migrating the old libs to the gitlab repo, but its not done yet and wont be done for a little while.

The repo was always something hosted by us and I got fed up of maintaining it, as ever the community has never offered with any of this type of stuff, so its off for now. It will reappear at some point in the next few weeks I expect.