> > unregistering the dependency (WindowsLogger) so the failure to activate
> > > is always going to be a possibility. However I think it's more likely
> > > that you ran into the defect I fixed recently FELIX-4166 where for a
> > > delayed component removing
You found a bug, FELIX-4171 . I've committed a
> > > > fix and am thinking about how to write a test.
> > > >
> > > > In the scenario I thought of, I think your failing component has at
> > > > least 2 dependencies and the WindowsLogger i
nough and you have enough logging turned on you
> > should be able to see the WindowsLogger get deactivated before your failing
> > component is activated.
> >
> > If this is not what is going on please let me know some more details!
> >
> > thanks
> >
u
> found.
>
> If my guesses are accurate enough and you have enough logging turned on you
> should be able to see the WindowsLogger get deactivated before your failing
> component is activated.
>
> If this is not what is going on please let me know some more details!
>
ossibly
> the problem already got fixed.
>
> thanks
> david jencks
>
> On Jul 17, 2013, at 11:39 AM, Adam Purkiss wrote:
>
> > We are noticing an intermittent issue with DependencyManager (build of 1.7
> > snapshot with all changes up to and including May 29). N
We are noticing an intermittent issue with DependencyManager (build of 1.7
snapshot with all changes up to and including May 29). Not sure what is causing
this behaviour. Does anyone have thoughts on what it might be? Are we doing
something wrong or is it a threading issue we are running into?
seen an error here in a long time.
> Also knowing your environment might be interesting…. I only build on a
> macbook pro, java 1.6.0_45-b06-451-11M4406
>
> many thanks
> david jencks
>
>
> On May 28, 2013, at 5:05 PM, Adam Purkiss wrote:
>
> > Ah ok
> &
.
>
> Your DS is not that outdated…. I only committed the problem on may 7 :-)
>
> thanks
> david jencks
>
> On May 28, 2013, at 1:44 PM, Adam Purkiss wrote:
>
> > I have noticed that with the slightly outdated head rev of SCR which I have
> > been using due
I have noticed that with the slightly outdated head rev of SCR which I have
been using due to bug fixes in it that I now get an error logged from felix
that seems to be related to the ConfigurationManager. I have not tried to
update that as I was hoping not to have to get head revs of everything
provide the logs from
> target/failsafe-reports/*.txt which corresponds to the failing tests ?
>
> regards;
> /Pierre
>
> On Thu, May 23, 2013 at 4:17 PM, Adam Purkiss wrote:
>
> > Recently a high priority bug was fixed
> > https://issues.apache.org/jira/browse/FE
Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
thanks
Adam Purkiss
11 matches
Mail list logo
