I've added a crontab to clean up old snapshots from the m2 snapshot
repo for ActiveMQ, Camel and ServiceMix.
If anyone needs to tinker with the script its here...
https://svn.apache.org/repos/asf/activemq/scripts/activemq-snapshots-clean.sh
This should hopefully keep the disk usage of our
Maybe we should use 30 days instead of 7 in case something wrong happen.
It may be safer...
On Aug 29, 2007, at 9:35 AM, James Strachan wrote:
I've added a crontab to clean up old snapshots from the m2 snapshot
repo for ActiveMQ, Camel and ServiceMix.
If anyone needs to tinker with the script
Servicemix tooling changes to generate JBISharedLibraryDescriptor
-
Key: SM-1045
URL: https://issues.apache.org/activemq/browse/SM-1045
Project: ServiceMix
Issue Type: New
[
https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523468
]
Vamsavardhana Reddy commented on GERONIMO-2964:
---
Looks like we can not have this in 2.0.2 without
[
https://issues.apache.org/jira/browse/GERONIMO-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523480
]
Manu T George commented on GERONIMO-3444:
-
Yes this is a threading issue. Thanks for the analysis Aman.
[
https://issues.apache.org/jira/browse/GSHELL-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-21.
--
Resolution: Won't Fix
Fix Version/s: (was: 0.0.3)
Moved to using Plexus
Extend
On 8/29/07, Nodet Guillaume [EMAIL PROTECTED] wrote:
Maybe we should use 30 days instead of 7 in case something wrong happen.
It may be safer...
How about 14 days, splitting the difference? :)
It'd be great if we could have some kinda major alarm email if we've
gone say 4 days without any
Hi,
I have moved the Tuscany Plugin for Geronimo from sandbox to Geronimo
Plugins. The svn URL is
https://svn.apache.org/repos/asf/geronimo/plugins/tuscany . I had to add a
few additional repositories to the parent pom so that the plugin can be
built successfully with a clean m2 local
[
https://issues.apache.org/jira/browse/GERONIMO-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated GERONIMO-3208:
--
Affects Version/s: 2.1
2.0.x
Fix Version/s:
OpenEJB trunk at 570815
Geronimo Revision: 570816 built with tests skipped
See the full build-1000.log file at
http://people.apache.org/~prasad/binaries/trunk/20070829/build-1000.log
Building Geronimo trunk at Revision: 570816
Building OpenEJB trunk at 570815
[INFO] Scanning for projects
[
https://issues.apache.org/jira/browse/GERONIMO-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy closed GERONIMO-3208.
-
Resolution: Fixed
Thanks Aman for providing the patch.
Fixed in trunk and
What ever way we want to deal with this, I have created a JIRA GERONIMO-3448
to track it.
Vamsi
On 8/28/07, Jacek Laskowski [EMAIL PROTECTED] wrote:
On 8/27/07, David Jencks [EMAIL PROTECTED] wrote:
Aren't we supposed to prevent ejbs from starting threads? Does the
commonj thread pool
New threads launched from an EJB do not run as the same Subject as the
launching thread
---
Key: GERONIMO-3448
URL: https://issues.apache.org/jira/browse/GERONIMO-3448
HSQLDB embeded database URL can hang Geronimo web console
-
Key: GERONIMO-3449
URL: https://issues.apache.org/jira/browse/GERONIMO-3449
Project: Geronimo
Issue Type: Bug
Security
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell closed GERONIMODEVTOOLS-182.
--
Resolution: Fixed
Fix Version/s: 2.0
Assignee: Tim
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell reassigned GERONIMODEVTOOLS-189:
--
Assignee: Tim McConnell
Error opening geronimo-web.xml
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523611
]
Tim McConnell commented on GERONIMODEVTOOLS-189:
Hi Shane, the IllegalArgumentException is
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523616
]
Tim McConnell commented on GERONIMODEVTOOLS-189:
Meant to say that the
I'm trying to understand what we have discussed/decided so far. Please
let me know if my summary is on track and help me correct course.
We haven't discussed the actual maven groupIds/artifactIds/directory
names yet. So all names used in this summary are just as examples.
Summary:
Should we create a top-level wiki page in our documentation for Plugins? Or
is there one already that I am unable to find?
Vamsi
AFAIK, there isn't a wiki page for our plugins. But there is some
info about our plugins at this related page
http://cwiki.apache.org/GMOxDEV/pluggable-administration-console.html
Cheers
Prasad
On 8/29/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
Should we create a top-level wiki page in
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at
http://people.apache.org/~prasad/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO] Scanning for projects
] wrote:
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at
http://people.apache.org/~prasad/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO] Scanning
/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO] Scanning for projects...
Downloading: http://download.java.net/maven/1//
org.apache.geronimo.genesis.config/poms/project-config-1.2.pom
[WARNING] Unable to get resource
This reply would be a good one for the docs.
Hernan, do you want to take a stab at this or can you point me at the
right area to update?
-David
Begin forwarded message:
Resent-From: [EMAIL PROTECTED]
From: David Blevins [EMAIL PROTECTED]
Date: August 29, 2007 11:34:24 AM PDT
To: [EMAIL
On Aug 28, 2007, at 7:35 PM, Karan Malhi wrote:
I dont even think they can change log levels. We used the logic that
- if conf is present - use logging.properties
- if conf is present - logging.properties is absent- install
logging.properties and use it
- if conf is absent, assume embedded and
I'm going to take a couple days to see if I can get the plugin
installer in better shape.
My goals are:
- new schema as in GERONIMO-3330
- jaxb based
- easier to use the local maven repo as a plugin repo. This might be
done by having a scan repo and generate geronimo-plugins.xml from
all
OpenEJB trunk at 570947
Geronimo Revision: 570950 built with tests skipped
See the full build-1800.log file at
http://people.apache.org/~prasad/binaries/trunk/20070829/build-1800.log
Building Geronimo trunk at Revision: 570950
Building OpenEJB trunk at 570947
[INFO] Scanning for projects
]
[EMAIL PROTECTED] wrote:
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at http://people.apache.org/
~prasad/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO
-
Cheers
Prasad
On 29 Aug 2007 18:14:26 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at http://people.apache.org/
~prasad/binaries/trunk/20070829/build-1400.log
Building
-
Cheers
Prasad
On 29 Aug 2007 18:14:26 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at http://people.apache.org/
~prasad/binaries/trunk/20070829/build-1400.log
[
https://issues.apache.org/jira/browse/GERONIMO-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523729
]
Paul McMahan commented on GERONIMO-3438:
if you provide an empty context root in your plan then it will
The only way I know of is to do something like
Logger openejb = Logger.getInstance(LogCategory.OPENEJB, Foo.class);
boolean configured = openejb.getAllAppenders().hasMoreElements();
If there is an appender for OPENEJB then configured will be true and
we will know that OPENEJB was configured
Just thinking, could we do something with a Thread Context, i.e. if it
is an App Server Thread Context, then we do not use
embedded.logging.properties file, if it is an OpenEJB thread context
which is trying to access the Logger, then if we go with our existing
strategy.
I dont even know what I
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523744
]
Shane Blake commented on GERONIMODEVTOOLS-189:
--
Ok. I downloaded the new plugin released
/
~prasad/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO] Scanning for projects...
Downloading: http://download.java.net/maven/1//
org.apache.geronimo.genesis.config/poms/project-config-1.2.pom
[WARNING] Unable to get
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523744
]
shane.blake edited comment on GERONIMODEVTOOLS-189 at 8/29/07 6:09 PM:
Or maybe in one of the very first OpenEJB methods called by Geronimo
to start openejb in embedded mode we could add some code like
System.setProperty(openejb.logging,external);
the first time the Logger class is loaded, we check for this property
and if it has a value of external, then we do not
] wrote:
OpenEJB trunk at 570880
Geronimo Revision: 570882 built with tests skipped
See the full build-1400.log file at http://people.apache.org/
~prasad/binaries/trunk/20070829/build-1400.log
Building Geronimo trunk at Revision: 570882
Building OpenEJB trunk at 570880
[INFO] Scanning
This sounds great! Thanks David.
Best wishes,
Paul
On Aug 29, 2007, at 3:26 PM, David Jencks wrote:
I'm going to take a couple days to see if I can get the plugin
installer in better shape.
My goals are:
- new schema as in GERONIMO-3330
- jaxb based
- easier to use the local maven repo as
I think we don't really need svn, lets just mail around patches we
make to the list and get rid of this scm crapo... too much work for
too little benifit lol
:-P
--jason
On Aug 29, 2007, at 10:12 AM, Prasad Kashyap wrote:
I'm trying to understand what we have discussed/decided so
Unable to Run Pluto 1.1 on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
42 matches
Mail list logo
