[
http://jira.codehaus.org/browse/MNG-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3515.
-----------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2.x (to be reviewed))
Assignee: Brett Porter
Maven 2.2.0 doesn't have a problem with this at least - I was able to use the
build-helper plugin to attach an artifact with no classifier and a different
type and install to the repository together
> Allow several synonymous main artifacts, e.g. zip and tar.gz, just like you
> can have with a classifier
> ------------------------------------------------------------------------------------------------------
>
> Key: MNG-3515
> URL: http://jira.codehaus.org/browse/MNG-3515
> Project: Maven 2 & 3
> Issue Type: New Feature
> Reporter: David Jencks
> Assignee: Brett Porter
>
> It's possible for a project to generate several synonymous main artifacts
> that are different packagings of the same content. The specific case I ran
> across is in https://svn.apache.org/repos/asf/activemq/branches/activemq-4.1
> assembly module rev 646965.
> The build happily constructs apache-activemq-4.1-SNAPSHOT.tar.gz/tar.bz2/zip
> artifacts in target but does not install or deploy them. However if I add a
> "bin" classifier all the artifacts are installed/deployed.
> Another possible example that jdcasey suggested would be a project that
> constructs both dll and so files.
> I don't see how this could introduce any ambiguity since any dependency on a
> non-jar artifact has to AFAIK specify the type explicitly.
>
--
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
