Well, the 1.7-SNAPSHOT in the apache nexus snapshot repo is up to date. I run mvn clean install in scr with no problems, using maven 3.0.4. What problems are you seeing?
thanks david jencks On Oct 29, 2013, at 10:54 AM, Dave Smith <[email protected]> wrote: > I tried following the instructions but It seems the scr is not built in and > when I try and run mvn in the scr dir that does not work either. > > I am following ... > > http://felix.apache.org/site/building-felix.html > > instructuctions > > Dave Smith > Candata Ltd. > 416-493-9020x2413 > Direct: 416-855-2413 > > > On Tue, Oct 29, 2013 at 11:41 AM, Dave Smith <[email protected]> wrote: > >> Latest 1.6.2. I will grab the snapshot and report back... >> >> Dave Smith >> Candata Ltd. >> 416-493-9020x2413 >> Direct: 416-855-2413 >> >> >> On Tue, Oct 29, 2013 at 11:38 AM, David Jencks <[email protected]>wrote: >> >>> Not telling us the exact version of the code you are using makes it >>> pretty much impossible to think about investigating this. >>> >>> Please see if this is a problem with the current trunk code which you can >>> build yourself or use the 1.7-SNAPSHOT on the apache snapshot repo. >>> >>> I'm working on a release and at this point we're finding and fixing bugs. >>> When we've stopped finding bugs I'll release. >>> >>> thanks >>> david jencks >>> >>> On Oct 29, 2013, at 8:15 AM, Dave Smith <[email protected]> wrote: >>> >>>> I posted a bug a few weeks back and the thought was a new version is >>> coming >>>> soon. Since it was more of an annoyance I decided to wait. I am now >>> having >>>> an intermittent problem with a service not getting activated. Here is a >>>> snippet from the log >>>> >>>> 2013-10-29 10:49:27 4 >>>> [com.candata.core.server.impl.ServiceConfigurationImpl] >>>> getParameterClass: Found class >>>> com.candata.core.server.services.RunAsService >>>> com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 4 >>>> [com.candata.core.server.impl.ServiceConfigurationImpl] doFindMethod: >>>> No method taking ServiceReference found, checking method taking >>>> com.candata.core.server.services.RunAsService >>>> com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 4 >>>> [com.candata.core.server.impl.ServiceConfigurationImpl] Found bind >>>> method: protected void >>>> >>> com.candata.core.server.impl.ServiceConfigurationImpl.setRunAsService(com.candata.core.server.services.RunAsService) >>>> com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 4 [com.candata.core.server.impl.ServiceRunnerImpl] >>>> dependency map already present, do not collect dependencies >>>> com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 4 [com.candata.core.server.impl.ServiceRunnerImpl] >>>> getService did not win collecting dependencies, try creating object >>>> anyway. com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 3 FrameworkEvent WARNING >>>> com.candata.core.server_1.0.0 [141] null null >>>> 2013-10-29 10:49:27 2 >>>> [com.candata.core.server.impl.ServiceConfigurationImpl] Could not get >>>> service from ref {com.candata.core.server.services.ServiceRunner, >>>> com.candata.core.server.services.RunAsService}={component.name >>> =com.candata.core.server.impl.ServiceRunnerImpl, >>>> component.id=233, service.id=91} com.candata.core.server_1.0.0 [141] >>> null null >>>> >>>> If -> getService did not win collecting dependencies, try creating >>> object >>>> anyway >>>> >>>> then the service never gets activated , if it wins then it does. I >>>> can see by the logs that the service is registered with OSGI farther >>>> up >>>> >>>> >>>> 2013-10-29 10:49:27 3 ServiceEvent REGISTERED >>>> com.candata.core.server_1.0.0 [141] >>>> {com.candata.core.server.services.ServiceRunner, >>>> com.candata.core.server.services.RunAsService}={component.name >>> =com.candata.core.server.impl.ServiceRunnerImpl, >>>> component.id=233, service.id=91} null >>>> >>>> Is the next release soon? Or has this code not changed and could be >>>> considered a bug >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
