On Sep 23, 2009, at 2:56 PM, Robby Pelssers wrote:

Ok...

Check in eclipse the value of M2_REPO:

Window -> Preferences - > Java -> Build path -> claspath variables ->
M2_REPO

I think it's got an incorrect value.

Robby



No. M2_REPO is pointing to /Users/sdm7g/.m2/repository/

And since I'm following the getting_started instructions,
I'm doing all the maven commands from the command line,
and using eclipse only for editing. ( Although I've done
all of the 'mvn eclipse:eclipse' commands so that eclipse
loads the project properly. )



-----Original Message-----
From: Steven D. Majewski [mailto:[email protected]]
Sent: Wednesday, September 23, 2009 8:45 PM
To: [email protected]
Subject: Re: problems with "Getting Started" 2.2 [was: Starting out with
Cocoon 2.2]


On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:

So if I understand you correctly you have one block depending on the
other?

Did you also add the dependency of myblock2 in the pom.xml of
myblock1?

Yes. ( And if I take that dependency out, it runs without complaint. )


I guess so... since that's what maven is complaining about...

Did you install myblock2 before running mbylock1$ mvn jetty:run  ??

Yes.


Can you check in your maven repository... location is configured in
settings.xml  of ${maven_home}/conf  if there is a folder
Edu/Virginia/lib/myBlock2 which contains the jar myBlock2.jar?



I'm using the defaults, so I didn't make a settings.xml:

$ find  ~/.m2/repository/edu/virginia/lib/ -type f -print
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock1/1.0.0/
myBlock1-1.0.0.jar
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock1/1.0.0/
myBlock1-1.0.0.pom
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock1/maven-metadata-
local.xml
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock2/1.0.0/
myBlock2-1.0.0.jar
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock2/1.0.0/
myBlock2-1.0.0.pom
/Users/sdm7g/.m2/repository/edu/virginia/lib//myBlock2/maven-metadata-
local.xml



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

Reply via email to