[
https://issues.apache.org/jira/browse/STANBOL-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127604#comment-13127604
]
Fabian Christ commented on STANBOL-344:
---------------------------------------
I have similar problems when executing the integration-tests on their own. In
this case Maven tries to download files with extension *.partialbundlelist
because by convention file names of artifacts have the ending of their type. If
you do a full build the artifacts are resolved correctly, because the sling
plugin does this right, I think.
For my system with Maven 2.2.1 it helps to
1) set the scope for all partialbundles in the full launchers POM to
<scope>provided</scope> and
2) set the scope of the full launcher in the integration-test POM to
<scope>provided</scope>
Suat, can you check if this solves the problem also in Maven 3.0.3?
> Create partial bundle lists of components so that they can be used from
> launchers
> ---------------------------------------------------------------------------------
>
> Key: STANBOL-344
> URL: https://issues.apache.org/jira/browse/STANBOL-344
> Project: Stanbol
> Issue Type: Improvement
> Reporter: Suat Gonul
> Priority: Minor
> Labels: launcher, partialbundlelist
> Attachments: integration-tests.error
>
>
> Each component should export its bundle list to be imported as a single
> dependency from launchers.
--
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
