Build problem

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Build problem

Daryl Richter-3
Hey-

I just updated my camel:

[prax:~/Code/Java/camel] ngzax% svn info
Path: .
URL: https://svn.apache.org/repos/asf/activemq/camel/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 574982
Node Kind: directory
Schedule: normal
Last Changed Author: jstrachan
Last Changed Rev: 574909
Last Changed Date: 2007-09-12 08:18:23 -0400 (Wed, 12 Sep 2007)

[prax:~/Code/Java/camel] ngzax% mvn -Dmaven.test.skip=true install
[INFO] Scanning for projects...
[INFO]  
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]  
------------------------------------------------------------------------
[INFO] The projects in the reactor contain a cyclic reference: Edge  
between 'Vertex{label='org.apache.camel:camel-maven-plugin'}' and  
'Vertex{label='org.apache.camel:camel-spring'}' introduces to cycle  
in the graph org.apache.camel:camel-spring --> org.apache.camel:camel-
maven-plugin --> org.apache.camel:camel-spring
[INFO]  
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]  
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Sep 12 11:02:37 EDT 2007
[INFO] Final Memory: 7M/13M
[INFO]  
------------------------------------------------------------------------

What's up with that?

Tried a clean.  It didn't help.

Is this another "delete your maven repo" thing?

--
Daryl
http://itsallsemantics.com

"I’m afraid of the easy stuff… its always harder than it seems…"
     -- Bill Hampton, 2006



Reply | Threaded
Open this post in threaded view
|

Re: Build problem

Willem.Jiang
Administrator
Hi

No, It is not the "delete your maven repo" issue.
BTW I am using the mvn 2.0.7 to build camel.
I just ran into the same problem with you . After went through the
camel-maven-plugin and camel-spring 's pom.xml, I found them relate on
each other .
So it is cyclic dependency problem.

My solution of this issue is remove the dependency of camel-spring from
the camel-maven-plugin's pom.xml.

Willem.

Daryl Richter wrote:

> Hey-
>
> I just updated my camel:
>
> [prax:~/Code/Java/camel] ngzax% svn info
> Path: .
> URL: https://svn.apache.org/repos/asf/activemq/camel/trunk
> Repository Root: https://svn.apache.org/repos/asf
> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> Revision: 574982
> Node Kind: directory
> Schedule: normal
> Last Changed Author: jstrachan
> Last Changed Rev: 574909
> Last Changed Date: 2007-09-12 08:18:23 -0400 (Wed, 12 Sep 2007)
>
> [prax:~/Code/Java/camel] ngzax% mvn -Dmaven.test.skip=true install
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The projects in the reactor contain a cyclic reference: Edge
> between 'Vertex{label='org.apache.camel:camel-maven-plugin'}' and
> 'Vertex{label='org.apache.camel:camel-spring'}' introduces to cycle in
> the graph org.apache.camel:camel-spring -->
> org.apache.camel:camel-maven-plugin --> org.apache.camel:camel-spring
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Wed Sep 12 11:02:37 EDT 2007
> [INFO] Final Memory: 7M/13M
> [INFO]
> ------------------------------------------------------------------------
>
> What's up with that?
>
> Tried a clean.  It didn't help.
>
> Is this another "delete your maven repo" thing?
>
> --
> Daryl
> http://itsallsemantics.com
>
> "I’m afraid of the easy stuff… its always harder than it seems…"
>     -- Bill Hampton, 2006
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Build problem

jstrachan
On 9/13/07, Willem Jiang <[hidden email]> wrote:

> Hi
>
> No, It is not the "delete your maven repo" issue.
> BTW I am using the mvn 2.0.7 to build camel.
> I just ran into the same problem with you . After went through the
> camel-maven-plugin and camel-spring 's pom.xml, I found them relate on
> each other .
> So it is cyclic dependency problem.
>
> My solution of this issue is remove the dependency of camel-spring from
> the camel-maven-plugin's pom.xml.

Sorry about that! I did a commit just before I lost wi-fi which broke
the build - huge appologies. Will be checking in a fix very shortly.
But yes - either zapping the dependency of camel-maven. plugin on
camel-spring, or of camel-spring on the camel-maven-plugin will fix
it.

--
James
-------
http://macstrac.blogspot.com/
Reply | Threaded
Open this post in threaded view
|

Re: Build problem

Daryl Richter-3
On Sep 13, 2007, at 5:36 AM, James Strachan wrote:

> On 9/13/07, Willem Jiang <[hidden email]> wrote:
>> Hi
>>
>> No, It is not the "delete your maven repo" issue.
>> BTW I am using the mvn 2.0.7 to build camel.
>> I just ran into the same problem with you . After went through the
>> camel-maven-plugin and camel-spring 's pom.xml, I found them  
>> relate on
>> each other .
>> So it is cyclic dependency problem.
>>
>> My solution of this issue is remove the dependency of camel-spring  
>> from
>> the camel-maven-plugin's pom.xml.
>
> Sorry about that! I did a commit just before I lost wi-fi which broke
> the build - huge appologies. Will be checking in a fix very shortly.
> But yes - either zapping the dependency of camel-maven. plugin on
> camel-spring, or of camel-spring on the camel-maven-plugin will fix
> it.

Funny, I thought that one of the things that svn improved upon cvs  
was that it has atomic commits?

Anyway, looks like the cyclic reference has been resolved.  
Unfortunately, it now fails do to another missing dependency:

[INFO]  
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]  
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.codehaus.groovy:groovy-all:jar:1.0

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.codehaus.groovy -
DartifactId=groovy-all \
           -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file

   Path to dependency:
         1) org.apache.camel:camel-script:jar:1.1-SNAPSHOT
         2) org.codehaus.groovy:groovy-all:jar:1.0

----------
1 required artifact is missing.

for artifact:
   org.apache.camel:camel-script:jar:1.1-SNAPSHOT


>
> --
> James
> -------
> http://macstrac.blogspot.com/

--
Daryl
http://itsallsemantics.com

"Hell, there are no rules here-- we're trying to accomplish something."
     -- Thomas A. Edison



Reply | Threaded
Open this post in threaded view
|

Re: Build problem

Willem.Jiang
Administrator
Hi Daryl,

I am also facing the same problem with you.
I do not figure out how to get the groovy to my repository so far.
If you just want to build the src without bother by the camel-script
You could use the below command from the trunk
mvn install -fae
It only fails the build afterwards and allows all non-impacted builds to
continue.

Willem.

Daryl Richter wrote:

> On Sep 13, 2007, at 5:36 AM, James Strachan wrote:
>
>> On 9/13/07, Willem Jiang <[hidden email]> wrote:
>>> Hi
>>>
>>> No, It is not the "delete your maven repo" issue.
>>> BTW I am using the mvn 2.0.7 to build camel.
>>> I just ran into the same problem with you . After went through the
>>> camel-maven-plugin and camel-spring 's pom.xml, I found them relate on
>>> each other .
>>> So it is cyclic dependency problem.
>>>
>>> My solution of this issue is remove the dependency of camel-spring from
>>> the camel-maven-plugin's pom.xml.
>>
>> Sorry about that! I did a commit just before I lost wi-fi which broke
>> the build - huge appologies. Will be checking in a fix very shortly.
>> But yes - either zapping the dependency of camel-maven. plugin on
>> camel-spring, or of camel-spring on the camel-maven-plugin will fix
>> it.
>
> Funny, I thought that one of the things that svn improved upon cvs was
> that it has atomic commits?
>
> Anyway, looks like the cyclic reference has been resolved.  
> Unfortunately, it now fails do to another missing dependency:
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.codehaus.groovy:groovy-all:jar:1.0
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=org.codehaus.groovy
> -DartifactId=groovy-all \
>           -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
>
>   Path to dependency:
>         1) org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>         2) org.codehaus.groovy:groovy-all:jar:1.0
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>   org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>
>
>>
>> --
>> James
>> -------
>> http://macstrac.blogspot.com/
>

Reply | Threaded
Open this post in threaded view
|

Re: Build problem

jstrachan
In reply to this post by Daryl Richter-3
Sorry - this one is my bad too; I was trying to check in changes
without breaking the build while travelling and failed dismally! I'd
missed a jar version when switching to the newer groovy builds.

I've fixed trunk now so touch wood it should now build fine for
everyone - apologies. Beers on me next time we're in the same bar! :)


On 9/17/07, Daryl Richter <[hidden email]> wrote:

> On Sep 13, 2007, at 5:36 AM, James Strachan wrote:
>
> > On 9/13/07, Willem Jiang <[hidden email]> wrote:
> >> Hi
> >>
> >> No, It is not the "delete your maven repo" issue.
> >> BTW I am using the mvn 2.0.7 to build camel.
> >> I just ran into the same problem with you . After went through the
> >> camel-maven-plugin and camel-spring 's pom.xml, I found them
> >> relate on
> >> each other .
> >> So it is cyclic dependency problem.
> >>
> >> My solution of this issue is remove the dependency of camel-spring
> >> from
> >> the camel-maven-plugin's pom.xml.
> >
> > Sorry about that! I did a commit just before I lost wi-fi which broke
> > the build - huge appologies. Will be checking in a fix very shortly.
> > But yes - either zapping the dependency of camel-maven. plugin on
> > camel-spring, or of camel-spring on the camel-maven-plugin will fix
> > it.
>
> Funny, I thought that one of the things that svn improved upon cvs
> was that it has atomic commits?
>
> Anyway, looks like the cyclic reference has been resolved.
> Unfortunately, it now fails do to another missing dependency:
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) org.codehaus.groovy:groovy-all:jar:1.0
>
>    Try downloading the file manually from the project website.
>
>    Then, install it using the command:
>        mvn install:install-file -DgroupId=org.codehaus.groovy -
> DartifactId=groovy-all \
>            -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
>
>    Path to dependency:
>          1) org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>          2) org.codehaus.groovy:groovy-all:jar:1.0
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
>    org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>
>
> >
> > --
> > James
> > -------
> > http://macstrac.blogspot.com/
>
> --
> Daryl
> http://itsallsemantics.com
>
> "Hell, there are no rules here-- we're trying to accomplish something."
>      -- Thomas A. Edison
>
>
>
>


--
James
-------
http://macstrac.blogspot.com/
Reply | Threaded
Open this post in threaded view
|

Re: Build problem

Daryl Richter-3
On Sep 17, 2007, at 6:13 AM, James Strachan wrote:

> Sorry - this one is my bad too; I was trying to check in changes
> without breaking the build while travelling and failed dismally! I'd
> missed a jar version when switching to the newer groovy builds.
>
> I've fixed trunk now so touch wood it should now build fine for
> everyone - apologies. Beers on me next time we're in the same bar! :)
>

[INFO]  
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]  
------------------------------------------------------------------------

Thanks and you're on!

>
> On 9/17/07, Daryl Richter <[hidden email]> wrote:
>> On Sep 13, 2007, at 5:36 AM, James Strachan wrote:
>>
>>> On 9/13/07, Willem Jiang <[hidden email]> wrote:
>>>> Hi
>>>>
>>>> No, It is not the "delete your maven repo" issue.
>>>> BTW I am using the mvn 2.0.7 to build camel.
>>>> I just ran into the same problem with you . After went through the
>>>> camel-maven-plugin and camel-spring 's pom.xml, I found them
>>>> relate on
>>>> each other .
>>>> So it is cyclic dependency problem.
>>>>
>>>> My solution of this issue is remove the dependency of camel-spring
>>>> from
>>>> the camel-maven-plugin's pom.xml.
>>>
>>> Sorry about that! I did a commit just before I lost wi-fi which  
>>> broke
>>> the build - huge appologies. Will be checking in a fix very shortly.
>>> But yes - either zapping the dependency of camel-maven. plugin on
>>> camel-spring, or of camel-spring on the camel-maven-plugin will fix
>>> it.
>>
>> Funny, I thought that one of the things that svn improved upon cvs
>> was that it has atomic commits?
>>
>> Anyway, looks like the cyclic reference has been resolved.
>> Unfortunately, it now fails do to another missing dependency:
>>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) org.codehaus.groovy:groovy-all:jar:1.0
>>
>>    Try downloading the file manually from the project website.
>>
>>    Then, install it using the command:
>>        mvn install:install-file -DgroupId=org.codehaus.groovy -
>> DartifactId=groovy-all \
>>            -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
>>
>>    Path to dependency:
>>          1) org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>>          2) org.codehaus.groovy:groovy-all:jar:1.0
>>
>> ----------
>> 1 required artifact is missing.
>>
>> for artifact:
>>    org.apache.camel:camel-script:jar:1.1-SNAPSHOT
>>
>>
>>>
>>> --
>>> James
>>> -------
>>> http://macstrac.blogspot.com/
>>
>> --
>> Daryl
>> http://itsallsemantics.com
>>
>> "Hell, there are no rules here-- we're trying to accomplish  
>> something."
>>      -- Thomas A. Edison
>>
>>
>>
>>
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/

--
Daryl
http://itsallsemantics.com


Reply | Threaded
Open this post in threaded view
|

Re: Build problem

jstrachan
On 9/17/07, Daryl Richter <[hidden email]> wrote:

> On Sep 17, 2007, at 6:13 AM, James Strachan wrote:
>
> > Sorry - this one is my bad too; I was trying to check in changes
> > without breaking the build while travelling and failed dismally! I'd
> > missed a jar version when switching to the newer groovy builds.
> >
> > I've fixed trunk now so touch wood it should now build fine for
> > everyone - apologies. Beers on me next time we're in the same bar! :)
> >
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
>
> Thanks and you're on!

Its a deal! :)
Glad its working for you finally.

--
James
-------
http://macstrac.blogspot.com/