[
https://jira.jboss.org/browse/JBBUILD-660?page=com.atlassian.jira.plugin....
]
Ian Springer commented on JBBUILD-660:
--------------------------------------
The jar file is there because I eventually ended up changing the packaging of my
archetype's pom from maven-archetype to jar to get things working. It looks as if both
the install plugin and the deploy plugin publish the artifact with the extension
.maven-archetype if the packaging to maven-archetype. The problem with this is that the
archetype:generate goal seems to assume the artifact has a .jar extension. Using an
archetype catalog file might be a workaround, if it is able to tell the archetype
plugin's generate goal the correct extension to look for. In any case, this looks like
a Maven issue and not a Nexus one.
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