directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot>
Subject Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/
Date Mon, 09 Aug 2010 08:36:46 GMT
Hi Felix,

Indeed, you're right, there's probably something we could do with the studio-plugin. :)

I think we would need to add additional parameters for the purpose of these specific plugins
(jar libraries rebrandred as eclipse plugins).

Basically, the '.classpath' file needs to be updated and this line:
<classpathentry excluding="**/*.java" path="src/main/resources" kind="src"/>
has to be replaced by this one:
<classpathentry kind="lib" path="src/main/resources" exported="true"/>

Notice that the 'kind' is different (from 'src' to 'lib') and that the classes need to be

A list of 'libClasspathEntries' will probably need to be added to the configuration of the

I will first try to have all the needed plugins working with a '.classpath' stored in SVN
and see if the app still works with the removal of the 'jars' plugin.
Then, I'll (try to) modify the studio-plugin to update the '.classpath' file accordingly (I
might need your help ;) ).


On 5 août 2010, at 22:34, Felix Knecht wrote:

> Hash: SHA1
>> At the moment, the only solution I found is to keep the .classpath and
>> .project files in SVN and don't generate them with Maven.
>> This plugin need something special in their .classpath that I can't
>> generate with Maven to be able to be run in Eclipse.
> IIRC these files (.classpath and .project) are both create/adapted by
> the studio-plugin when running mvn studio:eclipse. So if needed we
> should be able to adapt the studio-plugin?
> Regards
> Felix
> Version: GnuPG v2.0.16 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> oWcAoMryDGh4JmHc/favkq4swuMDB3rV
> =Q1nO

View raw message