[
https://issues.apache.org/jira/browse/FELIX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570043#action_12570043
]
Stefano Lenzi commented on FELIX-493:
-------------------------------------
I don't see a simple solution for this. I would like to propose some idea:
a) attached artifacts must bundle:installed/bundle:deployed manually
b) add a list of classifier to maven-configuration-plugin in order to identify
the one that we want to bundle:install and bundle:deploy. A list it is better
than a regex pattern because it could be require to have custom OBR metatada
for each classified artifact
c) add an ad-hoc behavior for well-know classifier like: sources, javadoc. So
that URL to those artifact could be liked as sourcesURL and javadocURL metadata
of the main artifact. (the best would be to change the maven-jar-plugin for
accomplish it without an ad-hoc setup)
WDYT?
> maven-bundle-plugin bundle:install goal install too many artifact
> -----------------------------------------------------------------
>
> Key: FELIX-493
> URL: https://issues.apache.org/jira/browse/FELIX-493
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Environment: maven-bundle-plugin:1.3.0-SNAPSHOT
> Reporter: Stefano Lenzi
>
> After the introduction of classifier in the maven-bundle-plugin and after the
> adaptation of the bundle:install goal in order to support classifier if you
> run
> mvn source:jar install
> the maven-bundle-plugin will install either the <bunlde>.jar and
> <bundle>-sources.jar in the local OBR repository.
> The repository.xml file seems to be readable by the plugin after the
> installtion of the duplicated artifact, but I think it won't be usable from
> OBR client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
