You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@maven.apache.org by Barrie Treloar <ba...@apache.org> on 2009/04/01 22:57:34 UTC
[ANN] Maven Eclipse Plugin 2.6 Released
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.6
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 should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.6</version>
</plugin>
Known Issues:
* [MECLIPSE-443] - Only include **/*.java in Java source directories
may affect you if you use ajdt or have non-java sources in your
directories that you expect to be compiled
Release 2.6.1 (which may get renamed to 2.7) has fixed this issue and
will be released shortly.
See http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&fixfor=15130
Release Notes - Maven 2.x Eclipse Plugin - Version 2.6
** Sub-task
* [MECLIPSE-479] - More "contaigner" entries
** Bug
* [MECLIPSE-111] - Additional webResources are not added to the
component list when using WTP projects generation
* [MECLIPSE-150] - [with PATCH] Plugin generates invalid Eclipse
project files when multiproject contains two references to the same
artifact
* [MECLIPSE-206] - IdeUtils.toRelativeAndFixSeparator broken on Windows
* [MECLIPSE-261] - IdeUtils.toRelativeAndFixSeparator returns
incomplete path
* [MECLIPSE-326] - m2eclipse goal does not respect
additionalBuildcommands and additionalProjectnatures defined in pom
* [MECLIPSE-337] - test failure needed to be commented out
* [MECLIPSE-364] - incorrect dependencies with different
projectNameTemplates in submodules
* [MECLIPSE-377] - eclipse:eclipse -DdownloadSources=true
shouldn't attempt download more than once in a multi-project
* [MECLIPSE-397] - Eclipse project set as dependency + test-jar
dependency is included twice in .classpath
* [MECLIPSE-414] - Not beeing @aggregator, eclipse plugin does not
require executedProject
* [MECLIPSE-415] - settings stored in wrong project directory
* [MECLIPSE-418] - OSGi 4 support for "Bundle-SymbolicName"
* [MECLIPSE-419] - Classpath generated by eclipse:myeclipse skip
provided dependencies
* [MECLIPSE-423] - NullPointerException when existing Manifest.MF
file has no Class-Path element
* [MECLIPSE-427] - .springBeans definition throws NullPointer if
BaseDir does not exist
* [MECLIPSE-445] - myeclipse target doesn't generate spring bean
files for hierarchical projects.
* [MECLIPSE-475] - Container mispelling
* [MECLIPSE-486] - ITs dont compare expected files if the IT is a
multi-module project
* [MECLIPSE-488] - InstallPluginsMojo throws NPE if a jar has no manifest
* [MECLIPSE-508] - If base artifact does not exist then the
unavailable cache was incorrectly updated
* [MECLIPSE-509] - Unavailable cache is incorrectly updated to
mark sources/javadoc as not available when downloads option is not
specified
** Improvement
* [MECLIPSE-318] - test classes and resources need to be first in
.classpath file
* [MECLIPSE-437] - Ordering of .classpath entries when using a
newer version of JARs already included in the JDK.
* [MECLIPSE-442] - Classpath container entries should come last in
.classpath
* [MECLIPSE-443] - Only include **/*.java in Java source directories
* [MECLIPSE-493] - Automatically locate workspace
** New Feature
* [MECLIPSE-200] - Please add support for the AJDT plugin
* [MECLIPSE-270] - Add support for classpathentry attributes
* [MECLIPSE-313] - AJDT feature
* [MECLIPSE-387] - download source should accept exclusion of artifact
* [MECLIPSE-504] - Add a new mojo eclipse:remove-cache
** Task
* [MECLIPSE-345] - Split unit tests and integration tests
* [MECLIPSE-349] - Move integration tests in the integration-tests profile
** Test
* [MECLIPSE-502] -
org.apache.maven.plugin.ide.IdeUtilsTest.testToRelativeAndFixSeparator_WhereOnDifferentDrivesAndAbsolutePaths()
fail if drive "D" doesnt exists)
Enjoy,
-The Maven team
Re: [ANN] Maven Eclipse Plugin 2.6 Released
Posted by linchongsu <su...@gmail.com>.
dear，although the maven throws exception when i ran the cmd "mvn clean
eclipse:clean eclipse:eclipse -Declipse.addVersionToProjectName=true" with
the log i have shown in my last send email,
but the maven eclipse(version) plugin generated my project actually
successfully while i have
not change the charset of my eclipse's workspace.
i have not just got why it happend to me !
in the way, thanks for Barrie Treloar reply! the maven runs well with me!
On Thu, Apr 2, 2009 at 6:12 PM, Barrie Treloar <ba...@gmail.com> wrote:
> > org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace
> > content allowed before start tag and not \u9518 (position: START_DOCUMENT
>
> \u9518 looks like international character sets.
>
> Not sure why it isn't whitespace.
>
> Same thing, try to make small test case and raise a JIRA.
> If you can compare the output from 2.5.1 and 2.6 that might help as well.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
漠洋(苏琳冲)
SuLinchong
Phone 13656669328
Qq 387973308
Msn sulinchong@hotmail.com
Re: [ANN] Maven Eclipse Plugin 2.6 Released
Posted by Barrie Treloar <ba...@gmail.com>.
> org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace
> content allowed before start tag and not \u9518 (position: START_DOCUMENT
\u9518 looks like international character sets.
Not sure why it isn't whitespace.
Same thing, try to make small test case and raise a JIRA.
If you can compare the output from 2.5.1 and 2.6 that might help as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Eclipse Plugin 2.6 Released
Posted by linchongsu <su...@gmail.com>.
oh, all right, but i think ,i should inspect the cmd
"-Declipse.addVersionToProjectName=true" more carefully.what's more, when i
comes to use version 2.6, my eclipse's workspace does not run as well as
before.
The follow is the log:
[WARNING] could not read workspace
project:D:\taobao.workspace\.metadata\.plugins\org.eclipse.core.resources\.projects\wangwang-plugin
org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace
content allowed before start tag and not \u9518 (position: START_DOCUMENT se
8... @1:1)
at
org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1519)
at
org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1395)
at
org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093)
at
org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:187)
at
org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:83)
at
org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:48)
at
org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readArtefact(ReadWorkspaceLocations.java:341)
at
org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readWorkspace(ReadWorkspaceLocations.java:533)
at
org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init(ReadWorkspaceLocations.java:94)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfiguration(EclipsePlugin.java:1784)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathContainers(EclipsePlugin.java:1350)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.setup(EclipsePlugin.java:807)
at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:498)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
The project wangwang-plugin is also in my workspace,but i have not
modified the project's file.
when i run the cmd "mvn clean eclipse:clean eclipse:eclipse
-Declipse.addVersionToProjectName=true"
for the bellow project
<projectDescription>
<name>**-connect-1.12-SNAPSHOT</name>
<comment>**</comment>
<projects>
<project>**-json</project>
<project>**-string</project>
<project>**-xml</project>
<project>**-server</project>
<project>**-config</project>
<project>**-core</project>
<project>**-dal</project>
<project>**-sm</project>
<project>**-engine</project>
<project>**-tim</project>
<project>**-client</project>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>
the maven throws the exception, and also the maven eclipse(2.6) plugin
didn't generate the eclipse project definite succssfully
,although the console tell me generate succssfully.
On Thu, Apr 2, 2009 at 2:24 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On Thu, Apr 2, 2009 at 4:03 PM, linchongsu <su...@gmail.com>
> wrote:
> > hi,dear
> > i found i can't run "mvn clean eclipse:clean eclipse:eclipse
> > -Declipse.addVersionToProjectName=true" all right with version 2.6
>
> If you can provide a small repeatable test case then raise a JIRA and
> we can look into it.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
漠洋(苏琳冲)
SuLinchong
Phone 13656669328
Qq 387973308
Msn sulinchong@hotmail.com
Re: [ANN] Maven Eclipse Plugin 2.6 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On Thu, Apr 2, 2009 at 4:03 PM, linchongsu <su...@gmail.com> wrote:
> hi,dear
> i found i can't run "mvn clean eclipse:clean eclipse:eclipse
> -Declipse.addVersionToProjectName=true" all right with version 2.6
If you can provide a small repeatable test case then raise a JIRA and
we can look into it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Eclipse Plugin 2.6 Released
Posted by linchongsu <su...@gmail.com>.
hi,dear
i found i can't run "mvn clean eclipse:clean eclipse:eclipse
-Declipse.addVersionToProjectName=true" all right with version 2.6
the plugin generate the project with version,however ,it has not generate
the dependency project with version?
such as:
<projectDescription>
<name>**-connect-1.12-SNAPSHOT</name>
<comment>**</comment>
<projects>
<project>**-json</project>
<project>**-string</project>
<project>**-xml</project>
<project>**-server</project>
<project>**-config</project>
<project>**-core</project>
<project>**-dal</project>
<project>**-sm</project>
<project>**-engine</project>
<project>**-tim</project>
<project>**-client</project>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>
is it a bug? or how can i add version to the denepency project name
Thanks for everyone's help!
su
On Thu, Apr 2, 2009 at 4:57 AM, Barrie Treloar <ba...@apache.org> wrote:
> The Maven team is pleased to announce the release of the Maven Eclipse
> Plugin, version 2.6
>
> 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 should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <version>2.6</version>
> </plugin>
>
> Known Issues:
> * [MECLIPSE-443] - Only include **/*.java in Java source directories
> may affect you if you use ajdt or have non-java sources in your
> directories that you expect to be compiled
> Release 2.6.1 (which may get renamed to 2.7) has fixed this issue and
> will be released shortly.
> See
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11133&fixfor=15130
>
> Release Notes - Maven 2.x Eclipse Plugin - Version 2.6
>
> ** Sub-task
> * [MECLIPSE-479] - More "contaigner" entries
>
> ** Bug
> * [MECLIPSE-111] - Additional webResources are not added to the
> component list when using WTP projects generation
> * [MECLIPSE-150] - [with PATCH] Plugin generates invalid Eclipse
> project files when multiproject contains two references to the same
> artifact
> * [MECLIPSE-206] - IdeUtils.toRelativeAndFixSeparator broken on Windows
> * [MECLIPSE-261] - IdeUtils.toRelativeAndFixSeparator returns
> incomplete path
> * [MECLIPSE-326] - m2eclipse goal does not respect
> additionalBuildcommands and additionalProjectnatures defined in pom
> * [MECLIPSE-337] - test failure needed to be commented out
> * [MECLIPSE-364] - incorrect dependencies with different
> projectNameTemplates in submodules
> * [MECLIPSE-377] - eclipse:eclipse -DdownloadSources=true
> shouldn't attempt download more than once in a multi-project
> * [MECLIPSE-397] - Eclipse project set as dependency + test-jar
> dependency is included twice in .classpath
> * [MECLIPSE-414] - Not beeing @aggregator, eclipse plugin does not
> require executedProject
> * [MECLIPSE-415] - settings stored in wrong project directory
> * [MECLIPSE-418] - OSGi 4 support for "Bundle-SymbolicName"
> * [MECLIPSE-419] - Classpath generated by eclipse:myeclipse skip
> provided dependencies
> * [MECLIPSE-423] - NullPointerException when existing Manifest.MF
> file has no Class-Path element
> * [MECLIPSE-427] - .springBeans definition throws NullPointer if
> BaseDir does not exist
> * [MECLIPSE-445] - myeclipse target doesn't generate spring bean
> files for hierarchical projects.
> * [MECLIPSE-475] - Container mispelling
> * [MECLIPSE-486] - ITs dont compare expected files if the IT is a
> multi-module project
> * [MECLIPSE-488] - InstallPluginsMojo throws NPE if a jar has no
> manifest
> * [MECLIPSE-508] - If base artifact does not exist then the
> unavailable cache was incorrectly updated
> * [MECLIPSE-509] - Unavailable cache is incorrectly updated to
> mark sources/javadoc as not available when downloads option is not
> specified
>
> ** Improvement
> * [MECLIPSE-318] - test classes and resources need to be first in
> .classpath file
> * [MECLIPSE-437] - Ordering of .classpath entries when using a
> newer version of JARs already included in the JDK.
> * [MECLIPSE-442] - Classpath container entries should come last in
> .classpath
> * [MECLIPSE-443] - Only include **/*.java in Java source directories
> * [MECLIPSE-493] - Automatically locate workspace
>
> ** New Feature
> * [MECLIPSE-200] - Please add support for the AJDT plugin
> * [MECLIPSE-270] - Add support for classpathentry attributes
> * [MECLIPSE-313] - AJDT feature
> * [MECLIPSE-387] - download source should accept exclusion of artifact
> * [MECLIPSE-504] - Add a new mojo eclipse:remove-cache
>
> ** Task
> * [MECLIPSE-345] - Split unit tests and integration tests
> * [MECLIPSE-349] - Move integration tests in the integration-tests
> profile
>
> ** Test
> * [MECLIPSE-502] -
>
> org.apache.maven.plugin.ide.IdeUtilsTest.testToRelativeAndFixSeparator_WhereOnDifferentDrivesAndAbsolutePaths()
> fail if drive "D" doesnt exists)
>
> Enjoy,
>
> -The Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
漠洋(苏琳冲)
SuLinchong
Phone 13656669328
Qq 387973308
Msn sulinchong@hotmail.com