Aaron,
What JIRA is associated with this change?
Thanks,
John
[EMAIL PROTECTED] wrote:
Author: ammulder
Date: Tue Jul 25 08:55:34 2006
New Revision: 425429
URL: http://svn.apache.org/viewvc?rev=425429&view=rev
Log:
Module and name are independent of artifact
Modified:
geronimo/branches/
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: jira-g--xerces-test.zip
Attached test application that demonstrates Xerces problem when TCCL is not
correctly set during deployment
Is
1.1\modules\deployment\src\java\org\apache\geronimo\deployment\SingleFileHotDeployer.java
still used? I can see anything referencing it except for some tests.
It was added in April 2006 by Dain in
http://svn.apache.org/viewcvs?rev=397307&view=rev
What is its relationship to the
org.apac
issues)
Components: website
Affects Versions: 1.2
Reporter: John Sisson
Priority: Minor
Fix For: 1.2
Currently the Geronimo site is build using Ant.
The Ant build has been recently updated to use Velocity to 1.5-dev (I built
from svn rev 386004) to
[ http://issues.apache.org/jira/browse/GERONIMO-1748?page=all ]
John Sisson closed GERONIMO-1748.
-
Fix Version/s: (was: 1.2)
Resolution: Duplicate
Assignee: John Sisson
I seem to remember Jacek saying (a while ago..) we should
: website
Reporter: John Sisson
Priority: Trivial
Currently the Geronimo site is build using Ant.
The Ant build has been recently updated to use Velocity to 1.5-dev (I built
from svn rev 386004) to fix issue where generated html files have inconsistent
line endings when
[
http://issues.apache.org/jira/browse/GERONIMO-2208?page=comments#action_12423200
]
John Sisson commented on GERONIMO-2208:
---
Could you please provide some more information on the steps to reproduce this
problem, along with a stackstrace
the XBean page itself).
Cheers!
Hernan
Jacek Laskowski wrote:
On 7/20/06, John Sisson <[EMAIL PROTECTED]> wrote:
Should a link be added on the
http://geronimo.apache.org/subprojects.html page to the
http://geronimo.apache.org/xbean/ site? Currently I don't think there
are any links
I plan to commit the patch attached to this JIRA soon for 1.1.1, as it
is a bug fix and trunk if there aren't any objections.
Regards,
John
John Sisson (JIRA) wrote:
Application errors in static initialization blocks during serialization of
configuration during deployment due to inco
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: GERONIMO--v1.patch
Proposed patch attached. Has been tested using the application previously
attached to this JIRA.
> Applicat
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: jira-g-.zip
Test application attached that prints out the TCCL during static initialization
in an EJB. If you deploy the EAR you will
URL: http://issues.apache.org/jira/browse/GERONIMO-
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 1.1, 1.0
Reporter: John Sisson
Assigned To: John
I don't see your mail there
http://mail-archives.apache.org/mod_mbox/ws-scout-dev/
John
Jason Dillon wrote:
So far no response from the scout peeps...
:-(
--jason
On Jul 19, 2006, at 4:34 PM, John Sisson wrote:
I noticed the scout.log entry below. I looked in
geronimo-1.1\repos
/56M
[INFO]
Building OpenEJB2...
Authentication realm: <https://svn.codehaus.org:443> openejb Repo
Password for 'sissonj':
John
Thanks,
--jason
On Jul 20, 2006, at 10:02 PM, John Sisson wrote:
It built successful
Versions: 2.5
Reporter: John Sisson
Assigned To: Dain Sundstrom
Priority: Minor
Fix For: 2.6
Update xbean poms with current site and mailing list addresses. They currently
point to xbean.org.
--
This message is automatically generated by JIRA.
-
If you
: public (Regular issues)
Components: website
Reporter: John Sisson
Assigned To: Dain Sundstrom
Priority: Minor
A link needs to be added on the http://geronimo.apache.org/subprojects.html
page to the http://geronimo.apache.org/xbean/ site
--
This message
It built successfully for me in cygwin (first attempt failed in timer
tests). I'll try to do some tests on the weekend.
I agree with Jeff's comments that we should have this pass the TCK
before it is merged back to trunk.
Thanks,
John
Jason Dillon wrote:
This should do the trick:
svn
Should a link be added on the
http://geronimo.apache.org/subprojects.html page to the
http://geronimo.apache.org/xbean/ site? Currently I don't think there
are any links to XBean from the Geronimo site.
The XBean poms also need to be updated with the new website address
instead of http://xbe
Hi Aaron,
What license is the documentation content at your
http://www.geronimoplugins.com site under? For example the FAQ and the
PDF http://www.geronimoplugins.com/geronimo-plugin-workshop.pdf ?
I would like to look at copying some of the documentation about the
plugin architecture to Ge
Sorry for the slow response.. comments inline.
Kevan Miller wrote:
On Jul 18, 2006, at 6:43 PM, Alan D. Cabrera wrote:
Kevan Miller wrote:
On Jul 18, 2006, at 8:53 AM, John Sisson wrote:
Whilst testing the geronimo eclipse plugin, eclipse prompted me to
acknowledge the Sun license at
I noticed the scout.log entry below. I looked in
geronimo-1.1\repository\scout\scout\0.5\scout-0.5.jar in the
log4j.properties file and it has log4j.debug uncommented!
I think that is the culprit. May want to send a mail to the scout
project http://ws.apache.org/scout/
John
Jason Dillon w
ot;release" to ibiblio should have appropriate
license and notice files (alternatively, we stop releasing the
artifact).
--kevan
Jason Dillon wrote:
If we want to keep these guys in the jars, then we should move them
to their standard src/main/resources/META-INF/* locations so that
On Jul 18, 2006, at 9:01 PM, John Sisson wrote:
I have already run into problems with path lengths in the 1.1 branch
with daytrader now we have moved to 1.1.1-SNAPSHOT. See
https://issues.apache.org/jira/browse/DAYTRADER-6
Considering the number of developers (and possibly future developers
I have already run into problems with path lengths in the 1.1 branch
with daytrader now we have moved to 1.1.1-SNAPSHOT. See
https://issues.apache.org/jira/browse/DAYTRADER-6
Considering the number of developers (and possibly future developers) on
the windows platform, we should ensure it wor
Installed eclipse 3.2, installed JST (J2EE Standard Tools and its
dependencies), pointed it to an existing geronimo installation and
created a J2EE project. I haven't had the time to read eclipse
tutorials on using the JST, so didn't build anything.
Have you thought about using a tool like wi
Whilst testing the geronimo eclipse plugin, eclipse prompted me to
acknowledge the Sun license at
http://developers.sun.com/license/berkeley_license.html when caching the
j2ee schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ).
This made me wonder whether this license has bee
[ http://issues.apache.org/jira/browse/DAYTRADER-6?page=all ]
John Sisson updated DAYTRADER-6:
Fix Version/s: (was: 1.1.1)
> Longer version (1.1.1) causes build failures on Windows in daytrader-jetty
>
[
http://issues.apache.org/jira/browse/DAYTRADER-6?page=comments#action_12421758
]
John Sisson commented on DAYTRADER-6:
-
I found that if I renamed the project.xml files in the following projects so
they are ignored the build succeeded
+1 to all of these if you have the time to get them into 1.1.1. Even
though some can be considered features they are really resolving
usability issues. After all, there is no point having a server that is
compliant but not usable in the real world.
Thanks,
John
Matt Hogstrom wrote:
I opened
[ http://issues.apache.org/jira/browse/GERONIMO-2117?page=all ]
John Sisson closed GERONIMO-2117.
-
Fix Version/s: 1.2
Resolution: Fixed
> Remove deployer-log4j.properties files - they are no longer u
[ http://issues.apache.org/jira/browse/GERONIMO-2197?page=all ]
John Sisson closed GERONIMO-2197.
-
Fix Version/s: 1.2
Resolution: Fixed
> NPE when the "edit" link is selected on the Security Realms
: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 1.1
Reporter: John Sisson
Assigned To: John Sisson
Fix For: 1.1.1
h1. Problem
Cannot edit a security realm by clicking on the "ed
Jason Dillon wrote:
Um... when were these ever included in the module's jars before?
--jason
On Jul 16, 2006, at 5:04 PM, John Sisson wrote:
Jason Dillon wrote:
Does each module really need LICENSE.txt and NOTICE.txt?
Or can we just have this at the top-level of the project?
I
Jason Dillon wrote:
Does each module really need LICENSE.txt and NOTICE.txt?
Or can we just have this at the top-level of the project?
I'd rather have less duplicate files to maintain...
Any comments?
--jason
I think they are needed as each downloadable jar (which each module has)
should co
It is related to some changes you made ages ago. The JIRA has all the
details.
I'll go ahead and delete the files once I have your confirmation.
Thanks,
John
[ http://issues.apache.org/jira/browse/GERONIMO-2117?page=all ]
John Sisson updated GERONIMO-2117:
--
Description:
Description
The Geronimo 1.1 distribution contains a var\log\deployer-log4j.properties
file but the file is not used.
Symptom
[ http://issues.apache.org/jira/browse/GERONIMO-2194?page=all ]
John Sisson closed GERONIMO-2194.
-
Resolution: Fixed
> Eclipse project names not generated consistently
>
>
> K
p for Geronimo Bugs is
simple enough. I can help. BTW, what about our RTC state
discussion? Can I go ahead and move on that idea?
Regards,
Alan
John Sisson wrote:
I'm fine with using fields instead, as it would be more work for
developers to use the wiki syntax (especially if they aren&
detail (e.g. example text).
Comments?
John
Jason Dillon wrote:
I think if we want to get folks to give us these sections of data that
we should probably add fields for them to fill in, not ask them to use
a wiki-based template.
--jason
On Jul 15, 2006, at 6:51 PM, John Sisson wrote:
A
x27;d have to have some descriptive
text so people could tell what to put where.
Thanks,
Aaron
On 7/15/06, John Sisson <[EMAIL PROTECTED]> wrote:
What does everyone think of adopting a format similar to what I have
used in http://issues.apache.org/jira/browse/GERONIMO-2194 for JIRA
issu
[ http://issues.apache.org/jira/browse/DAYTRADER-6?page=all ]
John Sisson updated DAYTRADER-6:
Fix Version/s: 1.1.1
Affects Version/s: 1.1.1
> Longer version (1.1.1) causes build failures on Windows in daytrader-jetty
>
: DayTrader
Issue Type: Bug
Components: buildsystem
Reporter: John Sisson
Whilst developing Geronimo 1.1 for the 1.1 release I was able to build ok from
a windows path C:\dev\geronimo\br\1.1 . Now that the versions have been bumped
up to 1.1.1 I am now getting build
What does everyone think of adopting a format similar to what I have
used in http://issues.apache.org/jira/browse/GERONIMO-2194 for JIRA
issues for "bug fixes". I expect we would use a different format for
enhancements. I got the idea from Derby's wiki page
http://wiki.apache.org/db-derby/Re
(Regular issues)
Components: buildsystem
Affects Versions: 1.1
Environment: Maven eclipse plugin version 1.11
Reporter: John Sisson
Assigned To: John Sisson
Priority: Trivial
Fix For: 1.1.1
h1. Problem
When running maven the maven
James Strachan wrote:
I've just applied 2 trivial bug fixes to the xbean-spring module of
XBean.
The first is a patch from Guillaume which is a one liner to create the
xml parser using a helper method (used by all the other
ApplicationContext implementations).
http://issues.apache.org/jira/brow
Jason Dillon wrote:
Seems reasonable to me.
This will also go into trunk?
Definitely :-)
Regards,
John
--jason
On Jul 6, 2006, at 8:04 PM, John Sisson wrote:
In the "Derby library does not have line number debug information"
mail thread [1] a few weeks ago I asked whether peo
In the "Derby library does not have line number debug information" mail
thread [1] a few weeks ago I asked whether people wanted to upgrade to
the Derby 10.1.3 maintenance release [2].
David Jencks was the only person who mentioned it should go in the 1.1.1
release but did not hear any objecti
[EMAIL PROTECTED] wrote:
Author: jdillon
Date: Thu Jul 6 18:43:26 2006
New Revision: 419764
URL: http://svn.apache.org/viewvc?rev=419764&view=rev
Log:
Merge changes for m2
Modified:
geronimo/trunk/m2-plugins/pom.xml (contents, props changed)
Hi Jason,
Can you please put the JIRA is
I have added the page "Committing patches to the Subversion Repository"
as a place to document the issues/recommendations involved in applying
and committing patches. See
http://cwiki.apache.org/confluence/display/GMOxDEV/Committing+patches+to+the+Subversion+Repository
It is very much under co
Congratulations Matt & Jeff!
Regards,
John
Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Last week the PMC voted to invite Jeff Genender and
Matt Hogstrom to join it. Both have accepted the
invitation and will be part of the team responsible
for overseeing the he
Jacek Laskowski wrote:
On 7/3/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
NOTE... the m2 build in trunk is already broken... this patches help
FIX MANY OF THOSE PROBLEMS!
NOTED, but... it's not broken. it has never worked so we can pretend
to call it broken. It's a small, but important point w
ds,
John
Take care,
Jeremy
P.S. - I'm a +1 on this if my vote isn't seen as biased. ;)
On 7/4/06, *John Sisson* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Alan,
What type of concerns do they have regarding its close association
with
Geronim
Jason,
INAL, but sections 10 B-E in their open source contract don't sound
appropriate for ASF use to me.
http://www.perforce.com/perforce/contracts/open_source.pdf
We wouldn't want the situation where we have to uninstall it or Apache
and the development community has to start paying for it
Matt Hogstrom wrote:
I think the Maven 2 work is a significant project. It appears to me
that RTC has worked really well in increasing e-mail traffic on the
list exponentially but I too would agree that it has not been totally
productive. Here is my assessment:
1. Everyone agrees that this
David,
I will ensure this gets followed up by Ken. CCing the PMC.
Regards,
John
David Jencks wrote:
On Jul 4, 2006, at 4:54 PM, John Sisson wrote:
Matt Hogstrom wrote:
I do not believe the +1's need to be from PMC members but other
committers. This is a snippet from Ken's pe
Alan,
What type of concerns do they have regarding its close association with
Geronimo?
Regards,
John
Alan D. Cabrera wrote:
I also am leaning towards the idea that it's good for OpenEJB to be
separate from Geronimo. Whenever I talk w/ users of OpenEJB, they are
always concerned about its
h when 1 got 3 committer +1s... And not even 1 PMC
member
looked at it. And that took over a week to garner enough votes.
Imagine
how long it would take if we had to get 3 PMC +1! I think we need to
clear
this up ASAP!
On 7/1/06, John Sisson <[EMAIL PROTECTED]> wrote:
AFAIK, it h
Jason Dillon wrote:
So far 2+ days, several patches... one PMC +1, one non-PMC +1 (with
caveat to ping JVZ)... now crazy problems with diff/patch.. which I'm
not exactly sure how that affects the current votes... or does adding
a new version of the patch negate anything else voted upon.
IMO, a
Jason Dillon wrote:
So far 2+ days, several patches... one PMC +1, one non-PMC +1 (with
caveat to ping JVZ)... now crazy problems with diff/patch.. which I'm
not exactly sure how that affects the current votes... or does adding
a new version of the patch negate anything else voted upon.
Have y
I had the same problem when you reported it, but didn't have time to
chase it up, but it seems fine now. Anyone know what happened?
John
Sachin Patel wrote:
So it looks like something is wrong with the mirrored jars on ibiblio.
If you take a look at any of the 1.1 jars Matt published to
htt
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
Lots of process...
* If a PMC member is the person who completes the vote (
three binding +1s and no vetos) for
[
http://issues.apache.org/jira/browse/GERONIMO-2132?page=comments#action_12418911
]
John Sisson commented on GERONIMO-2132:
---
What is the status of this JIRA, as there has been an svn commit for it
http://svn.apache.org/viewvc?rev=415034&view
[
http://issues.apache.org/jira/browse/GERONIMO-2161?page=comments#action_12418909
]
John Sisson commented on GERONIMO-2161:
---
My +1 above is for the GERONIMO-2161-v2.patch.
> [RTC] Remove Geronimo modules from dependencyManagement in root pom.
[
http://issues.apache.org/jira/browse/GERONIMO-2161?page=comments#action_12418906
]
John Sisson commented on GERONIMO-2161:
---
+1 : applied patch and tested build. Due to xmlbeans issue (which is a
separate problem not caused by this patch) It took
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
Lots of process...
* If a PMC member is the person who completes the vote (
three binding +1s and no vetos) for the latest version of the
patch then they
Alan D. Cabrera wrote:
John Sisson wrote:
Alan D. Cabrera wrote:
John Sisson wrote:
One of the issues I see with the current process we have for
changes under RTC is that it is hard to keep track of what patches
are pending RTC.
Ken suggested that we reintroduce the STATUS file as a way
[
http://issues.apache.org/jira/browse/GERONIMO-592?page=comments#action_12418821
]
John Sisson commented on GERONIMO-592:
--
Gorkem, can you please verify whether this problem still exists in the 1.1
release and if so provide more detailed error
[ http://issues.apache.org/jira/browse/GERONIMO-592?page=all ]
John Sisson closed GERONIMO-592:
Resolution: Cannot Reproduce
> Startup failure in Turkish language settings
>
>
> K
Alan D. Cabrera wrote:
John Sisson wrote:
One of the issues I see with the current process we have for changes
under RTC is that it is hard to keep track of what patches are
pending RTC.
Ken suggested that we reintroduce the STATUS file as a way of keeping
track of the status of patches
from an RTC needing three +1
votes from other committers to three +1 votes from a PMC member. Did
I miss an email that got sent out from the PMC?
Regards,
Alan
John Sisson wrote:
One of the issues I see with the current process we have for changes
under RTC is that it is hard to keep track
Jason Dillon wrote:
2. Not all communication regarding the fix is done in JIRA comments,
therefore people reviewing the fix have to search the mailing lists
and JIRA reducing the amount of time they have to actually review the
change. This also makes it harder for people in the future who look
One of the issues I see with the current process we have for changes
under RTC is that it is hard to keep track of what patches are pending RTC.
Ken suggested that we reintroduce the STATUS file as a way of keeping
track of the status of patches (
http://www.mail-archive.com/dev%40geronimo.apa
In the "Re: [RTC] Clarification please from the PMC" thread I raised
some issues regarding documenting changes made to the code and impacts
on the RTC process, other developers and end users.
Here is a summary of those comments:
There have been JIRAs for commits/RTCs where in the mailing list
Jason Dillon wrote:
NOTE: My comments below are not directed towards anyone in
particular... mostly this just expresses my frustration with some of
the more harmful politics that Apache Geronimo has picked up over the
past few months...
Although RTC has slowed down development a bit (or even
[
http://issues.apache.org/jira/browse/GERONIMO-2135?page=comments#action_12418545
]
John Sisson commented on GERONIMO-2135:
---
Comment from hiram on dev list 19th June (
http://www.mail-archive.com/dev%40geronimo.apache.org/msg24939.html) prior to
[
http://issues.apache.org/jira/browse/GERONIMO-2135?page=comments#action_12418544
]
John Sisson commented on GERONIMO-2135:
---
Comment from djencks on dev list 22nd June (
http://www.mail-archive.com/dev%40geronimo.apache.org/msg25153.html )
This
If we do move things around in trunk, will it make merging changes made
in the 1.1 branch more difficult? If so, how important is it to move
things now and would there be a better time to do it, e.g. when 1.1.1 is
released?
John
Jason Dillon wrote:
FYI, another reason to drop the old m1 file
I'd also be interested in calling in, preferably closer to 9:00pm if
possible.
http://www.timeanddate.com/worldclock/meetingtime.html?day=29&month=6&year=2006&p1=78&p2=240&p3=137&p4=179
John
Jules Gosnell wrote:
Matt Hogstrom wrote:
I was planning on attending the CeltiXFire BOF at 2100 Dubli
Matt Hogstrom wrote:
+1 John. If you would do that it would be excellent. The KEYS file
is http://www.apache.org/dist/geronimo/KEYS.
John Sisson wrote:
I noticed that the download page no longer has a KEYS link.
Yesterday (before the update to the site) the KEYS link at the very
bottom
)
Components: databases
Versions: 1.0, 1.1
Reporter: John Sisson
Assigned to: John Sisson
Fix For: 1.x
The Derby library we are using in Geronimo does not have line number debug
information, which is useful in stack traces. This has been addressed in the
upcoming Derby 10.1.3
I noticed that the download page no longer has a KEYS link. Yesterday
(before the update to the site) the KEYS link at the very bottom of the
download page pointed to http://people.apache.org/dist/geronimo/KEYS but
it seems there is a more up-to-date version in
http://www.apache.org/dist/geron
Jason Dillon wrote:
I agree that trunk should always be buildable... though its been
months since I've been able to build from the trunk :-P
I assume you mean you haven't been able to build using m2, not m1. m1
builds work fine for me.
John
--jason
On Jun 27, 2006, at 12:3
I don't think we should be removing files until we have a 100%
functional m2 build. The trunk should always be buildable.
If the M2 build isn't going to be straightforward we should have some
information in something like the README.txt file documenting how the
build should be executed.
Joh
Jason Dillon wrote:
Why does it fail the first time? This seems fishy too...
I'm rebuild again to see what it does, but that is painfully slow...
If we really do depend on a development version of the plugin, then we
should either...
Lobby to get the plugin released
or
Checkin and man
FYI.. This may be related to http://issues.apache.org/jira/browse/GERONIMO-2082
John
Jason Dillon wrote:
Any idea where the stax:stax-api:1.1.1-dev comes from?
The root pom states that stax:stax-api:1.0 should be used... but the
errors with the xmlbeans plugin all state 1.1.1-dev.
--jason
Jacek Laskowski wrote:
On 6/27/06, Jeff Genender <[EMAIL PROTECTED]> wrote:
I did it the old fashioned way...
I updated the svn for the raw code, then I made a short cut and just
edited the actual site. Made it so I didn't have to publish the whole
thing...I cheated ;-)
Does anyone know what
Jacek Laskowski wrote:
On 6/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Any objections to enabling wiki-rendering for the GERONIMO JIRA project?
This will allow comment and description fields to utilize Confluence-
style wiki markup.
Don't know what it will give us, but sounds fine.
Its
Are these being used/maintained? Should they be deleted to avoid confusion?
Thanks,
John
Jeff Genender wrote:
Hey folks,
I want to update the contributors page of the geronimo.apache.org site...
- Jeff Genender
Virtuas ---
+ Jeff Genender
Savoir Technologies
---
Is this ok?
Thanks,
Jeff
Congratulations.
Yo
Simon,
I just checked out http://svn.apache.org/repos/asf/geronimo/tags/1.1.0
and there were only two files containing 1.0-SNAPSHOT :
modules\activation\pom.xml
modules\client-builder\src\test-resources\plans\plan2.xml
Please try deleting your checkout of the tag and checkout again ( I seem
After looking more closely at your error, I think the problem may be due
to you hitting the windows filename length limit. Try building in a
directory whose name is too long.
I have been able to build the 1.1 branch on windows in a directory such
as "C:\dev\geronimo\br\1.1", but I believe tha
Hi Simon,
Can you try appending the "-e" maven option to your maven command, so
exceptions are displayed.
If after specifying the -e option you see it is an OutOfMemoryError,
then try setting the MAVEN_OPTS environment variable to:
-Xmx512m -XX:MaxPermSize=128m
If it was something else, p
Matt Hogstrom wrote:
A few days ago I had made a comment about Open for g-Business. Any
thoughts as to whether we should actually make this the server started
message? I don't know if this would be considered conflicting with
IBM's Open for e-Business message but I like the ring.
Thoughts?
[ http://issues.apache.org/jira/browse/GERONIMO-1564?page=all ]
John Sisson updated GERONIMO-1564:
--
Fix Version: 1.2
(was: 1.1)
Version: 1.1
> Use specific geronimo.assemble.xx properties in assembly project.xml fi
[ http://issues.apache.org/jira/browse/GERONIMO-1564?page=all ]
John Sisson reopened GERONIMO-1564:
---
This has been reopened as the proposed changes in the description have not been
made and are not in 1.1.
> Use specific geronimo.assemble
+1 to David's recap and to Matts plans below.
John
Matt Hogstrom wrote:
Thanks David, I tried to recap in the other thread and didn't receive
any additional responses so now that we have a branches/1.1.0
branches/1.1 and a branches/1.1.1 I don't think we quite nailed it.
Your summary is grea
Dain Sundstrom wrote:
On Jun 16, 2006, at 2:35 PM, David Jencks wrote:
--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
I have two thoughts:
1) we have an automated tool to track patches and it
can track votes
and send out these reports.
I'm not convinced automating this will work all that
we
+1 to release.
John
Matt Hogstrom wrote:
Here is the current status of voting.
I know we've had several issues we had to work through wrt to licenses
and other issues that have caused some respins. At this point I think
we're green for the release. Please take a few minutes to cast your
v
The Derby library we are using in Geronimo does not have line number
debug information, which is useful in stack traces.
This has been addressed in the upcoming Derby 10.1.3 release by
providing a lib-debug distribution (
http://issues.apache.org/jira/browse/DERBY-178 ) .
I'll raise a JIRA i
Matt Hogstrom wrote:
The corrections applied due to license files are first in this list.
Thanks to John for dogging this.
The distributions and builds were not affected. Based on previous
feedback the vote continues. Thanks for your feedback.
*Geronimo 1.1 Version*
*Source*
htt
101 - 200 of 1071 matches
Mail list logo
