You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/09/19 16:48:09 UTC

[jira] [Resolved] (SM-1490) The ServiceMix Maven archetypes are not being recognized as Maven Archetypes by the Nexus indexer

     [ https://issues.apache.org/jira/browse/SM-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-1490.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: archetypes-2011.01
         Assignee: Jean-Baptiste Onofré  (was: Bruce Snyder)

Nexus and Archiva use the Maven indexer. The latest version of the Maven indexer is looking for a archetype-resources directory in the jar.

> The ServiceMix Maven archetypes are not being recognized as Maven Archetypes by the Nexus indexer 
> --------------------------------------------------------------------------------------------------
>
>                 Key: SM-1490
>                 URL: https://issues.apache.org/jira/browse/SM-1490
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: 3.2.1, 3.2.2, 3.3
>            Reporter: Bruce Snyder
>            Assignee: Jean-Baptiste Onofré
>             Fix For: archetypes-2011.01
>
>
> h3. Problem 
> When the central repo is indexed by Nexus, the [MinimalArtifactInfoIndexCreator|http://svn.sonatype.org/nexus/trunk/nexus-indexer/src/main/java/org/sonatype/nexus/index/creator/MinimalArtifactInfoIndexCreator.java] scans for archetypes by looking for one of the following items: 
> * {{<packaging>maven-archetype</packaging>}} 
> * A groupId that contains the word 'archetype' 
> * An artifactId that contains the word 'archetype' 
> Because the ServiceMix archetypes do not meet any of this criteria, they are not properly indexed and therefore are not listed in the [m2eclipse|http://m2eclipse.codehaus.org/]. 
> h3. Proposed Fixes
> Either one of the following suggestions should fix the problem: 
> # To fix this in the both the 3.2 branch and the trunk, we could change either the groupId or artifactId to contain the word 'archetype'. I propose that the groupId for the archetypes be changed from {{org.apache.servicemix.tooling}} to {{org.apache.servicemix.tooling.archetypes}} or just simple {{org.apache.servicemix.archetypes}}. Either of these changes will be enough to cause the Nexus indexer to properly recognize the archetypes as such. 
> OR
> # Add a {{<packaging>maven-archetype</packaging>}} element to each archetype's POM 

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