Maven 1

Create a java source code artifact handler

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-beta-2
  • Fix Version/s: 1.1-beta-3
  • Component/s: model
  • Labels:
    None
  • Number of attachments :
    0

Description

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

${groupId}/java-sources/${artifactId}-${version}-sources.jar

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Stephane Nicoll added a comment -

Plugin added to the plugins sandbox

Please comment.

Show
Stephane Nicoll added a comment - Plugin added to the plugins sandbox Please comment.
Hide
Permalink
Stephane Nicoll added a comment -

Done. We now need to upgrade IDE plugins to use this location.

Show
Stephane Nicoll added a comment - Done. We now need to upgrade IDE plugins to use this location.
Hide
Permalink
Milos Kleint added a comment -

mevenide-netbeans updated to use the new location as well..

Show
Milos Kleint added a comment - mevenide-netbeans updated to use the new location as well..

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.