Applying a patch at runtime in Maven - maven

I'm trying to install Giraph 1.1 but ran into an issue. According to this thread I should apply a patch to my installation. Unfortunately, my problem stems from that. I downloaded and copied the .patch file linked in there to the source folder and added the following to the pom.xml:
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-patch-plugin</artifactId>
<version>1.2</version>
<configuration>
<patches>
<patch>GIRAPH-1110.02.patch</patch>
</patches>
...
</plugins>
Unfortunately when I run Maven with:
sudo mvn -Phadoop_yarn -Dhadoop.version=2.8.1 clean package -DskipTests
it still fails with the same error as it did before:
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /usr/local/giraph/giraph-core/target/munged/main/org/apache/giraph/job/GiraphJob.java:[213,11] setPingInterval(org.apache.hadoop.conf.Configuration,int) is not public in org.apache.hadoop.ipc.Client; cannot be accessed from outside package
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Giraph Parent ............................... SUCCESS [ 6.298 s]
[INFO] Apache Giraph Core ................................. FAILURE [ 9.359 s]
[INFO] Apache Giraph Examples ............................. SKIPPED
[INFO] Apache Giraph Distribution ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16.062 s
[INFO] Finished at: 2018-02-06T22:53:00+02:00
[INFO] Final Memory: 51M/640M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile (default-compile) on project giraph-core: Compilation failure
[ERROR] /usr/local/giraph/giraph-core/target/munged/main/org/apache/giraph/job/GiraphJob.java:[213,11] setPingInterval(org.apache.hadoop.conf.Configuration,int) is not public in org.apache.hadoop.ipc.Client; cannot be accessed from outside package
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
which clearly shows that the issue has not been patched. When I check the file manually, I can confirm that there's no change. If I change the file manually before compilation, the changes get discarded (I'm guessing the file gets redownloaded). Also can't run the installation with offline flag since it depends on downloading some dependencies. I'm at my wits end here.
My Maven version is 3.3.9.

Related

Building Gluon Apps in Multi-Module Project

TL;DR: How does one build a Gluon app that's part of a larger multi-module project?
I have a multi-module Mave project (that is, my top-level POM has "<packaging>pom</packaging>"). The project contains a bunch of libraries and related sub-projects, one of which is a Gluon app that will be what my actual users install. (The rest of the project is all the cloud-hosted plumbing that the client app connects to.)
When I try to build the Gluon app, per the Gluon documentation, I am getting the following error:
mvn gluonfx:build
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] app [pom]
[INFO] app-common [jar]
[INFO] app-server [jar]
[INFO] app-client [jar]
[INFO] app-test [jar]
[INFO] app-utilities [jar]
[INFO] app-integration-lambda [jar]
[INFO] app-integration-jakarta [war]
[INFO] app-gluon [jar]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for app 0.9:
[INFO]
[INFO] app ............................................ SKIPPED
[INFO] app-common ..................................... SKIPPED
[INFO] app-server ..................................... SKIPPED
[INFO] app-client ..................................... SKIPPED
[INFO] app-test ....................................... SKIPPED
[INFO] app-utilities .................................. SKIPPED
[INFO] app-integration-lambda ......................... SKIPPED
[INFO] app-integration-jakarta ........................ SKIPPED
[INFO] app-gluon ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.298 s
[INFO] Finished at: 2022-02-22T21:03:18+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'gluonfx' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\Administrator\.m2\repository), central (https://repo.maven.apache.org/maven2)] -> [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/NoPluginFoundForPrefixException
If I run Maven so that it only builds the Gluon application instead, like this:
mvn gluonfx:build --projects "app-gluon" --also-make
I get basically the same error. If I cd to app-gluon first, I get a different error (and I didn't expect this to work anyhow):
cd app-gluon
mvn gluonfx:build
[INFO] Scanning for projects...
[INFO]
[INFO] --------------------< com.whatever:app-gluon >--------------------
[INFO] Building app-gluon 0.9
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for com.whatever:app-common:jar:0.9 is missing, no dependency information available
[WARNING] The POM for com.whatever:app-client:jar:0.9 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.380 s
[INFO] Finished at: 2022-02-22T21:09:12+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project app-gluon: Could not resolve dependencies for project com.whatever:app-gluon:jar:0.9: The following artifacts could not be
resolved: com.whatever:app-common:jar:0.9, com.whatever:app-client:jar:0.9: com.whatever:app-common:jar:0.9 was not found in https://nexus.gluonhq.com/nexus/
content/repositories/releases during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of Gluon has elapsed or updates are forced -> [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
So my question is: how does one build a Gluon app that's part of a larger multi-module project?
If you have a multi module project, and your app module depends on other modules, you need to publish those modules to a repository, so the app module finds them, like any other third party dependency.
Typically, for local development, you can simply use mvn install from the root folder to deploy your project locally. Of course, for distribution, you should consider publishing them to a reachable repository.
Make sure all your modules are deployed to your ~/.m2 repository.
Then you can run from the root:
mvn gluonfx:build -f app-gluon
or enter in the app-gluon folder:
cd app-gluon
mvn gluonfx:build
And remember that every time you make any change to the other modules, you will need to publish them again before building the native image.
Also, since you can run your app on the JVM, before building the native image (which takes a couple of minutes), you can simply run and test:
mvn gluonfx:run
and if that works fine, do the native image build.

JanusGraph build failed (TinkerPop 3.2.4)

I cloned JanusGraph repo (d6b3d42) and build it without any problem. I need to use it with ThinkerPop 3.2.4 so I changed its version in pom.xml file. Then I run mvn clean install -DskipTests=true.
[WARNING] The POM for com.github.jeremyh:jBCrypt:jar:jbcrypt-0.4 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JanusGraph: Distributed Graph Database ............. SUCCESS [ 0.563 s]
[INFO] JanusGraph-Core: Core Library for JanusGraph ....... FAILURE [ 0.275 s]
[INFO] JanusGraph-Test: Test Suite for JanusGraph ......... SKIPPED
[INFO] JanusGraph CodePipelines CI: Distributed release testing. SKIPPED
[INFO] JanusGraph-BerkeleyJE: Distributed Graph Database .. SKIPPED
[INFO] JanusGraph-Cassandra: Distributed Graph Database ... SKIPPED
[INFO] JanusGraph-CQL: Distributed Graph Database ......... SKIPPED
[INFO] JanusGraph-ElasticSearch: Distributed Indexing Support SKIPPED
[INFO] JanusGraph-HBase: Parent Module .................... SKIPPED
[INFO] JanusGraph-HBase: Version-independent Core ......... SKIPPED
[INFO] JanusGraph-HBase: 0.98 Compatibility Shim .......... SKIPPED
[INFO] JanusGraph-HBase: 1.x Compatibility Shim ........... SKIPPED
[INFO] JanusGraph-HBase: Universal binary ................. SKIPPED
[INFO] JanusGraph-Hadoop: Parent Module ................... SKIPPED
[INFO] JanusGraph-Hadoop: Version-independent Core ........ SKIPPED
[INFO] JanusGraph-Hadoop: 2.x Compatibility Shim .......... SKIPPED
[INFO] JanusGraph-Hadoop: Universal binary ................ SKIPPED
[INFO] JanusGraph-Lucene: Indexing Support ................ SKIPPED
[INFO] JanusGraph-All: Complete JanusGraph Distribution ... SKIPPED
[INFO] JanusGraph-Solr: Distributed Indexing Support ...... SKIPPED
[INFO] JanusGraph-Dist: Tar and Zip Archives .............. SKIPPED
[INFO] JanusGraph-Dist: Archive with Hadoop 2 ............. SKIPPED
[INFO] JanusGraph-Doc: AsciiDoc Manual for JanusGraph ..... SKIPPED
[INFO] JanusGraph-Examples: Examples for JanusGraph ....... SKIPPED
[INFO] Example-Common: Common Graph Code for Examples ..... SKIPPED
[INFO] Example-BerkeleyJE: BerkeleyJE Storage, Lucene Index SKIPPED
[INFO] Example-Cassandra: C* Thrift Storage, ES Index ..... SKIPPED
[INFO] Example-Cql: C* CQL Storage, ES Index .............. SKIPPED
[INFO] Example-HBase: HBase Storage, Solr Index ........... SKIPPED
[INFO] Example-RemoteGraph: Example with RemoteGraph ...... SKIPPED
[INFO] Example-TinkerGraph: Example with TinkerGraph ...... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.557 s
[INFO] Finished at: 2017-09-27T16:44:59+02:00
[INFO] Final Memory: 24M/303M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project janusgraph-core: Could not resolve dependencies for project org.janusgraph:janusgraph-core:jar:0.2.0-SNAPSHOT: Failure to find com.github.jeremyh:jBCrypt:jar:jbcrypt-0.4 in http://download.oracle.com/maven was cached in the local repository, resolution will not be reattempted until the update interval of oracleReleases has elapsed or updates are forced -> [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 <goals> -rf :janusgraph-core
How can I build JanusGraph with TinkerPop 3.2.4 version?
Update the root pom.xml to add the Jitpack repository:
<repository>
<!-- for com.github.jeremyh:jBCrypt:jar -->
<id>jitpack.io</id>
<name>JitPack Package Repository</name>
<url>https://jitpack.io</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
This repository was removed the pom.xml because newer versions of Apache TinkerPop do not have this dependency.
Reference from janusgraph-users Google group:
That dependency isn't found in Maven central, jbcrypt-0.4 is found in the jitpack.io repository. You'll need to add a remote repository for it. You could use the dependency:get command:
mvn dependency:get -DremoteRepositories="https://jitpack.io" -Dartifact="com.github.jeremyh:jBCrypt:jbcrypt-0.4"
When you run the command above, you will download the required jBCrypt dependency into your local Maven repository so that you can continue to build JanusGraph. If you're interested in building a distribution zip, similar to the ones you can find on the JanusGraph downloads page, use this command:
mvn clean install -DskipTests=true -Dgpg.skip=true -Pjanusgraph-release
Then you can find the distribution zip under janusgraph-dist/janusgraph-dist-hadoop-2/target/janusgraph-0.2.0-SNAPSHOT-hadoop2.zip.

Apache Tez build fails

I am trying to build Apache Tez (Both 0.6.1 and 0.7.0 version) for hadoop-2.6.0 in windows using below command
mvn clean package -Dhadoop.version=2.6.0 -DskipTests -Dmaven.javadoc.skip
But i am getting below exception
[INFO]
[INFO] --- exec-maven-plugin:1.3.2:exec (Bower install) # tez-ui ---bower FileSaver.js#24b303f49213b905ec9062b708f7cd43d56a5dde ENOGIT git is not installed or not in the PATH
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] tez ................................................ SUCCESS [ 0.924 s]
[INFO] tez-api ............................................ SUCCESS [ 11.585 s]
[INFO] tez-common ......................................... SUCCESS [ 1.421 s]
[INFO] tez-runtime-internals .............................. SUCCESS [ 2.029 s]
[INFO] tez-runtime-library ................................ SUCCESS [ 4.751 s]
[INFO] tez-mapreduce ...................................... SUCCESS [ 2.553 s]
[INFO] tez-examples ....................................... SUCCESS [ 0.862 s]
[INFO] tez-dag ............................................ SUCCESS [ 8.363 s]
[INFO] tez-tests .......................................... SUCCESS [ 2.044 s]
[INFO] tez-ui ............................................. FAILURE [ 3.105 s]
[INFO] tez-plugins ........................................ SKIPPED
[INFO] tez-yarn-timeline-history .......................... SKIPPED
[INFO] tez-yarn-timeline-history-with-acls ................ SKIPPED
[INFO] tez-mbeans-resource-calculator ..................... SKIPPED
[INFO] tez-tools .......................................... SKIPPED
[INFO] tez-dist ........................................... SKIPPED
[INFO] Tez ................................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38.169 s
[INFO] Finished at: 2015-07-13T15:07:23+05:30
[INFO] Final Memory: 76M/1049M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (Bower install) on project tez-ui: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [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 <goals> -rf :tez-ui
How to solve this?
Based on the error, it seems like you need git installed:
ENOGIT git is not installed or not in the PATH
Also, this might be helpful for other errors: https://cwiki.apache.org/confluence/display/TEZ/Build+errors+and+solutions
Once look at this... this may help you.
Reason: You are running as root or with superuser permissions.
Solutions:
Recommended: Run without superuser permission, or as a non-root user.
Alternate: If you want to continue as root, add --allow-root to arguments tag of exec-maven-plugin in tez-ui/pom.xml.
Thank you.
Like hadoop_user proposed, I would firstly check this website and try all the fixes but with one remark: in 3rd fix (clearing folder node_tmp) - if you cannot find that folder try clearing the following folder: $TEZ_PATH/tez-X.Y.Z/ tez-ui/src/main/webapp/node_modules/
I tried deleting that folder once I tried everything else and then it worked.
Install git, node & npn. This worked in my case.
Installing git, node and npm worked for me as well.Before building install all the three and try to run the mvn package -DskipTests.This works.

Error building hadoop 2.6 on windows - corrupt or invalid inutils.vcxproj

I'm trying to build Hadoop 2.6 on windows and installed the prerequisite as mentioned on their website. I;m getting the following fatal error while building it and the process stops. Any suggestions. Hadoop 2.5.2 built fine without any issues.
Thank you!
s\winutils.vcxproj" (default target) (4) ->
(Link target) ->
LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or
corrupt [C:\Hadoop\hadoop-2.6.0-src\hadoop-common-project\hadoop-common\src\mai
n\winutils\winutils.vcxproj]
57 Warning(s)
1 Error(s)
Time Elapsed 00:00:05.67
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hadoop Main ................................ SUCCESS [0.671s]
[INFO] Apache Hadoop Project POM ......................... SUCCESS [0.577s]
[INFO] Apache Hadoop Annotations ......................... SUCCESS [1.734s]
[INFO] Apache Hadoop Assemblies .......................... SUCCESS [0.124s]
[INFO] Apache Hadoop Project Dist POM .................... SUCCESS [1.498s]
[INFO] Apache Hadoop Maven Plugins ....................... SUCCESS [1.734s]
[INFO] Apache Hadoop MiniKDC ............................. SUCCESS [1.390s]
[INFO] Apache Hadoop Auth ................................ SUCCESS [2.434s]
[INFO] Apache Hadoop Auth Examples ....................... SUCCESS [1.920s]
[INFO] Apache Hadoop Common .............................. FAILURE [13.970s]
................................
................................
................................
................................
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27.253s
[INFO] Finished at: Tue Dec 23 16:19:50 EST 2014
[INFO] Final Memory: 82M/1045M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:exec (com
pile-ms-winutils) on project hadoop-common: Command execution failed. Process ex
ited with an error: 1(Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :hadoop-common
You need to remove .NET Framework 4.5 and install .NET Framework 4. After that, try to rebuild with the following command :
mvn package -Pdist,native-win -DskipTests -Dtar
Hope it help.
I am not sure if this is still relevant to you but I found the answer. You need .NET Framework 4. I had to remove .NET Framework 4.5 and install 4. Once I did that, the error went away.
Someone in another question had answered it but it was not specific to hadoop.
Failure during conversion to COFF: file invalid or corrupt

Sakai 10 clog not compiling :(

I'm having a little trouble on compiling the clog tool for sakai 10...
https://github.com/adrianfish/clog/issues/5
I suspect adrian is busy on the 11 build at the moment, but I'm wondering if it's actually something that can be fixed by the user, or maybe others have hit this and are doing something simple that I don't know about..?
Basically the current stable version of clog (0.9.3 -https://confluence.sakaiproject.org/display/CLOG/Home) doesn't compile for the sakai 10 code base, there is what looks to be a related issue (CLOG-113) here...
https://github.com/adrianfish/clog/pull/3
but I'm not sure if the sakai-10 repository for maven exists as the error you get for compiling the sakai-10 branch of clog (https://github.com/adrianfish/clog/tree/sakai-10) is as follows:
bash-3.2$ mvn clean install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.sakaiproject.clog:clog:0.9.5-SNAPSHOT (/usr/local/sakai/sakai-src-10.0/clog-0.9.5-sakai-10branch/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.sakaiproject:master:pom:10.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM # line 12, column 13 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Has anyone managed to get clog to compile on sakai 10? This is a bit of a blocker for our sakai 10 deployment :(
Edit: (Also see "further edit" for solution)
After trying the suggestion (https://stackoverflow.com/a/24769111/3737856) below I get this error
*---snip---*
Downloaded: http://repo1.maven.org/maven2/org/apache/commons/commons-parent/17/commons-parent-17.pom (31 KB at 507.6 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom
Downloaded: http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom (15 KB at 320.3 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/projectlombok/lombok/0.11.6/lombok-0.11.6.pom
Downloaded: http://repo1.maven.org/maven2/org/projectlombok/lombok/0.11.6/lombok-0.11.6.pom (2 KB at 34.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] CLOG .............................................. SUCCESS [ 7.693 s]
[INFO] CLOG API .......................................... FAILURE [ 3.520 s]
[INFO] CLOG IMPL ......................................... SKIPPED
[INFO] CLOG PACK ......................................... SKIPPED
[INFO] CLOG HELP ......................................... SKIPPED
[INFO] CLOG TOOL ......................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.166 s
[INFO] Finished at: 2014-07-16T10:11:38+00:00
[INFO] Final Memory: 10M/59M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project clog-api: Could not resolve dependencies for project org.sakaiproject.clog:clog-api:jar:0.9.5-SNAPSHOT: Failed to collect depend encies at org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failed to read artifact descriptor for org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Could not find arti fact org.sakaiproject:kernel:pom:10.0 in central (http://repo1.maven.org/maven2) -> [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 <goals> -rf :clog-api
I have built the current sakai 10 release build from source (building the master directory then the root), placed the clog source in the root and built it there. This usually works.
In addition I also tried changing in the clog pom:
<name>CLOG</name>
<groupId>org.sakaiproject.clog</groupId>
<artifactId>clog</artifactId>
<version>0.9.5-SNAPSHOT</version>
<packaging>pom</packaging>
to:
<name>CLOG</name>
<groupId>org.sakaiproject.clog</groupId>
<artifactId>clog</artifactId>
<version>0.9.5</version>
<packaging>pom</packaging>
building with this and the other suggested change resulted in this error:
-bash-3.2$ mvn clean install
[INFO] Scanning for projects...
Downloading: http://repo.maven.apache.org/maven2/org/sakaiproject/master/10.0/master-10.0.pom
Downloaded: http://repo.maven.apache.org/maven2/org/sakaiproject/master/10.0/master-10.0.pom (59 KB at 172.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] CLOG API
[INFO] CLOG IMPL
[INFO] CLOG PACK
[INFO] CLOG HELP
[INFO] CLOG TOOL
[INFO] CLOG
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building CLOG API 0.9.5-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] CLOG API .......................................... FAILURE [ 1.374 s]
[INFO] CLOG IMPL ......................................... SKIPPED
[INFO] CLOG PACK ......................................... SKIPPED
[INFO] CLOG HELP ......................................... SKIPPED
[INFO] CLOG TOOL ......................................... SKIPPED
[INFO] CLOG .............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.584 s
[INFO] Finished at: 2014-07-16T10:19:02+00:00
[INFO] Final Memory: 8M/59M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project clog-api: Could not resolve dependencies for project org.sakaiproject.clog:clog-api:jar:0.9.5-SNAPSHOT: Failed to collect dependencies at org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failed to read artifact descriptor for org.sakaiproject.kernel:sakai-kernel-api:jar:10.0: Failure to find org.sakaiproject:kernel:pom:10.0 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [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
Additionally... I notice the donwloads are referencing maven2 repositories, I don't suppose that makes any difference, I'm definitely using maven3...
-bash-3.2$ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T17:37:52+00:00)
Maven home: /usr/local/maven2/current
Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
Java home: /usr/local/java/jdk1.6.0_27/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "2.6.18-348.18.1.el5", arch: "amd64", family: "unix"
Further edit:
D'OH!!!
It works now, I changed the pom only in the way suggested (10-SNAPSHOT -> 10) and --> "compiled as root" <-- what I was doing before was compiling as a non-super user, it looks like the initial build was compiled with root and/or I have permissions wrong somewhere, but clog is now compiling.
I think I'm going to submit a pull request to adrian for the pom change though...
It looks like Clog is setup correctly. You need to have the parent that this is depending on checked out (master) and built locally if you're doing a full source compile. Then you can build clog.
https://confluence.sakaiproject.org/pages/viewpage.action?pageId=93028745
Optionally you can change the version to 10.0 (which has released dependencies) and clog will compile. For instance:
--- a/pom.xml
+++ b/pom.xml
## -12,7 +12,7 ##
<parent>
<groupId>org.sakaiproject</groupId>
<artifactId>master</artifactId>
- <version>10.0-SNAPSHOT</version>
+ <version>10.0</version>
<relativePath>../master/pom.xml</relativePath>
</parent>
The externals for the tools which are on nightly and are known to work on 10 is here.
https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-experimental/.externals

Resources