You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Seelmann <se...@apache.org> on 2010/08/05 21:59:05 UTC

Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/

> Author: pamarcelot
> Date: Thu Aug  5 16:27:33 2010
> New Revision: 982679
>
> URL: http://svn.apache.org/viewvc?rev=982679&view=rev
> Log:
> Addded two new plugins for 'org.apache.commons.codec' and 'org.apache.commons.collections'.

Great. I guess you add those plugins so we can get rid of the "jars" plugin?

Kind Regards,
Stefan

Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/

Posted by Felix Knecht <fe...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Pierre-Arnaud

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

This would be nice.

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

+1, that's the way to go.

> Then, I'll (try to) modify the studio-plugin to update the '.classpath' file accordingly (I might need your help ;) ).

Just drop a note and I'll do my very best :-)

Regards
Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxfxzwACgkQ2lZVCB08qHHr2wCgpHgSpFmXZnkY+wV0jn0ym+Xu
WxsAnR9O0eWiVDKX/QucxEc7CTEZhq/f
=H89C
-----END PGP SIGNATURE-----

Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/

Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
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 'exported'.

A list of 'libClasspathEntries' will probably need to be added to the configuration of the studio-plugin.

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 ;) ).

Thanks,
Pierre-Arnaud

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

> -----BEGIN PGP SIGNED MESSAGE-----
> 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkxbIE8ACgkQ2lZVCB08qHEa3ACg7RvxACLZs13b5Jmj+s0D9PEA
> oWcAoMryDGh4JmHc/favkq4swuMDB3rV
> =Q1nO
> -----END PGP SIGNATURE-----


Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/

Posted by Felix Knecht <fe...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxbIE8ACgkQ2lZVCB08qHEa3ACg7RvxACLZs13b5Jmj+s0D9PEA
oWcAoMryDGh4JmHc/favkq4swuMDB3rV
=Q1nO
-----END PGP SIGNATURE-----

Re: svn commit: r982679 - in /directory/studio/trunk: ./ org.apache.commons.codec/ org.apache.commons.collections/

Posted by Pierre-Arnaud Marcelot <pa...@gmail.com>.
Hi Stefan,

Exactly, i'm running an experiment.

It seems to work great with the test I run with LDAP Servers plugin
and the Mina Core library rebranded as a plugin.

It was not easy to have the libraries rebranded as plugins working in
both Eclipse and Maven jar modes.
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.

Do you think it is a viable solution ?

Regards
PA

On 5 août 2010, at 21:59, Stefan Seelmann <se...@apache.org> wrote:

>> Author: pamarcelot
>> Date: Thu Aug  5 16:27:33 2010
>> New Revision: 982679
>>
>> URL: http://svn.apache.org/viewvc?rev=982679&view=rev
>> Log:
>> Addded two new plugins for 'org.apache.commons.codec' and 'org.apache.commons.collections'.
>
> Great. I guess you add those plugins so we can get rid of the "jars" plugin?
>
> Kind Regards,
> Stefan