Re: [VOTE] Release Apache ActiveMQ 4.0.1

+1 regards, Jonas Lim - Original Message - From: Hiram Chirino [EMAIL PROTECTED] To: activemq-dev@geronimo.apache.org Sent: Saturday, June 17, 2006 10:03 AM Subject: [VOTE] Release Apache ActiveMQ 4.0.1 Since the 4.0 release a bunch of small bug have been fixed and we felt it better

Re: [VOTE] Release Apache ActiveMQ 4.0.1

+1 Release ActiveMQ 4.0.1 Regards, Fritz Oconer - Original Message - From: Hiram Chirino [EMAIL PROTECTED] To: activemq-dev@geronimo.apache.org Sent: Saturday, June 17, 2006 10:03 AM Subject: [VOTE] Release Apache ActiveMQ 4.0.1 Since the 4.0 release a bunch of small bug have been

RTC Thoughts

I've been reading the RTC discussion here and I would like to express my thoughts about it. I'm not a comitter and not very familiar with the Apache house rules so forgive me if I raise some silly points :-) I think RTC will be good for maintaining a stable release. Keeping 1.1.x stable is

Re: [VOTE] 1.1 Release - Daytrader deployment questions

Has anyone successfully deployed the DayTrader ear from the release candidate? If so, what are the steps to deploy? I have tried deploying with only the ear and got the error below. I also tried deploying the ear using the daytrader\tags\1.1.0\plans\dayTrader-plan.xml file and also get a

Re: Namespace-driven builders and the UPA rule

Hi, Is there a way to do this substitution of JACC implementation by providing a substitutionGroup attribute to the security element? This may be not be correct; yet, this could look like this: xs:complexType name=security xs:sequence xs:element ref=security:security

Re: RTC Thoughts

Stefan Arentz wrote: skipping everything else I understand where Ken is coming from and how RTC works fine for a project like Apache's httpd. But just look at the number of sub-projects that Geronimo contains now, well over a hundred, and you RTC doesn't work fine for httpd. Trunk

Re: Request change to RTC Process

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jacek Laskowski wrote: Let's take this as an example. As we haven't discussed it yet, it seems to me that such a change requires 3x+1 from PMC members. So, only when this vote (it should possibly be a separate vote with 72-hour vote period to

[jira] Created: (GERONIMO-2134) Shutdown error in ConfigurationClassLoader

Shutdown error in ConfigurationClassLoader -- Key: GERONIMO-2134 URL: http://issues.apache.org/jira/browse/GERONIMO-2134 Project: Geronimo Type: Bug Security: public (Regular issues) Components: kernel Versions:

Re: XBean 2.4.x

Jeff Genender wrote: 2.0-M5 has...its on ibiblio... Alan D. Cabrera wrote: I can't seem to build this. It looks like it needs spring 2.0.0-m5 which has not been released. Regards, Alan Hmm, it seems to build for me now w/ the exception of the jaxb maven plugin. It seems that the

Re: XBean 2.4.x

jaxb2 maven plugin? I can fix it (since I am the author) ;-) or are you referring to the jaxb1 plugin from java.net? Jeff Alan D. Cabrera wrote: Jeff Genender wrote: 2.0-M5 has...its on ibiblio... Alan D. Cabrera wrote: I can't seem to build this. It looks like it needs spring

Re: 1.1.1 Release Goals

I'm not comfortable with the idea of putting improvements in a patch line but I will not do anything to try to stop it being done. Regards, Alan Matt Hogstrom wrote: Here is my proposal for defining the exit criteria for this release stream. I would like to volunteer to lead the 1.1.1

Re: XBean 2.4.x

groupIdcom.sun.tools.xjc.maven2/groupId artifactIdmaven-jaxb-plugin/artifactId version1.0/version You'll see in the maven repo at java.net they've added a '1' in the snapshot name of the POM. Regards, Alan Jeff Genender wrote: jaxb2 maven plugin? I can fix it (since I

Re: XBean 2.4.x

Yep...not mine...can't help here :( Alan D. Cabrera wrote: groupIdcom.sun.tools.xjc.maven2/groupId artifactIdmaven-jaxb-plugin/artifactId version1.0/version You'll see in the maven repo at java.net they've added a '1' in the snapshot name of the POM. Regards,

Re: [CONSENSUS] Default plugin site (was Re: Frustrations of a Release Manager)

David Blevins wrote: On Jun 15, 2006, at 2:27 PM, Alan D. Cabrera wrote: David Blevins wrote: Everyone, please read and ACK. On Jun 14, 2006, at 4:31 PM, John Sisson wrote: Hiram, I care if a private or commercial entity has control over the default option. I think Hiram does too, he

Re: Where did the 1.1 branch go?!?!

David Blevins wrote: On Jun 15, 2006, at 2:18 PM, Alan D. Cabrera wrote: David Blevins wrote: On Jun 15, 2006, at 12:22 PM, Alan D. Cabrera wrote: David Blevins wrote: On Jun 15, 2006, at 11:48 AM, David Blevins wrote: On Jun 15, 2006, at 11:18 AM, Alan D. Cabrera wrote: David

Re: XBean 2.4.x

No worries. 1.0 works fine. Regards, Alan Jeff Genender wrote: Yep...not mine...can't help here :( Alan D. Cabrera wrote: groupIdcom.sun.tools.xjc.maven2/groupId artifactIdmaven-jaxb-plugin/artifactId version1.0/version You'll see in the maven repo at java.net

Re: Namespace-driven builders and the UPA rule

I'll have to investigate this more. I'm not very familiar with substitution groups. If we can make this work, I think it would take care of at least some of Aarons concerns about anys, although for a generic build structure we might end up with something similar to anys. I don't like anys

Re: Do we need a Plugin Repo at the ASF ?

Dain Sundstrom wrote: On Jun 16, 2006, at 10:52 AM, Hiram Chirino wrote: On 6/16/06, Aaron Mulder [EMAIL PROTECTED] wrote: On 6/16/06, Hiram Chirino [EMAIL PROTECTED] wrote: +1 and perhaps even figure out what the url would be for the default asf site. Even if the site is not up and we are

[jira] Updated: (GERONIMO-1563) Make the JACC implementation pluggable

[ http://issues.apache.org/jira/browse/GERONIMO-1563?page=all ] David Jencks updated GERONIMO-1563: --- Attachment: GERONIMO-1563-step2.1-v2.diff GERONIMO-1563-step2.1-v2-openejb.diff Here's a version using any + noupa switch in xmlbeans.

Re: Request change to RTC Process

On Jun 17, 2006, at 10:21 AM, Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan Miller wrote: In Ken's announcement of the change to the commit model, he stated that a +1 to an RTC request means I have applied this patch and tested it and found it good.

Re: [openejb-dev] Merge of OpenEJB branch dead_2_2

I've discovered that I need a bunch of patched from geronimo's dead-1.2 branch to make openejb's dead_2_2 version work. The problem is these patches need openejb dead_2_2 or we will get compile errors. To ease this situation, I have created a private working directory for myself at

[jira] Created: (DAYTRADER-4) DayTrader README file out of date

DayTrader README file out of date - Key: DAYTRADER-4 URL: http://issues.apache.org/jira/browse/DAYTRADER-4 Project: DayTrader Type: Bug Versions: 1.1 Reporter: John Sisson This issue has been moved from GERONIMO-1436 -

[jira] Created: (DAYTRADER-5) Add LICENSE.txt and NOTICE.txt files

Add LICENSE.txt and NOTICE.txt files Key: DAYTRADER-5 URL: http://issues.apache.org/jira/browse/DAYTRADER-5 Project: DayTrader Type: Task Components: buildsystem Versions: 1.1 Reporter: John Sisson -- This

Re: [VOTE] 1.1 Release - Daytrader deployment questions

John, My thinking was to release the daytrader-ear-1.1.ear into the repo as it is really the only part of the application that requires versioning. However, your points below hilight that a quick 1.1.1 on DayTrader with improved documentation is in order. I propose we release the ear now

[jira] Closed: (GERONIMO-1436) [daytrader] Build instructions in applications\daytrader\README file out of date

[ http://issues.apache.org/jira/browse/GERONIMO-1436?page=all ] John Sisson closed GERONIMO-1436: - Resolution: Invalid Moved issue to http://issues.apache.org/jira/browse/DAYTRADER-4. Patch applied. [daytrader] Build instructions in

[jira] Created: (GERONIMO-2135) Improve the ActiveMQ GBeans

Improve the ActiveMQ GBeans --- Key: GERONIMO-2135 URL: http://issues.apache.org/jira/browse/GERONIMO-2135 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: ActiveMQ Reporter: Hiram Chirino

Updated 1.1 Release Binaries

I've updated the release with two items. 1. Moved tags/1.1.0 to branches/1.1.0 to address issues raised. (svn 414978) 2. I corrected the discrepancy about Tomcat logging pointed out by Paul. (svn 415233) 3. Updated the Release-Notes with the known issues (svn 414978) 4. Updated incorrect

Re: Updated 1.1 Release Binaries

I assume we should all try out these new binaries and then hold a new vote? I hope we can get TCK result on the new binaries soon too -- I'm not sure we should be counting votes until the TCK results are in. I'm in the process of pushing a set of 1.1 plugins and dependencies to the plugin

Re: Licenses displayed in console

I'm not sure we really need a license screen in the console -- it seems unlikely to always be up to date. But if we do want it, we should probably update it with everything in LICENSE.txt. Thanks, Aaron On 6/18/06, Matt Hogstrom [EMAIL PROTECTED] wrote: I'm not sure of the correct answer

Re: Request change to RTC Process

Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jacek Laskowski wrote: Let's take this as an example. As we haven't discussed it yet, it seems to me that such a change requires 3x+1 from PMC members. So, only when this vote (it should possibly be a separate vote

Re: [VOTE] 1.1 Release

+1 (assuming TCK tests pass). John Matt Hogstrom wrote: All, I have created what I hope is the final release of Geronimo 1.1. There has been a lot of work that has gone into this release (please review the RELEASE-NOTES). Here are the final release candidates for your review.