The problem is in the invoker. When the pom is specified as is in the
case of the plugin tools, the -F command line is used to specify it:
if ( !"pom.xml".equals( pom.getName() ) )
{
logger
.debug( "Specified POM file is not named
\'pom.xml\'. Using the \'-f\' command-line option to accommodate
non-standard filename..." );
// FIXME: Handle quotes in localRepo directory path...
cli.createArgument().setLine( "-f " + pom.getName() );
}
This is an edge case in the tests and doesn't affect the eclipse plugin
functionality, thus I'm of the opinion that the release should continue.
To fix this would require a release of the 2.0.7 invoker and would
effectively kill the eclipse release for a while; I need to move to some
other things for a while and won't have the time to do it myself.
-----Original Message-----
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 08, 2007 4:24 PM
To: Maven Developers List
Subject: Re: [VOTE] release eclipse 2.4 (take 2)
Sorry to -1 after all the recent hard work fixing the tests, but they
still break on Windows when run in a path with spaces - see
MECLIPSE-291.
Should be an easy fix, although I'm not sure if I'll get a chance to
take a proper look immediately.
Cheers,
Mark
On 08/07/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> It's been about 5 months since an eclipse plugin release and we have
> lots of fixes and a handful of enhancements. The issues detected in
the
> last vote (MECLIPSE-295) have been fixed in the currently staged
> plugin-testing-tools 1.0-alpha-2. As such, this release is dependent
on
> the successful release of the updated tools.
>
> The site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> The plugin is staged at:
> http://people.apache.org/~brianf/staging-repository
>
> The tag is at:
>
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-
> 2.4/
>
> Release Notes - Maven 2.x Eclipse Plugin - Version 2.4:
>
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001&styleName
> =Html&projectId=11133&Create=Create
>
> ** Bug
> * [MECLIPSE-108] - .wtpmodules with version 2.4 for
> javax.servlet:servlet-api:2.3
> * [MECLIPSE-109] - .component wb-resource source path incorrect
for
> ear packaging
> * [MECLIPSE-151] - Incorrect name for test sources jars
> * [MECLIPSE-198] - EJB version is not resloved
> * [MECLIPSE-215] - WTP 1.5 Documentation
> * [MECLIPSE-220] - Incorrect eclipse facet information when doing
> mvn eclipse:eclipse for war and ejb projects.
> * [MECLIPSE-225] - Invalid .classpath Entries.
> * [MECLIPSE-231] - Clean mojo assumes that POM projects never have
> .project files - this is incorrect
> * [MECLIPSE-233] - Manifest attributes incorrectly treated as
> case-sensitive
> * [MECLIPSE-234] - [PATCH] EclipsePlugin.extractResourceDirs()
> reuses String method argument causing maven-eclipse.xml copy-resources
> problems
> * [MECLIPSE-236] - eclipse:make-artifacts should preserve the
> resolution:=optional directive
> * [MECLIPSE-237] - unsafe EclipseSourceDir.equals() method
> * [MECLIPSE-239] - eclipse:eclipse fails to find dependency
> org.apache.maven.plugins:maven-eclipse-plugin:pom:test
> * [MECLIPSE-241] - Compiler settings in pluginManagement aren't
used
> in wtp facet
> * [MECLIPSE-243] - The last 2.4 SNAPSHOT forbid Apache Directory
> Server to be built
> * [MECLIPSE-248] - Tests fail due to incorrectly attempting to use
> released plugin version, not locally sandboxed one under test",
> * [MECLIPSE-255] - WTP Settings does not use servlet-api version
> defined in pom.xml
> * [MECLIPSE-263] - Project Facet 'Java' set to 1.4 instead of 5.0
in
> a Java 5.0 project
> * [MECLIPSE-278] - duplicated classpathentries
> * [MECLIPSE-279] - PDE projects should be considered java projects
> in all cases
> * [MECLIPSE-287] - Regression - fails to correctly construct
> classpath containing dependencies with classifiers
> * [MECLIPSE-295] - Eclipse plugin fails due to missing
> org.apache.maven.plugins:maven-eclipse-plugin:pom:test
>
> ** Improvement
> * [MECLIPSE-40] - Multi project dependencies should not require
> eclipse project names to be the artifactId
> * [MECLIPSE-207] - Add supprt for arbitrary facets, like JSF
> * [MECLIPSE-267] - Resolve version ranges in make-artifacts
> * [MECLIPSE-268] - [eclipse:rad goal] Make customization of
servlet
> version, jsp version, ... possible through pom configuration
> * [MECLIPSE-286] - Ability to skip generated-resources/rad6 folder
> creation while executing eclipse:rad
> * [MECLIPSE-292] - Behaviour for sources and Javadoc attachement
for
> dependencies should be consistent
>
> ** New Feature
> * [MECLIPSE-65] - Add contextName parameter to eclipse mojo so a
> webtool context name doesn't have to match artifactId/project name.
> * [MECLIPSE-119] - Allow custom project name for eclipse projects
> * [MECLIPSE-189] - addVersionToProjectName property
> * [MECLIPSE-251] - Allows prefixing of eclipse project name
> * [MECLIPSE-271] - Ability to skip
>
>
>
> Vote is open for 72hrs, please +1/+0/-1
>
>
> +1
>
>
> ---------------------------------------------------------------------
> 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]
