I'm not using the default repository location either. I think you may be right- 
it may have something to do with that.

-----Original Message-----
From: MATHUS Baptiste [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 8:29 AM
To: Maven Users List
Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released


+1. Same problem here. Just saw the behaviour some minutes ago.
Precision: I'm not using the default repository location, this might a cause of 
this problem.
Do you want someone to log a bug in the tracker, Arnaud?

Cheers.

-----Message d'origine-----
De : Hoover, William [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 18 mars 2008 13:11
À : Maven Users List
Cc : Maven Developers List
Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released

Using "mvn eclipse:clean eclipse:eclipse" with version 2.5. For example, if 
M2_REPO = /path/to/repo executing the command renders build paths for 
dependencies for project as 
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar

If I use version 2.4 M2_REPO is referenced properly (i.e. 
M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar):

        <build>
                <plugins>
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-eclipse-plugin</artifactId>
                                <version>2.4</version>
                        </plugin>
                </plugins>
        </build>

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER
Sent: Tuesday, March 18, 2008 6:33 AM
To: [EMAIL PROTECTED]; Maven Users List
Cc: Maven Developers List
Subject: [ANN] Maven Eclipse Plugin 2.5 Released


The Maven team is pleased to announce the release of the Maven Eclipse Plugin, 
version 2.5

This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules 
and the .settings folder) for use with a project.

http://maven.apache.org/plugins/maven-eclipse-plugin/

You can run mvn -up to get the latest version of the plugin, or specify the 
version in your project's plugin configuration:

<plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-eclipse-plugin</artifactId>
 <version>2.5</version>
</plugin>

In this release we added the support for myeclipse, WTP 2.0 and the possibility 
to connect your projects with existing ones in your workspace.
We also improved the support for rad 6 & 7 and fixed many bugs.
Thanks a lot for those who helped us by providing patches and/or by testing our 
snapshots.

Release Notes - Maven 2.x Eclipse Plugin - Version 2.5

** Bug
    * [MECLIPSE-56] - Generated .project-file misses encoding declaration
    * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin
    * [MECLIPSE-107] - Dependency Version Incorrectly Taken from 
DependencyManagement
    * [MECLIPSE-160] - Wrong description with the goal "add-maven-repo" 
documentation
    * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE 
or a "Execution Environment" is configured as ClasspathContainer.
    * [MECLIPSE-291] - tests fail with spaces in the path name
    * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is 
set
    * [MECLIPSE-297] - eclipse:clean deletes files from pom projects
    * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom'
    * [MECLIPSE-305] - souce-path is absolute versus relative with WAR
    * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor 
(with a relative path)
    * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and 
ignores warSourceDirectory
    * [MECLIPSE-316] - RadCleanMojo does not clean .war files
    * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
    * [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled
    * [MECLIPSE-342] - Found an equals call to check unrelated types
    * [MECLIPSE-346] - Transitive dependencies aren't used to resolve 
JEE/JSP/EJB/Servlet versions
    * [MECLIPSE-352] - RAD application.xml is not generated with good parameters
    * [MECLIPSE-356] - RadLibCopier does not respect warSourceDirectory setting 
of maven-war-plugin when copying dependencies
    * [MECLIPSE-357] - RadManifestWriter uses hardcoded web application source 
directory
    * [MECLIPSE-358] - plugin installed via eclipse:install-plugins have the 
wrong name
    * [MECLIPSE-366] - Test file(s) for Multi-project sample is missing
    * [MECLIPSE-367] - Dependency to artifact with classifier tests not 
distinguished from the regular artifact
    * [MECLIPSE-369] - source status cache not maintained.
    * [MECLIPSE-374] - Rename the expression ${eclipse.workspace} to 
${eclipse.projectDir} for the parameter eclipseProjectDir in the goal 
eclipse:eclipse
    * [MECLIPSE-378] - Projects with customized warSourceDirectory still 
creates empty directories of the default path
    * [MECLIPSE-379] - When downloading sources and javadocs dependency 
classifier is not respected.
    * [MECLIPSE-390] - myeclipse goal ignores additionalConfig
    * [MECLIPSE-399] - URL for javadoc attachments on Unix is invalid

** Improvement
    * [MECLIPSE-32] - Allow for forcing the creation of direct project 
references for dependencies
    * [MECLIPSE-79] - exclude dependencies from the Classpath Container
    * [MECLIPSE-120] - Force inter-project dependencies
    * [MECLIPSE-152] - Write .classpath with ordered dependencies [incl. Patch]
    * [MECLIPSE-163] - eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
    * [MECLIPSE-213] - more jee support for wtp
    * [MECLIPSE-219] - Allow file contents to be obtained from url or location
    * [MECLIPSE-256] - [PATCH]Flat Maven2 Multiproject Structures and Classpath 
Resolution as Projects (not binaries)
    * [MECLIPSE-264] - Support for WTP2.0
    * [MECLIPSE-281] - Documentation patch for PDE support
    * [MECLIPSE-292] - Behaviour for sources and Javadoc attachement for 
dependencies should be consistent
    * [MECLIPSE-294] - Sort items in the generated .classpath
    * [MECLIPSE-331] - Allow to use a packaging model to override the packaging 
defined in the pom
    * [MECLIPSE-333] - WTP-2.0 support with howto apt, refactoring and  
contextroot handling
    * [MECLIPSE-392] - Output is written to src/main/webapp instead of target

** New Feature
    * [MECLIPSE-74] - Workspace inspection when adding a project
    * [MECLIPSE-127] - Ability to add other workspace configuration similar to 
add-maven-repo goal
    * [MECLIPSE-158] - Add the ability to selectively treat a referenced 
project as a local repository file
    * [MECLIPSE-197] - Automatic reference of dependee projects
    * [MECLIPSE-260] - Ignore artifact version mismatches on creating 
references to sub-projects
    * [MECLIPSE-334] - Add a rule that determined artifacts will be always 
recognized as reactor projects
    * [MECLIPSE-341] - Support RAD7
    * [MECLIPSE-344] - connecting existing workspace artifact-projects
    * [MECLIPSE-359] - Add support for MyEclipse

** Wish
    * [MECLIPSE-308] - Change the method of verifying whether JRE is included 
in "classpathContainers"

Enjoy,

-The Maven team

..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com 
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to