Fwd: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7
FYI in case you missed it. In short: The OSGi R 4.3 libraries have been recompiled with Java 5 target and republished as version 4.3.1 to maven. So to use OSGi R 4.3 libraries in a Java 5 (and up) environment you should use the 4.3.1 version dependency. Nothing to be done when using older (4.2.0 and before) dependencies because they are compiled for Java 1.4. Regards Felix Anfang der weitergeleiteten E-Mail: Von: BJ Hargrave b...@bjhargrave.commailto:b...@bjhargrave.com Betreff: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7 Datum: 26. Oktober 2012 21:06:11 MESZ An: osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org Antwort an: Private list for OSGi blog discussion osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org Starting in version 4.3, OSGi started to use generics in some of the API including the Core specification. Generics were introducedhttps://en.wikipedia.org/wiki/Generics_in_Java to the Java language in Java 5. However, OSGi needed to continue to support embedded use cases which use the CDC/Foundation 1.1 runtime which is still based upon the Java 1.4 language level and JVM. To address this issue, OSGi compiled the APIs with -target jsr14http://www.ibm.com/developerworks/java/library/j-jtp02277/index.html; an undocumented javac flag introduced before Java 5 was final. So we had the best of both worlds: we can use generics and still compile to run on Java 1.4 based runtimes. This worked for Java 5 and Java 6. But when Java 7 shipped, two things changed: javac no longer understood the jsr14 option to -target and javac refused to recognize the attributes containing the generics information in class files already compiled with -target jsr14. The change to no longer support creating -target jsr14 class files was ok; we could continue to compile with Java 6 javac. But the change to the javac to cease to recognize the class file attributes with the generics information in existing class files was a bigger problem. It meant that the 4.3 API jars published by OSGi were not useable by people who need to compile with Java 7 javac. By not useable, I mean javac treated the classes as if they did not contain any generics information: they were raw. A bughttp://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7078419 was filed against Java to see if this was some mistake or oversight. The reply was that the change was intentional. At the time this was first noticedhttps://mail.osgi.org/pipermail/osgi-dev/2011-August/003223.html, Java 7 was new and not too widely used. OSGi also included the source code in the jars so you could recompile the code yourself if you needed. Later, when it came time to ship Core R5, we changed to compile the API classes with -target 1.5 and so they work fine on Java 7. So problem solved; the new release's jars don't use -target jsr14! Except some of the current OSGi implementations (I'm looking at you Felixhttps://felix.apache.org/ and Karafhttps://karaf.apache.org/) are still based upon Core 4.3 and thus people using those implementations still need to use the Core 4.3 API. And if they also want to use Java 7, they need to recompile the OSGi API source. So after some prodding by a few folks, OSGi rebuilt the Core and Compendium API jars as Core 4.3.1http://www.osgi.org/Download/File?url=/download/r4v43/osgi.core-4.3.1.jar and Compendium 4.3.1http://www.osgi.org/Download/File?url=/download/r4v43/osgi.cmpn-4.3.1.jar. The new jars have the same packages at the same package versions having the same API signatures. They are just not compiled with -target jsr14 so they work fine with Java 7. So if you need to use the 4.3 API with Java 7, pick up these new 4.3.1 jars. They should also be available on mavenhttp://mvnrepository.com/artifact/org.osgi shortly. -- Posted By BJ Hargrave to OSGi Alliance Bloghttp://blog.osgi.org/2012/10/43-companion-code-for-java-7.html at 10/26/2012 07:06:00 PM ___ osgi-blog mailing list osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-blog
Re: Fwd: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7
FYI, the 4.3.1 artifacts have not yet been deployed on Central. Regards JB On 10/29/2012 09:00 AM, Felix Meschberger wrote: FYI in case you missed it. In short: The OSGi R 4.3 libraries have been recompiled with Java 5 target and republished as version 4.3.1 to maven. So to use OSGi R 4.3 libraries in a Java 5 (and up) environment you should use the 4.3.1 version dependency. Nothing to be done when using older (4.2.0 and before) dependencies because they are compiled for Java 1.4. Regards Felix Anfang der weitergeleiteten E-Mail: Von: BJ Hargrave b...@bjhargrave.commailto:b...@bjhargrave.com Betreff: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7 Datum: 26. Oktober 2012 21:06:11 MESZ An: osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org Antwort an: Private list for OSGi blog discussion osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org Starting in version 4.3, OSGi started to use generics in some of the API including the Core specification. Generics were introducedhttps://en.wikipedia.org/wiki/Generics_in_Java to the Java language in Java 5. However, OSGi needed to continue to support embedded use cases which use the CDC/Foundation 1.1 runtime which is still based upon the Java 1.4 language level and JVM. To address this issue, OSGi compiled the APIs with -target jsr14http://www.ibm.com/developerworks/java/library/j-jtp02277/index.html; an undocumented javac flag introduced before Java 5 was final. So we had the best of both worlds: we can use generics and still compile to run on Java 1.4 based runtimes. This worked for Java 5 and Java 6. But when Java 7 shipped, two things changed: javac no longer understood the jsr14 option to -target and javac refused to recognize the attributes containing the generics information in class files already compiled with -target jsr14. The change to no longer support creating -target jsr14 class files was ok; we could continue to compile with Java 6 javac. But the change to the javac to cease to recognize the class file attributes with the generics information in existing class files was a bigger problem. It meant that the 4.3 API jars published by OSGi were not useable by people who need to compile with Java 7 javac. By not useable, I mean javac treated the classes as if they did not contain any generics information: they were raw. A bughttp://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7078419 was filed against Java to see if this was some mistake or oversight. The reply was that the change was intentional. At the time this was first noticedhttps://mail.osgi.org/pipermail/osgi-dev/2011-August/003223.html, Java 7 was new and not too widely used. OSGi also included the source code in the jars so you could recompile the code yourself if you needed. Later, when it came time to ship Core R5, we changed to compile the API classes with -target 1.5 and so they work fine on Java 7. So problem solved; the new release's jars don't use -target jsr14! Except some of the current OSGi implementations (I'm looking at you Felixhttps://felix.apache.org/ and Karafhttps://karaf.apache.org/) are still based upon Core 4.3 and thus people using those implementations still need to use the Core 4.3 API. And if they also want to use Java 7, they need to recompile the OSGi API source. So after some prodding by a few folks, OSGi rebuilt the Core and Compendium API jars as Core 4.3.1http://www.osgi.org/Download/File?url=/download/r4v43/osgi.core-4.3.1.jar and Compendium 4.3.1http://www.osgi.org/Download/F ile?url=/download/r4v43/osgi.cmpn-4.3.1.jar. The new jars have the same packages at the same package versions having the same API signatures. They are just not compiled with -target jsr14 so they work fine with Java 7. So if you need to use the 4.3 API with Java 7, pick up these new 4.3.1 jars. They should also be available on mavenhttp://mvnrepository.com/artifact/org.osgi shortly. -- Posted By BJ Hargrave to OSGi Alliance Bloghttp://blog.osgi.org/2012/10/43-companion-code-for-java-7.html at 10/26/2012 07:06:00 PM ___ osgi-blog mailing list osgi-b...@mail.osgi.orgmailto:osgi-b...@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-blog -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[jira] [Resolved] (FELIX-3740) Maintain the MetaTypeProvider service tracker on the MetaTypeService
[ https://issues.apache.org/jira/browse/FELIX-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3740. -- Resolution: Fixed Assignee: Felix Meschberger Implemented a single ServiceTracker for ManagedService[Factory] services instread of tracking the services in each MetaTypeInformationImpl object in Rev. r1403227. Now the MetaTypeInformationImpl objects are just data containers and are not linked to service tracking and registered in the framework. This also reduces the number of service listeners. In Rev. r1403229 streamline the trackers for ManagedService[Factory] and MetaTypeProvider to align and simplify them. This resolves this issue. Maintain the MetaTypeProvider service tracker on the MetaTypeService Key: FELIX-3740 URL: https://issues.apache.org/jira/browse/FELIX-3740 Project: Felix Issue Type: Improvement Components: Metatype Service Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: metatype-1.0.6 As of FELIX-3184 support for MetaTypeProvider service has been added with a MetaTypeProviderTracker service tracker. This is so far created and started for each MetaTypeInformationImpl instance. This makes cleanup of the tracker hard. Instead this tracker should be maintained on the MetaTypeServiceImpl and respective MetaTypeProvider services injected into the MetaTypeInformationImpl objects handed out by the service. Likewise, the ManagedService[Factory] services implementing the MetaTypeProvider interface should be tracked in the MetaTypeServiceImpl rather than in the ServiceMetaTypeInformation objects. The trick here is to only provide such MetaTypeProviders to MetaTypeInformationImpl objects not reading meta type information from descriptors. -- 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 Apache Felix Configuration Admin 1.6.0
Hi Time to tally the vote: +1 Felix Meschberger*, Jean-Baptiste Onofré, Pierr De Rop*, Clement Escoffier*, David Bosschaert, Carsten Ziegeler*, Ken Gilmer, Jamie G. 0 - -1 - This vote passes with 8 +1 votes (4 of which binding). I will continue publishing the artifacts. Thanks for your votes. Regards Felix Am 20.10.2012 um 12:36 schrieb Felix Meschberger: Hi, Here is the Apache Felix Configuration Admin 1.6.0 release implementing the most recent Configuration Admin Specification Version 1.5. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12320945 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-144/ You can use this 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 144 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-3532] - Source artifact is not being generated * [FELIX-3596] - Config Admin should track SynchronousConfigurationListeners * [FELIX-3721] - Configuration not always provided upon initial service registration ** Improvement * [FELIX-3577] - Refactor helpers and service trackers * [FELIX-3622] - ConfigurationManager.listConfigurations may not always properly log the configuration PID ** Task * [FELIX-3479] - [Config Admin 1.5] Implement Configuration.getChangeCount() * [FELIX-3480] - [Config Admin 1.5] Implement support for SynchronousConfigurationListener * [FELIX-3481] - [Config Admin 1.5] Implement support for Targeted PIDs * [FELIX-3483] - [Config Admin 1.5] Export cm API at version 1.5 * [FELIX-3554] - Prevent same configuration to be delivered multiple times * [FELIX-3562] - Use OSGi Configuration Admin 1.5 API classes * [FELIX-3578] - ConfigAdmin Maven build does not have Maven convention *-sources.jar artifacts
[RESULT] [VOTE] Release Apache Felix Configuration Admin 1.6.0
Oops, sorry. Three fixes: - correct subject - Pierre's name is spelled incorrectly (sorry) - Pierre is not actually a PMC member So, the correct result is 8 +1 votes (3 of which binding). This vote nevertheless succeeds and I continue with the publication. Regards Felix Am 29.10.2012 um 11:29 schrieb Felix Meschberger: Hi Time to tally the vote: +1 Felix Meschberger*, Jean-Baptiste Onofré, Pierr De Rop*, Clement Escoffier*, David Bosschaert, Carsten Ziegeler*, Ken Gilmer, Jamie G. 0 - -1 - This vote passes with 8 +1 votes (4 of which binding). I will continue publishing the artifacts. Thanks for your votes. Regards Felix Am 20.10.2012 um 12:36 schrieb Felix Meschberger: Hi, Here is the Apache Felix Configuration Admin 1.6.0 release implementing the most recent Configuration Admin Specification Version 1.5. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12320945 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-144/ You can use this 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 144 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-3532] - Source artifact is not being generated * [FELIX-3596] - Config Admin should track SynchronousConfigurationListeners * [FELIX-3721] - Configuration not always provided upon initial service registration ** Improvement * [FELIX-3577] - Refactor helpers and service trackers * [FELIX-3622] - ConfigurationManager.listConfigurations may not always properly log the configuration PID ** Task * [FELIX-3479] - [Config Admin 1.5] Implement Configuration.getChangeCount() * [FELIX-3480] - [Config Admin 1.5] Implement support for SynchronousConfigurationListener * [FELIX-3481] - [Config Admin 1.5] Implement support for Targeted PIDs * [FELIX-3483] - [Config Admin 1.5] Export cm API at version 1.5 * [FELIX-3554] - Prevent same configuration to be delivered multiple times * [FELIX-3562] - Use OSGi Configuration Admin 1.5 API classes * [FELIX-3578] - ConfigAdmin Maven build does not have Maven convention *-sources.jar artifacts
Re: [VOTE] Release of iPOJO Manipulator 1.8.6 and iPOJO Runtime 1.8.4
+1 (non-binding) This release fixes several blockers for us (we're on trunk just to work), it's very welcome. Thanks Clément! Simon On Sun, Oct 28, 2012 at 10:01 PM, Göktürk Gezer gokturk.ge...@gmail.com wrote: +1 (non-binding) Thanks, Gokturk On Sun, Oct 28, 2012 at 6:30 PM, Clement Escoffier clement.escoff...@gmail.com wrote: Hi, It's time to cut a release of the iPOJO Manipulator (1.8.6) and runtime project (1.8.4). This releases contains: * iPOJO Manipulator 1.8.6 * maven-ipojo-plugin 1.8.6 * iPOJO Ant Task 1.8.6 * iPOJO BND Plugin 1.8.6 * iPOJO Core 1.8.4 * iPOJO Composite 1.8.4 * iPOJO Annotations 1.8.4 * iPOJO Runtime Project 1.8.4 Those releases contain a lot of bugs fixes. The changelogs are below. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-172/ You can use this 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 172 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours (at least). Regards, Clement Changelog of the manipulator project (1.8.6): * [FELIX-3461] - Re-manipulation with annotated component produces corrupted MANIFEST * [FELIX-3466] - Pojoization.directoryManipulation() does not take MANIFEST file location into account. * [FELIX-3508] - IPojo Manipulator left out 'array of enums' in generated metadata * [FELIX-3539] - iPOJO Manipulator failed on classes containing expanded frames * [FELIX-3573] - IPojo bytecode manipulation generates a duplicate local variable * [FELIX-3574] - IPojo bytecode manipulation looses method argument names * [FELIX-3621] - Two dimensional array as argument to a method in a component Changelog of the runtime project (1.8.4): * [FELIX-3451] - instance.name attribute not recognized * [FELIX-3500] - InstanceManager concurrency issue: A methodID cannot be associated with a method from the POJO class * [FELIX-3501] - IPojo FactoryStateListener doesn't get notified while stopping factory * [FELIX-3545] - Memory leak when unregistering a component used by an aggregate dependency with an unbind callback * [FELIX-3548] - Concurrent access during startup * [FELIX-3567] - iPOJO Configuration Handler should not reuse the dictionary object from the configuration admin * [FELIX-3576] - iPOJO fails when using constructor injection and expecting BundleContext in ctor * [FELIX-3599] - Problem with 'subservice action=instantiate' in ipojo composite * [FELIX-3621] - Two dimensional array as argument to a method in a component * [FELIX-3672] - Potential Concurrent Modification Exception when a bundle is stopped * [FELIX-3560] - Extensions to IPojo's Factory and ComponentInstance documentation for custom handlers
Welcome new committer Chetan Mehrotra
Hi all In recognition of the contribution of the new Felix JAAS integration module and his willingness to continue maintaining the module, the Apache Felix PMC decided to invite Chetan Mehrotra to be a committer to the Apache Felix project. Chetan accepted this invitation. Please join me in congratulating and welcoming Chetan as our new committer. Regards Felix PS: Cheatan, if you like, you can add a few words of introduction.
Re: Welcome new committer Chetan Mehrotra
On Oct 29, 2012, at 12:44 , Felix Meschberger fmesc...@adobe.com wrote: In recognition of the contribution of the new Felix JAAS integration module and his willingness to continue maintaining the module, the Apache Felix PMC decided to invite Chetan Mehrotra to be a committer to the Apache Felix project. Chetan accepted this invitation. Please join me in congratulating and welcoming Chetan as our new committer. Welcome Chetan! Looking forward to working together and good luck with the JAAS integration module! Greetings, Marcel
[jira] [Closed] (FELIX-3578) ConfigAdmin Maven build does not have Maven convention *-sources.jar artifacts
[ https://issues.apache.org/jira/browse/FELIX-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3578. ConfigAdmin Maven build does not have Maven convention *-sources.jar artifacts -- Key: FELIX-3578 URL: https://issues.apache.org/jira/browse/FELIX-3578 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Darryl L. Miles Assignee: Felix Meschberger Labels: maven Fix For: configadmin-1.6.0 https://repository.apache.org/content/repositories/releases/org/apache/felix/org.apache.felix.configadmin/1.4.0/ There appears to be some kind of *.tar.gz and *.zip there is nothing wrong with these existing from the output of the assembly plugin however what should ALSO exist is the standardized *-sources.jar that can be used by tooling. Maven is about conventions. The previous release 1.2.8 does provide the standard artifacts (as are also provided for many other Felix modules). It would probably be more useful to have *-dist.tar.gz and *-dist.zip if your intention was to provide the whole project in an almost buildable format. -- 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] [Closed] (FELIX-3483) [Config Admin 1.5] Export cm API at version 1.5
[ https://issues.apache.org/jira/browse/FELIX-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3483. [Config Admin 1.5] Export cm API at version 1.5 --- Key: FELIX-3483 URL: https://issues.apache.org/jira/browse/FELIX-3483 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 The org.osgi.service.cm API must be exported at version 1.5 and re-imported as [1.5,1.6) -- 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] [Closed] (FELIX-3562) Use OSGi Configuration Admin 1.5 API classes
[ https://issues.apache.org/jira/browse/FELIX-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3562. Use OSGi Configuration Admin 1.5 API classes Key: FELIX-3562 URL: https://issues.apache.org/jira/browse/FELIX-3562 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 OSGi Enterprise R5 library has been published to the Maven repository and thus we should use that to provide the Configuration Admin 1.5 API classes for implementation and provisioning. -- 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] [Closed] (FELIX-3577) Refactor helpers and service trackers
[ https://issues.apache.org/jira/browse/FELIX-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3577. Refactor helpers and service trackers - Key: FELIX-3577 URL: https://issues.apache.org/jira/browse/FELIX-3577 Project: Felix Issue Type: Improvement Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 The ConfigurationManager class currently hosts quite a number of inner classes to help with its tasks. A few of these classes have overlapping functionality which makes it hard to easily implement targeted PIDs these functionalities should be better aligned: * ManagedService[Factory]Tracker don't really get the services but maintain a map of PIDs and assigned configurations (most importantly the targeted PID and configuration modification counter) * ManagedService[Factory] callbacks are also executed by the tracker classes * The ManagedService[Factory]Helper classes are renamed to [Factory]ConfigurationHelper since they are helpers to convey configuration to ManagedService[Factory] services through the respective trackers. * The ServiceHolder class is replaced by the ConfigurationMap class managed by the trackers. -- 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] [Closed] (FELIX-3479) [Config Admin 1.5] Implement Configuration.getChangeCount()
[ https://issues.apache.org/jira/browse/FELIX-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3479. [Config Admin 1.5] Implement Configuration.getChangeCount() --- Key: FELIX-3479 URL: https://issues.apache.org/jira/browse/FELIX-3479 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 Configuration Admin 1.5 (OSGi Enterprise Spec R5) adds a new method on the Configuration interface getChangeCount() returning the number of persisted updates to the configuration. -- 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] [Closed] (FELIX-3622) ConfigurationManager.listConfigurations may not always properly log the configuration PID
[ https://issues.apache.org/jira/browse/FELIX-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3622. ConfigurationManager.listConfigurations may not always properly log the configuration PID - Key: FELIX-3622 URL: https://issues.apache.org/jira/browse/FELIX-3622 Project: Felix Issue Type: Improvement Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 The ConfigurationManager.listConfigurations logs what it does with any configuration found. These log messages include the Service PID. If the configuration is just read from persistence and the ConfigurationImpl object created after the filter check (because the config is not cached yet), the config dictionary has the service.pid property removed and the log message will log null for the service.pid. Fix is to use the local pid variable which is extracted from the dictionary early during check to ensure the service.pid is actually available from the raw configuration dictionary. -- 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] [Closed] (FELIX-3596) Config Admin should track SynchronousConfigurationListeners
[ https://issues.apache.org/jira/browse/FELIX-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3596. Config Admin should track SynchronousConfigurationListeners --- Key: FELIX-3596 URL: https://issues.apache.org/jira/browse/FELIX-3596 Project: Felix Issue Type: Bug Components: Configuration Admin Affects Versions: configadmin-1.6.0 Reporter: Carsten Ziegeler Assignee: Felix Meschberger Fix For: configadmin-1.6.0 According to the 5.0 enterprise spec (104.8) synchronous configuration listeners register themselves with the SCL interface. Verified by BJ :) The current implementation in trunk expects them to register with the CL interface. (Even if a SCL registers as a CL it should be treated just like a CL) -- 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] [Closed] (FELIX-3532) Source artifact is not being generated
[ https://issues.apache.org/jira/browse/FELIX-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3532. Source artifact is not being generated -- Key: FELIX-3532 URL: https://issues.apache.org/jira/browse/FELIX-3532 Project: Felix Issue Type: Bug Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 The source plugin is not running with the following WARNING: [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ org.apache.felix.configadmin --- [WARNING] NOT adding sources to artifacts with classifier as Maven only supports one classifier per artifact. Current artifact [org.apache.felix:org.apache.felix.configadmin:bundle:1.4.1-SNAPSHOT] has a [] classifier. Have to check why this happens. -- 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] [Closed] (FELIX-3481) [Config Admin 1.5] Implement support for Targeted PIDs
[ https://issues.apache.org/jira/browse/FELIX-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3481. [Config Admin 1.5] Implement support for Targeted PIDs -- Key: FELIX-3481 URL: https://issues.apache.org/jira/browse/FELIX-3481 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 Configuration Admin 1.5 (OSGi Enterprise Spec R5) adds support for targeted PIDs which should be supported by our implementation. -- 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] [Closed] (FELIX-3480) [Config Admin 1.5] Implement support for SynchronousConfigurationListener
[ https://issues.apache.org/jira/browse/FELIX-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3480. [Config Admin 1.5] Implement support for SynchronousConfigurationListener - Key: FELIX-3480 URL: https://issues.apache.org/jira/browse/FELIX-3480 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 Configuration Admin 1.5 (OSGi Enterprise Spec R5) adds support for synchronous configuration listeners which should be supported by our implementation. -- 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] [Closed] (FELIX-3554) Prevent same configuration to be delivered multiple times
[ https://issues.apache.org/jira/browse/FELIX-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3554. Prevent same configuration to be delivered multiple times - Key: FELIX-3554 URL: https://issues.apache.org/jira/browse/FELIX-3554 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.6.0 It may happen, that configuration is delivered to a ManagedService[Factory] twice depending some timing issues. Here's the thing: * Thread1: Configuration pid1 is created * Thread1: ManagedServiceUpdate is scheduled (but not run yet) * Thread1: ManagedService for pid1 is registered and configuration provisioning scheduled (but not run yet) * Thread2: Configuration update for pid1 is dispatched to ManagedService on separate thread * Thread2: ManagedService is updated with configured due to its registration The second configuration update is not completely wrong but is not needed and might be prevented if the configuration revision counter would be checked before providing the configuration to the ManagedService. -- 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] [Closed] (FELIX-3721) Configuration not always provided upon initial service registration
[ https://issues.apache.org/jira/browse/FELIX-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed FELIX-3721. Configuration not always provided upon initial service registration --- Key: FELIX-3721 URL: https://issues.apache.org/jira/browse/FELIX-3721 Project: Felix Issue Type: Bug Components: Configuration Admin, Specification compliance Affects Versions: configadmin-1.6.0 Environment: Java 6 on Linux platforms Reporter: Felix Meschberger Assignee: Felix Meschberger Priority: Blocker Fix For: configadmin-1.6.0 With the changes to implement Targeted PIDs and refactoring of the service trackers for FELIX-3577 and FELIX-3481 a race condition has been introduced which may cause ManagedService and ManagedServiceFactory services to not be called back on initial registration. This has been exhibited by test build of the yet unpublished OSGi CT for Configuration Admin, for example: (1) ManagedService PID 1 registered (2) ManagedService PID 2 registered (3) ManagedService PID 2 called back The problem is, that before the call back to ManagedService PID 2, the call back to ManagedService PID 1 is expected. Turns out that this race condition takes place, which may primarily be reproduced on Linux platforms, probably due to different threading implementations on the platform: T1: register service T1: call ServiceTracker.addingService T1: schedule service update task T2: run update task T2: terminate update task without calling the service T1: return from ServiceTracker.addingService returning ConfigurationMap This is expected since the service update task in T2 expects the ConfigurationMap stored in the ServiceTracker. But this is not the case yet because the ServiceTracker.addingService method has not yet returned it for it to be stored in the ServiceTracker. Therefore T2 is not able to call back the service and thus the update call never takes place. The fix is either to delay the task execution in T2 or to prepare the ConfigurationMap in T1 and hand it over to the task to be executed in T2. The first solution is suboptimal because we cannot find a timing value which (a) does not delay too much bug (b) still makes sure the ConfigurationMap will ultimately be available. -- 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 of iPOJO Manipulator 1.8.6 and iPOJO Runtime 1.8.4
+1 (non binding) --G 2012/10/28 Göktürk Gezer gokturk.ge...@gmail.com +1 (non-binding) Thanks, Gokturk On Sun, Oct 28, 2012 at 6:30 PM, Clement Escoffier clement.escoff...@gmail.com wrote: Hi, It's time to cut a release of the iPOJO Manipulator (1.8.6) and runtime project (1.8.4). This releases contains: * iPOJO Manipulator 1.8.6 * maven-ipojo-plugin 1.8.6 * iPOJO Ant Task 1.8.6 * iPOJO BND Plugin 1.8.6 * iPOJO Core 1.8.4 * iPOJO Composite 1.8.4 * iPOJO Annotations 1.8.4 * iPOJO Runtime Project 1.8.4 Those releases contain a lot of bugs fixes. The changelogs are below. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-172/ You can use this 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 172 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours (at least). Regards, Clement Changelog of the manipulator project (1.8.6): * [FELIX-3461] - Re-manipulation with annotated component produces corrupted MANIFEST * [FELIX-3466] - Pojoization.directoryManipulation() does not take MANIFEST file location into account. * [FELIX-3508] - IPojo Manipulator left out 'array of enums' in generated metadata * [FELIX-3539] - iPOJO Manipulator failed on classes containing expanded frames * [FELIX-3573] - IPojo bytecode manipulation generates a duplicate local variable * [FELIX-3574] - IPojo bytecode manipulation looses method argument names * [FELIX-3621] - Two dimensional array as argument to a method in a component Changelog of the runtime project (1.8.4): * [FELIX-3451] - instance.name attribute not recognized * [FELIX-3500] - InstanceManager concurrency issue: A methodID cannot be associated with a method from the POJO class * [FELIX-3501] - IPojo FactoryStateListener doesn't get notified while stopping factory * [FELIX-3545] - Memory leak when unregistering a component used by an aggregate dependency with an unbind callback * [FELIX-3548] - Concurrent access during startup * [FELIX-3567] - iPOJO Configuration Handler should not reuse the dictionary object from the configuration admin * [FELIX-3576] - iPOJO fails when using constructor injection and expecting BundleContext in ctor * [FELIX-3599] - Problem with 'subservice action=instantiate' in ipojo composite * [FELIX-3621] - Two dimensional array as argument to a method in a component * [FELIX-3672] - Potential Concurrent Modification Exception when a bundle is stopped * [FELIX-3560] - Extensions to IPojo's Factory and ComponentInstance documentation for custom handlers
Re: [VOTE] Release of iPOJO Manipulator 1.8.6 and iPOJO Runtime 1.8.4
+1 Regards Felix Am 28.10.2012 um 17:30 schrieb Clement Escoffier: Hi, It's time to cut a release of the iPOJO Manipulator (1.8.6) and runtime project (1.8.4). This releases contains: * iPOJO Manipulator 1.8.6 * maven-ipojo-plugin 1.8.6 * iPOJO Ant Task 1.8.6 * iPOJO BND Plugin 1.8.6 * iPOJO Core 1.8.4 * iPOJO Composite 1.8.4 * iPOJO Annotations 1.8.4 * iPOJO Runtime Project 1.8.4 Those releases contain a lot of bugs fixes. The changelogs are below. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-172/ You can use this 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 172 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours (at least). Regards, Clement Changelog of the manipulator project (1.8.6): * [FELIX-3461] - Re-manipulation with annotated component produces corrupted MANIFEST * [FELIX-3466] - Pojoization.directoryManipulation() does not take MANIFEST file location into account. * [FELIX-3508] - IPojo Manipulator left out 'array of enums' in generated metadata * [FELIX-3539] - iPOJO Manipulator failed on classes containing expanded frames * [FELIX-3573] - IPojo bytecode manipulation generates a duplicate local variable * [FELIX-3574] - IPojo bytecode manipulation looses method argument names * [FELIX-3621] - Two dimensional array as argument to a method in a component Changelog of the runtime project (1.8.4): * [FELIX-3451] - instance.name attribute not recognized * [FELIX-3500] - InstanceManager concurrency issue: A methodID cannot be associated with a method from the POJO class * [FELIX-3501] - IPojo FactoryStateListener doesn't get notified while stopping factory * [FELIX-3545] - Memory leak when unregistering a component used by an aggregate dependency with an unbind callback * [FELIX-3548] - Concurrent access during startup * [FELIX-3567] - iPOJO Configuration Handler should not reuse the dictionary object from the configuration admin * [FELIX-3576] - iPOJO fails when using constructor injection and expecting BundleContext in ctor * [FELIX-3599] - Problem with 'subservice action=instantiate' in ipojo composite * [FELIX-3621] - Two dimensional array as argument to a method in a component * [FELIX-3672] - Potential Concurrent Modification Exception when a bundle is stopped * [FELIX-3560] - Extensions to IPojo's Factory and ComponentInstance documentation for custom handlers
[VOTE] Release Apache Felix Metatype Service 1.0.6
Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location
Re: [VOTE] Release Apache Felix Metatype Service 1.0.6
+1 Regards Felix Am 29.10.2012 um 16:54 schrieb Felix Meschberger: Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location
Re: [VOTE] Release Apache Felix Metatype Service 1.0.6
+1 (non binding) Regards JB On 10/29/2012 04:54 PM, Felix Meschberger wrote: Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: [VOTE] Release Apache Felix Metatype Service 1.0.6
+1 (non-binding) Cursory testing in my application looks good. Thanks a lot, Felix! Jeremias Maerki On 29.10.2012 16:54:07 Felix Meschberger wrote: Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location
Re: [VOTE] Release Apache Felix Metatype Service 1.0.6
+1, Regards, Clement On 29 oct. 2012, at 16:54, Felix Meschberger fmesc...@adobe.com wrote: Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location
Re: [VOTE] Release Apache Felix Metatype Service 1.0.6
+1 Carsten 2012/10/29 Clement Escoffier clement.escoff...@gmail.com: +1, Regards, Clement On 29 oct. 2012, at 16:54, Felix Meschberger fmesc...@adobe.com wrote: Hi, Here is the Apache Felix Metatype Service 1.0.6 release implementing the most recent MetaType Service Specification Version 1.2. The issues completed in this release are listed in the release notes at (also attached at the end of this message): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100version=12314144 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-177/ You can use this 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 177 /tmp/felix-staging Please vote to approve this release: [ ] +1 Release [ ] -1 Don't release, because ... This vote will be open for at least 72 hours. Regards Felix ** Bug * [FELIX-2094] - AttributeDefinition with an empty default value must attribute must result in a single (empty string) entry string array * [FELIX-2097] - DefaultMetaTypeProvider.getLocales() must not reuturn an empty string entry * [FELIX-2860] - getLocales() in DefaultMetaTypeProvider needs to check return of findEntries * [FELIX-2867] - getIcon() in LocalizedObjectClassDefinition keyset iteration incorrect * [FELIX-2868] - Icon only works if absolute path specified, but specification allows for relative urls * [FELIX-3183] - Attribute requirement is not validated * [FELIX-3364] - MetaDataReader exposes a private exception class on the public API * [FELIX-3720] - Designate's pid attribute is optional and not mandatory * [FELIX-3730] - AD.validate of string attributes must validate the string length * [FELIX-3732] - service.pid properties of ManagedServiceFactory services must be used as factory PIDs * [FELIX-3734] - MetaType: NPE in ServiceTracker for fragment bundle ** Improvement * [FELIX-3167] - Add support for new PASSWORD attribute type * [FELIX-3338] - Add support for optional attributes in the MetaDataReader as defined in the XML schema for metatype * [FELIX-3736] - Add support for MetaTypeProvider service modifications * [FELIX-3740] - Maintain the MetaTypeProvider service tracker on the MetaTypeService ** New Feature * [FELIX-2719] - Add name space support to the meta type implementation ** Task * [FELIX-2096] - Check MetaTypeProvider.getObjectClassDefinition(String, String) specification compliance * [FELIX-3182] - Update to use parent POM 2.1 * [FELIX-3184] - Add support for metatype extension by MetatypeProvider services * [FELIX-3731] - Multi-Value service.pid service properties must be supported * [FELIX-3733] - Clarify icon location -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release of iPOJO Manipulator 1.8.6 and iPOJO Runtime 1.8.4
+1 Carsten 2012/10/29 Felix Meschberger fmesc...@adobe.com: +1 Regards Felix Am 28.10.2012 um 17:30 schrieb Clement Escoffier: Hi, It's time to cut a release of the iPOJO Manipulator (1.8.6) and runtime project (1.8.4). This releases contains: * iPOJO Manipulator 1.8.6 * maven-ipojo-plugin 1.8.6 * iPOJO Ant Task 1.8.6 * iPOJO BND Plugin 1.8.6 * iPOJO Core 1.8.4 * iPOJO Composite 1.8.4 * iPOJO Annotations 1.8.4 * iPOJO Runtime Project 1.8.4 Those releases contain a lot of bugs fixes. The changelogs are below. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-172/ You can use this 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 172 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours (at least). Regards, Clement Changelog of the manipulator project (1.8.6): * [FELIX-3461] - Re-manipulation with annotated component produces corrupted MANIFEST * [FELIX-3466] - Pojoization.directoryManipulation() does not take MANIFEST file location into account. * [FELIX-3508] - IPojo Manipulator left out 'array of enums' in generated metadata * [FELIX-3539] - iPOJO Manipulator failed on classes containing expanded frames * [FELIX-3573] - IPojo bytecode manipulation generates a duplicate local variable * [FELIX-3574] - IPojo bytecode manipulation looses method argument names * [FELIX-3621] - Two dimensional array as argument to a method in a component Changelog of the runtime project (1.8.4): * [FELIX-3451] - instance.name attribute not recognized * [FELIX-3500] - InstanceManager concurrency issue: A methodID cannot be associated with a method from the POJO class * [FELIX-3501] - IPojo FactoryStateListener doesn't get notified while stopping factory * [FELIX-3545] - Memory leak when unregistering a component used by an aggregate dependency with an unbind callback * [FELIX-3548] - Concurrent access during startup * [FELIX-3567] - iPOJO Configuration Handler should not reuse the dictionary object from the configuration admin * [FELIX-3576] - iPOJO fails when using constructor injection and expecting BundleContext in ctor * [FELIX-3599] - Problem with 'subservice action=instantiate' in ipojo composite * [FELIX-3621] - Two dimensional array as argument to a method in a component * [FELIX-3672] - Potential Concurrent Modification Exception when a bundle is stopped * [FELIX-3560] - Extensions to IPojo's Factory and ComponentInstance documentation for custom handlers -- Carsten Ziegeler cziege...@apache.org
[jira] [Assigned] (FELIX-3739) scr-plugin: Annotated method {0} not found
[
https://issues.apache.org/jira/browse/FELIX-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-3739:
---
Assignee: Carsten Ziegeler
scr-plugin: Annotated method {0} not found
Key: FELIX-3739
URL: https://issues.apache.org/jira/browse/FELIX-3739
Project: Felix
Issue Type: Bug
Components: Maven SCR Plugin
Affects Versions: maven-scr-plugin-1.8.0
Environment: Linux, Maven 3, Java 7
Reporter: Johannes Schneider
Assignee: Carsten Ziegeler
I run in to that[1] problem.
The method that is not found looks like that:
@Nonnull public static T Entry? extends T create( @Nonnull T
object,
@Nonnull byte[] expected ) {
}
I have debugged this and it comes to that:
in ClassScanner#237 parameters are compared. The second parameter of
my method (byte[]) has a strange difference here:
parameterTypeName: [B
signature[index].getClassName(): byte[]
So I think this might be related to the asm usage
I *think* instead of signature[index].getClassName() there should be
called
signature[index].getDescriptor()
Any idea how I could work around that problem (without changing my
method's signature)?
Thanks,
Johannes
[1]
[ERROR] Failed to execute goal
org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found. - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:222)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.felix.scrplugin.SCRDescriptorException:
Annotated method create not found.
at
org.apache.felix.scrplugin.helper.ClassScanner.extractAnnotation(ClassScanner.java:249)
at
org.apache.felix.scrplugin.helper.ClassScanner.processClass(ClassScanner.java:180)
at
org.apache.felix.scrplugin.helper.ClassScanner.scanSources(ClassScanner.java:143)
at
org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:154)
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:217)
... 21 more
--
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] [Work started] (FELIX-3739) scr-plugin: Annotated method {0} not found
[
https://issues.apache.org/jira/browse/FELIX-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on FELIX-3739 started by Carsten Ziegeler.
scr-plugin: Annotated method {0} not found
Key: FELIX-3739
URL: https://issues.apache.org/jira/browse/FELIX-3739
Project: Felix
Issue Type: Bug
Components: Maven SCR Plugin
Affects Versions: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr
generator 1.2.0
Environment: Linux, Maven 3, Java 7
Reporter: Johannes Schneider
Assignee: Carsten Ziegeler
Fix For: maven-scr-plugin-1.8.2, scr ant task 1.2.2, scr
generator 1.2.2
I run in to that[1] problem.
The method that is not found looks like that:
@Nonnull public static T Entry? extends T create( @Nonnull T
object,
@Nonnull byte[] expected ) {
}
I have debugged this and it comes to that:
in ClassScanner#237 parameters are compared. The second parameter of
my method (byte[]) has a strange difference here:
parameterTypeName: [B
signature[index].getClassName(): byte[]
So I think this might be related to the asm usage
I *think* instead of signature[index].getClassName() there should be
called
signature[index].getDescriptor()
Any idea how I could work around that problem (without changing my
method's signature)?
Thanks,
Johannes
[1]
[ERROR] Failed to execute goal
org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found. - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:222)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.felix.scrplugin.SCRDescriptorException:
Annotated method create not found.
at
org.apache.felix.scrplugin.helper.ClassScanner.extractAnnotation(ClassScanner.java:249)
at
org.apache.felix.scrplugin.helper.ClassScanner.processClass(ClassScanner.java:180)
at
org.apache.felix.scrplugin.helper.ClassScanner.scanSources(ClassScanner.java:143)
at
org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:154)
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:217)
... 21 more
--
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:
[jira] [Commented] (FELIX-3739) scr-plugin: Annotated method {0} not found
[
https://issues.apache.org/jira/browse/FELIX-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486166#comment-13486166
]
Carsten Ziegeler commented on FELIX-3739:
-
Thanks for the report, I'Ve just committed a fix, could you please give it a
try?
scr-plugin: Annotated method {0} not found
Key: FELIX-3739
URL: https://issues.apache.org/jira/browse/FELIX-3739
Project: Felix
Issue Type: Bug
Components: Maven SCR Plugin
Affects Versions: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr
generator 1.2.0
Environment: Linux, Maven 3, Java 7
Reporter: Johannes Schneider
Assignee: Carsten Ziegeler
Fix For: maven-scr-plugin-1.8.2, scr ant task 1.2.2, scr
generator 1.2.2
I run in to that[1] problem.
The method that is not found looks like that:
@Nonnull public static T Entry? extends T create( @Nonnull T
object,
@Nonnull byte[] expected ) {
}
I have debugged this and it comes to that:
in ClassScanner#237 parameters are compared. The second parameter of
my method (byte[]) has a strange difference here:
parameterTypeName: [B
signature[index].getClassName(): byte[]
So I think this might be related to the asm usage
I *think* instead of signature[index].getClassName() there should be
called
signature[index].getDescriptor()
Any idea how I could work around that problem (without changing my
method's signature)?
Thanks,
Johannes
[1]
[ERROR] Failed to execute goal
org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found. - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:222)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.felix.scrplugin.SCRDescriptorException:
Annotated method create not found.
at
org.apache.felix.scrplugin.helper.ClassScanner.extractAnnotation(ClassScanner.java:249)
at
org.apache.felix.scrplugin.helper.ClassScanner.processClass(ClassScanner.java:180)
at
org.apache.felix.scrplugin.helper.ClassScanner.scanSources(ClassScanner.java:143)
at
org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:154)
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:217)
... 21 more
--
This message is
[jira] [Updated] (FELIX-3739) scr-plugin: Annotated method {0} not found
[
https://issues.apache.org/jira/browse/FELIX-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-3739:
Affects Version/s: scr ant task 1.2.0
scr generator 1.2.0
Fix Version/s: scr generator 1.2.2
scr ant task 1.2.2
maven-scr-plugin-1.8.2
scr-plugin: Annotated method {0} not found
Key: FELIX-3739
URL: https://issues.apache.org/jira/browse/FELIX-3739
Project: Felix
Issue Type: Bug
Components: Maven SCR Plugin
Affects Versions: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr
generator 1.2.0
Environment: Linux, Maven 3, Java 7
Reporter: Johannes Schneider
Assignee: Carsten Ziegeler
Fix For: maven-scr-plugin-1.8.2, scr ant task 1.2.2, scr
generator 1.2.2
I run in to that[1] problem.
The method that is not found looks like that:
@Nonnull public static T Entry? extends T create( @Nonnull T
object,
@Nonnull byte[] expected ) {
}
I have debugged this and it comes to that:
in ClassScanner#237 parameters are compared. The second parameter of
my method (byte[]) has a strange difference here:
parameterTypeName: [B
signature[index].getClassName(): byte[]
So I think this might be related to the asm usage
I *think* instead of signature[index].getClassName() there should be
called
signature[index].getDescriptor()
Any idea how I could work around that problem (without changing my
method's signature)?
Thanks,
Johannes
[1]
[ERROR] Failed to execute goal
org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found. - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.felix:maven-scr-plugin:1.8.0:scr
(generate-scr-scrdescriptor) on project test-utils:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException:
com.cedarsoft.serialization.test.utils.AbstractSerializerTest2 :
Annotated method create not found.
at
org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:222)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.felix.scrplugin.SCRDescriptorException:
Annotated method create not found.
at
org.apache.felix.scrplugin.helper.ClassScanner.extractAnnotation(ClassScanner.java:249)
at
org.apache.felix.scrplugin.helper.ClassScanner.processClass(ClassScanner.java:180)
at
org.apache.felix.scrplugin.helper.ClassScanner.scanSources(ClassScanner.java:143)
at
org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:154)
at
