[jira] Assigned: (GERONIMODEVTOOLS-182) Unable to open Deployment plan editor in Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-182: Assignee: Shiva Kumar H R Unable to open Deployment

[jira] Assigned: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-184: Assignee: Shiva Kumar H R An internal error occurred

[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521019 ] Kan Ogawa commented on GERONIMODEVTOOLS-184: Perhaps, XmlBeans library ( included in

Re: [VOTE] Geronimo 2.0.1 (rc1)

[X] +1 Release these binaries p.s. Couldn't think of a better (morning) present right after the long holidays of mine are over - being able to vote for 2.0.1. Jacek On 8/15/07, Matt Hogstrom [EMAIL PROTECTED] wrote: The updated binaries are available for review. I have incorporated the

Re: Merge ettiquette

On 8/17/07, David Jencks [EMAIL PROTECTED] wrote: I've noticed that sometimes when people merge bug fixes/changes from one branch to another they don't include the jira number from the original commit. This makes it exceedingly hard to figure out which branches something has been fixed in

[jira] Commented: (GERONIMO-3382) InvalidConfigurationException is thrown when starting the plugins from the console

[ https://issues.apache.org/jira/browse/GERONIMO-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521039 ] Song commented on GERONIMO-3382: No fixed... And No plugins are avaiable from the other provided Geronimo site:

[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521078 ] Ted Kirby commented on GERONIMODEVTOOLS-184: Thanks, Kan, that looks like the problem. The

Updating the Sun WebSite

Jeff / Joe, Can we get the Sun WebSite updated with Geronimo 2.0.1 being certified rather than 2.0-M6-rc1?

Removing 1.0 and 1.1 from the download site...any objections?

All, Since 1.1.1 is the stable version of Geronimo I'd like to propose that we remove the older versions from the download site. If there are no objections I'll do this tomorrow when we announce the 2.0.1 release.

Re: Removing 1.0 and 1.1 from the download site...any objections?

+1 Cheers Prasad On 8/20/07, Matt Hogstrom [EMAIL PROTECTED] wrote: All, Since 1.1.1 is the stable version of Geronimo I'd like to propose that we remove the older versions from the download site. If there are no objections I'll do this tomorrow when we announce the 2.0.1 release.

Re: Updating the Sun WebSite

Matt Hogstrom wrote: Jeff / Joe, Can we get the Sun WebSite updated with Geronimo 2.0.1 being certified rather than 2.0-M6-rc1? Jeff has the Sun contacts. Also, we certified 2.0.1 with a different OS and with a newer patch/exclude list. I'll put the updated information to document our

Re: Removing 1.0 and 1.1 from the download site...any objections?

+1 Matt Hogstrom wrote: All, Since 1.1.1 is the stable version of Geronimo I'd like to propose that we remove the older versions from the download site. If there are no objections I'll do this tomorrow when we announce the 2.0.1 release.

Re: Updating the Sun WebSite

Joe Bohn wrote: Matt Hogstrom wrote: Jeff / Joe, Can we get the Sun WebSite updated with Geronimo 2.0.1 being certified rather than 2.0-M6-rc1? Jeff has the Sun contacts. Also, we certified 2.0.1 with a different OS and with a newer patch/exclude list. I'll put the updated

Re: JASPI

On Aug 15, 2007, at 8:52 PM, David Jencks wrote: It looks like JASPI (jsr-196) has been approved and I think we should finish implementing it. Guillaume already implemented the spec jar from an earlier draft and I updated it recently to the pfd2 spec. Guillaume also started an

Press Release for 2.0.1

Now that we've gotten through the issues that stalled 2.0 we have a successful vote and I've updated the Press Release as well with version information. This should be pretty good as it was the mostly approved version before the security problem. Please review and perhaps the PRC can

Re: Removing 1.0 and 1.1 from the download site...any objections?

+1 Matt Hogstrom wrote: All, Since 1.1.1 is the stable version of Geronimo I'd like to propose that we remove the older versions from the download site. If there are no objections I'll do this tomorrow when we announce the 2.0.1 release.

Re: Removing 1.0 and 1.1 from the download site...any objections?

+1 vamsi On 8/20/07, Matt Hogstrom [EMAIL PROTECTED] wrote: All, Since 1.1.1 is the stable version of Geronimo I'd like to propose that we remove the older versions from the download site. If there are no objections I'll do this tomorrow when we announce the 2.0.1 release.

[jira] Commented: (GERONIMO-3382) InvalidConfigurationException is thrown when starting the plugins from the console

[ https://issues.apache.org/jira/browse/GERONIMO-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521119 ] Paul McMahan commented on GERONIMO-3382: This is not a bug. It is caused by the 2.0.1 plugins not being

[DISCUSS] 2.0.2 release

Time to start thinking about a 2.0.2 release, I think... We can safely assume that it will contain some number of fixes for newly-reported problems against 2.0.1. These activities will be driven by user problem reports. I'd assume that we'll also be fixing a number of problems which we

[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521125 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-184: -- Instead of

[jira] Updated: (GERONIMO-3354) Exception thrown by MDB involved in XA transaction

[ https://issues.apache.org/jira/browse/GERONIMO-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3354: --- Affects Version/s: 2.1 2.0.x Fix Version/s: 2.1

[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521137 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-184: -- Changing xmlbeans version to 2.3.0

Re: Press Release for 2.0.1

On 8/20/07, Matt Hogstrom [EMAIL PROTECTED] wrote: Apache Geronimo Version 2.0.1 I don't like Version uppercased - Apache Geronimo 2.0.1 is fine. released by Apache Software Foundation date/time/location—The Apache Software Foundation (ASF) announced today the release of Apache Geronimo

Re: Removing 1.0 and 1.1 from the download site...any objections?

+1 to removing 1.0 and 1.1 Also... If I remember correctly, the only issue that prevented 1.2 from releasing was the ConcurrentModificationException that came up under stress testing of DayTrader. Is that really enough to block the release? Especially since (as far as I know) there hasn't

[jira] Commented: (GERONIMO-2567) Remote admin of server using deployer.jar fails to connect

[ https://issues.apache.org/jira/browse/GERONIMO-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521149 ] Jay D. McHugh commented on GERONIMO-2567: - I'll see if I can figure out why I can't get a connection. I

[jira] Commented: (GERONIMODEVTOOLS-180) Upgrade supported eclipse level from 3.3RC2 to 3.3, and related packages.

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521151 ] Ted Kirby commented on GERONIMODEVTOOLS-180: I was able to install the plugin into the Eclipse

Re: Press Release for 2.0.1

On 8/20/07, Matt Hogstrom [EMAIL PROTECTED] wrote: Now that we've gotten through the issues that stalled 2.0 we have a successful vote and I've updated the Press Release as well with version information. This should be pretty good as it was the mostly approved version before the security

Re: [jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse

Hi Shiva, are you using the new 2.0.1 artifacts to build the plugin ?? And if so, did you change the pom.xml to use the geronimo-web-2.5-builder artifact instead of the geronimo-web-builder artifact ?? Shiva Kumar H R (JIRA) wrote: [

[jira] Created: (GERONIMO-3423) Ensure that users can change the ejb jndi name format

Ensure that users can change the ejb jndi name format - Key: GERONIMO-3423 URL: https://issues.apache.org/jira/browse/GERONIMO-3423 Project: Geronimo Issue Type: Improvement Security

Re: Press Release for 2.0.1

Thanks to Vamsi and Jacek. for their comments. I've incorporated all except the configuration by exception as my feeble mind couldn't wordsmith it well enough. Give me your +1 on this and we'll let 'er rip. Grat job everyone. On Aug 20, 2007, at 11:16 AM, Matt Hogstrom wrote: Now

Re: Press Release for 2.0.1

On Aug 20, 2007, at 5:04 PM, Matt Hogstrom wrote: Thanks to Vamsi and Jacek. for their comments. I've incorporated all except the configuration by exception as my feeble mind couldn't wordsmith it well enough. Give me your +1 on this and we'll let 'er rip. Grat job everyone. Looks

Re: Press Release for 2.0.1

Looks good to me with one possible exception. This: In addition, the Certification Authority portlet lets you setup a Certification Authority, your own Public-Key Infrastructure, very easily and use server/client Digital Certificates for securing your applications. doesn't read quite right

[jira] Reopened: (GERONIMO-3420) Remote deploy of an EAR without an application.xml plan fails

[ https://issues.apache.org/jira/browse/GERONIMO-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reopened GERONIMO-3420: Remote deployment of WAR files need their original filenames, so the context root will be

[jira] Commented: (GERONIMO-3420) Remote deploy of an EAR without an application.xml plan fails

[ https://issues.apache.org/jira/browse/GERONIMO-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521275 ] Donald Woods commented on GERONIMO-3420: Also, the remote-deploy configs are missing geronimo-plugin.xml

automatic build of trunk

Can we setup automatic builds of trunk? I just discovered it doesn't build. Jarek

[jira] Created: (GERONIMO-3424) Fatal error in geronimo-service-builder during copy-xmlbeans-schemas on windows

Fatal error in geronimo-service-builder during copy-xmlbeans-schemas on windows --- Key: GERONIMO-3424 URL: https://issues.apache.org/jira/browse/GERONIMO-3424 Project:

Re: project involvement

Hey Sachin, Congrats and best wishes on your new job(s) :-) You'll be missed here. Hopefully it's for a very short time. Cheers Prasad On 8/17/07, Sachin Patel [EMAIL PROTECTED] wrote: Hello community members... I'd thought I'd shoot of a note to explain my limited involvement in the

Re: automatic build of trunk

--- Prasad Kashyap [EMAIL PROTECTED] wrote: Same 5 builds a day as current 2.0 ? +1 Thanks Anita Or some 2.0 builds and some trunk builds ? Cheers Prasad On 8/20/07, Jarek Gawor [EMAIL PROTECTED] wrote: Can we setup automatic builds of trunk? I just discovered it doesn't build.

[jira] Created: (GERONIMO-3425) Add deployment plan schemas to geronimo web site

Add deployment plan schemas to geronimo web site Key: GERONIMO-3425 URL: https://issues.apache.org/jira/browse/GERONIMO-3425 Project: Geronimo Issue Type: Improvement Security Level:

[jira] Commented: (GERONIMO-2567) Remote admin of server using deployer.jar fails to connect

[ https://issues.apache.org/jira/browse/GERONIMO-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521314 ] Kevan Miller commented on GERONIMO-2567: 1) No. 2) Remote server E.g: I have a Geronimo server running

[jira] Closed: (GERONIMO-3420) Remote deploy of an EAR without an application.xml plan fails

[ https://issues.apache.org/jira/browse/GERONIMO-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-3420. -- Resolution: Fixed Committed revision 567934 in branches/2.0 Committed revision 567944 in

[jira] Created: (GERONIMO-3426) The Holder object contains duplicated injections

The Holder object contains duplicated injections Key: GERONIMO-3426 URL: https://issues.apache.org/jira/browse/GERONIMO-3426 Project: Geronimo Issue Type: Bug Security Level: public

[jira] Created: (SM-1034) Use a single hotdeploy directory, put components inside it, and start servicemix in the SERVICEMIX_HOME directory by default

Use a single hotdeploy directory, put components inside it, and start servicemix in the SERVICEMIX_HOME directory by default Key: SM-1034

[jira] Created: (SM-1035) Continuation problems when Max Idle Time ocurr

Continuation problems when Max Idle Time ocurr -- Key: SM-1035 URL: https://issues.apache.org/activemq/browse/SM-1035 Project: ServiceMix Issue Type: Bug Components: servicemix-http

Re: [VOTE] Release XBean 3.1

+1 It's already approved, but just for the record. Jacek On 8/1/07, David Blevins [EMAIL PROTECTED] wrote: I have tagged an XBean 3.1 version at http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.1/ Binaries: http://people.apache.org/~dblevins/stage/org/apache/xbean/ Please