sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SLING-8008) Create dedicated parent for bundle projects
Date Wed, 24 Oct 2018 10:50:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662089#comment-16662089
] 

Konrad Windszus edited comment on SLING-8008 at 10/24/18 10:49 AM:
-------------------------------------------------------------------

PR created in [https://github.com/apache/sling-parent/pull/3|https://github.com/apache/sling-parent/pull/3.] Please
check and give feedback. I will not merge for at least one week to give everyone enough time
to check this.


was (Author: kwin):
PR created in [https://github.com/apache/sling-parent/pull/3.] Please check and give feedback.
I will not merge for at least one week to give everyone enough time to check this.

> 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
>            Assignee: Konrad Windszus
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As followup to the Sling Hackathon in Berlin in September (compare with [https://www.mail-archive.com/dev@sling.apache.org/msg79953.html
|https://www.mail-archive.com/dev@sling.apache.org/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)

Mime
View raw message