Hi, I checked out OODT trunk. For a while I've been working on some inherited code which to put it politely is an utter disgrace/disaster. I am just fed up fixing something, then something else breaks. I've therefore succumbed to my instinct and turned to OODT in an attempt to manage my data workflow.
I checked out trunk 2 minutes ago and when I try to build with the following, it fails law@CEE279Law3-Linux:~/Downloads/asf/oodt$ mvn -v Apache Maven 3.0.4 (r1232337; 2012-01-17 00:44:56-0800) Maven home: /home/law/Downloads/apache-maven-3.0.4 Java version: 1.7.0_11, vendor: Oracle Corporation Java home: /home/law/Downloads/jdk1.7.0_11/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.2.0-39-generic", arch: "amd64", family: "unix" Maven gives me this law@CEE279Law3-Linux:~/Downloads/asf/oodt$ mvn eclipse:eclipse [INFO] Scanning for projects... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.oodt:opendapps:0.6-SNAPSHOT (/home/law/Downloads/asf/oodt/opendapps/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.apache.oodt:oodt-core:pom:0.6-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 So I added the usual law@CEE279Law3-Linux:~/Downloads/asf/oodt$ svn diff Index: opendapps/pom.xml =================================================================== --- opendapps/pom.xml (revision 1458949) +++ opendapps/pom.xml (working copy) @@ -23,6 +23,7 @@ <groupId>org.apache.oodt</groupId> <artifactId>oodt-core</artifactId> <version>0.6-SNAPSHOT</version> + <relativePath>../core/pom.xml</relativePath> </parent> <build> <plugins> And the build works fine. Is this worth opening an issue and submitting a patch? I looked at the OODT Jenkins builds and the install target seems to work flawlessly... so I am confused as to why it is mucked up for me locally. Thanks Lewis -- *Lewis*
