ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jun aoki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7005) ambari trunk commit build fails due to unresolvable eclipselink plugin when the first time mvn build
Date Wed, 27 Aug 2014 21:20:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112870#comment-14112870
] 

jun aoki commented on AMBARI-7005:
----------------------------------

It happens at the very first time you build ambari (mvn clean install)
Then you can also remove eclipselink from your local repo to reproduce.

{code}
rm -rf ~/.m2/repository/org/eclipse/persistence/eclipselink
mvn clean install
{code}

The question is ambari-server/pom.xml inherits from ambari-project/pom.xml which has a repo
setting to eclipselink. Why ?

> ambari trunk commit build fails due to unresolvable eclipselink plugin when the first
time mvn build
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7005
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7005
>             Project: Ambari
>          Issue Type: Bug
>          Components: build
>            Reporter: jun aoki
>
> https://builds.apache.org/job/Ambari-trunk-Commit/
> has been failing. The latest failure shows some dependency not found error.
> I will try to reproduce on my environment.
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main ....................................... SUCCESS [  5.919 s]
> [INFO] Apache Ambari Project POM ......................... SUCCESS [  0.887 s]
> [INFO] Ambari Web ........................................ SUCCESS [ 45.660 s]
> [INFO] Ambari Views ...................................... SUCCESS [ 10.575 s]
> [INFO] Ambari Admin View ................................. SUCCESS [02:16 min]
> [INFO] Ambari Server ..................................... FAILURE [01:11 min]
> [INFO] Ambari Agent ...................................... SKIPPED
> [INFO] Ambari Client ..................................... SKIPPED
> [INFO] Ambari Python Client .............................. SKIPPED
> [INFO] Ambari Groovy Client .............................. SKIPPED
> [INFO] Ambari Shell ...................................... SKIPPED
> [INFO] Ambari Python Shell ............................... SKIPPED
> [INFO] Ambari Groovy Shell ............................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 04:35 min
> [INFO] Finished at: 2014-08-25T18:09:29+00:00
> [INFO] Final Memory: 41M/344M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal au.com.alderaan:eclipselink-staticweave-maven-plugin:1.0.4:weave
(default) on project ambari-server: Execution default of goal au.com.alderaan:eclipselink-staticweave-maven-plugin:1.0.4:weave
failed: Plugin au.com.alderaan:eclipselink-staticweave-maven-plugin:1.0.4 or one of its dependencies
could not be resolved: The following artifacts could not be resolved: org.eclipse.persistence:eclipselink:jar:2.4.0,
commonj.sdo:commonj.sdo:jar:2.1.1.v201112051852: Could not find artifact org.eclipse.persistence:eclipselink:jar:2.4.0
in maven2-repository.dev.java.net (http://download.java.net/maven/2/) -> [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/PluginResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :ambari-server
> Build step 'Execute shell' marked build as failure
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message