Ok....
I traced your mistake:
Take a look at your dependency in myblock1 pom.xml:
<dependency>
<groupId>edu.virginia.lib</groupId>
<artifactId>myBlock2</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
While in myBlock2 pom.xml
<name>myBlock2</name>
<groupId>edu.virginia.lib</groupId>
<artifactId>myBlock2</artifactId>
<version>1.0.0</version>
So you need to set the version's equal !!!
Kind regards and glad to be of assistance.
Robby Pelssers
-----Original Message-----
From: Robby Pelssers [mailto:[email protected]]
Sent: Wednesday, September 23, 2009 9:30 PM
To: [email protected]
Subject: RE: problems with "Getting Started" 2.2 [was: Starting out with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the minute...
I wouldn't expect maven to complain without a good reason. Maybe some
small typo is causing this.
Robby
-----Original Message-----
From: Steven D. Majewski [mailto:[email protected]]
Sent: Wednesday, September 23, 2009 9:22 PM
To: [email protected]
Subject: Re: problems with "Getting Started" 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 3:14 PM, Robby Pelssers wrote:
> Ok...here is what I want you to do in this order !!!
>
> In myblock2:
> -Mvn clean
> -Mvn eclipse:eclipse
> -Mvn install
>
>
> In myBlock1..
> -mvn clean
> -add dependency on myBlock2 again
> -mvn eclipse:eclipse
> -mvn install
>
> If this does not work I'm puzzled.
>
> Robby
>
Following those steps I get the same error on mvn install of myBlock1:
[INFO] Failed to resolve artifact.
Missing:
----------
1) edu.virginia.lib:myBlock2:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
[...]
> ??? This is really weird...
>
> That would mean that somehow the myBlock2.jar is in the classpath of
> myBlock1... the only possible explanation I can think of is that you
> configured this dependency in the rcl file...
I *do* have it in the rcl file, and I haven't commented that out.
( maybe that's why it continues to work with the dependencies removed
from the pom. )
myBlock1/rcl.properties:
edu.virginia.lib.myBlock1.service%classes-dir=./target/classes
edu.virginia.lib.myBlock2.service%classes-dir=../myBlock2/target/classes
%exclude-lib=edu.virginia.lib:myBlock2
>
> -----Original Message-----
> From: Robby Pelssers [mailto:[email protected]]
> Sent: Wednesday, September 23, 2009 9:10 PM
> To: [email protected]
> Subject: RE: problems with "Getting Started" 2.2 [was: Starting out
> with
> Cocoon 2.2]
>
> Aha... so that explains why the myBlock2.jar IS still in the
> classpath... lol
>
> If you were to do mvn eclipse:eclipse again which you should after
> adding/ removing dependencies... stuff wil NOT work anymore.
>
> Robby
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
