[ http://issues.apache.org/jira/browse/GERONIMO-2577?page=all ]
Kaoru Matsumura updated GERONIMO-2577:
--
Attachment: geronimo-new.log
Adding information
I have attached the whole geronimo.log(except [McastService] ping) of the last
remaining node.
Are there new features for 1.2 already?
Since it takes a while for us to get releases out, its probably best
to minimize non-bugfix changes to the branch, though I suppose if its
a minor improvement that is should be fine, major feature work should
be avoided (preferring that for 2.0 actual
Hi Jason,
Thank you for your clarification. Since 1.2 beta is out, I was under the
impression that we will be stabilizing the 1.2 branch and not put any new
functions/improvements. New functions/improvements can still go into 1.x.
My confusion was whether to hold back commits to branches\1.2 un
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=comments#action_12461148
]
Kaoru Matsumura commented on GERONIMO-2577:
---
Thank you for advice.
I tried your geronimo-web-new.xml.
I observed the same log message as you noticed
Um... its where code for the 1.2* line of Geronimo goes.
I'd imagine that if a a fix for "1.x" is applicable for the 1.2 line
then it could be committed there, probably also to branches/1.1 too
if its a bug fix for both.
Sure improvement fixes can still go into 1.2, and be marked for fix
APACHE GERONIMO STATUS: -*-text-*-
Last modified at [$Date: 2006-12-07 13:03:14 -0500 (Thu, 07 Dec 2006) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/geronimo/server/trunk/STATUS
Upcoming Releases:
Geronimo 1
A little holiday update on build automation muck...
Turns out jolly ole st. nick brought me some coal for all of this
anthill effort. I had thought that it would be easier/faster to get
automated TCK builds up and running with direct effect than it would
be to put more time into the GBuild codeb
Vote passes with 9 +1s (8 binding) and no other votes.
-David
On Dec 20, 2006, at 10:54 PM, David Blevins wrote:
I've done the work to fix some of our spec jars so they are
compliant and would like us to start releasing them and removing
snapshot references from our builds.
The first one
Vote passes with 7 +1s (6 binding) and no other votes.
-David
On Dec 20, 2006, at 11:55 PM, David Blevins wrote:
Fixed, verified to be compliant and ready for release.
Release Branch: https://svn.apache.org/repos/asf/geronimo/specs/
branches/geronimo-jpa_3.0_spec-1.0
I hereby propose we r
Vote passes with 8 +1s (7 binding) and no other votes.
-David
On Dec 20, 2006, at 11:47 PM, David Blevins wrote:
Verified and compliant and ready for release.
Release Branch: https://svn.apache.org/repos/asf/geronimo/specs/
branches/geronimo-interceptor_3.0_spec-1.0
I hereby propose we re
Vote passes with 8 +1s (7 binding) and no other votes.
-David
On Dec 20, 2006, at 11:40 PM, David Blevins wrote:
Verified and compliant and ready for release.
Release Branch: https://svn.apache.org/repos/asf/geronimo/specs/
branches/geronimo-jta_1.1_spec-1.0
I hereby propose we release th
What is the purpose of branches\1.2 as it stands now? Can fixes targeted
for "1.x" be committed to this branch? If not, where should this ffixes
go? Can fixes for JIRAs marked as "Improvement" be still committed to
branches\1.2 and designated as fixed in "1.2"?
--vamsi
we actually do nightly builds on ws.zones.apache.org and the snapshots
are available there:
ws.zones.apache.org/repository/
the snapshot jars are also ssh/copied over to
people.apache.org/repo/m1-snapshot-repository/
So that makes it 2 points of failure instead of just one. We did this
during th
On Dec 27, 2006, at 6:05 PM, Davanum Srinivas wrote:
Example: We could host a https://geronimo.zones.apache.org/repository
there and nightlies off of continuum. Of course, #asfinfra folks won't
let us run our own svn server :)
If they won't let us run our own svn server... then we loose much of
Example: We could host a https://geronimo.zones.apache.org/repository
there and nightlies off of continuum. Of course, #asfinfra folks won't
let us run our own svn server :)
How about a bazaar backed maven2 repo? (http://bazaar-vcs.org/)
-- dims
On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> wr
Not that I am aware of... though I'm not sure what we would do with a
zone anyways... from talking with some peeps in #infra seems like we
are really restricted to what we can run on a zone, so I don't see
the point of using it.
But maybe if we could run a simple svn server there for this r
Do we have a request pending for a geronimo.zones.apache.org?
-- dims
On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Thanks Kevan for looking into this.
This is one of the big issues I have with mvn and SNAPSHOT
artifacts... other peoples projects can break your projects build
with out a
Thanks Kevan for looking into this.
This is one of the big issues I have with mvn and SNAPSHOT
artifacts... other peoples projects can break your projects build
with out any notice, no change log, and in many cases hours of
someone debugging a build to figure it out.
Perhaps we should sim
I updated the project Pom to refer to the older SNAPSHOT for now.
I'll contact the XMLBeans guys to work on the issue.
On Dec 27, 2006, at 12:33 PM, Kevan Miller wrote:
On Dec 26, 2006, at 6:55 PM, Jason Dillon wrote:
I've run the server/trunk build twice on JDK 1.5 twice from a
clean re
On Dec 26, 2006, at 6:55 PM, Jason Dillon wrote:
I've run the server/trunk build twice on JDK 1.5 twice from a clean
repo, both times it fails here:
[INFO]
--
--
[INFO] Building Geronimo :: Service :: Builder
[INFO]
[ http://issues.apache.org/jira/browse/GERONIMO-2577?page=all ]
Jeff Genender updated GERONIMO-2577:
Attachment: geronimo-web-new.xml
> Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current
> node is down.
> -
[
http://issues.apache.org/jira/browse/GERONIMO-2577?page=comments#action_12461007
]
Jeff Genender commented on GERONIMO-2577:
-
I am able to get the listeners running fine for the geronimo-web-new.xml file
that I have attached. You wil
[ http://issues.apache.org/jira/browse/GERONIMO-2027?page=all ]
Vamsavardhana Reddy closed GERONIMO-2027.
-
Resolution: Fixed
Fixed in rev 490485 in branches\1.1, branches\1.2 and trunk.
> Mismatched passwords when editing user in web console
> -
[ https://issues.apache.org/activemq/browse/SM-794?page=all ]
Guillaume Nodet resolved SM-794.
Resolution: Fixed
Author: gnodet
Date: Wed Dec 27 04:09:58 2006
New Revision: 490484
URL: http://svn.apache.org/viewvc?view=rev&rev=490484
Log:
SM-794: jsr181
[ http://issues.apache.org/jira/browse/GERONIMO-2027?page=all ]
Vamsavardhana Reddy updated GERONIMO-2027:
--
Fix Version/s: 1.1.2
1.2
2.0-M2
Affects Version/s: 1.1.1
1.1.
jsr181 proxy does not throw faults correctly when used in jaxws mode
Key: SM-794
URL: https://issues.apache.org/activemq/browse/SM-794
Project: ServiceMix
Issue Type: Bug
+1
On Dec 21, 2006, at 1:54 AM, David Blevins wrote:
I've done the work to fix some of our spec jars so they are
compliant and would like us to start releasing them and removing
snapshot references from our builds.
The first one I fixed is javax.annotation 1.0:
Release Branch: https://sv
[ http://issues.apache.org/jira/browse/GERONIMO-1464?page=all ]
Vamsavardhana Reddy updated GERONIMO-1464:
--
Patch Info: [Patch Available]
> Avoid use of file.deleteOnExit() - will cause allocation of 1K of memory per
> call until JVM terminates
[ http://issues.apache.org/jira/browse/GERONIMO-1464?page=all ]
Vamsavardhana Reddy updated GERONIMO-1464:
--
Attachment: G-1464.patch
G-1464.patch:
I have scanned the trunk (rev 490474) and found references to deleteOnExit() in
the following cl
29 matches
Mail list logo
