[
http://issues.apache.org/jira/browse/GERONIMO-1466?page=comments#action_12362774
]
David Jencks commented on GERONIMO-1466:
I don't understand your question. We have fixed a bug in geronimo (jetty
security problem, requiring changing jetty
[ http://issues.apache.org/jira/browse/GERONIMO-1466?page=all ]
David Jencks reassigned GERONIMO-1466:
--
Assign To: Alan Cabrera (was: David Jencks)
Also, please don't change the assignment of an issue to ask a question. The
mailing list is more
Matt Hogstrom wrote:
First, I see there is a structure for versioning like:
v.r.m[.f] where:
v = Version
r = Release
m = modification
f = fix (optional)
Another minor point - these names are a bit unwieldy and it is
difficult to say:
1.0 is the version of a Version release.
1.0.1
Matt,
good initiative!
I would like to see the philosophy include a bit of process about how
a version is create.
For example a believe a fix release should definitely be created by
the application of a few carefully QA'd patches to an existing released
branch of the code.
More over, I would
I would like to create a dev branch to start working on some
1.1 and 2.0 stuff.
But I don't think it is appropriate to pollute /branch with
private branches as it will be good to be able to go there and see
all the official branches:
/branch/1.0
/branch/1.1
without seeing
Cross site scripting vulnerabilites
---
Key: GERONIMO-1474
URL: http://issues.apache.org/jira/browse/GERONIMO-1474
Project: Geronimo
Type: Bug
Components: console
Versions: 1.0
Reporter: Greg Wilkins
Fix For:
oliver karow wrote:
I played arround with geronimo 1.0 / Jetty 5.1.9 on Windows platform and
found two vulnerabilities:
thanks.
I've created http://issues.apache.org/jira/browse/GERONIMO-1474
cheers
[ http://issues.apache.org/jira/browse/GERONIMO-1474?page=all ]
Aaron Mulder updated GERONIMO-1474:
---
Component: security
Fix Version: 1.1
Description:
Reported by oliver karow:
The Web-Access-Log viewer does no filtering for
On 14 Jan 2006, at 22:27, lichtner wrote:
On Fri, 13 Jan 2006, James Strachan wrote:
The infiniband transport would be native code, so you could use JNI.
However, it would definitely be worth it.
Agreed! I'd *love* a Java API to Infiniband! Have wanted one for ages
google every once in a
Matt Hogstrom wrote, On 1/14/2006 9:02 PM:
I've seen several posts about the upcoming 1.0.x release and 1.1 and 2.0
etc. lately and I think its great that we're having these discussions.
I'd like to use this thread to aggregate people's thoughts about this
topic in a single thread for
[ http://issues.apache.org/jira/browse/GERONIMO-1466?page=all ]
Alan Cabrera reassigned GERONIMO-1466:
--
Assign To: Matt Hogstrom (was: Alan Cabrera)
Preparing 1.0 branch for development of 1.0.1
-
[
http://issues.apache.org/jira/browse/GERONIMO-1466?page=comments#action_12362790
]
Alan Cabrera commented on GERONIMO-1466:
You have updated the OpenEJB version during the course of your work to fix the
problem reported in GERONIMO-1433. When
Greg Wilkins wrote, On 1/15/2006 4:21 AM:
I would like to create a dev branch to start working on some
1.1 and 2.0 stuff.
But I don't think it is appropriate to pollute /branch with
private branches as it will be good to be able to go there and see
all the official branches:
/branch/1.0
I support your idea. Making branches for new feature development is
a common practice.
Were you thinking of doing it for every single change request, or only for
big ones?
On Sun, 15 Jan 2006, Greg Wilkins wrote:
I would like to create a dev branch to start working on some
1.1 and 2.0
APR's versioning guidelines are an awfully good practice, in my
experience.
http://apr.apache.org/versioning.html
-Brian
On Jan 15, 2006, at 10:42 AM, Alan D. Cabrera wrote:
Matt Hogstrom wrote, On 1/14/2006 9:02 PM:
I've seen several posts about the upcoming 1.0.x release and 1.1
and
I think I have found some information which if I had hardware available
would lead me to skip the prototyping stage entirely:
This paper benchmarks the performance of infiniband through 1) UDAPL and
2) Sockets Direct Protocol (SDP) - also available from openib.org:
Sockets Direct Protocol over
David,
To paraphrase what you said (if I understand correctly), the choices are
to either back clustering out of geronimo for the 1.0.1 release and work on it
for a future release, or to make minimal changes to it to make it work
in geronimo as is.
I think it's unlikely that there will be a
lichtner wrote:
Were you thinking of doing it for every single change request, or only for
big ones?
I don't think it is needed for every single change request.
Anything that is destined for the next release can be done in
trunk.
But a good place for dev branches would be great for anything
[
http://issues.apache.org/jira/browse/GERONIMO-1466?page=comments#action_12362793
]
David Jencks commented on GERONIMO-1466:
I assume you in the previous comment means me, david jencks. I personally
had nothing to do with fixing 1433, and fixing
[
http://issues.apache.org/jira/browse/GERONIMO-1475?page=comments#action_12362794
]
David Jencks commented on GERONIMO-1475:
Won't this break the packaging build from configs? These use the same
configurations, and rely on the jars being in the
[ http://issues.apache.org/jira/browse/GERONIMO-1475?page=all ]
Donald Woods updated GERONIMO-1475:
---
Attachment: Geronimo-1475.patch
attaching patch for client-system and j2ee-system to not duplicate Xerces files
into Repository
Configs needing
Changes to default log4j.rootCategory are not dynamic
-
Key: GERONIMO-1476
URL: http://issues.apache.org/jira/browse/GERONIMO-1476
Project: Geronimo
Type: Bug
Components: Logging
Versions: 1.0
[ http://issues.apache.org/jira/browse/GERONIMO-1466?page=all ]
Alan Cabrera updated GERONIMO-1466:
---
type: Task (was: Improvement)
Preparing 1.0 branch for development of 1.0.1
-
Key:
[
http://issues.apache.org/jira/browse/GERONIMO-1457?page=comments#action_12362801
]
David Jencks commented on GERONIMO-1457:
I don't see exactly how this can be related to the version change, but 2 spec
jars that are needed in lib weren't getting
[ http://issues.apache.org/jira/browse/GERONIMO-1396?page=all ]
Alan Cabrera updated GERONIMO-1396:
---
Fix Version: 1.1
1.x
(was: 1.0.1)
This is not a fix for a bug. It needs to go into trunk.
Provide consistent
[ http://issues.apache.org/jira/browse/GERONIMO-1182?page=all ]
Alan Cabrera updated GERONIMO-1182:
---
Fix Version: 1.1
1.x
(was: 1.0.1)
This is not a fix for a bug. It needs to go into trunk.
Connector portlet
JMX debug tool should not be loaded in the supplied config.xml
--
Key: GERONIMO-1477
URL: http://issues.apache.org/jira/browse/GERONIMO-1477
Project: Geronimo
Type: Bug
Components: security
[ http://issues.apache.org/jira/browse/GERONIMO-1448?page=all ]
Donald Woods updated GERONIMO-1448:
---
Attachment: Geronimo-1448.patch
Attaching patch created against latest AG 1.0 branch code for 1.0.1, which
fixed this on my local Tomcat build and
[ http://issues.apache.org/jira/browse/GERONIMO-1448?page=all ]
Donald Woods updated GERONIMO-1448:
---
Geronimo Info: [Patch Available]
Fix Version: 1.1
Assign To: Donald Woods
debug-tool does not work on Tomcat
Lets make something clear here...
There are two facets of clustering in Geronimo right now. WADI and
Tomcat clustering. The Tomcat clustering uses the Tomcat clustering
objects and GBeans and they work and have been tested including a full
howto in Confluence:
hi Jason,
I have tried without XA to keep it simple. XA would also work without
any issues. You can try this for XA support (
https://genericjmsra.dev.java.net/docs/userguide/userguide.html ).
With some modifications this works on geronimo.
Regards
Krishnakumar B
On 1/14/06, Jason Dillon
[
http://issues.apache.org/jira/browse/GERONIMO-1475?page=comments#action_12362814
]
Donald Woods commented on GERONIMO-1475:
David, I confirmed that my attached patch worked on WinXP by deleting my local
.maven directory and running the build
[
http://issues.apache.org/jira/browse/GERONIMO-1477?page=comments#action_12362817
]
David Jencks commented on GERONIMO-1477:
Fixed in head:
Sendingassemblies/j2ee-jetty-server/src/var/config/config.xml
Sending
[ http://issues.apache.org/jira/browse/GERONIMO-1477?page=all ]
David Jencks resolved GERONIMO-1477:
Resolution: Fixed
Assign To: David Jencks (was: Donald Woods)
Marking resolved pending discussion on port to 1.0.1
JMX debug tool
[
http://issues.apache.org/jira/browse/GERONIMO-1448?page=comments#action_12362820
]
David Jencks commented on GERONIMO-1448:
Applied to trunk, although since geronimo-web.xml is not used I removed it.
(it has been replaced by the plans in
35 matches
Mail list logo
