[jira] [Commented] (FELIX-4186) NPE in DependencyManager Logger
[
https://issues.apache.org/jira/browse/FELIX-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768104#comment-13768104
]
Bram de Kruijff commented on FELIX-4186:
Looks fine to me. Thanks Pierre!
NPE in DependencyManager Logger
---
Key: FELIX-4186
URL: https://issues.apache.org/jira/browse/FELIX-4186
Project: Felix
Issue Type: Bug
Components: Dependency Manager
Affects Versions: dependencymanager-3.1.0
Reporter: Bram de Kruijff
Assignee: Pierre De Rop
Logger line 191 is missing a null check on m_logRef
{code}
ERROR: Bundle com.lopexs.arl.gadgets.mastercontrol [34] EventDispatcher:
Error during dispatch. (java.lang.NullPointerException)
java.lang.NullPointerException
at org.apache.felix.dm.impl.Logger.serviceChanged(Logger.java:191)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
at org.apache.felix.framework.Felix.access$000(Felix.java:74)
at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:390)
at
org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:148)
at
org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:127)
at
org.apache.felix.framework.ServiceRegistry.unregisterServices(ServiceRegistry.java:191)
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2386)
at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:980)
at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:967)
at
org.apache.felix.deploymentadmin.spi.StopBundleCommand.execute(StopBundleCommand.java:57)
at
org.apache.felix.deploymentadmin.spi.DeploymentSessionImpl.call(DeploymentSessionImpl.java:73)
at
org.apache.felix.deploymentadmin.DeploymentAdminImpl.installDeploymentPackage(DeploymentAdminImpl.java:214)
at
org.apache.ace.deployment.deploymentadmin.DeploymentAdminDeployer.install(DeploymentAdminDeployer.java:51)
at
org.apache.ace.deployment.service.impl.DeploymentServiceImpl.installVersion(DeploymentServiceImpl.java:120)
at
org.apache.ace.deployment.task.DeploymentUpdateTask.run(DeploymentUpdateTask.java:57)
at org.apache.ace.scheduler.Executer.run(Executer.java:92)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-4135) Bnd scrplugin contrib
[ https://issues.apache.org/jira/browse/FELIX-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768124#comment-13768124 ] Carsten Ziegeler commented on FELIX-4135: - Great! I guess we can now resolve this issue and create separate issues for all to come :) Bnd scrplugin contrib - Key: FELIX-4135 URL: https://issues.apache.org/jira/browse/FELIX-4135 Project: Felix Issue Type: Improvement Components: Maven SCR Plugin Reporter: Pierre De Rop Priority: Minor Attachments: bnd-scr-plugin.2.tgz, bnd-scr-plugin.3.tgz, bnd-scr-plugin.tgz, test.bndtools.scrplugin.2.tgz, test.bndtools.scrplugin.tgz This issue is related to the following post, which is about writing a bndtools plugin for the Apache Felix Scrplugin annotations: http://www.mail-archive.com/dev@felix.apache.org/msg29200.html If this may help, I have attached to this issue a simple BND plugin, which internally invokes the SCRDescriptorGenerator in order to generate the descriptors for Apache Felix Scr annotations, as well as DS 1.2 annotations (using the scrplugin generator). Basically, just adding the following parameter in a directives.bnd file allows to invoke the plugin: -plugin org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=target/classes I did some tests using a BND Ant task, and it seems to work, and will try to do a test with bndtools this week (for now I don't know how to add a plugin in bndtools, but I guess it's easy). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE RESULT] Apache Felix Metatype 1.0.8 Release
The vote passed with three binding +1 votes from Pierre De Rop, Carsten Ziegeler, and Clement Escoffier. No other votes have been cast. Thanks Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (FELIX-4176) ScrService should provide method to get Component configuration (if present)
[ https://issues.apache.org/jira/browse/FELIX-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768188#comment-13768188 ] Felix Meschberger commented on FELIX-4176: -- [~laeubi] I fear you are mixing concerns here. A component gets its configuration which is a mix of different sources (see the spec for details). That's all the component is really concerned with. This configuration can be retrieved from the ComponentContext as a Dictionary or can be passed into the activate (or modified) method as a MapString, ?). Other than that components are not interested to know where this configuration really comes from. That's none of the business of the component. If you have diagnostics bundles, those bundles have a very valid reason to access any configuration for diagnostics purposes and should therefore have appropriate permissions to access any and all configuration. In addition, adding a Configuration object to the picture, would in fact create a Configuration Admin dependency into the DS API, which would bring some problematic coupling. So, I agree with [~david_jen...@yahoo.com] that we should not add such API. ScrService should provide method to get Component configuration (if present) Key: FELIX-4176 URL: https://issues.apache.org/jira/browse/FELIX-4176 Project: Felix Issue Type: Improvement Components: Declarative Services (SCR) Reporter: Christoph Läubrich Priority: Minor Currently the Properties can be quieried, but it is not possible to access the configuration the component has currently in use. It would be nice if at least the pid can be querried (this is usefull for factory configurations). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Maven/SVN issues while releasing Felix HTTP
Hi Jan-Willem, disclaimer: I have never done a Felix release so there may be something I am missing :) Having said so.. svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 As the http root pom does not specify any scm info the developerConnection is inherited from the released 2.1 parent pom and postfixed with the project.artifactId. Hence the ' .../felix/releases/felix-parent-2.1/org.apache.felix.http'. This is the maven default heuristic that works if you use a hierarchical layout where artifactId matches directory name and you do a multi-module release In this case obviously fails. Running 'maven help:effective-pom' shows this info as well; scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/developerConnection urlhttp://svn.apache.org/viewvc/felix/releases/?root=Apache-SVN/felix-parent-2.1/org.apache.felix.http/url /scm The straightforward approach is to specify the scm info in each pom. This also seems to be implicitly suggested by the release page [0] (see Staging the release candidate #4). So for example in the http/pom.xml scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/trunk/http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/trunk/http/developerConnection urlhttp://svn.apache.org/viewvc/felix/trunk/http//url /scm However, as none of the poms have this info I am wondering how this has been released before. Not sure. Obvisouly you can also pass the parameters as java options on the command line.. Regards, Bram [0] http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates On Fri, Sep 13, 2013 at 8:06 PM, Jan Willem Janssen janwillem.jans...@luminis.eu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to release Felix HTTP v2.2.1 (using [1]), but running `mvn release:prepare` (from the `http` directory) fails while trying to create a release tag of the current sources (full log below): [ERROR] The svn tag command failed. [ERROR] Command output: [ERROR] svn: E160013: '/repos/asf/!svn/rvr/1522993/felix/releases/felix-parent-2.1/org.apache.felix.http' path not found The actual command being (shortened a little for readability): svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 Somehow, Maven has an incorrect notion of where the Felix HTTP sources are residing in the SVN tree. It thinks that they are residing underneath `releases/felix-parent-2.1/org.apache.felix.http`, while they obviously reside underneath `trunk/http`. - From the history, it appears that this is the first time a release is made with the Felix parent POM v2.1 (release v2.2.0 used v1.2 of the Felix parent POM), which might be a clue as to why it fails this time. Anybody able to help me out on this? How does Maven get the strange notion on where the sources should reside in SVN? Thanks in advance, Jan Willem 1. http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates Relevant output log: - --snip-- [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive commit --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-586998340.commit - --targets /var/folders/3w/s23k21td37bgc 4_z7_hgh370gn/T/maven-scm-3764299962992961060-targets [INFO] Working directory: /Users/jawi/Sources/felix/http [INFO] Tagging release with the label org.apache.felix.http-2.2.1... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive copy --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-1604415565.commit - --revision 1522994 https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.http-2.2.1 [INFO] Working directory: /Users/jawi/Sources/felix/http [INFO] - [INFO] Reactor Summary: [INFO] [INFO] Apache Felix Http Parent POM .. SKIPPED [INFO] Apache Felix Http Api . SKIPPED [INFO] Apache Felix Http Base SKIPPED [INFO] Apache Felix Http Bridge .. SKIPPED [INFO] Apache Felix Http Jetty ... SKIPPED [INFO] Apache Felix Http Proxy ...
[jira] [Created] (FELIX-4228) Improve dependency identification in log messages and exceptions
Clement Escoffier created FELIX-4228: Summary: Improve dependency identification in log messages and exceptions Key: FELIX-4228 URL: https://issues.apache.org/jira/browse/FELIX-4228 Project: Felix Issue Type: Improvement Components: iPOJO Reporter: Clement Escoffier Assignee: Clement Escoffier Fix For: ipojo-runtime-1.10.2 Standardize dependency description in messages (either logged or raised). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Maven/SVN issues while releasing Felix HTTP
On Mon, Sep 16, 2013 at 11:43 AM, Bram de Kruijff bdekrui...@gmail.com wrote: Hi Jan-Willem, disclaimer: I have never done a Felix release so there may be something I am missing :) Having said so.. svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 As the http root pom does not specify any scm info the developerConnection is inherited from the released 2.1 parent pom and postfixed with the project.artifactId. Hence the ' .../felix/releases/felix-parent-2.1/org.apache.felix.http'. This is the maven default heuristic that works if you use a hierarchical layout where artifactId matches directory name and you do a multi-module release In this case obviously fails. Running 'maven help:effective-pom' shows this info as well; scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/developerConnection urlhttp://svn.apache.org/viewvc/felix/releases/?root=Apache-SVN/felix-parent-2.1/org.apache.felix.http/url /scm The straightforward approach is to specify the scm info in each pom. This also seems to be implicitly suggested by the release page [0] (see Staging the release candidate #4). So for example in the http/pom.xml scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/trunk/http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/trunk/http/developerConnection urlhttp://svn.apache.org/viewvc/felix/trunk/http//url /scm However, as none of the poms have this info I am wondering how this has been released before. Not sure. Obvisouly you can also pass the parameters as java options on the command line.. Ps. Looking at the recently released projects (eg metatype, prefs, scr) adding this scm info seems to be the way it is done. grz Bram Regards, Bram [0] http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates On Fri, Sep 13, 2013 at 8:06 PM, Jan Willem Janssen janwillem.jans...@luminis.eu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to release Felix HTTP v2.2.1 (using [1]), but running `mvn release:prepare` (from the `http` directory) fails while trying to create a release tag of the current sources (full log below): [ERROR] The svn tag command failed. [ERROR] Command output: [ERROR] svn: E160013: '/repos/asf/!svn/rvr/1522993/felix/releases/felix-parent-2.1/org.apache.felix.http' path not found The actual command being (shortened a little for readability): svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 Somehow, Maven has an incorrect notion of where the Felix HTTP sources are residing in the SVN tree. It thinks that they are residing underneath `releases/felix-parent-2.1/org.apache.felix.http`, while they obviously reside underneath `trunk/http`. - From the history, it appears that this is the first time a release is made with the Felix parent POM v2.1 (release v2.2.0 used v1.2 of the Felix parent POM), which might be a clue as to why it fails this time. Anybody able to help me out on this? How does Maven get the strange notion on where the sources should reside in SVN? Thanks in advance, Jan Willem 1. http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates Relevant output log: - --snip-- [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive commit --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-586998340.commit - --targets /var/folders/3w/s23k21td37bgc 4_z7_hgh370gn/T/maven-scm-3764299962992961060-targets [INFO] Working directory: /Users/jawi/Sources/felix/http [INFO] Tagging release with the label org.apache.felix.http-2.2.1... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive copy --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-1604415565.commit - --revision 1522994 https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.http-2.2.1 [INFO] Working directory: /Users/jawi/Sources/felix/http [INFO] - [INFO] Reactor Summary: [INFO] [INFO] Apache Felix Http Parent POM .. SKIPPED [INFO] Apache Felix Http Api . SKIPPED [INFO] Apache
[VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3
Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. A sample launcher showing the required dependencies can be found here: http://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh --- Changes from 0.1.2 to 0.1.3 --- ** Bugs * [FELIX-3898] name parsing issue on BundleDependency * [FELIX-4162] incorrect loop detection ** Improvements * [FELIX-3899] switch to Scala 2.10 * [FELIX-3769] webconsole categories * [FELIX-4163] command line interface * circular dependencies shown on a separate graph with or wihtout optionals * new visualisations of the service registry: service providers, using bundles, and bundles wiring via services * show components as implementations and services as interfaces * graph filter supports basic logical expressions Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-053/ https://repository.apache.org/content/repositories/orgapachefelix-054/ You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh O53 /tmp/felix-staging-parent sh check_staged_release.sh 054 /tmp/felix-staging-plugin Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun
Re: Maven/SVN issues while releasing Felix HTTP
Hi Yes, Bram is correct: You need to add the scm element as proposed to the reactor POM. Http Service is currently a special biest in the Apache Felix context: All bundles are released in one go along with the reactor. Hence setting the scm on the reactor should (theoretically) be enough to create the tag in the right location. The ultimate goal is to break this release everything together lock also for these projects. At this time, we will have to add scm elements on each of the projects. Regards Felix Am 16.09.2013 um 11:43 schrieb Bram de Kruijff: Hi Jan-Willem, disclaimer: I have never done a Felix release so there may be something I am missing :) Having said so.. svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 As the http root pom does not specify any scm info the developerConnection is inherited from the released 2.1 parent pom and postfixed with the project.artifactId. Hence the ' .../felix/releases/felix-parent-2.1/org.apache.felix.http'. This is the maven default heuristic that works if you use a hierarchical layout where artifactId matches directory name and you do a multi-module release In this case obviously fails. Running 'maven help:effective-pom' shows this info as well; scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http/developerConnection urlhttp://svn.apache.org/viewvc/felix/releases/?root=Apache-SVN/felix-parent-2.1/org.apache.felix.http/url /scm The straightforward approach is to specify the scm info in each pom. This also seems to be implicitly suggested by the release page [0] (see Staging the release candidate #4). So for example in the http/pom.xml scm connectionscm:svn:http://svn.apache.org/repos/asf/felix/trunk/http/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/felix/trunk/http/developerConnection urlhttp://svn.apache.org/viewvc/felix/trunk/http//url /scm However, as none of the poms have this info I am wondering how this has been released before. Not sure. Obvisouly you can also pass the parameters as java options on the command line.. Regards, Bram [0] http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates On Fri, Sep 13, 2013 at 8:06 PM, Jan Willem Janssen janwillem.jans...@luminis.eu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to release Felix HTTP v2.2.1 (using [1]), but running `mvn release:prepare` (from the `http` directory) fails while trying to create a release tag of the current sources (full log below): [ERROR] The svn tag command failed. [ERROR] Command output: [ERROR] svn: E160013: '/repos/asf/!svn/rvr/1522993/felix/releases/felix-parent-2.1/org.apache.felix.http' path not found The actual command being (shortened a little for readability): svn --non-interactive copy \ --file /path/to/maven-scm-1604415565.commit \ --revision 1522994 \ .../felix/releases/felix-parent-2.1/org.apache.felix.http \ .../felix/releases/org.apache.felix.http-2.2.1 Somehow, Maven has an incorrect notion of where the Felix HTTP sources are residing in the SVN tree. It thinks that they are residing underneath `releases/felix-parent-2.1/org.apache.felix.http`, while they obviously reside underneath `trunk/http`. - From the history, it appears that this is the first time a release is made with the Felix parent POM v2.1 (release v2.2.0 used v1.2 of the Felix parent POM), which might be a clue as to why it fails this time. Anybody able to help me out on this? How does Maven get the strange notion on where the sources should reside in SVN? Thanks in advance, Jan Willem 1. http://felix.apache.org/documentation/development/release-management-nexus.html#staging-the-release-candidates Relevant output log: - --snip-- [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive commit --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-586998340.commit - --targets /var/folders/3w/s23k21td37bgc 4_z7_hgh370gn/T/maven-scm-3764299962992961060-targets [INFO] Working directory: /Users/jawi/Sources/felix/http [INFO] Tagging release with the label org.apache.felix.http-2.2.1... [INFO] Executing: /bin/sh -c cd /Users/jawi/Sources/felix/http svn - --non-interactive copy --file /var/folders/3w/s23k21td37bgc4_z7_hgh370gn/T/maven-scm-1604415565.commit - --revision 1522994 https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.http
[jira] [Resolved] (FELIX-4228) Improve dependency identification in log messages and exceptions
[ https://issues.apache.org/jira/browse/FELIX-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier resolved FELIX-4228. -- Resolution: Fixed Improve dependency identification in log messages and exceptions Key: FELIX-4228 URL: https://issues.apache.org/jira/browse/FELIX-4228 Project: Felix Issue Type: Improvement Components: iPOJO Reporter: Clement Escoffier Assignee: Clement Escoffier Fix For: ipojo-runtime-1.10.2 Standardize dependency description in messages (either logged or raised). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-4228) Improve dependency identification in log messages and exceptions
[ https://issues.apache.org/jira/browse/FELIX-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768231#comment-13768231 ] Clement Escoffier commented on FELIX-4228: -- Fixed in trunk Improve dependency identification in log messages and exceptions Key: FELIX-4228 URL: https://issues.apache.org/jira/browse/FELIX-4228 Project: Felix Issue Type: Improvement Components: iPOJO Reporter: Clement Escoffier Assignee: Clement Escoffier Fix For: ipojo-runtime-1.10.2 Standardize dependency description in messages (either logged or raised). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3
+1 I wonder, whether a parent project is really needed for a single project making use of that parent ? In any case, the parent project will probably only be pushed to the Maven repo but not to .../dist, right ? Regards Felix Am 16.09.2013 um 12:54 schrieb Arjun Panday: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. A sample launcher showing the required dependencies can be found here: http://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh --- Changes from 0.1.2 to 0.1.3 --- ** Bugs * [FELIX-3898] name parsing issue on BundleDependency * [FELIX-4162] incorrect loop detection ** Improvements * [FELIX-3899] switch to Scala 2.10 * [FELIX-3769] webconsole categories * [FELIX-4163] command line interface * circular dependencies shown on a separate graph with or wihtout optionals * new visualisations of the service registry: service providers, using bundles, and bundles wiring via services * show components as implementations and services as interfaces * graph filter supports basic logical expressions Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-053/ https://repository.apache.org/content/repositories/orgapachefelix-054/ You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh O53 /tmp/felix-staging-parent sh check_staged_release.sh 054 /tmp/felix-staging-plugin Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3
+1 I wonder, whether a parent project is really needed for a single project making use of that parent ? In any case, the parent project will probably only be pushed to the Maven repo but not to .../dist, right ? Right, the parent is there only because of my sample subproject containing my test cases and playground.. which should not be released. so as such it may seem awkward, but at some point I may also split the diagnostics engine (calculating the dependencies) from the graphical representation (the webconsole plugin) or the shell interface. So if the parent doesn't bother too much I'd rather keep it. Thanks for the vote :) /arjun Regards Felix Am 16.09.2013 um 12:54 schrieb Arjun Panday: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. A sample launcher showing the required dependencies can be found here: http://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh --- Changes from 0.1.2 to 0.1.3 --- ** Bugs * [FELIX-3898] name parsing issue on BundleDependency * [FELIX-4162] incorrect loop detection ** Improvements * [FELIX-3899] switch to Scala 2.10 * [FELIX-3769] webconsole categories * [FELIX-4163] command line interface * circular dependencies shown on a separate graph with or wihtout optionals * new visualisations of the service registry: service providers, using bundles, and bundles wiring via services * show components as implementations and services as interfaces * graph filter supports basic logical expressions Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-053/ https://repository.apache.org/content/repositories/orgapachefelix-054/ You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh O53 /tmp/felix-staging-parent sh check_staged_release.sh 054 /tmp/felix-staging-plugin Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3
Hi Arjun, +1 /Pierre On Mon, Sep 16, 2013 at 12:54 PM, Arjun Panday arjun.pan...@alcatel-lucent.com wrote: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. A sample launcher showing the required dependencies can be found here: http://svn.apache.org/repos/**asf/felix/trunk/webconsole-** plugins/servicediagnostics/**run.shhttp://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh --- Changes from 0.1.2 to 0.1.3 --- ** Bugs * [FELIX-3898] name parsing issue on BundleDependency * [FELIX-4162] incorrect loop detection ** Improvements * [FELIX-3899] switch to Scala 2.10 * [FELIX-3769] webconsole categories * [FELIX-4163] command line interface * circular dependencies shown on a separate graph with or wihtout optionals * new visualisations of the service registry: service providers, using bundles, and bundles wiring via services * show components as implementations and services as interfaces * graph filter supports basic logical expressions Staging repository: https://repository.apache.org/**content/repositories/**orgapachefelix-053/https://repository.apache.org/content/repositories/orgapachefelix-053/ https://repository.apache.org/**content/repositories/**orgapachefelix-054/https://repository.apache.org/content/repositories/orgapachefelix-054/ You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/**asf/felix/trunk/check_staged_**release.shhttp://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh O53 /tmp/felix-staging-parent sh check_staged_release.sh 054 /tmp/felix-staging-plugin Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3
+1 (non binding) Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: Felix Meschberger fmesc...@adobe.com To: dev@felix.apache.org dev@felix.apache.org Subject: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.3 Date: Mon, Sep 16, 2013 2:06 pm +1 I wonder, whether a parent project is really needed for a single project making use of that parent ? In any case, the parent project will probably only be pushed to the Maven repo but not to .../dist, right ? Regards Felix Am 16.09.2013 um 12:54 schrieb Arjun Panday: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. A sample launcher showing the required dependencies can be found here: http://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh --- Changes from 0.1.2 to 0.1.3 --- ** Bugs * [FELIX-3898] name parsing issue on BundleDependency * [FELIX-4162] incorrect loop detection ** Improvements * [FELIX-3899] switch to Scala 2.10 * [FELIX-3769] webconsole categories * [FELIX-4163] command line interface * circular dependencies shown on a separate graph with or wihtout optionals * new visualisations of the service registry: service providers, using bundles, and bundles wiring via services * show components as implementations and services as interfaces * graph filter supports basic logical expressions Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-053/ https://repository.apache.org/content/repositories/orgapachefelix-054/ You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh O53 /tmp/felix-staging-parent sh check_staged_release.sh 054 /tmp/felix-staging-plugin Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun
[jira] [Resolved] (FELIX-4135) Bnd scrplugin contrib
[ https://issues.apache.org/jira/browse/FELIX-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop resolved FELIX-4135. -- Resolution: Fixed Assignee: Pierre De Rop ok, let's resolve this issue (a small tutorial has been added in scrplugin documentation). Bnd scrplugin contrib - Key: FELIX-4135 URL: https://issues.apache.org/jira/browse/FELIX-4135 Project: Felix Issue Type: Improvement Components: Maven SCR Plugin Reporter: Pierre De Rop Assignee: Pierre De Rop Priority: Minor Attachments: bnd-scr-plugin.2.tgz, bnd-scr-plugin.3.tgz, bnd-scr-plugin.tgz, test.bndtools.scrplugin.2.tgz, test.bndtools.scrplugin.tgz This issue is related to the following post, which is about writing a bndtools plugin for the Apache Felix Scrplugin annotations: http://www.mail-archive.com/dev@felix.apache.org/msg29200.html If this may help, I have attached to this issue a simple BND plugin, which internally invokes the SCRDescriptorGenerator in order to generate the descriptors for Apache Felix Scr annotations, as well as DS 1.2 annotations (using the scrplugin generator). Basically, just adding the following parameter in a directives.bnd file allows to invoke the plugin: -plugin org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=target/classes I did some tests using a BND Ant task, and it seems to work, and will try to do a test with bndtools this week (for now I don't know how to add a plugin in bndtools, but I guess it's easy). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-4126) Discontinue creation of single XML descriptor files
[ https://issues.apache.org/jira/browse/FELIX-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769207#comment-13769207 ] Christian Moser commented on FELIX-4126: Would be nice to note this in the plugin documentation: http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-maven-scr-plugin-use.html Discontinue creation of single XML descriptor files --- Key: FELIX-4126 URL: https://issues.apache.org/jira/browse/FELIX-4126 Project: Felix Issue Type: Improvement Components: Maven SCR Plugin Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: maven-scr-plugin 1.14.0, scr ant task 1.8.0, scr generator 1.8.0 As discussed in the mailing list, the support for creating a single XML descriptor file for DS and metatype makes the current code complicated and doesn't provide any benefit over creating separate files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
