[
https://jira.jboss.org/browse/JBBUILD-660?page=com.atlassian.jira.plugin....
]
Paul Gier updated JBBUILD-660:
------------------------------
Fix Version/s: Repository Support 2010
The directory has both a .jar file and a .maven-archetype file. I'm not sure why
Nexus created the .maven-archetype file, but it might have something to do with the
packaging in the POM. According to the archetype plugin site, the packaging should be
"maven-archetype" instead of "jar".
http://maven.apache.org/archetype/maven-archetype-plugin/faq.html
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: Sonatype
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/...
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira