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 2006/01/22 14:40:06 UTC
[jira] Closed: (MECLIPSE-57) Add a way to indicate that path ==
sourcepath
[ http://jira.codehaus.org/browse/MECLIPSE-57?page=all ]
fabrizio giustina closed MECLIPSE-57:
-------------------------------------
Assign To: fabrizio giustina
Resolution: Won't Fix
Sorry, but since maven doesn't support such "unified" artifacts and has a different standard way for handling source artifacts I can't see any good reason for the eclipse plugin to support that. Also, I can't see any way we could handle mixed standard/unified source paths.
Any particolar reason why you can't use standard maven source artifacts?
> Add a way to indicate that path == sourcepath
> ---------------------------------------------
>
> Key: MECLIPSE-57
> URL: http://jira.codehaus.org/browse/MECLIPSE-57
> Project: Maven 2.x Eclipse Plugin
> Type: Improvement
> Versions: 2.0
> Reporter: Matthew Beermann
> Assignee: fabrizio giustina
> Priority: Minor
> Fix For: 2.1
>
>
> Our repository is populated with "unified" jars, which include the class files and source code both. In other words, for our .classpath files, path == sourcepath. It would be very handy if there were some way to indicate this in the plugin's parameters.
--
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