You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Petr Kozelka (JIRA)" <ji...@codehaus.org> on 2010/09/23 23:46:34 UTC
[jira] Commented: (MINSTALL-66) The plugin should only install
attached artifacts to the project if they have a classifier
[ http://jira.codehaus.org/browse/MINSTALL-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236288#action_236288 ]
Petr Kozelka commented on MINSTALL-66:
--------------------------------------
in my company we use attached artifacts without classifier for:
- ZIP modules - the result of build is packaged as ZIP and there is no other "primary" artifact
- ISO modules - the final product is packaged as ISO (=iso9660) - complete result ready to be burned
Yes, I can invent a string to use as the classifier; but ... why ?
On the other hand, I do not understand why attached artifacts without classifier should be ignored, as Bruno suggests. That would completely break my use cases :(
> The plugin should only install attached artifacts to the project if they have a classifier
> ------------------------------------------------------------------------------------------
>
> Key: MINSTALL-66
> URL: http://jira.codehaus.org/browse/MINSTALL-66
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
> Components: install:install
> Affects Versions: 2.3
> Reporter: Bruno Duarte
> Priority: Minor
>
> When running in the lifecycle of a project, the plugin installs attached artifacts that don't have a classifier and overrides the file of the default one.
> Ideally the plugin should ignore attached artifacts that don't have a classifier associated and should write a warning about the ones that is unable to install.
--
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