[
https://issues.apache.org/jira/browse/SLING-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-8008:
-----------------------------------
Description:
As followup to the Sling Hackathon in Berlin in September (compare with
[https://www.mail-archive.com/[email protected]/msg79953.html
|https://www.mail-archive.com/[email protected]/msg79953.html).]there is the
proposal to split up the current parent pom into two pieces: one for
JARs/general aspect, another one for bundles (covering only those aspects).
The reasons for this switch are:
- we would like to switch completely to bnd-maven-plugin, but without the need
for a separate bnd file
- we currently have only one parent pom for bundle modules and non-bundle
modules, making it difficult to configure the bnd-maven-plugin globally so it
gets up picked only for bundles, not for simple jar files.
- using maven profiles would be an option, but there is no nice way to trigger
the profile without ugly hacks like having an empty bnd file present.
- https://issues.apache.org/jira/browse/MJAR-193 would be another solution
(haven the bnd plugin handing over the manifest extensions to the maven jar
plugin), but this feature is not available yet
The proposed solutions looks like this
- create an additional "sling-bundle-parent" inheriting from the existing
"sling-parent"
- all bundle-related stuff goes there and will be removed from "sling-parent"
- old maven-bundle-plugin and bnd-maven-plugin should be removed from
sling-parent
- maven-bundle-plugin should be banned from sling-bundle-parent
- one repo for both, always released together
- start with next version 36
- make a wiki page with migration steps
- bundle modules will use "sling-bundle-parent", jar modules "sling-parent"
was:
As followup to the Sling Hackathon in Berlin in September (compare with
[https://www.mail-archive.com/[email protected]/msg79953.html
|https://www.mail-archive.com/[email protected]/msg79953.html).]there is the
proposal to split up the current parent pom into two pieces: one for
JARs/general aspect, another one for bundles (covering only those aspects).
The reasons for this switch are:
- we would like to switch completely to bnd-maven-plugin, but without the need
for a separate bnd file
- we currently have only one parent pom for bundle modules and non-bundle
modules, making it difficult to configure the bnd-maven-plugin globally so it
gets up picked only for bundles, not for simple jar files.
- using maven profiles would be an option, but there is no nice way to trigger
the profile without ugly hacks like having an empty bnd file present.
- https://issues.apache.org/jira/browse/MJAR-193 would be another solution
(haven the bnd plugin handing over the manifest extensions to the maven jar
plugin), but this feature is not available yet
The proposed solutions looks like this
- create an additional "sling-bundle-parent" inheriting from the existing
"sling-parent"
- all bundle-related stuff goes there and will be removed from "sling-parent"
- old maven-bundle-plugin and bnd-maven-plugin should be removed from
sling-parent
- maven-bundle-plugin should be banned from sling-bundle-parent
- one repo for both, always released together
- start with next version 36
- make a wiki page with migration steps
- bundle modules will use "sling-bundle-parent", jar modules "sling-parent"
> Create dedicated parent for bundle projects
> -------------------------------------------
>
> Key: SLING-8008
> URL: https://issues.apache.org/jira/browse/SLING-8008
> Project: Sling
> Issue Type: Improvement
> Components: General
> Affects Versions: Parent 34
> Reporter: Konrad Windszus
> Priority: Major
>
> As followup to the Sling Hackathon in Berlin in September (compare with
> [https://www.mail-archive.com/[email protected]/msg79953.html
> |https://www.mail-archive.com/[email protected]/msg79953.html).]there is
> the proposal to split up the current parent pom into two pieces: one for
> JARs/general aspect, another one for bundles (covering only those aspects).
>
> The reasons for this switch are:
> - we would like to switch completely to bnd-maven-plugin, but without the
> need for a separate bnd file
> - we currently have only one parent pom for bundle modules and non-bundle
> modules, making it difficult to configure the bnd-maven-plugin globally so it
> gets up picked only for bundles, not for simple jar files.
> - using maven profiles would be an option, but there is no nice way to
> trigger the profile without ugly hacks like having an empty bnd file present.
> - https://issues.apache.org/jira/browse/MJAR-193 would be another solution
> (haven the bnd plugin handing over the manifest extensions to the maven jar
> plugin), but this feature is not available yet
>
> The proposed solutions looks like this
> - create an additional "sling-bundle-parent" inheriting from the existing
> "sling-parent"
> - all bundle-related stuff goes there and will be removed from "sling-parent"
> - old maven-bundle-plugin and bnd-maven-plugin should be removed from
> sling-parent
> - maven-bundle-plugin should be banned from sling-bundle-parent
> - one repo for both, always released together
> - start with next version 36
> - make a wiki page with migration steps
> - bundle modules will use "sling-bundle-parent", jar modules "sling-parent"
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
