[
https://issues.apache.org/jira/browse/FELIX-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032215#comment-14032215
]
Felix Meschberger commented on FELIX-4530:
------------------------------------------
[~cziegeler] It's about a default behaviour of the bundle plugin and how the
SCR plugin interferes.
I am absolutely in favor of the SCR plugin adding the generated descriptors to
the project resources. But this is just the manifests not the complete folder
where they reside in.
If the only way to add the desciptors is to add the complete descriptor target
folder, then using target/classes is not a good idea because then you loose all
the fine tuning that the bundle plugin and bnd offer.
And maybe, it is the Sling tooling which should be more intelligent ?
> [SCR Plugin] Revisit setting the default output to target/classes
> -----------------------------------------------------------------
>
> Key: FELIX-4530
> URL: https://issues.apache.org/jira/browse/FELIX-4530
> Project: Felix
> Issue Type: Bug
> Components: SCR Tooling
> Affects Versions: maven-scr-plugin 1.17.0
> Reporter: Felix Meschberger
> Priority: Critical
> Fix For: maven-scr-plugin 1.17.2
>
>
> With FELIX-4241 the default value for the descriptor output files has been
> set to {{target/classes}}. Unfortunately this causes {{target/classes}} to be
> added to the Maven Input Resources resulting in all contents of
> {{target/classes}} to be included in the final bundle regardless of whether
> this is actually desired or not.
> Regardless of tooling integration noted in FELIX-4241, it is against the
> spirit of the bundle plugin to blindly include everything in
> {{target/classes}} in the bundle. So the resolution for FELIX-4241 must be
> revisited.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
