[jira] Updated: (FELIX-2598) Hang in Felix: thread owing a bundle lock waits for ever to lock it again
[ https://issues.apache.org/jira/browse/FELIX-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahoo updated FELIX-2598: - Attachment: hang.txt jstack output > Hang in Felix: thread owing a bundle lock waits for ever to lock it again > - > > Key: FELIX-2598 > URL: https://issues.apache.org/jira/browse/FELIX-2598 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.2 >Reporter: Sahoo >Assignee: Richard S. Hall > Fix For: framework-3.2.0 > > Attachments: hang.txt > > > In GlassFish, I detected a hang. PFA jstack output. The scenario happens like > this: > a) I updated a bundle using telnet console. This thread is holding the bundle > lock. > b) Upon receiving the UPDATED event, one of our extenders bundle enhances the > bundle and calls PackageAdmin.refreshPackages(bundle). > c) PackageAdmin thread holds the global lock and tries to hold the bundle > lock, which is currently held by telnetconsole thread. > d) telnetconsole thread is waiting indefinitely to obtain the bundle lock. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2598) Hang in Felix: thread owing a bundle lock waits for ever to lock it again
Hang in Felix: thread owing a bundle lock waits for ever to lock it again - Key: FELIX-2598 URL: https://issues.apache.org/jira/browse/FELIX-2598 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-3.0.2 Reporter: Sahoo Assignee: Richard S. Hall Fix For: framework-3.2.0 In GlassFish, I detected a hang. PFA jstack output. The scenario happens like this: a) I updated a bundle using telnet console. This thread is holding the bundle lock. b) Upon receiving the UPDATED event, one of our extenders bundle enhances the bundle and calls PackageAdmin.refreshPackages(bundle). c) PackageAdmin thread holds the global lock and tries to hold the bundle lock, which is currently held by telnetconsole thread. d) telnetconsole thread is waiting indefinitely to obtain the bundle lock. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2597) Deadlock during delivery of resolved event
Deadlock during delivery of resolved event -- Key: FELIX-2597 URL: https://issues.apache.org/jira/browse/FELIX-2597 Project: Felix Issue Type: Improvement Components: Framework Affects Versions: framework-3.0.2 Reporter: Richard S. Hall Assignee: Richard S. Hall Priority: Minor Fix For: framework-3.2.0 When the framework resolves a bundle, it fires the RESOLVED event to synchronous bundle listeners while holding the global lock. This caused a deadlock in a specific scenario where two threads T1 and T2 were racing to resolve bundled B1 and B2, respectively. T1 was resolving a dynamic import for B2 which started from a loadClassInternal() call from the JVM which locks B2's class loader. T1 lost the race for the global lock and had to wait for T2 to do its resolve of B2. T2 ended up firing a RESOLVED event to B1. In B1's callback method, a loadClassInternal() was triggered by T2 when it accessed some static, which caused it to deadlock when the JRE tried to lock the B1's class loader on T2, which was already held by T1. This issue is actually related to the JVM being too aggressively in its locking of class loaders: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4670071 Regardless, we might be able to loosen this up a little bit by not holding the global lock at all. This might slightly violate the definition of synchronous bundle listener, since the state could change, but at least it will still be delivered synchronously on the instigating thread. More information here: https://glassfish.dev.java.net/issues/show_bug.cgi?id=13329 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[REPORT] Apache Felix
*Community* * Added Sanjeeb Sahoo as a committer. *Software* * Recent subproject releases: o Bundle Repository (1.6.4) o Configuration Admin (1.2.8) o Event Admin (1.2.4) o File Install (3.0.2) - Maintenance release for auto-bundle deployer. o Framework (3.0.1, 3.0.2) - Core OSGi framework maintenance releases. o Framework Security (1.4.0) - Framework security provider implementation maintenance release. o iPOJO Arch for Gogo (1.0.0) - Initial release of Gogo shell command for inspecting iPOJO components. o iPOJO Core, Annotations and Manipulator (1.6.4) - Maintenance release for OSGi-based component framework. o Main (3.0.1, 3.0.2) - Framework launcher maintenance releases. o Remote Shell (1.1.0) - Minor feature improvement release to simple telnet service. o SCR (Declarative Services) (1.6.0) o Web Console (3.1.0, 3.1.2) o Web Console Memory Usage Plugin (1.0.2) *Licensing and other issues* * Karaf subproject promoted to TLP. * Need to have discussion on how to handle provisional OSGi APIs in our releases. It is not clear if we should include provisional OSGi API since it is not officially released by the OSGi Alliance and is therefore subject to change and/or not always officially sanctioned (i.e., made publicly available by the OSGi Alliance). At a minimum, we need to define an approach to informing users if provisional API is included that it is not [yet] official OSGi API.
[jira] Closed: (FELIX-2567) Karaf documentation still appears on felix site
[ https://issues.apache.org/jira/browse/FELIX-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Donald closed FELIX-2567. --- Resolution: Fixed This has since been addressed > Karaf documentation still appears on felix site > --- > > Key: FELIX-2567 > URL: https://issues.apache.org/jira/browse/FELIX-2567 > Project: Felix > Issue Type: Task > Components: Karaf >Reporter: Peter Donald >Priority: Minor > > Karaf documentation still appears on the felix site. This is confusing now > that karaf has moved to a separate TLP. This should be removed ... it seems > to be from a wiki but I couldn't figure out how to perform the edits myself. > While at it you can probably remove the old site cruft via > svn rm http://svn.apache.org/repos/asf/felix/site -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2566) Remove reference to Karaf from build scripts
[ https://issues.apache.org/jira/browse/FELIX-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Donald closed FELIX-2566. --- Resolution: Fixed Looks like this has since been fixed > Remove reference to Karaf from build scripts > > > Key: FELIX-2566 > URL: https://issues.apache.org/jira/browse/FELIX-2566 > Project: Felix > Issue Type: Task > Components: Karaf >Reporter: Peter Donald > Attachments: RemoveKarafReferences.diff > > > Karaf is still referenced in some of the build scripts. This patch just > removes those references. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2554) Improve unit test setup to allow for easier use of integration tests from within IDEs
[ https://issues.apache.org/jira/browse/FELIX-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2554. Closing issues after Configuration Admin 1.2.8 release > Improve unit test setup to allow for easier use of integration tests from > within IDEs > - > > Key: FELIX-2554 > URL: https://issues.apache.org/jira/browse/FELIX-2554 > Project: Felix > Issue Type: Improvement > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > Currently running unit tests from within IDEs is somewhat complicated. This > can be simplified by adding a build profile which creates a bundle file which > can then be picked up by the integration tests to launch PAX Exam. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2557) ConfigurationEvent delivery not building the listener list correctly
[ https://issues.apache.org/jira/browse/FELIX-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2557. Closing issues after Configuration Admin 1.2.8 release > ConfigurationEvent delivery not building the listener list correctly > > > Key: FELIX-2557 > URL: https://issues.apache.org/jira/browse/FELIX-2557 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > According to the Configuration Admin Specification 1.3, Section 104.8 > Configuration Events, the configuration events must be delivered "the same as > described in Delivering Events on > page 116 of the Core specification." > This means, that : > - the list of interested ConfigurationListener services must be built at > event creation time > - at event delivery time, all listeners must be called if their providing > bundle is still active > It is important to note, that listeners not registered at event creation time > but registered at event delivery time must _not_ be called. On the other hand > listeners registered at event creation time but unregistered at event > delivery time must still be called (unless their providing bundle has been > stopped). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1727) Properties with leading dots not allowed
[ https://issues.apache.org/jira/browse/FELIX-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1727. Closing issues after Configuration Admin 1.2.8 release > Properties with leading dots not allowed > > > Key: FELIX-1727 > URL: https://issues.apache.org/jira/browse/FELIX-1727 > Project: Felix > Issue Type: Bug > Components: Configuration Admin, Specification compliance >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > Even though the OSGi R4.2 Configuration Admin Spec (v 1.3 of the spec) now > explicitly allows properties with leading dots, the current implementation > prevents them from being used. > Specification states: > The format of a property name should be: >property-name ::= public | private >public ::= symbolic-name // See 1.3.2 >private ::= '.' symbolic-name -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1543) Remove org.osgi.service.cm from configadmin project as soon as R4.2 compendium library is available from the Maven Repository
[ https://issues.apache.org/jira/browse/FELIX-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1543. Closing issues after Configuration Admin 1.2.8 release > Remove org.osgi.service.cm from configadmin project as soon as R4.2 > compendium library is available from the Maven Repository > - > > Key: FELIX-1543 > URL: https://issues.apache.org/jira/browse/FELIX-1543 > Project: Felix > Issue Type: Task > Components: Configuration Admin >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > To include the official org.osgi.service.cm API classes in the configadmin > bundle the sources have been added to the configadmin project in SVN in Rev > 809193 for FELIX-1541. > As soon as the official OSGi Compendium R4.2 library is available from the > Central Maven Repository this source should be removed again and the offical > one be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2184) PID with space causes ERROR log, but otherwise works
[ https://issues.apache.org/jira/browse/FELIX-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2184. Closing issues after Configuration Admin 1.2.8 release > PID with space causes ERROR log, but otherwise works > > > Key: FELIX-2184 > URL: https://issues.apache.org/jira/browse/FELIX-2184 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 > Environment: Linux bono 2.6.32-16-generic #24-Ubuntu SMP Sat Mar 6 > 12:33:21 UTC 2010 i686 GNU/Linux > java version "1.6.0_18" > Java(TM) SE Runtime Environment (build 1.6.0_18-b07) > Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing) >Reporter: Martin Zdila >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > Attachments: org_apache_felix_cm_impl_DynamicBindings.config > > > Reading the specification I am not sure what characters are really allowed > for PIDs. We are using PIDs with spaces. All works fine, just the exception > is logged upon startup. I will attach the > org_apache_felix_cm_impl_DynamicBindings.config file that causes the parsing > error. > *ERROR* Failure setting up dynamic configuration bindings > java.io.IOException: Unexpected token 78; expected: 61 (line=2, pos=10) > at > org.apache.felix.cm.file.ConfigurationHandler.readFailure(ConfigurationHandler.java:652) > at > org.apache.felix.cm.file.ConfigurationHandler.readInternal(ConfigurationHandler.java:273) > at > org.apache.felix.cm.file.ConfigurationHandler.read(ConfigurationHandler.java:236) > at > org.apache.felix.cm.file.FilePersistenceManager._load(FilePersistenceManager.java:542) > at > org.apache.felix.cm.file.FilePersistenceManager.load(FilePersistenceManager.java:487) > at > org.apache.felix.cm.impl.DynamicBindings.(DynamicBindings.java:51) > at > org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:211) > at > org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1756) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1678) > at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1124) > at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1907) Improve documentation on PersistenceManager API
[ https://issues.apache.org/jira/browse/FELIX-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1907. Closing issues after Configuration Admin 1.2.8 release > Improve documentation on PersistenceManager API > --- > > Key: FELIX-1907 > URL: https://issues.apache.org/jira/browse/FELIX-1907 > Project: Felix > Issue Type: Improvement > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > The PersistenceManager API must be extended to be able to more stably > implement the interface: > * It must be clarified that the getters and putters may be called while > the Enumeration returned by getDictionaries is being used >(Prevent ConcurrentModificationException) > * It must be clarified that the Dictionary objects returned by the > PersistenceManager are modified by Configuration Admin >--> alternatively Configuration Admin should be modified to treat > the returned Dictionary as read-only. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2559) Adapt Configuration Admin LICENSE and NOTICE files
[ https://issues.apache.org/jira/browse/FELIX-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2559. Closing issues after Configuration Admin 1.2.8 release > Adapt Configuration Admin LICENSE and NOTICE files > -- > > Key: FELIX-2559 > URL: https://issues.apache.org/jira/browse/FELIX-2559 > Project: Felix > Issue Type: Sub-task > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > Rename the existing NOTICE file to DEPENDENCIES and add a new ASF compliant > NOTICE file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2552) Add caching PersistenceManager proxy
[ https://issues.apache.org/jira/browse/FELIX-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2552. Closing issues after Configuration Admin 1.2.8 release > Add caching PersistenceManager proxy > > > Key: FELIX-2552 > URL: https://issues.apache.org/jira/browse/FELIX-2552 > Project: Felix > Issue Type: Improvement > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > > Each call to the ConfigurationAdmin.listConfigurations method causes a call > to the PersistenceManager.getDictionaries() method. The current file-based > implementation of this interface scans the configuration location and loads > configuration files each time this method is called. Depending on the number > of stored configurations, this may sum up to a considerable amount of time, > In an inhouse implementation using Declarative Services (Apache Felix SCR > 1.6.0) and Configuration Admin the use of > ConfigurationAdmin.listConfigurations by the Declarative Services > implementation increases system startup time considerably. With a simple > caching layer ontop of the file-based PersistenceManager service we were able > to cut down ca. 10s of a total system startup time of roughly 25s. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1545) Configurations may still be delivered more than once (or not at all)
[ https://issues.apache.org/jira/browse/FELIX-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-1545. Closing issues after Configuration Admin 1.2.8 release > Configurations may still be delivered more than once (or not at all) > > > Key: FELIX-1545 > URL: https://issues.apache.org/jira/browse/FELIX-1545 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > Attachments: cm-stress-test.tgz > > > Even after "fixing" FELIX-1146 and FELIX-1542 configurations may be delivered > more than once. Under lab conditions it can even be observed, that > configuration is not delivered at all. > After digging into this issue a bit further (and writing test cases), it > looks like we have three issues: > (1) The granularity of System.currentTimeMillis() to feed the last > modification time and last update time fields is to coarse causing false > positives when testing whether configuration should be supplied or not > (2) In contrast to service update due to Configuration.update(Dictionary), > the updates cause by ManagedService[Factory] service registration do not > observe the last update time field and thus may cause duplicate delivery > T1: update configuration, schedule update task > T2: register ManagedService, schedule update task > T3: run update task from T1 --> ManagedService is registered and updated > T3: run update task from T1 --> ManagedService is updated because last > update time flag is ignored > This last update call should not take place and must be guarded > (3) After a service update the ManagedService update tasks (handling update > after ManagedService registration) always sets the last update time flag, > regardless of whether configuration properties exist or not. > T1: create (empty) configuration > T2: register ManagedService, schedule update task > T1: update configuration, schedule update task > T3: runs update task from T2, updates ManagedService with null (no > proeprties) and updates last update time > (last update time is now higher than last modification time even > though no properties have been supplied) > T3: runs update task from T1, but does *not* update ManagedService > because last update > last modification > Please note, that the third issue is actually much worse since it prevents > the ManagedService from getting configuration at all ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1984) Components starts disabled
[
https://issues.apache.org/jira/browse/FELIX-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-1984.
Closing issues after Configuration Admin 1.2.8 release
> Components starts disabled
> --
>
> Key: FELIX-1984
> URL: https://issues.apache.org/jira/browse/FELIX-1984
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
>Affects Versions: configadmin-1.2.4
> Environment: felix-2.0.2
>Reporter: Artur Opala
>Assignee: Felix Meschberger
> Fix For: configadmin-1.2.8
>
> Attachments: configuration-status-20100113-1209+0100.zip
>
>
> From SCR version 1.2.0 all components starts with state 'disabled', SCR 1.0.8
> worked fine. Configuration dump attached as zip file.
> {code}
> 0=[pl.eurobank.osgi.springframework.web.SpringServletContextListener]
> Bundlepl.eurobank.osgi.springframework-bundle (11)
> State=disabled
> DefaultState=enabled
> Activation=delayed
> ServiceType=service
> Services=javax.servlet.ServletContextListener
> Properties=
> component.id=0
> component.name=pl.eurobank.osgi.springframework.web.SpringServletContextListener
> service.pid=pl.eurobank.osgi.springframework.web.SpringServletContextListener
> 1=[pl.eurobank.osgi.launcher.bundle.internal.LauncherSupportActivator]
> Bundlepl.eurobank.osgi.launcher-bundle (18)
> State=disabled
> DefaultState=enabled
> Activation=immediate
> Reference=bundleProviderService, Satisfied
> Service Name: pl.eurobank.osgi.deployment.BundleProviderService
> Multiple: single
> Optional: optional
> Policy: dynamic
> No Services bound
> Reference=httpService, Satisfied
> Service Name: org.osgi.service.http.HttpService
> Multiple: single
> Optional: optional
> Policy: dynamic
> No Services bound
> Reference=logReader, Satisfied
> Service Name: org.osgi.service.log.LogReaderService
> Multiple: single
> Optional: optional
> Policy: dynamic
> No Services bound
> Properties=
> component.id=1
> component.name=pl.eurobank.osgi.launcher.bundle.internal.LauncherSupportActivator
> service.pid=pl.eurobank.osgi.launcher.bundle.internal.LauncherSupportActivator
> 2=[pl.eurobank.osgi.struts.internal.TestFilter]
> Bundlepl.eurobank.osgi.struts-1-2-bundle (19)
> State=disabled
> DefaultState=enabled
> Activation=delayed
> ServiceType=service
> Services=javax.servlet.Filter
> Properties=
> alias=/test2/*
> component.id=2
> component.name=pl.eurobank.osgi.struts.internal.TestFilter
> contextPath=/bar
> init.testparam=testvalue
> service.pid=pl.eurobank.osgi.struts.internal.TestFilter
> service.ranking=50
> 3=[pl.eurobank.osgi.struts.internal.IndexServlet]
> Bundlepl.eurobank.osgi.struts-1-2-bundle (19)
> State=disabled
> DefaultState=enabled
> Activation=delayed
> ServiceType=service
> Services=javax.servlet.Servlet
> Properties=
> alias=/index
> component.id=3
> component.name=pl.eurobank.osgi.struts.internal.IndexServlet
> contextPath=/
> init.testparam=testvalue
> service.pid=pl.eurobank.osgi.struts.internal.IndexServlet
> 4=[pl.eurobank.osgi.struts.internal.StrutsProxyServlet]
> Bundlepl.eurobank.osgi.struts-1-2-bundle (19)
> State=disabled
> DefaultState=enabled
> Activation=delayed
> ServiceType=service
> Services=javax.servlet.Servlet
> Properties=
> alias=*.ebk
> component.id=4
> component.name=pl.eurobank.osgi.struts.internal.StrutsProxyServlet
> service.pid=pl.eurobank.osgi.struts.internal.StrutsProxyServlet
> 5=[pl.eurobank.osgi.jsp.internal.JspProxyServlet]
> Bundlepl.eurobank.osgi.jsp-bundle (20)
> State=disabled
> DefaultState=enabled
> Activation=delayed
> ServiceType=service
> Services=org.osgi.util.tracker.BundleTrackerCustomizer, java.io.Serializable,
> javax.servlet.Servlet, javax.servlet.ServletConfig
> Properties=
> alias=*.jsp
> component.id=5
> component.name=pl.eurobank.osgi.jsp.internal.JspProxyServlet
> service.pid=pl.eurobank.osgi.jsp.internal.JspProxyServlet
> 6=[pl.eurobank.multipulpit.system.menu.MenuService]
> Bundleeb-multipulpit-system (25)
> State=disabled
> DefaultState=enabled
> Activation=immediate
> ServiceType=service
> Services=pl.eurobank.multipulpit.system.menu.MenuService
> Properties=
> component.id=6
> component.name=pl.eurobank.multipulpit.system.menu.MenuService
> service.pid=pl.eurobank.multipulpit.system.menu.MenuService
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2179) junit does not need to be a compile scope dependency of configadmin
[ https://issues.apache.org/jira/browse/FELIX-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-2179. Closing issues after Configuration Admin 1.2.8 release > junit does not need to be a compile scope dependency of configadmin > --- > > Key: FELIX-2179 > URL: https://issues.apache.org/jira/browse/FELIX-2179 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Affects Versions: configadmin-1.2.4 >Reporter: David Jencks >Assignee: Felix Meschberger > Fix For: configadmin-1.2.8 > > Attachments: FELIX=2179.diff > > > Junit is currently a compile-scope dependency of configadmin. It doesn't need > to be. This is confusing to a system that attempts to assemble runtime > bundle dependencies that will work with a bundle from maven dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
