felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3381) Support for {maven-test-resources} and {maven-test-sources} placeholders
Date Fri, 07 Jun 2013 15:22:21 GMT

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

Stuart McCulloch updated FELIX-3381:
------------------------------------

    Labels: patch  (was: )
    
> Support for {maven-test-resources} and {maven-test-sources} placeholders
> ------------------------------------------------------------------------
>
>                 Key: FELIX-3381
>                 URL: https://issues.apache.org/jira/browse/FELIX-3381
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven Bundle Plugin
>            Reporter: Tuomas Kiviaho
>            Priority: Minor
>              Labels: patch
>             Fix For: maven-bundle-plugin-2.4.0
>
>         Attachments: FELIX-3381.diff
>
>
> I've found the plugin suitable for producing test bundles although bundle plugin states
that test scope isn't supported.
> Currently I have to manually keep up with the test resources/sources so that my test
fragment bundle wouldn't be considering {maven-resources} and {maven-sources}. This is quite
ok compared to having a proper test-bundle goal but I'd love to see corresponding {maven-test-resources}
and {maven-test-sources} placeholder support which would streamline the configuration. 
> Now I'm getting WARN messages when I tamper with Include-Resource _sourcepath. It is
also quite error prone to manually list multiple resource and source locations. Only classifier
and outputDirectory have to be configured in addition to these instructions and dependency
embedding works also when transitive dependencies are not used (in fact test scope isn't even
transitive)

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

Mime
View raw message