You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oodt.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2013/03/20 18:21:48 UTC

Addition of relativePath in opendapps/pom.xml

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*

Re: Addition of relativePath in opendapps/pom.xml

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Lewis,

Happy for a JIRA issue + patch or just the patch, whatever. Thanks man.

Another option is to bootstrap your build by  doing:

svn export http://svn.apache.org/repos/asf/oodt/trunk/core
cd core
mvn install
cd $HOME/src
svn export http://svn.apache.org/repos/asf/oodt/trunk oodt
cd oodt ; mvn install

Cheers,
Chris


From: Lewis John Mcgibbney <le...@gmail.com>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Saturday, March 23, 2013 1:48 PM
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Addition of relativePath in opendapps/pom.xml

Hi,
I didn't hear anything back about this.
Does anyone else experience problems when checking out and attempting to build trunk?
It is a one line patch which I show below. This fixed it for me locally.
Thanks
Lewis

On Wed, Mar 20, 2013 at 10:21 AM, Lewis John Mcgibbney <le...@gmail.com>> wrote:
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



--
Lewis

Re: Addition of relativePath in opendapps/pom.xml

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Lewis,

Happy for a JIRA issue + patch or just the patch, whatever. Thanks man.

Another option is to bootstrap your build by  doing:

svn export http://svn.apache.org/repos/asf/oodt/trunk/core
cd core
mvn install
cd $HOME/src
svn export http://svn.apache.org/repos/asf/oodt/trunk oodt
cd oodt ; mvn install

Cheers,
Chris


From: Lewis John Mcgibbney <le...@gmail.com>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Saturday, March 23, 2013 1:48 PM
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Addition of relativePath in opendapps/pom.xml

Hi,
I didn't hear anything back about this.
Does anyone else experience problems when checking out and attempting to build trunk?
It is a one line patch which I show below. This fixed it for me locally.
Thanks
Lewis

On Wed, Mar 20, 2013 at 10:21 AM, Lewis John Mcgibbney <le...@gmail.com>> wrote:
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



--
Lewis

Re: Addition of relativePath in opendapps/pom.xml

Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
I didn't hear anything back about this.
Does anyone else experience problems when checking out and attempting to
build trunk?
It is a one line patch which I show below. This fixed it for me locally.
Thanks
Lewis

On Wed, Mar 20, 2013 at 10:21 AM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:

> 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*
>



-- 
*Lewis*

Re: Addition of relativePath in opendapps/pom.xml

Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
I didn't hear anything back about this.
Does anyone else experience problems when checking out and attempting to
build trunk?
It is a one line patch which I show below. This fixed it for me locally.
Thanks
Lewis

On Wed, Mar 20, 2013 at 10:21 AM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:

> 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*
>



-- 
*Lewis*