[jira] [Resolved] (MRELEASE-669) provide support for project "byproducts"

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold resolved MRELEASE-669.
--------------------------------------------
    Resolution: Won't Fix

Since there's no activity here and this issue is scheduled for autoclosure anyway, I'm going to make an opinionated call that we shouldn't fix this. This is not how maven addresses this need. 

> provide support for project "byproducts"
> ----------------------------------------
>
>                 Key: MRELEASE-669
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-669
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>    Affects Versions: 2.1
>            Reporter: Ryan Heaton
>            Priority: Major
>         Attachments: project-artifact-byproducts.diff, project-artifact-byproducts2.diff
>
>
> We need to be able to provide support for the notion of "project artifact byproducts". These "byproducts" are simply artifacts that are produced by and associated to a project, but they differ from "attached" artifacts because they are their own independent artifacts with their own pom and dependency tree.
> The most notable examples of this are [Enunciate-generated client-side artifacts|http://docs.codehaus.org/display/ENUNCIATE/Client-side+artifacts+and+Maven]. See ENUNCIATE-501.
> The attached patch allows for these byproduct artifacts to be declared as part of the project properties. It is applied at https://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)