You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2006/01/02 15:37:13 UTC
[jira] Created: (MAVEN-1736) Create a java source code artifact
handler
Create a java source code artifact handler
------------------------------------------
Key: MAVEN-1736
URL: http://jira.codehaus.org/browse/MAVEN-1736
Project: Maven
Type: New Feature
Components: model
Versions: 1.1-beta-2
Reporter: Stephane Nicoll
Assigned to: Stephane Nicoll
Maven one does not allow to deploy java source code to the remote repository. This is needed to improve IDE supports in order to be able to debug code and have a link to the source code.
Both the eclipse plugin and the mevenide plugin use a custom solution to link to source code. We need to standardize this behavior to allow the artifact plugin to deploy java source code.
The proposed standardization is
{noformat}
${groupId}/java-sources/${artifactId}-${version}-sources.jar
{noformat}
Note that this format is currently used by the eclise plugin 1.10 and is the standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout.
--
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
[jira] Commented: (MAVEN-1736) Create a java source code artifact
handler
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1736?page=comments#action_55004 ]
Stephane Nicoll commented on MAVEN-1736:
----------------------------------------
Plugin added to the [plugins sandbox|http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins-sandbox/trunk/source/]
Please comment.
> Create a java source code artifact handler
> ------------------------------------------
>
> Key: MAVEN-1736
> URL: http://jira.codehaus.org/browse/MAVEN-1736
> Project: Maven
> Type: New Feature
> Components: model
> Versions: 1.1-beta-2
> Reporter: Stephane Nicoll
> Assignee: Stephane Nicoll
>
>
> Maven one does not allow to deploy java source code to the remote repository. This is needed to improve IDE supports in order to be able to debug code and have a link to the source code.
> Both the eclipse plugin and the mevenide plugin use a custom solution to link to source code. We need to standardize this behavior to allow the artifact plugin to deploy java source code.
> The proposed standardization is
> {noformat}
> ${groupId}/java-sources/${artifactId}-${version}-sources.jar
> {noformat}
> Note that this format is currently used by the eclise plugin 1.10 and is the standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout.
--
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
[jira] Commented: (MAVEN-1736) Create a java source code artifact
handler
Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1736?page=comments#action_55154 ]
Milos Kleint commented on MAVEN-1736:
-------------------------------------
mevenide-netbeans updated to use the new location as well..
> Create a java source code artifact handler
> ------------------------------------------
>
> Key: MAVEN-1736
> URL: http://jira.codehaus.org/browse/MAVEN-1736
> Project: Maven
> Type: New Feature
> Components: model
> Versions: 1.1-beta-2
> Reporter: Stephane Nicoll
> Assignee: Stephane Nicoll
> Fix For: 1.1-beta-3
>
>
> Maven one does not allow to deploy java source code to the remote repository. This is needed to improve IDE supports in order to be able to debug code and have a link to the source code.
> Both the eclipse plugin and the mevenide plugin use a custom solution to link to source code. We need to standardize this behavior to allow the artifact plugin to deploy java source code.
> The proposed standardization is
> {noformat}
> ${groupId}/java-sources/${artifactId}-${version}-sources.jar
> {noformat}
> Note that this format is currently used by the eclise plugin 1.10 and is the standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout.
--
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
[jira] Closed: (MAVEN-1736) Create a java source code artifact
handler
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1736?page=all ]
Stephane Nicoll closed MAVEN-1736:
----------------------------------
Resolution: Fixed
Fix Version: 1.1-beta-3
Done. We now need to upgrade IDE plugins to use this location.
> Create a java source code artifact handler
> ------------------------------------------
>
> Key: MAVEN-1736
> URL: http://jira.codehaus.org/browse/MAVEN-1736
> Project: Maven
> Type: New Feature
> Components: model
> Versions: 1.1-beta-2
> Reporter: Stephane Nicoll
> Assignee: Stephane Nicoll
> Fix For: 1.1-beta-3
>
>
> Maven one does not allow to deploy java source code to the remote repository. This is needed to improve IDE supports in order to be able to debug code and have a link to the source code.
> Both the eclipse plugin and the mevenide plugin use a custom solution to link to source code. We need to standardize this behavior to allow the artifact plugin to deploy java source code.
> The proposed standardization is
> {noformat}
> ${groupId}/java-sources/${artifactId}-${version}-sources.jar
> {noformat}
> Note that this format is currently used by the eclise plugin 1.10 and is the standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout.
--
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