[
https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3747.
--
Resolution: Fixed
Module parentage has been updated so that the module's parent is
I've fixed a few things in the testsuite and it seems to be running
fine. Most of the tests seemed to pass, though I do recall seeing one
failure, but I'm sleepy and can't remember where.
I checked the javaee5 and minimal assemblies to make sure they boot
up... which they do. Might have
I recently fixed a bug in the jacc spec jar so we need to finish
making sure it still works :-), release it, and get it into 2.1.
We should take a look at the specs in general and make sure the svn
tree is appropriately cleaned up. I think there are some problems
like the root pom
[
https://issues.apache.org/jira/browse/GERONIMO-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561611#action_12561611
]
David Jencks commented on GERONIMO-3776:
rev 614454 fixes the problem in a new
I see the following in Deployer.java
// todo jar url handling with Sun's VM on Windows leaves a lock
on the module file *preventing rebuilds*
// to address this we use a gross hack and copy the file to a
temporary directory
// the lock on the file will prevent
Well, with maven 2.0.7 and the 1,2 sources pulled from svn, I did the staged
build. The -Dstage=bootstrap built fine but the second -Dstage=assemble
failed with:
[INFO]
[INFO] Building Geronimo Configs :: OpenEJB
[INFO]
Has anyone come across this build error Error installing artifact's
metadata: Error installing metadata: Error updating group repository
metadata. only whitespace content allowed before start tag and not \u0
(position: START_DOCUMENT seen \u0... @1:1)? Output from build window
given below.
...OK, after tracking down some revision problems, I changed the openejb
version to 2.2-incubating and fixed the yoko version in the pom it
downloaded. Man, is maven a tangled web of lost dependencies... Anyway, I've
got it built.
Is this version of openejb a problem, it wanted the
[
https://issues.apache.org/jira/browse/GERONIMO-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561675#action_12561675
]
Vamsavardhana Reddy commented on GERONIMO-3764:
---
Incase of offline
On Jan 23, 2008, at 5:23 AM, Vamsavardhana Reddy wrote:
I see the following in Deployer.java
// todo jar url handling with Sun's VM on Windows leaves
a lock on the module file preventing rebuilds
// to address this we use a gross hack and copy the file
to a
On Jan 23, 2008, at 8:32 AM, Vamsavardhana Reddy wrote:
Has anyone come across this build error Error installing artifact's
metadata: Error installing metadata: Error updating group repository
metadata. only whitespace content allowed before start tag and not
\u0 (position: START_DOCUMENT
Sangjin Lee wrote:
The modified patch is there on JIRA. Some follow-up discussions...
I think the current implementation works well, but one thing that's
difficult to do is to collecting timing data. For example, some of
the most important instrumentation data are things like average
The changes you made look really nice. I think my only concern is
whether the Executor used by the EventDispatcher needs to be cleaned up
at some point. If it gets finalized appropriately and doesn't leave
dangling threads, then I guess I'm ok with it.
Rick
Sangjin Lee wrote:
I took a
Kevan,
I am testing this with an ear file. So, the EARConfiBuilder should be
reading this file. I guess it is the same with other builders as well. The
JarFileClassLoader has the following comment
* Note: This implementation currently does not work reliably on windows,
since the jar URL
argh... My bad... I should have read the message more carefully :(. I
thought it is failing to build the car. While building G 2.0 branch, my
system crashed 3 times in a span of 2 hours and the metadata file must have
got corrupted. Thanks Kevan.
On Jan 23, 2008 8:02 PM, Kevan Miller [EMAIL
On Jan 23, 2008, at 10:02 AM, Vamsavardhana Reddy wrote:
Kevan,
I am testing this with an ear file. So, the EARConfiBuilder should
be reading this file. I guess it is the same with other builders as
well. The JarFileClassLoader has the following comment
* Note: This implementation
Integrate and package samples and examples
---
Key: GERONIMODEVTOOLS-271
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-271
Project: Geronimo-Devtools
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-264:
---
Component/s: eclipse-plugin
Affects Version/s: 2.1.0
[
https://issues.apache.org/jira/browse/GERONIMO-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Leong updated GERONIMO-3778:
---
Attachment: GERONIMO-3778.patch
This patch will now report the list of plugins being
[
https://issues.apache.org/jira/browse/GERONIMO-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Leong resolved GERONIMO-3778.
Resolution: Fixed
Patch posted
downloadStatus page in plugin installer isn't grabbing
Jason,
Some modules there were moved from applications/ directory use
org.apache.geronimo.applications as groupId and some use
org.apache.geronimo.plugins. Should we use org.apache.geronimo.plugins
for all these apps to be consistent?
Jarek
On Jan 23, 2008 3:34 AM, Jason Dillon [EMAIL
[
https://issues.apache.org/jira/browse/GERONIMO-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Leong reopened GERONIMO-3778:
My apologies, it's not committed yet. Issue Re-opened
downloadStatus page in plugin
[
https://issues.apache.org/jira/browse/GERONIMO-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Leong updated GERONIMO-3778:
---
Patch Info: [Patch Available]
downloadStatus page in plugin installer isn't grabbing
Server assembly is not respecting version specified in pom
--
Key: GERONIMO-3779
URL: https://issues.apache.org/jira/browse/GERONIMO-3779
Project: Geronimo
Issue Type: Bug
On Jan 23, 2008, at 9:17 AM, Jarek Gawor wrote:
Jason,
Some modules there were moved from applications/ directory use
org.apache.geronimo.applications as groupId and some use
org.apache.geronimo.plugins. Should we use org.apache.geronimo.plugins
for all these apps to be consistent?
Yes, I
The executor created in the EventDispatcher is a daemon thread pool (that's
why I added DaemonThreadFactory), so it will go away cleanly without
cleanup.
Thanks,
Sangjin
On Jan 23, 2008 6:54 AM, Rick McGuire [EMAIL PROTECTED] wrote:
The changes you made look really nice. I think my only
I have found the culprit. It is the URLs that we use to read content from
an archive, for e.g., META-INF/application.xml from an ear file. The
deployer is creating a JarFile and closing the JarFile after the deployment
operation is completed. JarFile.close() closes all the InputStreams
obtained
[
https://issues.apache.org/jira/browse/GERONIMO-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561773#action_12561773
]
Vasily Zakharov commented on GERONIMO-3757:
---
Vamsavardhana,
I've tested the
Description of core feature confusing
-
Key: GERONIMODEVTOOLS-272
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272
Project: Geronimo-Devtools
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Kirby updated GERONIMODEVTOOLS-272:
---
Attachment: GD-272.patch
this patch changes the wording of the core
[
https://issues.apache.org/jira/browse/GERONIMO-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3677.
--
Resolution: Fixed
Add support for cli options for host/port and user/pass for commands
[
https://issues.apache.org/jira/browse/GERONIMO-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-2996:
--
Assignee: David Jencks (was: Jason Dillon)
I think you've implemented this right?
[
https://issues.apache.org/jira/browse/GERONIMO-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3771.
--
Resolution: Fixed
Move maven-plugins/* to buildsupport/* and update groupId to
On Jan 23, 2008 6:50 AM, Rick McGuire [EMAIL PROTECTED] wrote:
Only if it can be done without having to maintain the same sort of
request-to-start time map that you don't wish to do with the listener.
The process of adding data collection should cause memory bloat there
either, particularly
[
https://issues.apache.org/jira/browse/GERONIMO-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-2996.
--
Resolution: Fixed
Fix Version/s: 2.1
This got implemented some time ago.
Car
[
https://issues.apache.org/jira/browse/GERONIMO-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3761:
--
Attachment: GERONIMO-3761-v3.patch
A suggestion for adding request start time and connect
[
https://issues.apache.org/jira/browse/GERONIMO-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3761:
--
Attachment: TimeMonitor.java
A proof of concept for measuring average response time. For
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh reassigned GERONIMO-3451:
---
Assignee: Jay D. McHugh
Restricted listeners property file not found error
Hello all.
I have a new private snapshot of Tomcat ready to be checked into
Geronimo trunk. But G 2.0.x is using Tomcat 6.0.13 (trunk is using 6.0.14).
Does anyone have an objection to upgrading G 2.0.x to use Tomcat 6.0.14?
Jay
Jay D. McHugh (JIRA) wrote:
[
The specs tree seems to be in a mess with stuff in branches and waay
too much stuff in trunk, and many trunk poms having a xxx-SNAPSHOT
version where the latest tag is xxx.
I've attempted to document our previous decisions on spec development
and release in specs/branches/README:
WARNING
On Jan 23, 2008 10:02 PM, Alan D. Cabrera [EMAIL PROTECTED] wrote:
I would move what we hope someone else to pick up into the sandbox.
Everything else can get trashed.
I'd go even further - move everything to be retired to sandbox/retired
and let people work on it if/when they can benefit from
[
https://issues.apache.org/jira/browse/GERONIMO-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-3764:
--
Attachment: GERONIMO-3764-deploymentutil.patch
[
https://issues.apache.org/jira/browse/XBEAN-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera updated XBEAN-77:
--
Fix Version/s: (was: 3.1)
3.4
ClassFinder needs better error handling
[
https://issues.apache.org/jira/browse/XBEAN-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera updated XBEAN-92:
--
Fix Version/s: 3.4
UrlSet excludePaths() method throws a nullpointer exception if the pathString
[
https://issues.apache.org/jira/browse/GERONIMO-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3776.
--
Resolution: Fixed
rev 614698, used in geronimo. releasing the spec jar will happen during
Howdy,
I'm working on documenting the deployment plans for 2.1, part of that
documentation includes covering the XML schemas.
While looking at the schemas I see attributes-1.1.xsd and attributes-1.2.xsd
although I haven't found any reference to attributes-1.1. Are we still using
this schema?
Howdy,
I'm working on documenting the deployment plans for 2.1, part of that
documentation includes covering the XML schemas.
While looking at the schemas I see attributes-1.1.xsd and attributes-1.2.xsd
although I haven't found any reference to attributes-1.1. Are we still using
this schema?
Geronimo Revision: 614643 built with tests included
See the full build-1500.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080123/build-1500.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080123
[INFO] BUILD SUCCESSFUL
[INFO
Hey Hernan,
We should not be using 1.1 anymore.
If you -had- found somewhere that it was being used, then that would
have been a problem. The 1.2 version is where comment support was added
to the config.xml file.
Jay
Hernan Cunico wrote:
Howdy,
I'm working on documenting the deployment
My thunderbird just crashed and I lost all 2008 mails. I thought this one
didn't make it, cool it still hit the list.
I'm using rev #612130 and the binaries include a schema/attributes-1.1.xsd
I'll skip documenting attributes-1.1.xsd but somebody should remove it from the
build if we no
[
https://issues.apache.org/jira/browse/GERONIMO-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561855#action_12561855
]
Vasily Zakharov commented on GERONIMO-3757:
---
Another idea maybe to add the
Don't think we need a JIRA.
I'll go ahead and get rid of the old version.
It is still in use for Geronimo 2.0.x (and older).
Jay
Hernan Cunico wrote:
My thunderbird just crashed and I lost all 2008 mails. I thought this
one didn't make it, cool it still hit the list.
I'm using rev #612130
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561891#action_12561891
]
Jay D. McHugh commented on GERONIMO-3451:
-
Resolved this issue on trunk with a
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3451.
-
Resolution: Fixed
Fix Version/s: 2.1
Restricted listeners property file not
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561895#action_12561895
]
Jay D. McHugh commented on GERONIMO-3451:
-
Checked into branches/2.0 also:
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh closed GERONIMO-3451.
---
Restricted listeners property file not found error logged during Tomcat
server startup
[
https://issues.apache.org/jira/browse/GERONIMO-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh reassigned GERONIMO-3549:
---
Assignee: Jay D. McHugh
Potential vulnerability in Apache Tomcat Webdav servlet
[
https://issues.apache.org/jira/browse/GERONIMO-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3549.
-
Resolution: Fixed
Commits for Geronimo-3451 ('restricted listeners') also include
[
https://issues.apache.org/jira/browse/GERONIMO-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh closed GERONIMO-3549.
---
Potential vulnerability in Apache Tomcat Webdav servlet
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3450.
-
Resolution: Invalid
See Ramesh's comment.
Unable to Run Pluto 1.1 on Geronimo 2.0
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh closed GERONIMO-3450.
---
Unable to Run Pluto 1.1 on Geronimo 2.0
---
Jay,
Did you miss the new patch file when you checked this in? Actually,
would it be possible to create just one patch file that includes all the
changes in your tomcat source image and check that in? That way we only
need to apply one patch to recreate the image and all of the revision #s
Hi All,
I just checked out the latest trunk and am having trouble using the
install-plugin option. Here is the stack trace
22:27:02,812 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state:
abstractName=org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/c
Hmm... it looks like commons-logging-1.0.4.jar is getting included in
multiple places now:
[EMAIL PROTECTED]:~/target find . -name *logging*.jar
./geronimo-tomcat6-javaee5-2.1-SNAPSHOT/repository/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar
There were some odd compile problems for webapps which needed jcl. I'm not sure
why. Any help to fix would be appriciated. Also had to ad xmlbeans in a few
places too.
--jason
-Original Message-
From: Jarek Gawor [EMAIL PROTECTED]
Date: Wed, 23 Jan 2008 23:40:38
I think the install-plugin command only works for single plugins and
for some reason doesn't figure out what repository to look for
dependencies in. Try list-plugins where you specify the repo you
want to use.
thanks
david jencks
On Jan 23, 2008, at 8:16 PM, Viet Nguyen wrote:
Hi All,
[
https://issues.apache.org/jira/browse/GERONIMO-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561967#action_12561967
]
David Jencks commented on GERONIMO-3778:
Would you consider some code something
On Jan 23, 2008, at 12:42 PM, Dain Sundstrom wrote:
I think we have some modules that are no longer used by anyone and
the developer has given up on them, and was wondering if we should
retire them? Off the top of my head this is where we stand:
Keep:
xbean-classloader - Geronimo and
68 matches
Mail list logo
