[
http://jira.codehaus.org/browse/MINSTALL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108836
]
Brill Pappin commented on MINSTALL-42:
--------------------------------------
Yes, your right... I just didn't have time to produce a test.
Should be easy though. The exact command I'm running is:
CALL mvn install:install-file -Dfile=gwt-dev-windows.jar
-DgroupId=com.google.gwt -DartifactId=gwt-dev -Dversion=1.4.60 -Dpackaging=jar
-Dclassifier=windows -DgeneratePom=true -DcreateChecksum=true
I expect the repo to have:
.m2\repository\com\google\gwt\gwt-dev\1.4.60\gwt-dev-1.4.60-windows.jar
but am getting:
.m2\repository\com\google\gwt\gwt-dev\1.4.60\gwt-dev-1.4.60.jar
quick fix is to copy the gwt-dev-1.4.60.jar to gwt-dev-1.4.60-windows.jar and
the dependencies are then resolved.
However its not consistent between two on my machines:
Both machines are using maven 2.0.7 with an identical environment setup (with
regards to java and maven) the only difference being the actual paths.
It's not clear if its some sort of environment setting that makes the
difference, but because of the nature of the beast it should not be making a
difference. A classifier designation should behave the same regardless of the
system setup or the version of maven. The *only* thing that might change it is
repository layout (which I have not set and the default new version should be
used).
Now, this could be some sort of bug in maven and not the plugin (maven not
passing information to the plugin) but I am unable to verify that right now.
> classifier seems to be ignored
> ------------------------------
>
> Key: MINSTALL-42
> URL: http://jira.codehaus.org/browse/MINSTALL-42
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Maven 2.0.7. I'm unsure of the specific plugin version.
> Reporter: Brill Pappin
>
> install-file is failing to take into account the classifier option... this
> used to work (as of last week) but is being ignored when I do the same thing
> again.
> The repo structure its using is incorrect.
> That or possible maven has changed the way that classifier is used.
--
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
