[
http://jira.codehaus.org/browse/MECLIPSE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-419.
-----------------------------------
Resolution: Fixed
As part of this change a lot of methods on EclipsePlugin were made final or
hidden as private.
This is to avoid the problems in the future where subclasses are extending at
the wrong points and getting out of sync. e.g. MyEclipse plugin overroad
writeConfiguration() but missed all the WTP changes.
Added javadocs for public/protected methods that were missing docs.
Renamed methods used for subclassing to be consistent with a "Extras" suffix.
MyEclipse now just writes MyEclipse specific files and EclipsePlugin handles
the rest.
Updated ITs to include provided jars in classpath.
As part of the EclipsePlugin/WTP handling target/generated-resources/eclipse
will be added to the classpath with the generated META-INF/MANIFEST.MF file.
> Classpath generated by eclipse:myeclipse skip provided dependencies
> -------------------------------------------------------------------
>
> Key: MECLIPSE-419
> URL: http://jira.codehaus.org/browse/MECLIPSE-419
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: MyEclipse support
> Affects Versions: 2.5
> Environment: maven 2.0.8 / jkd 1.5 / windows XP
> Reporter: Arnaud Heritier
> Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> When we use the mojo eclipse:myeclipse, provided dependencies aren't added in
> the eclipse classpath. In eclipse:eclipse and others mojos they are.
> Provided dependencies are required to build some parts of our code or to
> launch some tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
