cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <>
Subject Re: [M10N] end of first flattening round
Date Fri, 06 Jan 2006 13:35:41 GMT
Maven has some cool features!

$ mvn -Declipse.downloadSources=true eclipse:eclipse

Downloads the source code for the dependencies if they are avaliable in 
the  M2 repository. Not all of the projects have source code in the 
repository, but quite a few has.

The plugin also attach the source code to the jars in Eclipse.

As our local repository often refuses connections, it is probably better 
to run the above goal on one project at a time instead of from top level.


Daniel Fagerstrom skrev:
> Thanks, got it working. It should be M2_REPO rather than M2_HOME. I set 
> the classpath variable M2_REPO by: Project->Proterties->(clicking on any 
>  jar starting with M2_REPO)->Edit...->Variable...->New... Is there some 
> less obscure way?
> /Daniel
> Jorg Heymans skrev:
>> Daniel Fagerstrom wrote:
>>> How do I use the Eclipse plugin? I have used the eclipse-project goal in
>>> ant before that create one Eclipse project for all of Cocoon trunk. But
>>> I guess that each sub project of trunk becomes an own Eclipse project 
>>> now.
>>> So starting with a checked out Cocoon trunk what steps are needed to get
>>> e.g. cocoon-core into Eclipse?
>> Right.
>> from /trunk, run mvn eclipse:clean first to remove any left over eclipse
>> files. Then run mvn eclipse:eclipse.
>> Next go to eclipse, and make sure you haven't got trunk mounted as a
>> project already. Do File-Import->Existing projects into workspace, then
>> point to your trunk directory and it should detect the newly created
>> blocks as projects.
>> Note that you need to declare the M2_HOME classpath variable in your
>> workspace, it should point to your local m2 repository. At the moment
>> there are still compilation problems because of htmlunit, but this
>> should be enough to get you going already.
>> Jorg

View raw message