[
https://issues.apache.org/jira/browse/OODT-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187085#comment-13187085
]
Cameron Goodale commented on OODT-369:
--------------------------------------
Hey guys I saw that Adam's original issue was with building the OPeNDAPPS
component...but is this issue ultimately going to be resolved when all of OODT
builds using Maven 3? The title of the issue appears that way.
If this is the update maven build process to use maven 3, then I think
sub-issues per module would help break up the work.
> 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.4
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
