You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/10/09 18:56:12 UTC
[jira] Closed: (MPECLIPSE-101) [aggregate record] patch for some MPECLIPSE open issues
[ http://jira.codehaus.org/browse/MPECLIPSE-101?page=all ]
fabrizio giustina closed MPECLIPSE-101:
---------------------------------------
Assign To: fabrizio giustina
Resolution: Fixed
Patch committed to svn. Will close and comment related issues.
> [aggregate record] patch for some MPECLIPSE open issues
> -------------------------------------------------------
>
> Key: MPECLIPSE-101
> URL: http://jira.codehaus.org/browse/MPECLIPSE-101
> Project: maven-eclipse-plugin
> Type: Task
> Versions: 1.9
> Reporter: fabrizio giustina
> Assignee: fabrizio giustina
> Fix For: 1.10
> Attachments: MPECLIPSE_aggregate.diff
>
>
> as sent to the dev mailing list, the attached diff addresses many actual plugin issues:
> http://marc.theaimsgroup.com/?l=turbine-maven-dev&m=112644857100031&w=2
> fixes:
> MPECLIPSE-96 classpathentry contains trailing pipe character that confuses Eclipse 3.1
> MPECLIPSE-80 Generate .wtpmodules files
> MPECLIPSE-78 avoid duplicated builders/natures
> MPECLIPSE-63 dont want the hardcoded org.eclipse.jdt.core.javabuilder
> MPECLIPSE-92 Setting relative path value to "maven.eclipse.output.dir" generates wrong absolute classpath entry
> MPECLIPSE-72 Failing use cases for projects with just resources
> MPECLIPSE-57 Make sourcepath more flexible
> Actually a won't fix, related to the change explained in changes.xml:
> Java source location now defaults to MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar
> (standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout).
> The path ${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension} is still supported for backward
> compatibility and it will be used only if a file already exists at that location.
> Since now there is well defined standard it doesn't make sense to make the artifact name and location configurable.
> duplicate:
> MPECLIPSE-81 Resources are added as path even if they do not exist in the filesystem
> -> see MPECLIPSE-72
> MPECLIPSE-74 javanature / javabuilder for every kind of project
> -> see MPECLIPSE-63 (different solution, java nature is not added if there are no source/resource folders)
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org