Board report time again
I've taken a quick stab at our initial board report here: https://cwiki.apache.org/confluence/display/FELIX/Board+Report+%282010-09%29 Please help me with any community and/or software contributions that I may have forgotten about. Thanks! -> richard
[jira] Updated: (FELIX-2522) sigil build requires buildQualifer to be set as a -D flag to ant in order to properly override default .SNAPSHOT qualifier
[
https://issues.apache.org/jira/browse/FELIX-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage updated FELIX-2522:
Fix Version/s: (was: sigil-1.0.0)
move to unscheduled for time being to aid release planning
> sigil build requires buildQualifer to be set as a -D flag to ant in order to
> properly override default .SNAPSHOT qualifier
> --
>
> Key: FELIX-2522
> URL: https://issues.apache.org/jira/browse/FELIX-2522
> Project: Felix
> Issue Type: Improvement
> Components: Sigil
>Reporter: David Savage
>Priority: Minor
>
> In order to build a "valid"/useful set of bundles for install into eclipse
> the bundle filename must be of the form _maj.min.min.qualifier and this
> must match the Bundle_SymbolicName and Bundle_Version attributes in the
> bundle manifest.
> The sigil build defaults to setting the qualifier to .SNAPSHOT in the
> bldcommon/build.properties file
> However if a .SNAPSHOT version is installed in eclipse then it can never be
> updated as eclipse sees other snapshots as being equivalent. Therefore the
> release script I run to build a release has the following:
> $ more release.sh
> now=$(date +%Y%m%d_%H%M%S)
> ant -DbuildQualifier=$now clean dist $*
> It would be better to use the option of ant but this doesn't seem
> to work properly
> I've added:
> $ svn diff bldcommon/build.properties build.xml
> Index: bldcommon/build.properties
> ===
> --- bldcommon/build.properties (revision 982153)
> +++ bldcommon/build.properties (working copy)
> @@ -2,7 +2,7 @@
> # easier to set here than in xml file
>
> buildRelease= 0.9.0
> -buildQualifier = SNAPSHOT
> +#buildQualifier = SNAPSHOT
> buildVersion= ${buildRelease}.${buildQualifier}
>
> # set common.dir when used without ant (e.g. IvyDE)
> Index: build.xml
> ===
> --- build.xml (revision 982153)
> +++ build.xml (working copy)
> @@ -21,6 +21,9 @@
>xmlns:ivy="antlib:org.apache.ivy.ant"
>xmlns:groovy="antlib:org.codehaus.groovy">
>
> +
> +
> +
>
>
>
> @@ -31,6 +34,9 @@
>
>
>
> +
> +DEBUG ${buildQualifier}
> +
>
>
>
> This results in the file name being created with the correct version but the
> Bundle-Version - set from sigil-defaults.properties is still set to .SNAPSHOT
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1678) Update sigil properties file format to reuse as much grammar as possible from bnd properties file format
[ https://issues.apache.org/jira/browse/FELIX-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage updated FELIX-1678: Fix Version/s: (was: sigil-1.0.0) move to unscheduled for time being to aid release planning > Update sigil properties file format to reuse as much grammar as possible from > bnd properties file format > > > Key: FELIX-1678 > URL: https://issues.apache.org/jira/browse/FELIX-1678 > Project: Felix > Issue Type: Improvement > Components: Sigil >Reporter: David Savage > > Will create sub tasks to monitor progress towards this goal -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse
[ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage updated FELIX-1324: Fix Version/s: (was: sigil-1.0.0) move to unscheduled for time being to aid release planning > Add support for runtime debug/launch of felix via eclipse > - > > Key: FELIX-1324 > URL: https://issues.apache.org/jira/browse/FELIX-1324 > Project: Felix > Issue Type: New Feature > Components: Sigil >Reporter: David Savage >Assignee: David Savage > > Sigil previously had the ability to launch and debug a Newton OSGi container. > This has been removed in the port to apache as it brought in dependencies on > a product that was not compatible with the apache licence. > Should be possible to rebuild this using existing felix tools -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1697) Sigil variable substitution at ant properties level does not work when loaded via ivysettings
[
https://issues.apache.org/jira/browse/FELIX-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage updated FELIX-1697:
Fix Version/s: (was: sigil-1.0.0)
move to unscheduled for time being to aid release planning
> Sigil variable substitution at ant properties level does not work when loaded
> via ivysettings
> -
>
> Key: FELIX-1697
> URL: https://issues.apache.org/jira/browse/FELIX-1697
> Project: Felix
> Issue Type: Improvement
> Components: Sigil
>Reporter: David Savage
>Priority: Minor
>
> Specifically bldcommon/sigil-repos.properties contains entries of the form:
> bld-ant;dir:${cache.dir:-${..}/cache}/ant/lib
> This is correctly substituted if set at the System properties level i.e.
> ANT_OPTS=-Dcache.dir=/var/tmp/sigil/cache ant clean dist
> But not if set at the ant properties level
> ant -Dcache.dir=/var/tmp/sigil/cache clean dist
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1587) Setup server side build of sigil to publish artifacts
[ https://issues.apache.org/jira/browse/FELIX-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage updated FELIX-1587: Fix Version/s: (was: sigil-1.0.0) move to unscheduled for time being to aid release planning > Setup server side build of sigil to publish artifacts > - > > Key: FELIX-1587 > URL: https://issues.apache.org/jira/browse/FELIX-1587 > Project: Felix > Issue Type: Task > Components: Sigil >Reporter: David Savage >Assignee: David Savage > > The sigil build now generates a number of artifacts to > $felix-svn/sigil/site/** these are usable bundles but there is currently no > way to automatically build them at apache and make them available. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2416) iPOJO Dependency classloaders (for smart proxies, nullables, and dynamic proxies) should shortcut 'com.sun.reflect' loading to the system classloader
[ https://issues.apache.org/jira/browse/FELIX-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-2416. > iPOJO Dependency classloaders (for smart proxies, nullables, and dynamic > proxies) should shortcut 'com.sun.reflect' loading to the system classloader > - > > Key: FELIX-2416 > URL: https://issues.apache.org/jira/browse/FELIX-2416 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The proxy cannot load sun.reflect classes. To avoid that, such loading > request should be delegated to the system classloader. > ava.lang.NoClassDefFoundError: sun/reflect/MethodAccessorImpl at > sun.misc.Unsafe.defineClass(Native Method) at > sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at > sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) > at java.security.AccessController.doPrivileged(Native Method) at > sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) > at > sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorGenerator.java:59) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:28) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) at > org.jabsorb.serializer.AccessibleObjectResolver.invokeAccessibleObject(AccessibleObjectResolver.java:161) > at org.jabsorb.JSONRPCBridge.call(JSONRPCBridge.java:548) at > org.jabsorb.JSONRPCServlet.service(JSONRPCServlet.java:289) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at > org.mortbay.jetty.servlet.OsgiServletHolder.handle(OsgiServletHolder.java:101) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363) > at > org.mortbay.jetty.servlet.OsgiServletHandler.handle(OsgiServletHandler.java:117) > at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:324) at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741) at > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213) at > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403) at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) > Caused by: java.lang.ClassNotFoundException: sun.reflect.MethodAccessorImpl > at > org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:814) > at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61) at > org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at > org.apache.felix.ipojo.handlers.dependency.Dependency$SmartProxyFactory.loadClass(Dependency.java:900) > ... 28 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2485) Improve the performance of the manipulator on large files
[ https://issues.apache.org/jira/browse/FELIX-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-2485. > Improve the performance of the manipulator on large files > - > > Key: FELIX-2485 > URL: https://issues.apache.org/jira/browse/FELIX-2485 > Project: Felix > Issue Type: Improvement > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The manipulator manipulates jar files. To achieve this task the jar files is > firs tunzipped and then recreated. During this re-jarization, the performance > of the class / files copies can be improved by using a buffered copy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2568) Rename Transactionnal to Transactional
[ https://issues.apache.org/jira/browse/FELIX-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier updated FELIX-2568: - Fix Version/s: iPOJO-1.8.0 > Rename Transactionnal to Transactional > -- > > Key: FELIX-2568 > URL: https://issues.apache.org/jira/browse/FELIX-2568 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Aleksander Bandelj >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > Transactional is the correct spelling -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2416) iPOJO Dependency classloaders (for smart proxies, nullables, and dynamic proxies) should shortcut 'com.sun.reflect' loading to the system classloader
[ https://issues.apache.org/jira/browse/FELIX-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905866#action_12905866 ] Clement Escoffier commented on FELIX-2416: -- Included in the 1.6.4 releases > iPOJO Dependency classloaders (for smart proxies, nullables, and dynamic > proxies) should shortcut 'com.sun.reflect' loading to the system classloader > - > > Key: FELIX-2416 > URL: https://issues.apache.org/jira/browse/FELIX-2416 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The proxy cannot load sun.reflect classes. To avoid that, such loading > request should be delegated to the system classloader. > ava.lang.NoClassDefFoundError: sun/reflect/MethodAccessorImpl at > sun.misc.Unsafe.defineClass(Native Method) at > sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at > sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) > at java.security.AccessController.doPrivileged(Native Method) at > sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) > at > sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorGenerator.java:59) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:28) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) at > org.jabsorb.serializer.AccessibleObjectResolver.invokeAccessibleObject(AccessibleObjectResolver.java:161) > at org.jabsorb.JSONRPCBridge.call(JSONRPCBridge.java:548) at > org.jabsorb.JSONRPCServlet.service(JSONRPCServlet.java:289) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at > org.mortbay.jetty.servlet.OsgiServletHolder.handle(OsgiServletHolder.java:101) > at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363) > at > org.mortbay.jetty.servlet.OsgiServletHandler.handle(OsgiServletHandler.java:117) > at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) > at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:324) at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879) > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:741) at > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213) at > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403) at > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) > Caused by: java.lang.ClassNotFoundException: sun.reflect.MethodAccessorImpl > at > org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:814) > at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61) at > org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at > org.apache.felix.ipojo.handlers.dependency.Dependency$SmartProxyFactory.loadClass(Dependency.java:900) > ... 28 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2561) Properties set as required instead of optional in the component type descriptions
[ https://issues.apache.org/jira/browse/FELIX-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-2561. > Properties set as required instead of optional in the component type > descriptions > -- > > Key: FELIX-2561 > URL: https://issues.apache.org/jira/browse/FELIX-2561 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The component type description lists component types properties. However, > optional properties without default values are set as 'REQUIRED' instead of > optional. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2430) IPOJO manipulation (ant task) results in invalid classes throwing java.lang.VerifyError at runtime in InstanceManager (line 584)
[ https://issues.apache.org/jira/browse/FELIX-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905862#action_12905862 ] Clement Escoffier commented on FELIX-2430: -- Included in the 1.6.4 releases > IPOJO manipulation (ant task) results in invalid classes throwing > java.lang.VerifyError at runtime in InstanceManager (line 584) > > > Key: FELIX-2430 > URL: https://issues.apache.org/jira/browse/FELIX-2430 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.4.0, iPOJO-1.6.0 >Reporter: Frederic Desmons >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > Attachments: ipojo-2430-verify_error.zip > > > Logs: > [ERROR] ipojo.SecurityErrorRaisingIPOJOService : > [ipojo.SecurityErrorRaisingIPOJOService-0] createInstance -> The POJO > constructor invocation failed : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack > java.lang.VerifyError: (class: ipojo/SecurityErrorRaisingIPOJOService, > method: signature: (Lorg/apache/felix/ipojo/InstanceManager;)V) > Expecting to find object/array on stack caught here: > java.lang.Class.getDeclaredConstructors0(Native Method) > java.lang.Class.privateGetDeclaredConstructors(Unknown Source) > java.lang.Class.getConstructor0(Unknown Source) > java.lang.Class.getDeclaredConstructor(Unknown Source) > org.apache.felix.ipojo.InstanceManager.createObject(InstanceManager.java:584) > org.apache.felix.ipojo.InstanceManager.getPojoObject(InstanceManager.java:777) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.__stateChanged(LifecycleCallbackHandler.java:156) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.stateChanged(LifecycleCallbackHandler.java) > org.apache.felix.ipojo.InstanceManager.setState(InstanceManager.java:441) > org.apache.felix.ipojo.InstanceManager.start(InstanceManager.java:322) > org.apache.felix.ipojo.ComponentFactory.createInstance(ComponentFactory.java:155) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:301) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:238) > > org.apache.felix.ipojo.InstanceCreator$ManagedInstance.create(InstanceCreator.java:343) > org.apache.felix.ipojo.InstanceCreator.addInstance(InstanceCreator.java:89) > org.apache.felix.ipojo.Extender.parse(Extender.java:269) > org.apache.felix.ipojo.Extender.startManagementFor(Extender.java:208) > org.apache.felix.ipojo.Extender.access$600(Extender.java:52) > org.apache.felix.ipojo.Extender$CreatorThread.run(Extender.java:682) > java.lang.Thread.run(Unknown Source) > [ERROR] ipojo.SecurityErrorRaisingIPOJOService : Cannot create a POJO > instance, the POJO constructor invocation has thrown an exception : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack > java.lang.RuntimeException: Cannot create a POJO instance, the POJO > constructor invocation has thrown an exception : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack caught here: > org.apache.felix.ipojo.InstanceManager.createObject(InstanceManager.java:640) > org.apache.felix.ipojo.InstanceManager.getPojoObject(InstanceManager.java:777) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.__stateChanged(LifecycleCallbackHandler.java:156) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.stateChanged(LifecycleCallbackHandler.java) > org.apache.felix.ipojo.InstanceManager.setState(InstanceManager.java:441) > org.apache.felix.ipojo.InstanceManager.start(InstanceManager.java:322) > org.apache.felix.ipojo.ComponentFactory.createInstance(ComponentFactory.java:155) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:301) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:238) > > org.apache.felix.ipojo.InstanceCreator$ManagedInstance.create(InstanceCreator.java:343) > org.apache.felix.ipojo.InstanceCreator.addInstance(InstanceCreator.java:89) > org.apache.felix.ipojo.Extender.parse(Extender.java:269) > org.apache.felix.ipojo.Extender.startManagementFor(Extender.java:208) > org.apache.felix.ipojo.Extender.access$600(Extender.java:52) > org.apache.felix.ipojo.Extender$CreatorThread.run(Extender.java:682) > java.lang.Thread.run(Unknown Source) > [ERROR] ipojo.SecurityErrorRa
[jira] Commented: (FELIX-2561) Properties set as required instead of optional in the component type descriptions
[ https://issues.apache.org/jira/browse/FELIX-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905864#action_12905864 ] Clement Escoffier commented on FELIX-2561: -- Included in the 1.6.4 releases > Properties set as required instead of optional in the component type > descriptions > -- > > Key: FELIX-2561 > URL: https://issues.apache.org/jira/browse/FELIX-2561 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The component type description lists component types properties. However, > optional properties without default values are set as 'REQUIRED' instead of > optional. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2485) Improve the performance of the manipulator on large files
[ https://issues.apache.org/jira/browse/FELIX-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905865#action_12905865 ] Clement Escoffier commented on FELIX-2485: -- Included in the 1.6.4 releases > Improve the performance of the manipulator on large files > - > > Key: FELIX-2485 > URL: https://issues.apache.org/jira/browse/FELIX-2485 > Project: Felix > Issue Type: Improvement > Components: iPOJO >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > > The manipulator manipulates jar files. To achieve this task the jar files is > firs tunzipped and then recreated. During this re-jarization, the performance > of the class / files copies can be improved by using a buffered copy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2542) Annotations on methods parameters are not moved on public methods after manipulation
[
https://issues.apache.org/jira/browse/FELIX-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier closed FELIX-2542.
> Annotations on methods parameters are not moved on public methods after
> manipulation
>
>
> Key: FELIX-2542
> URL: https://issues.apache.org/jira/browse/FELIX-2542
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
>Affects Versions: iPOJO-1.6.0
> Environment: Win xp, java 1.6
>Reporter: Nicolas Dumont
>Assignee: Clement Escoffier
>Priority: Minor
> Fix For: iPOJO-1.8.0
>
>
> The iPojo byte code manipulation replace real public method with private one,
> and annotation on methods are moved to the new public methods. But this
> behavior is not used for parameters annotations.
> For exemple :
> public class MyClass {
> @MyAnnotation
> public void myMethod(@MyParameterAnnotation int param) {
> //my code here
> }
> }
> is transformed into:
> public class MyClass {
> @MyAnnotation
> public void myMethod(int param) {
> // iPojo code here
> }
> private void _myMethod(@MyParameterAnnotation int param) {
>// my code here
> }
> It should have been transformed into:
> public class MyClass {
> @MyAnnotation
> public void myMethod(@MyParameterAnnotation int param) {
> // iPojo code here
> }
> private void _myMethod(int param) {
>// my code here
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2420) Enum support for @Property annotation
[ https://issues.apache.org/jira/browse/FELIX-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905861#action_12905861 ] Clement Escoffier commented on FELIX-2420: -- Included in the 1.6.4 releases > Enum support for @Property annotation > - > > Key: FELIX-2420 > URL: https://issues.apache.org/jira/browse/FELIX-2420 > Project: Felix > Issue Type: Improvement > Components: iPOJO >Reporter: Joel Schuster >Assignee: Clement Escoffier >Priority: Minor > Fix For: iPOJO-1.8.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > It would be nice if the @Property annotation would support Enum types as well > as the String and numeric types. > Ideally the value would be taken as a String or numeric and the appropriate > Enum would be chosen based on the valueOf method or the ordinal. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2430) IPOJO manipulation (ant task) results in invalid classes throwing java.lang.VerifyError at runtime in InstanceManager (line 584)
[ https://issues.apache.org/jira/browse/FELIX-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-2430. > IPOJO manipulation (ant task) results in invalid classes throwing > java.lang.VerifyError at runtime in InstanceManager (line 584) > > > Key: FELIX-2430 > URL: https://issues.apache.org/jira/browse/FELIX-2430 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: iPOJO-1.4.0, iPOJO-1.6.0 >Reporter: Frederic Desmons >Assignee: Clement Escoffier > Fix For: iPOJO-1.8.0 > > Attachments: ipojo-2430-verify_error.zip > > > Logs: > [ERROR] ipojo.SecurityErrorRaisingIPOJOService : > [ipojo.SecurityErrorRaisingIPOJOService-0] createInstance -> The POJO > constructor invocation failed : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack > java.lang.VerifyError: (class: ipojo/SecurityErrorRaisingIPOJOService, > method: signature: (Lorg/apache/felix/ipojo/InstanceManager;)V) > Expecting to find object/array on stack caught here: > java.lang.Class.getDeclaredConstructors0(Native Method) > java.lang.Class.privateGetDeclaredConstructors(Unknown Source) > java.lang.Class.getConstructor0(Unknown Source) > java.lang.Class.getDeclaredConstructor(Unknown Source) > org.apache.felix.ipojo.InstanceManager.createObject(InstanceManager.java:584) > org.apache.felix.ipojo.InstanceManager.getPojoObject(InstanceManager.java:777) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.__stateChanged(LifecycleCallbackHandler.java:156) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.stateChanged(LifecycleCallbackHandler.java) > org.apache.felix.ipojo.InstanceManager.setState(InstanceManager.java:441) > org.apache.felix.ipojo.InstanceManager.start(InstanceManager.java:322) > org.apache.felix.ipojo.ComponentFactory.createInstance(ComponentFactory.java:155) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:301) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:238) > > org.apache.felix.ipojo.InstanceCreator$ManagedInstance.create(InstanceCreator.java:343) > org.apache.felix.ipojo.InstanceCreator.addInstance(InstanceCreator.java:89) > org.apache.felix.ipojo.Extender.parse(Extender.java:269) > org.apache.felix.ipojo.Extender.startManagementFor(Extender.java:208) > org.apache.felix.ipojo.Extender.access$600(Extender.java:52) > org.apache.felix.ipojo.Extender$CreatorThread.run(Extender.java:682) > java.lang.Thread.run(Unknown Source) > [ERROR] ipojo.SecurityErrorRaisingIPOJOService : Cannot create a POJO > instance, the POJO constructor invocation has thrown an exception : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack > java.lang.RuntimeException: Cannot create a POJO instance, the POJO > constructor invocation has thrown an exception : (class: > ipojo/SecurityErrorRaisingIPOJOService, method: signature: > (Lorg/apache/felix/ipojo/InstanceManager;)V) Expecting to find object/array > on stack caught here: > org.apache.felix.ipojo.InstanceManager.createObject(InstanceManager.java:640) > org.apache.felix.ipojo.InstanceManager.getPojoObject(InstanceManager.java:777) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.__stateChanged(LifecycleCallbackHandler.java:156) > > org.apache.felix.ipojo.handlers.lifecycle.callback.LifecycleCallbackHandler.stateChanged(LifecycleCallbackHandler.java) > org.apache.felix.ipojo.InstanceManager.setState(InstanceManager.java:441) > org.apache.felix.ipojo.InstanceManager.start(InstanceManager.java:322) > org.apache.felix.ipojo.ComponentFactory.createInstance(ComponentFactory.java:155) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:301) > > org.apache.felix.ipojo.IPojoFactory.createComponentInstance(IPojoFactory.java:238) > > org.apache.felix.ipojo.InstanceCreator$ManagedInstance.create(InstanceCreator.java:343) > org.apache.felix.ipojo.InstanceCreator.addInstance(InstanceCreator.java:89) > org.apache.felix.ipojo.Extender.parse(Extender.java:269) > org.apache.felix.ipojo.Extender.startManagementFor(Extender.java:208) > org.apache.felix.ipojo.Extender.access$600(Extender.java:52) > org.apache.felix.ipojo.Extender$CreatorThread.run(Extender.java:682) > java.lang.Thread.run(Unknown Source) > [ERROR] ipojo.SecurityErrorRaisingIPOJOService : Cannot create a POJO > instance, the POJO constructor invocation has
[jira] Commented: (FELIX-2542) Annotations on methods parameters are not moved on public methods after manipulation
[
https://issues.apache.org/jira/browse/FELIX-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905863#action_12905863
]
Clement Escoffier commented on FELIX-2542:
--
Included in the 1.6.4 releases
> Annotations on methods parameters are not moved on public methods after
> manipulation
>
>
> Key: FELIX-2542
> URL: https://issues.apache.org/jira/browse/FELIX-2542
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
>Affects Versions: iPOJO-1.6.0
> Environment: Win xp, java 1.6
>Reporter: Nicolas Dumont
>Assignee: Clement Escoffier
>Priority: Minor
> Fix For: iPOJO-1.8.0
>
>
> The iPojo byte code manipulation replace real public method with private one,
> and annotation on methods are moved to the new public methods. But this
> behavior is not used for parameters annotations.
> For exemple :
> public class MyClass {
> @MyAnnotation
> public void myMethod(@MyParameterAnnotation int param) {
> //my code here
> }
> }
> is transformed into:
> public class MyClass {
> @MyAnnotation
> public void myMethod(int param) {
> // iPojo code here
> }
> private void _myMethod(@MyParameterAnnotation int param) {
>// my code here
> }
> It should have been transformed into:
> public class MyClass {
> @MyAnnotation
> public void myMethod(@MyParameterAnnotation int param) {
> // iPojo code here
> }
> private void _myMethod(int param) {
>// my code here
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2461) Allow specifying the targeted service interface in the @ServiceController
[
https://issues.apache.org/jira/browse/FELIX-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier closed FELIX-2461.
> Allow specifying the targeted service interface in the @ServiceController
> -
>
> Key: FELIX-2461
> URL: https://issues.apache.org/jira/browse/FELIX-2461
> Project: Felix
> Issue Type: New Feature
> Components: iPOJO
>Reporter: Clement Escoffier
>Assignee: Clement Escoffier
> Fix For: iPOJO-1.8.0
>
>
> The @serviceController annotation does not allow to set the targeted
> specification. By adding a 'specification' attribute, the controller can be
> assigned to control one interface only and then allowing fine tuning like:
> @Component
> @Provides
> public class MyClass implements Service1, Service2 {
> @ServiceController(specification=Service1.class)
> boolean m_controller1;
> @ServiceController(specification=Service2.class)
> boolean m_controller2;
> }
> If no 'specification' set, all not-already-targeted interfaces are targeted.
> @Component
> @Provides
> public class MyClass implements Service1, Service2, Service3 {
> @ServiceController(specification=Service1.class)
> boolean m_controller1;
> @ServiceController // Control Service2 and Service 3
> boolean m_controller2;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2461) Allow specifying the targeted service interface in the @ServiceController
[
https://issues.apache.org/jira/browse/FELIX-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905860#action_12905860
]
Clement Escoffier commented on FELIX-2461:
--
Included in the 1.6.4 releases
> Allow specifying the targeted service interface in the @ServiceController
> -
>
> Key: FELIX-2461
> URL: https://issues.apache.org/jira/browse/FELIX-2461
> Project: Felix
> Issue Type: New Feature
> Components: iPOJO
>Reporter: Clement Escoffier
>Assignee: Clement Escoffier
> Fix For: iPOJO-1.8.0
>
>
> The @serviceController annotation does not allow to set the targeted
> specification. By adding a 'specification' attribute, the controller can be
> assigned to control one interface only and then allowing fine tuning like:
> @Component
> @Provides
> public class MyClass implements Service1, Service2 {
> @ServiceController(specification=Service1.class)
> boolean m_controller1;
> @ServiceController(specification=Service2.class)
> boolean m_controller2;
> }
> If no 'specification' set, all not-already-targeted interfaces are targeted.
> @Component
> @Provides
> public class MyClass implements Service1, Service2, Service3 {
> @ServiceController(specification=Service1.class)
> boolean m_controller1;
> @ServiceController // Control Service2 and Service 3
> boolean m_controller2;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2420) Enum support for @Property annotation
[ https://issues.apache.org/jira/browse/FELIX-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-2420. > Enum support for @Property annotation > - > > Key: FELIX-2420 > URL: https://issues.apache.org/jira/browse/FELIX-2420 > Project: Felix > Issue Type: Improvement > Components: iPOJO >Reporter: Joel Schuster >Assignee: Clement Escoffier >Priority: Minor > Fix For: iPOJO-1.8.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > It would be nice if the @Property annotation would support Enum types as well > as the String and numeric types. > Ideally the value would be taken as a String or numeric and the appropriate > Enum would be chosen based on the valueOf method or the ordinal. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2568) Rename Transactionnal to Transactional
[ https://issues.apache.org/jira/browse/FELIX-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier updated FELIX-2568: - Assignee: Clement Escoffier > Rename Transactionnal to Transactional > -- > > Key: FELIX-2568 > URL: https://issues.apache.org/jira/browse/FELIX-2568 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Aleksander Bandelj >Assignee: Clement Escoffier > > Transactional is the correct spelling -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Felix iPOJO Core, Manipulator and Annotations 1.6.4
On 01.09.2010, at 21:27, Richard S. Hall wrote: > +1 > > The DEPS file for Manipulator mentions Apache software in the "Used > Third-Party Software" section, but Apache software isn't third party since > this is an Apache release. For Apache software we have a single catch all at > the beginning of the DEPS file. Not a big deal, though. Thanks, I've modified the file in the trunk. Clement > > -> richard > > On 8/29/10 6:08, Clement Escoffier wrote: >> I'd like to call a vote on a couple of iPOJO sub-projects releases. The >> following issues have been addressed: >> - FELIX-2420 Enum support for @Property annotation >> - FELIX-2430 IPOJO manipulation (ant task) results in invalid classes >> throwing java.lang.VerifyError at runtime in InstanceManager (line 584) >> - FELIX-2461 Allow specifying the targeted service interface in the >> @ServiceController >> - FELIX-2485 Improve the performance of the manipulator on large files >> - FELIX-2542 Annotations on methods parameters are not moved on public >> methods after manipulation >> - FELIX-2561 Properties set as required instead of optional in the >> component type descriptions >> >> Three sub-projects are impacted: >> - Apache Felix iPOJO Core >> - Apache Felix iPOJO Manipulator >> - Apache Felix iPOJO Annotations >> >> >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachefelix-155/ >> >> 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 155 /tmp/felix-staging >> >> Please vote to approve this release: >> >> [ ] +1 Approve the release >> [ ] -1 Veto the release (please provide specific comments)
Re: [VOTE][RESULT] Release Apache Felix iPOJO Core, Manipulator and Annotations 1.6.4
Time to close the vote on the Felix iPOJO Core, Manipulator and Annotations 1.6.4 subproject releases. * +1 votes from Richard S. Hall, Karl Pauls, Carsten Ziegeler and Clement Escoffier * No other votes The vote is successful. I will make the release artifacts available as soon as possible. Thanks and Regards, Clement On 03.09.2010, at 12:17, Clement Escoffier wrote: > +1, > > Regards, > > Clement > > > On 03.09.2010, at 10:53, Carsten Ziegeler wrote: > >> +1 >> >> Carsten >> >> Karl Pauls wrote >>> +1 >>> >>> regards, >>> >>> Karl >>> >>> On Wed, Sep 1, 2010 at 9:27 PM, Richard S. Hall >>> wrote: +1 The DEPS file for Manipulator mentions Apache software in the "Used Third-Party Software" section, but Apache software isn't third party since this is an Apache release. For Apache software we have a single catch all at the beginning of the DEPS file. Not a big deal, though. -> richard On 8/29/10 6:08, Clement Escoffier wrote: > > I'd like to call a vote on a couple of iPOJO sub-projects releases. The > following issues have been addressed: > - FELIX-2420 Enum support for @Property annotation > - FELIX-2430 IPOJO manipulation (ant task) results in invalid classes > throwing java.lang.VerifyError at runtime in InstanceManager (line 584) > - FELIX-2461 Allow specifying the targeted service interface in the > @ServiceController > - FELIX-2485 Improve the performance of the manipulator on large files > - FELIX-2542 Annotations on methods parameters are not moved on public > methods after manipulation > - FELIX-2561 Properties set as required instead of optional in the > component type descriptions > > Three sub-projects are impacted: > - Apache Felix iPOJO Core > - Apache Felix iPOJO Manipulator > - Apache Felix iPOJO Annotations > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-155/ > > 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 155 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) >>> >>> >>> >> >> >> -- >> Carsten Ziegeler >> cziege...@apache.org >
[jira] Resolved: (FELIX-2576) NewSigilProjectWizard should allow bundle symbolic name to be set separately to project name
[ https://issues.apache.org/jira/browse/FELIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage resolved FELIX-2576. - Assignee: David Savage Fix Version/s: sigil-1.0.0 Resolution: Fixed > NewSigilProjectWizard should allow bundle symbolic name to be set separately > to project name > > > Key: FELIX-2576 > URL: https://issues.apache.org/jira/browse/FELIX-2576 > Project: Felix > Issue Type: Improvement > Components: Sigil >Reporter: David Savage >Assignee: David Savage >Priority: Trivial > Fix For: sigil-1.0.0 > > > currently bsn defaults to the name of the project but this is not always > desirable - provide way to set it explicitly to something else when creating > a project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2575) new project wizard creates duplicate src entries and empty headers
[ https://issues.apache.org/jira/browse/FELIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage resolved FELIX-2575. - Assignee: David Savage Fix Version/s: sigil-1.0.0 Resolution: Fixed > new project wizard creates duplicate src entries and empty headers > -- > > Key: FELIX-2575 > URL: https://issues.apache.org/jira/browse/FELIX-2575 > Project: Felix > Issue Type: Bug > Components: Sigil >Reporter: David Savage >Assignee: David Savage >Priority: Minor > Fix For: sigil-1.0.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2574) NPE in background task when sigil project is deleted from workspace
[ https://issues.apache.org/jira/browse/FELIX-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage resolved FELIX-2574. - Fix Version/s: sigil-1.0.0 Resolution: Fixed > NPE in background task when sigil project is deleted from workspace > --- > > Key: FELIX-2574 > URL: https://issues.apache.org/jira/browse/FELIX-2574 > Project: Felix > Issue Type: Bug > Components: Sigil >Reporter: David Savage >Priority: Minor > Fix For: sigil-1.0.0 > > > java.lang.NullPointerException >at > org.apache.felix.sigil.eclipse.internal.model.project.SigilProject.getBundle(SigilProject.java:369) >at > org.apache.felix.sigil.eclipse.job.ResolveProjectsJob.isDependent(ResolveProjectsJob.java:105) >at > org.apache.felix.sigil.eclipse.job.ResolveProjectsJob.runInWorkspace(ResolveProjectsJob.java:81) >at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) >at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Felix iPOJO Core, Manipulator and Annotations 1.6.4
+1, Regards, Clement On 03.09.2010, at 10:53, Carsten Ziegeler wrote: > +1 > > Carsten > > Karl Pauls wrote >> +1 >> >> regards, >> >> Karl >> >> On Wed, Sep 1, 2010 at 9:27 PM, Richard S. Hall wrote: >>> +1 >>> >>> The DEPS file for Manipulator mentions Apache software in the "Used >>> Third-Party Software" section, but Apache software isn't third party since >>> this is an Apache release. For Apache software we have a single catch all at >>> the beginning of the DEPS file. Not a big deal, though. >>> >>> -> richard >>> >>> On 8/29/10 6:08, Clement Escoffier wrote: I'd like to call a vote on a couple of iPOJO sub-projects releases. The following issues have been addressed: - FELIX-2420 Enum support for @Property annotation - FELIX-2430 IPOJO manipulation (ant task) results in invalid classes throwing java.lang.VerifyError at runtime in InstanceManager (line 584) - FELIX-2461 Allow specifying the targeted service interface in the @ServiceController - FELIX-2485 Improve the performance of the manipulator on large files - FELIX-2542 Annotations on methods parameters are not moved on public methods after manipulation - FELIX-2561 Properties set as required instead of optional in the component type descriptions Three sub-projects are impacted: - Apache Felix iPOJO Core - Apache Felix iPOJO Manipulator - Apache Felix iPOJO Annotations Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-155/ 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 155 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) >>> >> >> >> > > > -- > Carsten Ziegeler > cziege...@apache.org
[jira] Created: (FELIX-2577) NPE if eclipse plugins are updated vs installed and rebooted
NPE if eclipse plugins are updated vs installed and rebooted Key: FELIX-2577 URL: https://issues.apache.org/jira/browse/FELIX-2577 Project: Felix Issue Type: Bug Components: Sigil Reporter: David Savage Priority: Minor java.lang.NullPointerException at org.apache.felix.sigil.eclipse.ui.internal.views.RepositoryViewPart.dispose(RepositoryViewPart.java:224) at org.eclipse.ui.internal.WorkbenchPartReference.doDisposePart(WorkbenchPartReference.java:737) at org.eclipse.ui.internal.ViewReference.doDisposePart(ViewReference.java:101) at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:684) at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1715) at org.eclipse.ui.internal.WorkbenchPage.partRemoved(WorkbenchPage.java:1707) at org.eclipse.ui.internal.ViewFactory.releaseView(ViewFactory.java:257) at org.eclipse.ui.internal.Perspective.dispose(Perspective.java:293) at org.eclipse.ui.internal.WorkbenchPage.disposePerspective(WorkbenchPage.java:1850) at org.eclipse.ui.internal.WorkbenchPage.closePerspective(WorkbenchPage.java:1583) at org.eclipse.ui.internal.WorkbenchPage.closePerspective(WorkbenchPage.java:1500) at org.eclipse.ui.internal.WorkbenchPage.closePerspective(WorkbenchPage.java:1455) at org.eclipse.ui.internal.handlers.ClosePerspectiveHandler.closePerspective(ClosePerspectiveHandler.java:67) at org.eclipse.ui.internal.registry.PerspectiveRegistry.removeExtension(PerspectiveRegistry.java:728) at org.eclipse.ui.internal.registry.UIExtensionTracker$1.run(UIExtensionTracker.java:46) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:155) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3405) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3102) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2576) NewSigilProjectWizard should allow bundle symbolic name to be set separately to project name
NewSigilProjectWizard should allow bundle symbolic name to be set separately to project name Key: FELIX-2576 URL: https://issues.apache.org/jira/browse/FELIX-2576 Project: Felix Issue Type: Improvement Components: Sigil Reporter: David Savage Priority: Trivial currently bsn defaults to the name of the project but this is not always desirable - provide way to set it explicitly to something else when creating a project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Felix iPOJO Core, Manipulator and Annotations 1.6.4
+1 Carsten Karl Pauls wrote > +1 > > regards, > > Karl > > On Wed, Sep 1, 2010 at 9:27 PM, Richard S. Hall wrote: >> +1 >> >> The DEPS file for Manipulator mentions Apache software in the "Used >> Third-Party Software" section, but Apache software isn't third party since >> this is an Apache release. For Apache software we have a single catch all at >> the beginning of the DEPS file. Not a big deal, though. >> >> -> richard >> >> On 8/29/10 6:08, Clement Escoffier wrote: >>> >>> I'd like to call a vote on a couple of iPOJO sub-projects releases. The >>> following issues have been addressed: >>> - FELIX-2420 Enum support for @Property annotation >>> - FELIX-2430 IPOJO manipulation (ant task) results in invalid classes >>> throwing java.lang.VerifyError at runtime in InstanceManager (line 584) >>> - FELIX-2461 Allow specifying the targeted service interface in the >>> @ServiceController >>> - FELIX-2485 Improve the performance of the manipulator on large files >>> - FELIX-2542 Annotations on methods parameters are not moved on public >>> methods after manipulation >>> - FELIX-2561 Properties set as required instead of optional in the >>> component type descriptions >>> >>> Three sub-projects are impacted: >>> - Apache Felix iPOJO Core >>> - Apache Felix iPOJO Manipulator >>> - Apache Felix iPOJO Annotations >>> >>> >>> Staging repository: >>> https://repository.apache.org/content/repositories/orgapachefelix-155/ >>> >>> 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 155 /tmp/felix-staging >>> >>> Please vote to approve this release: >>> >>> [ ] +1 Approve the release >>> [ ] -1 Veto the release (please provide specific comments) >> > > > -- Carsten Ziegeler cziege...@apache.org
[jira] Created: (FELIX-2575) new project wizard creates duplicate src entries and empty headers
new project wizard creates duplicate src entries and empty headers -- Key: FELIX-2575 URL: https://issues.apache.org/jira/browse/FELIX-2575 Project: Felix Issue Type: Bug Components: Sigil Reporter: David Savage Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2574) NPE in background task when sigil project is deleted from workspace
NPE in background task when sigil project is deleted from workspace --- Key: FELIX-2574 URL: https://issues.apache.org/jira/browse/FELIX-2574 Project: Felix Issue Type: Bug Components: Sigil Reporter: David Savage Priority: Minor java.lang.NullPointerException at org.apache.felix.sigil.eclipse.internal.model.project.SigilProject.getBundle(SigilProject.java:369) at org.apache.felix.sigil.eclipse.job.ResolveProjectsJob.isDependent(ResolveProjectsJob.java:105) at org.apache.felix.sigil.eclipse.job.ResolveProjectsJob.runInWorkspace(ResolveProjectsJob.java:81) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
