Just had a second thought on this :) I think we can forget about
supporting pom inheritance for bundle lists. We have the partial
bundle lists for this. This leaves us with profiles which should be
easy to support.
Regards
Carsten
2011/11/5 Carsten Ziegeler :
> 2011/11/5 Jukka Zitting :
>> Hi,
>>
2011/11/5 Jukka Zitting :
> Hi,
>
> On Sun, Nov 6, 2011 at 12:11 AM, Carsten Ziegeler
> wrote:
>> Yes, but the tooling point only applies partially - there is no
>> tooling for the various plugin configurations including the new
>> configuration for this plugin. So there is no tooling support for
Hi,
On Sun, Nov 6, 2011 at 12:11 AM, Carsten Ziegeler wrote:
> Yes, but the tooling point only applies partially - there is no
> tooling for the various plugin configurations including the new
> configuration for this plugin. So there is no tooling support for that
> regardless which way we go.
Yes, but the tooling point only applies partially - there is no
tooling for the various plugin configurations including the new
configuration for this plugin. So there is no tooling support for that
regardless which way we go.
I agree for inheritance and profiles...however I think we could go
with
Hi,
On Sat, Nov 5, 2011 at 3:03 AM, Carsten Ziegeler wrote:
> [...] just read the pom file ourselves to parse the annotations [...]
What about POM inheritance and profiles? Or stuff like polyglot POMs?
Sticking with standard Maven dependencies and the normal plugin
configuration mechanism is IM
On 04.11.11 22:03, "Justin Edelson" wrote:
>On Fri, Nov 4, 2011 at 6:13 AM, Felix Meschberger
>wrote:
>>So I am contemplating the following change to the
>>SlingAuthenticator.handleSecurity method: If the method would return
>>with true (indicating regular request processing) but the request is
On Sat, Nov 5, 2011 at 3:03 AM, Carsten Ziegeler wrote:
> Hi,
>
> I really appreciate the work spent in this stuff - but how many
> different ways do we now have to configure the bundle list? And none
> of them is really satisfying I think. Still the best approach we have
> right now from a config
