You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2012/11/15 08:10:13 UTC

[jira] (MINDEXER-41) Allow to index several artifacts with no classifier

    [ https://jira.codehaus.org/browse/MINDEXER-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313575#comment-313575 ] 

Milos Kleint commented on MINDEXER-41:
--------------------------------------

also true for netbeans module development where both .jar and .nbm files are created.
jglick's solution to the problem for our netbeans.org repository index was a custom cmd line indexer. https://bitbucket.org/jglick/nexus-for-netbeans/src/65478662cdd2/src/main/java/Main.java
                
> Allow to index several artifacts with no classifier
> ---------------------------------------------------
>
>                 Key: MINDEXER-41
>                 URL: https://jira.codehaus.org/browse/MINDEXER-41
>             Project: Maven Indexer
>          Issue Type: Improvement
>            Reporter: Julien HENRY
>
> See details in this thread: http://maven.40175.n5.nabble.com/Search-with-several-artifacts-same-GAV-different-type-extension-td4902408.html
> The key used by indexer is GAVC (GAV + classifier where classifier can be null).
> With current design the indexer will only index one artifact with no classifier (= main artifact) + optionally additional secondary artifacts with classifier.
> This is an issue for custom packaging types that publish several artifacts with different extensions but no classifier.
> For example:
> {code}
> groupId
>    /artifactId
>       /version
>          /artifactId-version.pom
>          /artifactId-version.jar
>          /artifactId-version.tld
>          /artifactId-version.config
> {code}
> It would be good to include the extension in the index key => GAVCE. This way a search will return jar, tld and config artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira