[jboss-jira] [JBoss JIRA] Updated: (JBBUILD-660) extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy

[Paul Gier (JIRA)]

     [ https://jira.jboss.org/browse/JBBUILD-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated JBBUILD-660:
------------------------------

    Component/s: Artifact Repositories
                     (was: Sonatype)


> extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy 
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBBUILD-660
>                 URL: https://jira.jboss.org/browse/JBBUILD-660
>             Project: JBoss Build System
>          Issue Type: Bug
>          Components: Artifact Repositories
>    Affects Versions: Maven Repository Nexus Rollout
>            Reporter: Ian Springer
>            Assignee: Paul Gier
>            Priority: Critical
>             Fix For: Repository Support 2010
>
>
> I published the following artifact using 'mvn deploy' from a project with type maven-archetype:
> https://repository.jboss.org/nexus/content/repositories/releases/org/rhq/maven/smartgwt-war-archetype/1.0/
> Notice the jarfile's extension got changed from .jar to .maven-archetype. I'm not sure if it was the maven deploy plugin or Nexus that did this. but I suspect it was Nexus.
> It needs to have the extension .jar, because the archetype:generate goal assumes all archetype artifacts will have that extension.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira