Hi,
scanning our project reveals the following component factories:
jcr/jackrabbit-server : SlingServerRepository
jcr/jackrabbit-client : SlingClientRepository
jcr/classloader : RepositoryClassLoaderProviderImpl
engine : RequestLoggerService
I created SLING-502 to change them to "manual" descriptors and SLING-503
to revert to "automatic" descriptors after any maven-scr-plugin release.
Regards
Felix
Am Dienstag, den 03.06.2008, 12:17 +0200 schrieb Felix Meschberger:
> Hi,
>
> Am Dienstag, den 03.06.2008, 12:07 +0200 schrieb Carsten Ziegeler:
> > Felix Meschberger wrote:
> > > It _will_ run with the scr 1.0.0 snapshot, unless the immediate flag is
> > > set, which is the real bug behind this. If the immediate flag is not
> > > explicitly set to any value, both versions of SCR -- 1.0.0 and
> > > 1.0.1-SNAPSHOT -- assume their own default value valid in their context.
> > > And hence the bundle works.
> > >
> > Yes, that's my understanding as well :)
> >
> > > The real "culprit", if you wish, is the maven-scr-plugin, which always
> > > sets this flag to an explict "true" value, thus prevent the bundle to
> > > work.
> > >
> > > We might need a maven-scr-plugin release ??
> > Yes, but we don't want to wait for that I guess/hope :) therefore why
> > not hand writing the scr config without the explicit flag just for the
> > release?
> > The alternative would be to release the scr plugin (and we could then
> > also release the scr to get the latest version), but this would require
> > us to delay the release until next week.
>
> After considering this, I agree, that handwriting is probably the best
> for the moment being.
>
> Regards
> Felix
>
> >
> > Carsten
