Congrats!
On Tue, Sep 9, 2008 at 1:56 AM, Ashish Jain [EMAIL PROTECTED] wrote:
Congrats BJ!!
On Tue, Sep 9, 2008 at 11:14 AM, Jarek Gawor [EMAIL PROTECTED] wrote:
Congrats!
Jarek
On Mon, Sep 8, 2008 at 5:11 PM, Tim McConnell [EMAIL PROTECTED]
wrote:
Hi Everyone, The Geronimo PMC is
On Sep 9, 2008, at 1:48 AM, Jason Dillon wrote:
No comments?
Your description sounds great but I won't really know until I try it
out or study it in great detail which I haven't had time for. The
organization looks way better than what we have now.
Can we use the stage plugin to copy
Thanks everyone.
Jason Warner wrote:
Congrats!
On Tue, Sep 9, 2008 at 1:56 AM, Ashish Jain [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Congrats BJ!!
On Tue, Sep 9, 2008 at 11:14 AM, Jarek Gawor [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Congrats!
[
https://issues.apache.org/jira/browse/GERONIMO-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629475#action_12629475
]
David Jencks commented on GERONIMO-4284:
rev 693451 adds simple multicast
I like the new option to force staging instead of publishing to
apache.releases (which I was bit by last week.) Would be nice if the
default was to force staging and require a command line override to
allow publishing to apache.releases (as I think every project to publish
to a staging directory
I am going to update server/trunk to use Genesis 2.0 shortly. Yes I
will add some new wiki pages, just wanted to get some feedback first.
--jason
On Sep 9, 2008, at 8:12 PM, Donald Woods wrote:
I like the new option to force staging instead of publishing to
apache.releases (which I was
Geronimo Revision: 693197 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080908/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080908
[INFO] BUILD
Looks good Jason. I too agree that it should be required to stage
locally and scp to a public location for the vote. I too have had
things accidentally pushed to rsync too soon.
Will the release:rollback and stage:copy remain unchanged? Also, has
this been validated with multiple
We rolled back to OpenJPA 1.0.3 yesterday, due to TCK failures with the
newer 1.2.0 release. As soon as Jason W. verifies that most of the
problems he was seeing are gone, I'll publish a RC1 for everyone to
start looking at.
-Donald
Donald Woods wrote:
Time to start the discussion on
[
https://issues.apache.org/jira/browse/GERONIMO-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned GERONIMO-4285:
-
Assignee: Jarek Gawor
The simple mode of server command general option --syserr and
Upgrade to OpenJPA 1.0.3
Key: GERONIMO-4288
URL: https://issues.apache.org/jira/browse/GERONIMO-4288
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components:
[
https://issues.apache.org/jira/browse/GERONIMO-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-4288.
--
Resolution: Fixed
Rev693197 in branches/2.1.3
Rev693490 in branches/2.0 (2.0.3-SNAPSHOT)
[
https://issues.apache.org/jira/browse/GERONIMO-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4278:
---
Fix Version/s: (was: 2.1.3)
(was: 2.0.3)
backed down to 1.0.3
[saaj] javax.xml.soap.MessageFactory property is not optional
-
Key: GERONIMO-4289
URL: https://issues.apache.org/jira/browse/GERONIMO-4289
Project: Geronimo
Issue Type: Bug
[
https://issues.apache.org/jira/browse/GERONIMO-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated GERONIMO-4289:
---
Attachment: saaj.diff
[saaj] javax.xml.soap.MessageFactory property is not
[
https://issues.apache.org/jira/browse/GERONIMO-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned GERONIMO-4289:
--
Assignee: Jarek Gawor
[saaj] javax.xml.soap.MessageFactory property is not
[
https://issues.apache.org/jira/browse/GERONIMO-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4285.
---
Resolution: Fixed
Fix Version/s: 2.2
2.1.3
Changed the short
pop3s: java.lang.IllegalArgumentException: hostname can't be null
-
Key: GERONIMO-4290
URL: https://issues.apache.org/jira/browse/GERONIMO-4290
Project: Geronimo
Issue Type:
[
https://issues.apache.org/jira/browse/GERONIMO-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire reassigned GERONIMO-4290:
--
Assignee: Rick McGuire
pop3s: java.lang.IllegalArgumentException: hostname can't
[
https://issues.apache.org/jira/browse/GERONIMO-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-4290.
Resolution: Fixed
Committed revision 693530.
pop3s:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed closed GERONIMODEVTOOLS-485.
--
Resolution: Fixed
Applied patch at r693553 that included the changes
When running the testsuite from maven, the Geronimo branding does not show up
-
Key: GERONIMODEVTOOLS-512
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-512
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-512:
---
Issue Type: Sub-task (was: Test)
Parent:
Unable to deploy tomcat app with WADI Cluster
-
Key: GERONIMO-4291
URL: https://issues.apache.org/jira/browse/GERONIMO-4291
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
[
https://issues.apache.org/jira/browse/GERONIMO-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-4291.
--
Resolution: Fixed
Rev693561 in branches/2.1.3
Rev693562 in branches/2.1 (2.1.4-SNAPSHOT)
[
https://issues.apache.org/jira/browse/GERONIMO-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629581#action_12629581
]
Jarek Gawor commented on GERONIMO-4276:
---
I committed some updates so that the
[
https://issues.apache.org/jira/browse/GERONIMO-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4276:
---
Fix Version/s: (was: 2.1.4)
2.1.3
Updated fix version from 2.1.4
[
https://issues.apache.org/jira/browse/GERONIMO-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Kirby resolved GERONIMO-4276.
-
Resolution: Fixed
Fix Version/s: (was: 2.1.3)
2.1.4
Is there a reason why we don't redirect java.util.logging to SLF4J? I
think some applications use java.util.logging (spring?) to log the
info and so it might be confusing to the user which file to modify the
enable appropriate debugging for the application
(server-log4j.properties or JVM's
Geronimo Revision: 693568 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080909/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080909
[INFO] BUILD
Monitoring console is pulling in DWR 2.0.1
--
Key: GERONIMO-4292
URL: https://issues.apache.org/jira/browse/GERONIMO-4292
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
Geronimo Revision: 693673 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080909/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080909/unit-test
Hi Donald,
Looks like all the big ones that popped up have been dealt with. I'll run
the RC through whenever it's ready.
Thanks!
On Tue, Sep 9, 2008 at 10:38 AM, Donald Woods [EMAIL PROTECTED] wrote:
We rolled back to OpenJPA 1.0.3 yesterday, due to TCK failures with the
newer 1.2.0
[
https://issues.apache.org/jira/browse/GERONIMO-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-4292.
--
Resolution: Fixed
Rev693679 in branches/2.1.3
Rev693678 in branches/2.1 (2.1.4-SNAPSHOT)
Here is what is done as of Rev693682 which will be used to create RC1:
- branches/2.1.3 updated to version=2.1.3
- mvn rat:check run on source and generated artifacts/assemblies
- RELEASE-NOTES-2.1.3 updated
- Release Status page udpated -
I looked at the new plugin groups stuff and have a couple ideas/
suggestions.
I'm going to create a framework plugin group. Is there some reason
this won't work?
I'd like to see the plugin groups distributed closer to where their
components are found, e.g. web-jetty in plugins/jetty.
use generics in the kernel interface and related code.
--
Key: GERONIMO-4293
URL: https://issues.apache.org/jira/browse/GERONIMO-4293
Project: Geronimo
Issue Type: Bug
Security
On Sep 9, 2008, at 11:56 PM, David Jencks wrote:
I looked at the new plugin groups stuff and have a couple ideas/
suggestions.
I'm going to create a framework plugin group. Is there some reason
this won't work?
I'd like to see the plugin groups distributed closer to where their
[
https://issues.apache.org/jira/browse/GERONIMO-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629697#action_12629697
]
David Jencks commented on GERONIMO-4293:
rev 693702 fixes the stuff that bothers
[
https://issues.apache.org/jira/browse/GERONIMO-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629698#action_12629698
]
David Jencks commented on GERONIMO-4284:
rev 693703 fixes a lot of jpa problems
[
https://issues.apache.org/jira/browse/GERONIMO-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629701#action_12629701
]
David Jencks commented on GERONIMO-4284:
rev 693704 adds a plugin-farm-node
41 matches
Mail list logo
