You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (Assigned) (JIRA)" <ji...@apache.org> on 2012/03/06 00:07:57 UTC

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

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

Rupert Westenthaler reassigned STANBOL-406:
-------------------------------------------

    Assignee: Suat Gonul

Hi, I think this is resolved in the meantime.
                
> 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
>            Assignee: Suat Gonul
>
> 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