[
https://issues.apache.org/jira/browse/OODT-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569929#comment-13569929
]
Chris A. Mattmann commented on OODT-369:
----------------------------------------
OODT now builds with Maven3:
{noformat}
[INFO] Catalog and Archive Crawling Framework ............ SUCCESS [23.319s]
[INFO] CAS Curation Interface ............................ SUCCESS [11.988s]
[INFO] CAS PGE Adaptor Framework ......................... SUCCESS [23.682s]
[INFO] CAS Installer Maven Mojo .......................... SUCCESS [4.950s]
[INFO] CAS Push-Pull-Framework ........................... SUCCESS [27.955s]
[INFO] Product Service ................................... SUCCESS [5.324s]
[INFO] Profile Service ................................... SUCCESS [7.890s]
[INFO] OODT Web Grid ..................................... SUCCESS [9.439s]
[INFO] XML-configured, DBMS-based Product and Profile Server SUCCESS [11.627s]
[INFO] Apache OODT Configurable OPeNDAP Profile Server ... SUCCESS [24.015s]
[INFO] Process Control System Core Package ............... SUCCESS [15.763s]
[INFO] OODT Wicket Web Components ........................ SUCCESS [9.174s]
[INFO] CAS File Manager Browser Web App .................. SUCCESS [11.052s]
[INFO] CAS Product Server ................................ SUCCESS [7.099s]
[INFO] CAS Workflow Manager Monitor Web App .............. SUCCESS [8.015s]
[INFO] Catalog and Archive File Management Browser ....... SUCCESS [11.706s]
[INFO] Catalog and Archive Workflow Management GUI Editor SUCCESS [25.189s]
[INFO] Process Control System Operator Interface Webapp .. SUCCESS [11.721s]
[INFO] OODT Process Control System JAX-RS service layer .. SUCCESS [10.265s]
[INFO] Apache OODT ....................................... SUCCESS [0.114s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:15.928s
[INFO] Finished at: Sun Feb 03 15:24:49 PST 2013
[INFO] Final Memory: 57M/128M
[INFO] ------------------------------------------------------------------------
[chipotle:~/tmp/oodt0.6] mattmann%
{noformat}
Tested with MVN3:
{noformat}
[chipotle:~/tmp/oodt0.6] mattmann% mvn3 --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800)
Maven home: /usr/local/maven3
Java version: 1.6.0_37, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
[chipotle:~/tmp/oodt0.6] mattmann%
{noformat}
> Building with Maven3
> --------------------
>
> Key: OODT-369
> URL: https://issues.apache.org/jira/browse/OODT-369
> Project: OODT
> Issue Type: Bug
> Components: build proces
> Environment: Mac
> Reporter: Adam Estrada
> Assignee: Chris A. Mattmann
> Labels: build-failure
> Fix For: 0.6
>
>
> I get the following build error.
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project org.apache.oodt:opendapps:0.4-SNAPSHOT
> (/Users/adamestrada/Documents/Apache/OODT/opendapps/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> org.apache.oodt:oodt-core:pom:0.4-SNAPSHOT and 'parent.relativePath' points
> at wrong local POM @ line 22, column 11 -> [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
> The fix for this is to add
> <relativePath>../core/pom.xml</relativePath>
> within the <parent> tags in opendapps/pom.xml
> Adam
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
