[jira] [Commented] (FELIX-4179) SCRService should provide state "FAILED" for failing components
[ https://issues.apache.org/jira/browse/FELIX-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767382#comment-13767382 ] Christoph Läubrich commented on FELIX-4179: --- Hi [~djencks] can you explain what has changed? And when 1.8 will be released? My point is not that the component might not activate properly later, it is just hat currently (with 1.6) there is no way to know it has failed AT THE MOMMENT, because it is just reported as UNSATISFIED what is confusing since all references are satisfied, but the activator failed. e.g. Equinox let those components reside in the ACTIVATING state and reports back the exception in its 'comp' command. What I want to archive is an automatic diagnostic tool that tells me whenever something is wrong at the current time, at the mommernt I try to guess this by check if all components are satisfied, but the same state can occur when the configuration policy is require so its a little ugly to guess whats wrong, an explicit state, or a "activation exception" would help alot. > SCRService should provide state "FAILED" for failing components > --- > > Key: FELIX-4179 > URL: https://issues.apache.org/jira/browse/FELIX-4179 > Project: Felix > Issue Type: Improvement > Components: Declarative Services (SCR) >Reporter: Christoph Läubrich >Assignee: David Jencks > Fix For: scr-1.8.0 > > > At the momment the state "UNSATISFIED" is reported for component throwing an > exception in the activate method. This is confusing since in fact all > references/configurations are satisfied. It would be better to report this > problem with a state of "FAILED" -- 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-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-tabpanel&focusedCommentId=13767381#comment-13767381 ] Christoph Läubrich commented on FELIX-4176: --- Hi [~djensen] thanks for looking at this. About the ungetting of CA: Should then the component configuration be resetted to default? Beside this, I would also be happy to just get a Map back. The reason for this is, that for analysis it is somethimes good to know what are the original/actual values and wich are overriden by the cfg, but sure it would also be possible to fetch the Configuration on my own, it is just an extra step and in a secured envirourment I might not be allowed to fetch arbitary configuration objects from my diagnostic bundle! And since the SCR already has all information at hand it seems legal to me to expose that via the 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: Problem for updating Felix documentation site using CMS
Great ! after having updated, I can now edit my new page using CMS interface. thanks! :-) /Pierre On Fri, Sep 13, 2013 at 7:44 AM, Felix Meschberger wrote: > Hi > > Have you tried updating your CMS checkout with the "Update" button ? > > The CMS keeps a checked out workspace on your behalf which you have to > manually update to get "foreign" changes into your workspace. > > Regards > Felix > > Am 12.09.2013 um 23:46 schrieb Pierre De Rop: > > > Hi; > > > > I'm trying to add a tutorial for the new SCR annotations BndTools plugin > in > > Felix documentation, however It's the first time I'm using CMS and I have > > some problems. > > > > What I would like to do is adding a reference in the current > > apache-felix-maven-scr-plugin.mdtext (in the "Where to go from here" > part) > > to my new apache-felix-scr-bndtools-use.mdtext" file, which I already > have > > committed manually. For now, this new page only contains a title and an > > excerpt, and I would like to finish it using the CMS interface. > > > > So, to be clear: > > > > 1) I first committed a new apache-felix-scr-bndtools-use.mdtext file > > manually in > > > felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.mdtext > > > > 2) and I used the CMS bookmarklet in order to modify > > > felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin.mdtext > > for adding the reference to my new apache-felix-scr-bndtools-use.mdtext > > > > So far: everything is ok: from > > > http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html > > , > > I see my new link to the new bndtools doc in the "Where to go from here" > > section (see new ref "Using the Apache Felix SCR Annotations Bnd plugin > to > > generate Declarative Services and Metatype Service descriptors in > > BndTools."). > > > > Now, I click on > > > http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.htmland > > finally, I then I click on the CMS bookmarklet for editing my new > > page. > > > > The problem is that I see a directory listing and now I'm not sure how I > > can edit the content of my new page using CMS GUI ? > > I suppose I did something wrong; could anyone help me about this ? > > > > thanks in advance; > > /Pierre > >
[jira] [Commented] (FELIX-4135) Bnd scrplugin contrib
[ https://issues.apache.org/jira/browse/FELIX-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766435#comment-13766435 ] Pierre De Rop commented on FELIX-4135: -- please ignore my previous message, I finally successfully bootstrapped the tutorial using CMS interface (work in progress). > 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
Maven/SVN issues while releasing Felix HTTP
-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 ... SKIPPED [INFO] Apache Felix Http Whiteboard .. SKIPPED [INFO] Apache Felix Http Cometd .. SKIPPED [INFO] Apache Felix Http Bundle .. SKIPPED [INFO] Apache Felix Http SSL Filter .. SKIPPED [INFO] Apache Felix Http Samples - Filter SKIPPED [INFO] Apache Felix Http Samples - Bridge SKIPPED [INFO] Apache Felix Http Samples - Whiteboard SKIPPED [INFO] Apache Felix Http Samples - Cometd SKIPPED [INFO] Apache Felix Http Reactor . FAILURE [2:36.879s] [INFO] - [INFO] BUILD FAILURE [INFO] - [INFO] Total time: 2:38.195s [INFO] Finished at: Fri Sep 13 18:06:40 CEST 2013 [INFO] Final Memory: 16M/618M [INFO] - [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project org.apache.felix.http: Unable to tag SCM [ERROR] Provider message: [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 [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :org.apache.felix.http - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is revolving around PulseOn and Amdatu/ Luminis Technologies B.V. J.C. Wilslaan 29 7313 HK Apeldoorn +31 88 586 46 30 http://www.luminis-technologies.com
Re: Problem for updating Felix documentation site using CMS
Hi Have you tried updating your CMS checkout with the "Update" button ? The CMS keeps a checked out workspace on your behalf which you have to manually update to get "foreign" changes into your workspace. Regards Felix Am 12.09.2013 um 23:46 schrieb Pierre De Rop: > Hi; > > I'm trying to add a tutorial for the new SCR annotations BndTools plugin in > Felix documentation, however It's the first time I'm using CMS and I have > some problems. > > What I would like to do is adding a reference in the current > apache-felix-maven-scr-plugin.mdtext (in the "Where to go from here" part) > to my new apache-felix-scr-bndtools-use.mdtext" file, which I already have > committed manually. For now, this new page only contains a title and an > excerpt, and I would like to finish it using the CMS interface. > > So, to be clear: > > 1) I first committed a new apache-felix-scr-bndtools-use.mdtext file > manually in > felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.mdtext > > 2) and I used the CMS bookmarklet in order to modify > felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin.mdtext > for adding the reference to my new apache-felix-scr-bndtools-use.mdtext > > So far: everything is ok: from > http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin.html > , > I see my new link to the new bndtools doc in the "Where to go from here" > section (see new ref "Using the Apache Felix SCR Annotations Bnd plugin to > generate Declarative Services and Metatype Service descriptors in > BndTools."). > > Now, I click on > http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.htmland > finally, I then I click on the CMS bookmarklet for editing my new > page. > > The problem is that I see a directory listing and now I'm not sure how I > can edit the content of my new page using CMS GUI ? > I suppose I did something wrong; could anyone help me about this ? > > thanks in advance; > /Pierre smime.p7s Description: S/MIME cryptographic signature
