[jira] [Commented] (STANBOL-406) Maven artifacts with bundlelist classifier break the build when using maven 3

["Rupert Westenthaler (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STANBOL-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163072#comment-13163072 ] 

Rupert Westenthaler commented on STANBOL-406:
---------------------------------------------

FYI: declaring such dependencies as <scope>provided</scope> solves (workarounds) this problem.

e.g. 

    <!-- Stanbol Enhancer Bundle List -->
    <dependency>
      <groupId>org.apache.stanbol</groupId>
      <artifactId>org.apache.stanbol.enhancer.bundlelist</artifactId>
      <type>partialbundlelist</type>
      <scope>provided</scope>
    </dependency>

I added this to all the "partialbundlelist" dependencies to get the build working with maven 3

                
> Maven artifacts with bundlelist classifier break the build when using maven 3
> -----------------------------------------------------------------------------
>
>                 Key: STANBOL-406
>                 URL: https://issues.apache.org/jira/browse/STANBOL-406
>             Project: Stanbol
>          Issue Type: Bug
>            Reporter: Olivier Grisel
>
> Apparently maven 3 does not tolerate non standard artifact classifiers. Would it be possible to switch back to regular jars?
> On a related note, it would be great if we could package src/resources/bundles/list.xml files into jars available in the classpath of other bundles as a test dependency so as to be able to use pax-exam to build a lightweight integration test harness that is able to check the consistency of those lists in terms of runtime deployment in an OSGi container.

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