Arnaud HERITIER wrote:
Can't it create a problem with WTP ?
Create Problem - unlikely. Will it make any difference for WTP
projects? Very unlikely.
So, you can still have WTP-only projects and Maven-only projects in
your workspace, but m2eclipse plugin won't be able to manage
dependencies for WTP-enabled project (actually WTP have issues issues
with standard JDT classpath containers, which may will be fixed in WTP
2.0).
On the other hand that should not prevent you from using Maven
executor and other features.
Someone tested it ?
Yes. Someone did.
regards,
Eugene
Arnaud
On 2/26/07, *Jason van Zyl* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
On 26 Feb 07, at 7:30 AM 26 Feb 07, < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
> Hi guys!
> Maybe you can outline a strategy to work with the plugin with mvn
> eclipse:eclipse generated files:
> Eclipse error is:
> Build path contains duplicate entry: 'Z:Documents and Settings/
> tgdroti1/.m2/repository/cglib/cglib-full/2.0/cglib-full-2.0.jar'
> for project contentdelivery-api
>
> What would be ideal is a possibility to surpress the creation of
> the 'Maven 2 Dependencies' library.
>
The maven-eclipse-plugin (not to be confused with the integration
work) now has an eclipse:m2eclipse goal which produces a compatible
file format that John Casey has tried with the 0.10 release.
A snapshot has been deploy.
Jason.
>
> Regards
> Tilman
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
<http://xircles.codehaus.org/manage_email>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
