[jira] [Updated] (GERONIMO-6310) Server can not shutdown or deploy when enable configured encryption and JMX security at the same time

[ https://issues.apache.org/jira/browse/GERONIMO-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saphen Qiu updated GERONIMO-6310: - Attachment: ConfiguredEncryptionWithSecure.patch Make some updates Server

[jira] [Updated] (GERONIMO-6310) Server can not shutdown or deploy when enable configured encryption and JMX security at the same time

[ https://issues.apache.org/jira/browse/GERONIMO-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saphen Qiu updated GERONIMO-6310: - Attachment: (was: ConfiguredEncryptionANDsecure.patch) Server can not shutdown or

[jira] [Updated] (GERONIMO-6310) Server can not shutdown or deploy when enable configured encryption and JMX security at the same time

[ https://issues.apache.org/jira/browse/GERONIMO-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saphen Qiu updated GERONIMO-6310: - Attachment: (was: ConfiguredEncryptionWithSecure.patch) Server can not shutdown or

[jira] [Resolved] (GERONIMO-6055) improve server startup time

[ https://issues.apache.org/jira/browse/GERONIMO-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6055. --- Resolution: Fixed Fix Version/s: 3.0-beta-1 I think this task could be closed

[jira] [Resolved] (GERONIMO-6017) JAVA_HOME environment variable with blank spaces in Windows

[ https://issues.apache.org/jira/browse/GERONIMO-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6017. --- Resolution: Won't Fix Environment configuration issue, use Russell's way could build

[jira] [Resolved] (GERONIMO-5988) deploy:new-server-instance does not deploy a full new server instance

[ https://issues.apache.org/jira/browse/GERONIMO-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5988. --- Resolution: Duplicate deploy:new-server-instance does not deploy a full new server

[jira] [Commented] (GERONIMO-6287) Server instance which created by gogo command deploy:new-server-instance can't be started

[ https://issues.apache.org/jira/browse/GERONIMO-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240324#comment-13240324 ] Shawn Jiang commented on GERONIMO-6287: --- The patch

Re: Geronimo release cycle

1.x J2EE 1.4 2.0 Java EE 1.5 2.1 Java EE 1.5 2.2 Java EE 1.5 3.0 Java EE 1.6 Considering the previous practice, we'd better to move current trunk to 3.1 and change current beta branch to 3.0. On Tue, Mar 27, 2012 at 11:48 PM, Forrest Xia forres...@gmail.com wrote: Saw this query, have

Re: Geronimo release cycle

On Wed, Mar 28, 2012 at 6:08 PM, Shawn Jiang genspr...@gmail.com wrote: 1.x J2EE 1.4 2.0 Java EE 1.5 2.1 Java EE 1.5 2.2 Java EE 1.5 3.0 Java EE 1.6 Considering the previous practice, we'd better to move current trunk to 3.1 and change current beta branch to 3.0. Sounds good.

[jira] [Resolved] (GERONIMO-5979) Some objects to be injected were not found in jndi: No EJB found for reference

[ https://issues.apache.org/jira/browse/GERONIMO-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5979. --- Resolution: Fixed Fix Version/s: 3.0-beta-2 Fixed on samples side, however, there

[jira] [Resolved] (GERONIMO-5970) NoClassDefFoundError

[ https://issues.apache.org/jira/browse/GERONIMO-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5970. --- Resolution: Cannot Reproduce NoClassDefFoundError

[jira] [Commented] (GERONIMO-5960) Enable the functionality of add, edit, delete start/stop a broker in JMS portlets

[ https://issues.apache.org/jira/browse/GERONIMO-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240380#comment-13240380 ] Forrest Xia commented on GERONIMO-5960: --- Turning ActiveMQ module from blueprint

[jira] [Commented] (GERONIMO-5889) Avoid macros confusion with Tuscany templates

[ https://issues.apache.org/jira/browse/GERONIMO-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240386#comment-13240386 ] Forrest Xia commented on GERONIMO-5889: --- Jeff, can you take a look at this issue

[jira] [Resolved] (GERONIMO-5834) add a do not fail option for server startup

[ https://issues.apache.org/jira/browse/GERONIMO-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5834. --- Resolution: Duplicate Fix Version/s: 3.0-beta-2 GERONIMO-5802 provides a fix for

[jira] [Resolved] (GERONIMO-5822) Improve startup monitor

[ https://issues.apache.org/jira/browse/GERONIMO-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5822. --- Resolution: Won't Fix I used to --long option to show the startup progress for now. For

[jira] [Resolved] (GERONIMO-5762) Some dirty files in the root of server code tree after built, they cannot be cleaned by mvn clean

[ https://issues.apache.org/jira/browse/GERONIMO-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5762. --- Resolution: Won't Fix Some dirty files in the root of server code tree after built,

[jira] [Resolved] (GERONIMO-5744) bundle urls and 3rd party libraries

[ https://issues.apache.org/jira/browse/GERONIMO-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5744. --- Resolution: Fixed Fix Version/s: 3.0-beta-2 3.0 bundle

[jira] [Resolved] (GERONIMO-5553) Fail to enchance entities on Geronimo

[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5553. --- Resolution: Invalid Fail to enchance entities on Geronimo

[jira] [Resolved] (GERONIMO-5460) Update console-testsuite

[ https://issues.apache.org/jira/browse/GERONIMO-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5460. --- Resolution: Fixed Fix Version/s: 3.0-beta-1 Update console-testsuite

[jira] [Resolved] (GERONIMO-5262) Make testsuites run again

[ https://issues.apache.org/jira/browse/GERONIMO-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5262. --- Resolution: Fixed Make testsuites run again -

[jira] [Resolved] (GERONIMO-5220) mini-servers profile for plugin specific test servers

[ https://issues.apache.org/jira/browse/GERONIMO-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5220. --- Resolution: Fixed mini-servers profile for plugin specific test servers

[jira] [Resolved] (GERONIMO-5195) change txmanager component version(s) to larger major version

[ https://issues.apache.org/jira/browse/GERONIMO-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5195. --- Resolution: Fixed change txmanager component version(s) to larger major version

[jira] [Closed] (GERONIMO-5245) Version property variables should be used for all configuration versions in the framework startup.properties file.

[ https://issues.apache.org/jira/browse/GERONIMO-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5245. - Resolution: Fixed Version property variables should be used for all configuration

[jira] [Resolved] (GERONIMO-5090) Upgrade from java ee 5 to java ee 6 support

[ https://issues.apache.org/jira/browse/GERONIMO-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5090. --- Resolution: Fixed Upgrade from java ee 5 to java ee 6 support

[jira] [Resolved] (GERONIMO-5058) Move the term j2ee to javaee refered by plugin names and package names

[ https://issues.apache.org/jira/browse/GERONIMO-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5058. --- Resolution: Won't Fix Move the term j2ee to javaee refered by plugin names and

[jira] [Resolved] (GERONIMO-5051) Taglib discovery does not work

[ https://issues.apache.org/jira/browse/GERONIMO-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5051. --- Resolution: Fixed Taglib discovery does not work --

[jira] [Commented] (GERONIMO-6287) Server instance which created by gogo command deploy:new-server-instance can't be started

[ https://issues.apache.org/jira/browse/GERONIMO-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240477#comment-13240477 ] Russell E Glaue commented on GERONIMO-6287: --- I agree with the patch

[jira] [Issue Comment Edited] (GERONIMO-6287) Server instance which created by gogo command deploy:new-server-instance can't be started

[ https://issues.apache.org/jira/browse/GERONIMO-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240477#comment-13240477 ] Russell E Glaue edited comment on GERONIMO-6287 at 3/28/12 3:40 PM:

[jira] [Commented] (GERONIMO-5164) Incomplete feature for deploy:new-instance command in geronimo3.0

[ https://issues.apache.org/jira/browse/GERONIMO-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240483#comment-13240483 ] Russell E Glaue commented on GERONIMO-5164: --- Regarding patch

Re: Geronimo release cycle

move current trunk to 3.1 and change current beta branch to 3.0. +1 As long as 3.0-beta-2 passes Java EE 1.6 tests and also provides no broken core/primary functionality we have 2.2, we should stamp it as 3.0. 3.1 can focus on the continuation of 3.x enhancements. -RG On 03/28/2012 06:46

Re: Geronimo release cycle

I consider the changes made in trunk quite substantial so I think I would call trunk 4.x and call beta branch 3.x. Jarek On Wed, Mar 28, 2012 at 12:26 PM, Russell E Glaue rgl...@cait.org wrote: move current trunk to 3.1 and change current beta branch to 3.0. +1 As long as 3.0-beta-2 passes

[jira] [Updated] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[ https://issues.apache.org/jira/browse/GERONIMO-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-6305: -- Attachment: startBundlesInOrder_6305_fix.patch The new patch is startBundlesInOrder_6305_fix.patch

[jira] [Commented] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[ https://issues.apache.org/jira/browse/GERONIMO-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240553#comment-13240553 ] Yi Xiao commented on GERONIMO-6305: --- Sorry for response so late. Ivan, 12 I have

OSGi 4.3 API

Hi, I'm wondering if we should expose OSGi 4.3 API in Geronimo. Currently, in Geronimo 3 we are using Equinox 3.7.1 which already implements OSGi 4.3 API so I think it's just a matter of updating the exports out of the system bundle and updating the OSGi API jars the code is compiled against.

Re: Geronimo release cycle

I do think we should release something like current beta as 3.0. I have a slight preference for trunk to move to 4.0; at least to 3.5. At current rate of progress it will be a very long time before the trunk code is really ready. thanks david jencks On Mar 28, 2012, at 10:00 AM, Jarek Gawor

Re: OSGi 4.3 API

I think this is a great idea I actually thought the 3.0-beta branch was on 4.3, I guess I've been too immersed in trunk. thanks david jencks On Mar 28, 2012, at 12:46 PM, Jarek Gawor wrote: Hi, I'm wondering if we should expose OSGi 4.3 API in Geronimo. Currently, in Geronimo 3 we are

Re: OSGi 4.3 API

agree, with the new wiring api, think we could remove the use of package admin, and the hook api should be also useful. 2012/3/29 David Jencks david_jen...@yahoo.com I think this is a great idea I actually thought the 3.0-beta branch was on 4.3, I guess I've been too immersed in trunk.

[jira] [Issue Comment Edited] (GERONIMO-6305) Start bundles in EBA according to bundle dependencies

[ https://issues.apache.org/jira/browse/GERONIMO-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240553#comment-13240553 ] Yi Xiao edited comment on GERONIMO-6305 at 3/29/12 1:41 AM:

[jira] [Created] (GERONIMO-6312) Expose OSGi 4.3 core API

Expose OSGi 4.3 core API Key: GERONIMO-6312 URL: https://issues.apache.org/jira/browse/GERONIMO-6312 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi

[jira] [Commented] (GERONIMO-6312) Expose OSGi 4.3 core API

[ https://issues.apache.org/jira/browse/GERONIMO-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240976#comment-13240976 ] Jarek Gawor commented on GERONIMO-6312: --- Updated code in revision 1306713. The