You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2008/08/05 08:25:52 UTC

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

    [ https://issues.apache.org/activemq/browse/SM-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44730#action_44730 ] 

Bruce Snyder commented on SM-1490:
----------------------------------

Well it looks like Maven doesn't even support a packaging type of maven-archetype, so I'm not sure why the Nexus indexer is even looking for that packaging type. So it seems that the only solution may be changing the groupId or the artifactId. 

> The ServiceMix Maven archetypes are not being recognized as Maven Archetypes by the Nexus indexer 
> --------------------------------------------------------------------------------------------------
>
>                 Key: SM-1490
>                 URL: https://issues.apache.org/activemq/browse/SM-1490
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: archetypes
>    Affects Versions: 3.2.1, 3.2.2, 3.3
>            Reporter: Bruce Snyder
>            Assignee: Bruce Snyder
>
> 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, 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.
-
You can reply to this email to add a comment to the issue online.