- a list of bugs that *someone* ought to look at for a release
- features (and more rarely, bugs) that should be looked at, but not
in the current release
- features that people have asked for but are not possible in the
near term
If we got the JIRA label plugin ( http://confluence.atlassian.c
Matt Hogstrom wrote:
John Sisson wrote:
Henri Yandell wrote:
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Having done two releases I have some thoughts on how we are using
JIRA. I imagine that there are a
number of thoughts on how we can manage JIRA.
I tend to do release managemen
On Jun 2, 2006, at 8:42 PM, John Sisson wrote:
Kevan Miller wrote:
It seems that there are now +1's from 3 committers for this
change. Although I also support the change (once copyrights are
corected), I cannot offer a +1. Apologies for being a pedant, but
to my knowledge the current RTC
David J,
These are the results with rev 411279 and PluginBootstrap2. I will
submit the patch in the morning. Just thought you would like to know..
Thanks
Anita
PSHOT\upgrade-cli-1.2-SNAPSHOT.car
INFO]
INFO]
INFO]
INFO
Create a Geronimo Bug Guidelines Page
-
Key: GERONIMO-2080
URL: http://issues.apache.org/jira/browse/GERONIMO-2080
Project: Geronimo
Type: Improvement
Security: public (Regular issues)
Components: website
Reporter: Joh
Kevan Miller wrote:
It seems that there are now +1's from 3 committers for this change.
Although I also support the change (once copyrights are corected), I
cannot offer a +1. Apologies for being a pedant, but to my knowledge
the current RTC "rules" we are living under are:
'I have applied
I'm getting the feeling that you understand this JIRA stuff pretty well :)
Maybe I am... ;-)
I introduced PBT (where I'm about to leave) to JIRA about a year ago,
and was the admin for about 10 months. I've implemented some crude,
yet custom, workflows for our IT operations production change p
John Sisson wrote:
Henri Yandell wrote:
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Having done two releases I have some thoughts on how we are using
JIRA. I imagine that there are a
number of thoughts on how we can manage JIRA.
I tend to do release management tasks too, so though
I'm getting the feeling that you understand this JIRA stuff pretty well :)
Version is being abused and your suggestion is much better.
Jason Dillon wrote:
What about creating a new issue status of the same name instead of using versions... Which I think is a bit misused in this context.
--jas
Yes, thanks...JIRA
Geir Magnusson Jr wrote:
Do you mean JIRA?
Matt Hogstrom wrote:
Geir,
Can you grant me SVN Karma to add contributors? Dain is on vacation.
Thanks
Matt
I have a feeling someone else had this issue recently. You may be out
of memory.
Try running maven with the -e option to see the exception. If it is a
memory problem, try running with the MAVEN_OPTS environment variable set to:
-Xmx512m -XX:MaxPermSize=128m
I have always had MAVEN_OPTS se
Prasad Kashyap wrote:
Just before v1.0, the % of code we had covered in our unit test were
about 30%. I don't know expect that to have gone up significantly
higher since then.
Check out this site -
http://developer.spikesource.com/testresults/index.jsp?show=component-results&category=all&comp-id
David J,
I have been working with rev 409296, and openejb 2659. Today I
updated to rev 411279. There have been changes in o.a.g.kernel that
affect PackageBuilder, MavenConfigStore, and MavenAttributeStore. I
need to incorporate these changes into m2 plugin and retest everything.
:( I am assumin
Henri Yandell wrote:
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Having done two releases I have some thoughts on how we are using
JIRA. I imagine that there are a
number of thoughts on how we can manage JIRA.
I tend to do release management tasks too, so thought I'd offer thoughts.
Matt,
Could you please update the events page (
https://svn.apache.org/repos/asf/geronimo/site/xdocs/events.xml ) when
you have the details.
Thanks,
John
Matt Hogstrom wrote:
I plan on being there. I'll look to get the registration completed
today.
Gianny Damour wrote:
Hi,
I believe
[
http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414538
]
David Jencks commented on GERONIMO-2071:
I've applied parts of some of these patches:
openejb.patch dated 02/june/06 applied in openejb rev 2663
geronimo.patch da
Project facet Utility Module 1.0 is not supported by target runtime Apache
Geronimo v1.0
Key: GERONIMODEVTOOLS-82
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-82
Project:
Do you mean JIRA?
Matt Hogstrom wrote:
> Geir,
>
> Can you grant me SVN Karma to add contributors? Dain is on vacation.
>
> Thanks
>
> Matt
>
>
Geir,
Can you grant me SVN Karma to add contributors? Dain is on vacation.
Thanks
Matt
No methodProxy in EJBInvocation at startup under heavy load
---
Key: GERONIMO-2079
URL: http://issues.apache.org/jira/browse/GERONIMO-2079
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Com
Hi,
Just pulled down the sources and upon building it I'm getting the
following error message:
+
| configurations Geronimo Configuration for performing service deployments
| Memory: 44M/51M
+
DEPRECATED: the default
[ http://issues.apache.org/jira/browse/GERONIMO-2077?page=all ]
David Jencks closed GERONIMO-2077:
--
Resolution: Fixed
Fixed in openejb rev 2662.
Moral of story: be sure to clean up pool entries BEFORE returning them to the
pool, not after they ha
Deployment errors can lead to directories and other artifacts not being cleaned
up in the repo
--
Key: GERONIMO-2078
URL: http://issues.apache.org/jira/browse/GERONIMO-2078
Project:
Under load receiving Null Pointer Exceptions in CMPGetter
-
Key: GERONIMO-2077
URL: http://issues.apache.org/jira/browse/GERONIMO-2077
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Repor
[ http://issues.apache.org/jira/browse/GERONIMO-1182?page=all ]
Paul McMahan updated GERONIMO-1182:
---
Attachment: GERONIMO-1182-1.patch
ported the patch to v1.2 (no code changes, just rearranged the patch metadata).
tested the patch and it works as a
[ http://issues.apache.org/jira/browse/GERONIMO-1423?page=all ]
Matt Hogstrom updated GERONIMO-1423:
Fix Version: Verification Required
(was: 1.1)
> log4j.properties's category is ignored
> --
Just before v1.0, the % of code we had covered in our unit test were
about 30%. I don't know expect that to have gone up significantly
higher since then.
Check out this site -
http://developer.spikesource.com/testresults/index.jsp?show=component-results&category=all&comp-id=197086#pkgtest
But I
[ http://issues.apache.org/jira/browse/GERONIMO-1492?page=all ]
Paul McMahan updated GERONIMO-1492:
---
Attachment: GERONIMO-1492-1.patch
Thanks for the feedback. I am attaching a new patch that addresses your
concerns. Following David Jencks' suggest
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36229 ]
Christopher G. Stach II commented on AMQ-731:
-
So, with that being said, should endedXATransactionContexts actually be a Map
of LinkedHashSets?
> Redeliveries don'
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36228 ]
Christopher G. Stach II commented on AMQ-731:
-
Okay, this is the stack trace with a breakpoint put at TransactionContext line
560. It happens over and over and ove
On 6/1/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
Jacek, David J, Guillaume, and others
I would like a clarification regarding this work. This patch
includes work that was already part of the old trunk. There were minor
modifications to accommodate 1.1. Should this code be reviewed ag
[
http://issues.apache.org/jira/browse/GERONIMO-1860?page=comments#action_12414506
]
Jacek Laskowski commented on GERONIMO-1860:
---
ccardona is in geronimo-contributor group. He can assign the issue to himself
whenever he intend to. Welcome Chris!
[ http://issues.apache.org/jira/browse/GERONIMO-1860?page=all ]
Paul McMahan reassigned GERONIMO-1860:
--
Assign To: (was: Paul McMahan)
Chris Cardona (ccardona) has been investigating this JIRA and has provided some
test results. He requested
Do you happen to know of any examples where Retrotranslation fails?
--jason
-Original Message-
From: "James Strachan" <[EMAIL PROTECTED]>
Date: Thu, 1 Jun 2006 12:03:44
To:dev@geronimo.apache.org
Cc:[EMAIL PROTECTED]
Subject: Re: Retrotranslator KICKS ASS!!!
On 5/31/06, Jason Dillon <[
Hi,
Just a thought that sprung to my mind. I must admit that I haven't
followed the progress on 1.1 branch carefully enough and most likely
lost track. I'm going to get up to speed with the latest whistles and
bells and thought to take a look at the unit tests and how much we've
got them so far.
Here's what I'd like:
- a prioritized list of stuff I plan to work on for a release (where
the priorities are priorities on my list, not necessarily
corresponding to severity of problem, etc.)
- a list of bugs that *someone* ought to look at for a release
- features (and more rarely, bugs) that s
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36227 ]
Christopher G. Stach II commented on AMQ-731:
-
Oh, I should add, that once the redeliveries are exhausted, it ends up getting
a ConnectionClosedException and jumpin
On 6/2/06, Bryan Noll <[EMAIL PROTECTED]> wrote:
I guess the downside to assigning JIRA's to non-committers is that who
knows whether the person asking to have the JIRA assigned to him/her is
someone who will actually resolve it, or someone who thinks that they
would like to and then it doesn't
What about creating a new issue status of the same name instead of using
versions... Which I think is a bit misused in this context.
--jason
-Original Message-
From: Matt Hogstrom <[EMAIL PROTECTED]>
Date: Fri, 02 Jun 2006 12:08:23
To:dev@geronimo.apache.org
Subject: New JIRA "Version
+1
Matt Hogstrom wrote:
All,
After moving some of the JIRAs for the third time today there is a
recurring pattern of bugs that are reported and are so old that we don't
know if they are issues anymore. To separate these from the other bugs
that can be worked on directly I created a new Vers
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
I'm moving several JIRAs in there today. If there is strong objection then
they can easily be moved
out and put into some version number. I'm trying to change some of the way we
look at JIRA because
there are a large number of the open ones
So... an observation from a non-committer. If there's a JIRA that a
non-committer would like to fix, can that non-committer be assigned the
JIRA? I ask because the prospect of diving into something, spending
several hours on it, and submitting a patch only to find out that in the
meantime, an
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36226 ]
Christopher G. Stach II commented on AMQ-731:
-
Okay, here's a bit more information. While stepping through a rollback, I've
found l.elementData in TransactionConte
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
I'm not sure how to handle assignment of JIRAs as they generally fall into
someone's area of
expertise but I think the fact their assigned to someone might scare someone
away from looking at it
. Thoughts?
What I wish to happen is to re
Hi,
After much longer than anticipated pause I'm revving up and am almost
ready to help with the M2 migration. I wonder however how to apply RTC
principles to M2-related changes. There're two active non-committers -
Anita and Prasad and I wonder whether their votes are binding in this
matter give
Can we mark some of the older M* builds are archived? That will help make the "Raised In Versions (non-archived))" portlet more useful.I'm curious... has everyone setup their JIRA home/dashboard to show more details specific to Geronimo... if not, I'd recommend creating a new "Geronimo" portal pag
On 6/2/06, David Jencks <[EMAIL PROTECTED]> wrote:
I'm applying patches from GERONIMO-2071, and consulting on IRC with
Anita and Prasad to make sure I'm getting the right ones. You've
worked with m2 much more than me, so if you would like to apply them
let me know, I will stop :-). I'd like to
Okay, well so far no one objected... so I am going to look into how we
can get this setup.
--jason
On 5/31/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Since Apache tends to prefer mailing lists... but IRC is so convent
for effective communication. Maybe we should have a daily post of the
last
Have we considered using the voting system built into JIRA to figure
out which JIRAs should really get attention? Sometimes when I have a
few spare cycles I'll go looking for JIRAs to fix and this additional
metric would help me choose. It would also give us an additional way
to listen to the us
[ http://issues.apache.org/jira/browse/GERONIMO-1436?page=all ]
Scott Nicholls updated GERONIMO-1436:
-
Patch Info: [Patch Available]
Updated README with build instructions for Maven 2.
> [daytrader] Build instructions in applications\daytrader\REA
[ http://issues.apache.org/jira/browse/GERONIMO-1764?page=all ]
Bryan Noll updated GERONIMO-1764:
-
Attachment: createDB-cygwin.patch
Ignore the first attachment (createDB.sh), this is the appliable patch. The
patch was created from the following dir:
[ http://issues.apache.org/jira/browse/GERONIMO-1436?page=all ]
updated GERONIMO-1436:
---
Attachment: readme.patch
> [daytrader] Build instructions in applications\daytrader\README file out of
> date
> --
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Having done two releases I have some thoughts on how we are using JIRA. I
imagine that there are a
number of thoughts on how we can manage JIRA.
I tend to do release management tasks too, so thought I'd offer thoughts.
Currently we create
[ http://issues.apache.org/jira/browse/GERONIMO-1182?page=all ]
Matt Hogstrom updated GERONIMO-1182:
Fix Version: 1.2
(was: 1.1)
> Connector portlet improvement (delete connector confirmation, more form
> buttons)
>
[ http://issues.apache.org/jira/browse/GERONIMO-1182?page=all ]
Matt Hogstrom updated GERONIMO-1182:
Adding to 1.2 we need to verfiy that this works or clsoe this JIRA
> Connector portlet improvement (delete connector confirmation, more form
> button
Having done two releases I have some thoughts on how we are using JIRA. I imagine that there are a
number of thoughts on how we can manage JIRA.
Currently we create a release and then pretty much dump most everything into it. What ends up
happening is that we end up with more JIRAs than we ha
[
http://issues.apache.org/jira/browse/GERONIMO-1764?page=comments#action_12414475
]
Bryan Noll commented on GERONIMO-1764:
--
Went back and looked at the createDB.sh script I attached (first of all, it
should've been a patch, so whoops there by me) and
[
http://issues.apache.org/jira/browse/GERONIMO-1674?page=comments#action_12414470
]
Kevan Miller commented on GERONIMO-1674:
I recall getting an NPE if I forgot to initialize Daytrader (create the DB,
setup the users, # of issues, etc). I believe
I would be happy to help out.
Jeff
> Hi,
>
> I believe that OSCON is offering free booth space to the ASF. The
> registration deadline for the next OSCON in Portland (end of July) is
> this Monday, June 5.
>
> IBM is offering the PRC logistical and financial support, e.g. t-shirts
> et cetera, f
It sounds great. Actually I received a bunch of questions about writing tests cases, this would be
just the right place to start.
Cheers!
Hernan
Matt Hogstrom wrote:
All,
After moving some of the JIRAs for the third time today there is a
recurring pattern of bugs that are reported and are so
[ http://issues.apache.org/jira/browse/GERONIMO-1560?page=all ]
Jeff Genender closed GERONIMO-1560:
---
Resolution: Fixed
Yep...I had fixed this. Please re-open if you still have issues.
> [DayTrader] EJB spec violations
> -
Works for me.
Aaron
On 6/2/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
All,
After moving some of the JIRAs for the third time today there is a recurring
pattern of bugs that
are reported and are so old that we don't know if they are issues anymore. To
separate these from
the other bugs tha
[ http://issues.apache.org/jira/browse/GERONIMO-1173?page=all ]
Matt Hogstrom updated GERONIMO-1173:
Fix Version: Wish List
(was: 1.1)
> Make DatabaseInfo load from file; separate JDBC and XA portlets
> --
[
http://issues.apache.org/jira/browse/GERONIMO-1674?page=comments#action_12414459
]
Bryan Noll commented on GERONIMO-1674:
--
Can you please give some specifics on what exact action you are taking in the
gui to get this to occur? Are you running a sce
[ http://issues.apache.org/jira/browse/GERONIMO-1082?page=all ]
Matt Hogstrom updated GERONIMO-1082:
Fix Version: Verification Required
(was: 1.1)
> Deployment doesn't ensure queries defined for ejbSelect methods
> --
We've talked about it in the past. There are a number of projects that are already DB focused.
OpenJPA (if there is ever a code commit) will likely displace the TranQL persistence piece. The
connectors are still valid and may find a home here. I think we need to let the dust settle before
we
All,
After moving some of the JIRAs for the third time today there is a recurring pattern of bugs that
are reported and are so old that we don't know if they are issues anymore. To separate these from
the other bugs that can be worked on directly I created a new Version called "Verification
R
[
http://issues.apache.org/jira/browse/GERONIMO-1560?page=comments#action_12414455
]
Bryan Noll commented on GERONIMO-1560:
--
I believe jgenender fixed this somewhere along the way. I don't know if it was
associated with a JIRA and the patch was attac
That will happen as we close out the final bugs Donald. The transaction problem will most likely be
in one of the components you named below so they haven't been requested to version yet. Hopefully
soon :)
Donald Woods wrote:
Can everyone add a reply to this email thread as the dependent SNA
We'll have an idea later today. I think its critical and I am opening a JIRA
for it.
Jeff Genender wrote:
Matt Hogstrom wrote:
I posted a note a few days ago with my proposed plan for releasing 1.1.
There was only one response from Jason so I will take the silence as
acceptance of the plan
[ https://issues.apache.org/activemq/browse/SM-443?page=all ]
Guillaume Nodet resolved SM-443:
Resolution: Fixed
Author: gnodet
Date: Fri Jun 2 08:59:39 2006
New Revision: 411195
URL: http://svn.apache.org/viewvc?rev=411195&view=rev
Log:
SM-443: C
[ http://issues.apache.org/jira/browse/GERONIMO-1079?page=all ]
Matt Hogstrom updated GERONIMO-1079:
Fix Version: Verification Required
(was: 1.1)
> Better error for missing primkey-field
> --
Change transaction semantic and improve support
---
Key: SM-443
URL: https://issues.apache.org/activemq/browse/SM-443
Project: ServiceMix
Type: Improvement
Components: servicemix-core
Reporter: Guillaume Nodet
Ass
[ http://issues.apache.org/jira/browse/GERONIMO-1056?page=all ]
Matt Hogstrom updated GERONIMO-1056:
Fix Version: 1.x
(was: 1.1)
> Redeploy database pool, app blows up (in CMP finder/prefetch code)
> -
[ http://issues.apache.org/jira/browse/GERONIMO-960?page=all ]
Matt Hogstrom updated GERONIMO-960:
---
Fix Version: 1.x
(was: 1.1)
> NPE related to EJB while deploying EAR
> --
>
> Key: GER
[ http://issues.apache.org/jira/browse/GERONIMO-1023?page=all ]
Matt Hogstrom updated GERONIMO-1023:
Fix Version: 1.x
(was: 1.1)
> Web DD option to disable directory listings
> ---
>
>
[ http://issues.apache.org/jira/browse/GERONIMO-1176?page=all ]
Matt Hogstrom updated GERONIMO-1176:
Fix Version: 1.2
(was: 1.1)
> Bad "resource" reference is not caught at deployment time
> --
[ http://issues.apache.org/jira/browse/GERONIMO-927?page=all ]
Matt Hogstrom closed GERONIMO-927:
--
Resolution: Fixed
Completed in TranQL Connector 1.2 and TranQL Vendors DB2 1.0
> Provide a statement cache for TranQL for JDBCs drivers that don't i
[ http://issues.apache.org/jira/browse/GERONIMO-897?page=all ]
Matt Hogstrom updated GERONIMO-897:
---
Fix Version: 1.x
(was: 1.1)
> Finish implementing JMS Broker portlet
> --
>
> Key: GER
Matt,
By the way, are there any plans to make TranQL an Apache project, or
even a Geronimo component?
Vasily Zakharov
Intel Middleware Products Division
-Original Message-
From: Matt Hogstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 6:54 AM
To: dev@geronimo.apache.org
Su
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=all ]
Matt Hogstrom updated GERONIMO-803:
---
Fix Version: 1.2
(was: 1.1)
> Deploy failure during redeploy leaves app undeployed
> --
[ http://issues.apache.org/jira/browse/GERONIMO-734?page=all ]
Matt Hogstrom updated GERONIMO-734:
---
Fix Version: 1.2
(was: 1.1)
> Adding CORBA settings to local-only EJB appears to give NPE
> ---
[ http://issues.apache.org/jira/browse/GERONIMO-454?page=all ]
Matt Hogstrom updated GERONIMO-454:
---
Fix Version: 1.2
(was: 1.1)
> Support Group Name = Role Name Role Mapping
> ---
>
>
[ http://issues.apache.org/jira/browse/GERONIMO-1383?page=all ]
Matt Hogstrom updated GERONIMO-1383:
Fix Version: 1.2
(was: 1.1)
> Connector DConfigBeans don't load correctly from XML
> ---
[ http://issues.apache.org/jira/browse/GERONIMO-411?page=all ]
Matt Hogstrom updated GERONIMO-411:
---
Fix Version: 1.2
(was: 1.1)
> Add Hash Password Rewrite to File Realm
> ---
>
> Key: G
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ]
Matt Hogstrom updated GERONIMO-348:
---
Fix Version: 1.2
(was: 1.1)
> Invalid module path or references in plan should result in failed deployment
> or warning
>
Can everyone add a reply to this email thread as the dependent SNAPSHOT
projects (like OpenEJB, TranQL, ActiveMQ, ...) have created a release
version and its available on one of the default Maven repos? Given how
interdependent Geronimo, OpenEJB and TranQL are on each other, those
need to all
[ http://issues.apache.org/jira/browse/GERONIMO-1135?page=all ]
Matt Hogstrom updated GERONIMO-1135:
Fix Version: 1.2
(was: 1.1)
> Keystore password in System.properties
> --
>
> Key:
[
http://issues.apache.org/jira/browse/GERONIMO-1492?page=comments#action_12414442
]
David Jencks commented on GERONIMO-1492:
re
2) There are sections like the one below in many of the files. I'm not
convinced this is correct syntax. Is it legal to
Matt Hogstrom wrote:
> I posted a note a few days ago with my proposed plan for releasing 1.1.
> There was only one response from Jason so I will take the silence as
> acceptance of the plan. Today I will:
>
> * be moving all JIRAs out from 1.1 and moving them to 1.2.
> * Cutting a release bui
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-
Attachment: openejb.patch
This patch has the openejb-builder
> Move Geronimo build to M2 (new 1.2 trunk)
> ---
After some recent commits I seem to be running into out-of-memory
during the build, and its partially my fault with whats happening
within the build like the launching of a headless eclipse. I found
out that the Tuscany project is doing alot of EMF generation in their
build without launchi
I posted a note a few days ago with my proposed plan for releasing 1.1. There was only one response
from Jason so I will take the silence as acceptance of the plan. Today I will:
* be moving all JIRAs out from 1.1 and moving them to 1.2.
* Cutting a release build for review and will post it to
I plan on being there. I'll look to get the registration completed today.
Gianny Damour wrote:
Hi,
I believe that OSCON is offering free booth space to the ASF. The
registration deadline for the next OSCON in Portland (end of July) is
this Monday, June 5.
IBM is offering the PRC logistica
One option is if we could allow non-committers to vote if they
declare that they have applied AND tested the patch.
On Jun 2, 2006, at 10:23 AM, Kevan Miller wrote:
It seems that there are now +1's from 3 committers for this change.
Although I also support the change (once copyrights are cor
FYI, I've already committed the change, and was gonna just run
thought the entire source tree to update all copyrights for any file
created this year.
On Jun 2, 2006, at 10:23 AM, Kevan Miller wrote:
It seems that there are now +1's from 3 committers for this change.
Although I also suppor
On Jun 2, 2006, at 7:14 AM, Jacek Laskowski wrote:
On 6/2/06, David Jencks <[EMAIL PROTECTED]> wrote:
Several people have asserted the claim in the subject above and
AFAICT no one on the board or PMC have argued with it. I'm going to
assume there are no objections.
+1
In particular I plan
It seems that there are now +1's from 3 committers for this change.
Although I also support the change (once copyrights are corected), I
cannot offer a +1. Apologies for being a pedant, but to my knowledge
the current RTC "rules" we are living under are:
'I have applied this patch and tes
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-
Attachment: pom.xml
Latest pom.xml with codehaus reppo for tranql and dwrVersion set to 1.1.1
> Move Geronimo build to M2 (new 1.2 trunk)
> --
On 6/2/06, David Jencks <[EMAIL PROTECTED]> wrote:
Several people have asserted the claim in the subject above and
AFAICT no one on the board or PMC have argued with it. I'm going to
assume there are no objections.
+1
In particular I plan to check that the m2 patches don't break the
trunk bu
1 - 100 of 111 matches
Mail list logo
