karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nino martinez wael <nino.martinez.w...@gmail.com>
Subject Re: How to add <repository> elements to aggregated feature repositories?
Date Thu, 03 May 2018 18:18:23 GMT
What about doing it based on pom and what scope the declared dependency
feature types are in?

On Sat, 21 Apr 2018, 23:46 Steinar Bang, <sb@dod.no> wrote:

> >>>>> Jean-Baptiste Onofré <jb@nanthrax.net>:
>
> > That's tricky because users might want different behavior about features
> repositories dependencies.
>
> > As already mentioned, it gives more control to write the features
> repository XML by hand and verify using the plugin.
>
> Yes, but that means maintaining the dependencies in multiple places.
>
> How about adding an attribute that can tell karaf-maven-plugin to
> include it when aggregating features?
>
> Eg. something like this
>  <repository includeinaggregaterepo="true" .../>
>
> Default would be false (ie the current behaviour).
>
> The karaf-maven-plugin would then include it in an aggregate repository
> (stripping this attribute in the process).
>
> Alternatively: if the aggregate has a template feature file with
> <repository> elements, then include those elements in the generated
> aggregate (this was the behaviour I expected to see).
>
> This wouldn't be ideal in that I would have to maintain the URL in two
> places (but I could use a maven property and just maintain the actual
> URL in a single location).
>
>

Mime
View raw message