I too faced the same problem recently while building GEP with an empty m2
repo, and I resolved it by copying missing artifacts from the repository of
a Geronimo 2.0.1 install.
But, this should be fixed before we release GEP 2.1.
On Thu, Feb 28, 2008 at 12:46 PM, Jacek Laskowski [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/GSHELL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573190#action_12573190
]
Jason Dillon commented on GSHELL-92:
What about the annotations that are used to
[
https://issues.apache.org/jira/browse/GSHELL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573197#action_12573197
]
Guillaume Nodet commented on GSHELL-92:
---
No, annotated objects can be loaded without
Upgrade SLF4J to 1.5.0
--
Key: GSHELL-104
URL: https://issues.apache.org/jira/browse/GSHELL-104
Project: GShell
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Build
[
https://issues.apache.org/jira/browse/GSHELL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-92.
--
Resolution: Fixed
Added {{LayoutMarshaller}} to hold all the {{marshal}} and {{unmarshall}}
related
[
https://issues.apache.org/jira/browse/GSHELL-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-105.
---
Resolution: Fixed
Upgrade Log4j to 1.2.15
---
Key:
Upgrade Log4j to 1.2.15
---
Key: GSHELL-105
URL: https://issues.apache.org/jira/browse/GSHELL-105
Project: GShell
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Build
[
https://issues.apache.org/jira/browse/GSHELL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-104.
---
Resolution: Fixed
Upgrade SLF4J to 1.5.0
--
Key: GSHELL-104
Sangjin Lee wrote:
That worked. Thanks! Just curious, that step was not needed
previously. Something must have changed since?
When the 2.1 release branch was taken, the trunk versions get a bump in
version number. This includes the samples as well as the main server.
If you were working
[
https://issues.apache.org/jira/browse/GERONIMO-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573283#action_12573283
]
Donald Woods commented on GERONIMO-3876:
Cool, looks good. Can we also get this
Jason upgraded GShell to use Xstream 1.3, which has nothing to do with
Devtools. Devtools should always use the same levels of depends as the
server (2.1) it's targeting...
-Donald
Jacek Laskowski wrote:
On Wed, Feb 27, 2008 at 6:07 PM, [EMAIL PROTECTED] wrote:
Author: mcconne
Date: Wed
Mdb container ids not set during creation.
--
Key: GERONIMO-3882
URL: https://issues.apache.org/jira/browse/GERONIMO-3882
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
One suggestion, would be to move the current samples and daytrader
branch back into the server builds. That way, we keep them updated and
release them as part of a server release. Also, it would allow us to
use them as part of the integration testsuite, for hot/console/cmdline
deploy
[
https://issues.apache.org/jira/browse/GERONIMO-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George updated GERONIMO-3882:
Attachment: g3882_r631981.patch
Mdb container ids not set during creation.
[
https://issues.apache.org/jira/browse/GERONIMO-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George reassigned GERONIMO-3882:
---
Assignee: (was: Manu T George)
Mdb container ids not set during creation.
[
https://issues.apache.org/jira/browse/GERONIMO-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3882:
---
Patch Info: [Patch Available]
Affects Version/s: 2.2
Geronimo Revision: 631946 built with tests included
See the full build-0800.log file at
http://geronimo.apache.org/maven/server/binaries/2.1/20080228/build-0800.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/2.1/20080228
[INFO] BUILD SUCCESSFUL
[INFO
I moved over some of the sample migration documents as we had discussed, but
I noticed that about half of them were empty pages. I didn't move those
over. I imagine they were created at some point with the intent of
populating the pages with juicy information, but it seems to have never
Documentation updates
-
Key: GERONIMODEVTOOLS-290
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-290
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim McConnell
Assignee:
[
https://issues.apache.org/jira/browse/GERONIMO-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573341#action_12573341
]
David Jencks commented on GERONIMO-3878:
I just tried with trunk and downloaded
Here are some specific areas that I think we should have more tests for:
1) Command line tools like deploy, client, jaxws-tools, etc. and their
gshell counterparts.
2) Deploying applications using the different methods or options:
using the command line tools, using the console, hot deploy,
Database wizard looses track of which connector to use if you download a driver
jar
---
Key: GERONIMO-3883
URL: https://issues.apache.org/jira/browse/GERONIMO-3883
[
https://issues.apache.org/jira/browse/GERONIMO-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573342#action_12573342
]
David Jencks commented on GERONIMO-3878:
btw I opened GERONIMO-3883 about the
Hi All,
question regarding the
http://cwiki.apache.org/GMOxDOC21/constructing-a-special-purpose-server-using-maven.html
doc
Is there a way to identify all the maven archetypes we provide and their
purpose? I think we should cover that somewhere in the doc.
Cheers!
Hernan
Geronimo Revision: 631978 built with tests included
See the full build-0900.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080228/build-0900.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080228
[INFO] BUILD SUCCESSFUL
[INFO
AFAIK the only ones are the module (which should probably be called
plugin) and assembly archetypes, and they are only in 2.2 so far.
Does eclipse provide ways to set up bits of maven project such as by
running archetypes?
Can you get this page into a prominent and appropriate part of the
In the 2.1 documentation, rather than creating children pages for the bullet
points under the Geronimo Administration Console - i've appropriately
integrated them into the Geronimo Administration Console root page. So if
someone with the correct access privilege could please remove the following
Console gshell action to upgrade an artifact (jar/car) from a handy repo
such as apache-snapshot
---
Key: GERONIMO-3884
URL:
Ralf,
One thing that may be causing you some trouble is that some of the
database types expect the driver to be installed in the repository with
a particular group and artifact - otherwise they don't appear in the list.
In the case of PostgreSQL, the group and artifact must be:
Group -
[
https://issues.apache.org/jira/browse/GERONIMO-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573388#action_12573388
]
David Jencks commented on GERONIMO-3871:
I wrote up more instructions on the
Doesn't samples have an archetype? Is that not within the scope of the
conversation? I just noticed it when I was poking through the samples.
On Thu, Feb 28, 2008 at 12:38 PM, David Jencks [EMAIL PROTECTED]
wrote:
AFAIK the only ones are the module (which should probably be called
plugin)
[
https://issues.apache.org/jira/browse/GERONIMO-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George updated GERONIMO-3811:
Attachment: openejb.zip
EJB portlet initial version
The openejb.zip file should be
[
https://issues.apache.org/jira/browse/GERONIMO-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George reassigned GERONIMO-3811:
---
Assignee: (was: Manu T George)
EjbServer portlet
-
[
https://issues.apache.org/jira/browse/GERONIMO-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George updated GERONIMO-3811:
Attachment: g3811_r632068.patch
EjbServer portlet
-
Our official release process docs
http://cwiki.apache.org/confluence/display/GMOxPMGT/Release+Branching
+Process
were mostly written before the maven-release-plugin worked at all and
before we had much of the current variety of projects. Despite the
maven-release-plugins warts it's still
Hi
I opened a JIRA and attached an initial patch for a new portlet for
displaying information regarding the different ejb containers and the
ejbs deployed in them. The JIRA is
http://issues.apache.org/jira/browse/GERONIMO-3811. Currently to after
changing the properties like pool size etc the
Hi everyone,
If someone with the correct privileges could remove the following children
pages from the AG2.1 Tools and commands:
-client.jar
-deploy
-Deployer tool
-geronimo
-jpa.jar
-shutdown
-startup
In light of our discussion about reducing tree hierarchy for a less tedious
navigation system,
I went to a selenium get together Monday and think we have some great
opportunities for improving and speeding up our testsuite.
The bits I think would be of most benefit, from my perspective as a
non-test-engineer, are:
selenium grid. This lets you run basically any number of selenium
just to make sure, no need to delete these pages. These are still needed.
Cheers!
Hernan
Joseph Leong wrote:
In the 2.1 documentation, rather than creating children pages for the
bullet points under the Geronimo Administration Console - i've
appropriately integrated them into the Geronimo
yeah, I know of that one. Worked with Prasad on this, however this does not
apply to all the sample apps we have, does it?
Cheers!
Hernan
Jason Warner wrote:
Doesn't samples have an archetype? Is that not within the scope of the
conversation? I just noticed it when I was poking through the
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573417#action_12573417
]
Vamsavardhana Reddy commented on GERONIMODEVTOOLS-287:
--
The
OK, any reason why we don't follow a similar dir structure as in the repo?
Cheers!
Hernan
Jacek Laskowski wrote:
On Tue, Feb 26, 2008 at 12:21 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
I think we discussed long time ago what goes into /lib. What I think the
answer was does not seem to
On Thu, Feb 28, 2008 at 11:47 AM, Hernan Cunico [EMAIL PROTECTED] wrote:
OK, any reason why we don't follow a similar dir structure as in the repo?
Good question! Perhaps because it's easier to make a single directory
with the minimum files in it and don't bother with the long-ish paths.
Can't
Jacek Laskowski wrote:
On Thu, Feb 28, 2008 at 11:47 AM, Hernan Cunico [EMAIL PROTECTED] wrote:
OK, any reason why we don't follow a similar dir structure as in the repo?
Good question! Perhaps because it's easier to make a single directory
with the minimum files in it and don't bother with
On Feb 28, 2008, at 12:06 PM, Hernan Cunico wrote:
Jacek Laskowski wrote:
On Thu, Feb 28, 2008 at 11:47 AM, Hernan Cunico
[EMAIL PROTECTED] wrote:
OK, any reason why we don't follow a similar dir structure as in
the repo?
Good question! Perhaps because it's easier to make a single
I ran
find . -name *archetype*
at the root of my not-completely-updated geronimo checkout and found
these, eliminating most branches and tags
samples/trunk/geronimo-samples-archetype
sandbox/restructure/maven-plugins/testsuite-archetype-plugin
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573436#action_12573436
]
Vamsavardhana Reddy commented on GERONIMODEVTOOLS-287:
--
I agree - great list. I welcome others to add more to the list,
especially functions we don't feel work quite well.
After collecting everyone's thoughts, I plan to use a wiki page to
keep track of the key functions that deserves testing with possible
coverage by automation or manual testing.
Geronimo Revision: 632109 built with tests included
See the full build-1500.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080228/build-1500.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080228
[INFO] BUILD SUCCESSFUL
[INFO
I created a very high level view of our documentation as it exists
across the various versions. Hopefully a very macro few of things may
help us clear the fog on documentation related thinking. At least I
found it very difficult to see the whole elephant.
A few years ago I read about an information based perpetual motion
machine someone came up with. IIRC many people studied it for quite
a while before realizing that the flaw was an assumption that erasing
information was free. It turned out to require the same energy as
apparently
The sandbox/james is now quietly sleeping in my compost pile in my
back yard.
Regards,
Alan
On Feb 28, 2008, at 3:07 PM, David Jencks wrote:
A few years ago I read about an information based perpetual motion
machine someone came up with. IIRC many people studied it for
quite a while
Feel free to remove the two branches I created.
On Fri, Feb 29, 2008 at 12:07 AM, David Jencks [EMAIL PROTECTED] wrote:
A few years ago I read about an information based perpetual motion
machine someone came up with. IIRC many people studied it for quite
a while before realizing that the
This is great!!
Some of the links seem to be in red and claim that if you click them
they will create a new page. Anyone know what that means?
Also, how do the translations (spanish and polish?) work? I haven't
seen how to get to them before.
thanks
david jencks
On Feb 28, 2008, at
On Feb 28, 2008, at 3:07 PM, David Jencks wrote:
A few years ago I read about an information based perpetual motion
machine someone came up with. IIRC many people studied it for quite
a while before realizing that the flaw was an assumption that
erasing information was free. It turned
On Feb 28, 2008, at 3:45 PM, David Jencks wrote:
This is great!!
Some of the links seem to be in red and claim that if you click them
they will create a new page. Anyone know what that means?
I put - links in just to make it easier if someone wants to create
the page. Though links to
Deleted my two.
-David
On Feb 28, 2008, at 3:07 PM, David Jencks wrote:
A few years ago I read about an information based perpetual motion
machine someone came up with. IIRC many people studied it for quite
a while before realizing that the flaw was an assumption that
erasing
[
https://issues.apache.org/jira/browse/GSHELL-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-66.
--
Resolution: Fixed
Applied, thx Jason
Auto-generate cli syntax/usage string when displaying --help
[
https://issues.apache.org/jira/browse/GSHELL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-46.
--
Resolution: Fixed
Applied... thx Jason :-)
Add flag to show exception stacktraces
[
https://issues.apache.org/jira/browse/GSHELL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-17:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
New command: subshell
[
https://issues.apache.org/jira/browse/GSHELL-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-38:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Add rfile:// remote-file
[
https://issues.apache.org/jira/browse/GSHELL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-51:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Generalize the transport access
[
https://issues.apache.org/jira/browse/GSHELL-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-25:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Sub-shell syntax support
[
https://issues.apache.org/jira/browse/GSHELL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-18:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
New command: exec
[
https://issues.apache.org/jira/browse/GSHELL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-1:
--
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Add ${...} parsing to the
[
https://issues.apache.org/jira/browse/GSHELL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-52:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Expose real SSL configuration
[
https://issues.apache.org/jira/browse/GSHELL-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-22:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Input/output redirection
[
https://issues.apache.org/jira/browse/GSHELL-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-27:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Exec command eats an additional
[
https://issues.apache.org/jira/browse/GSHELL-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-24:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Support background commands
[
https://issues.apache.org/jira/browse/GSHELL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-3:
--
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Hook up backtick and execute
[
https://issues.apache.org/jira/browse/GSHELL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-43:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Add role-based layout selection
[
https://issues.apache.org/jira/browse/GSHELL-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-72:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Externalize command help pages
[
https://issues.apache.org/jira/browse/GSHELL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-16:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
New command: ssh
[
https://issues.apache.org/jira/browse/GSHELL-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-19:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
New command: vfs/browse
[
https://issues.apache.org/jira/browse/GSHELL-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-23:
---
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
Command pipe-lines
[
https://issues.apache.org/jira/browse/GSHELL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-102:
Summary: Update MINA to 1.1.6 (was: Update MINA to latest (ATM thats
1.1.6))
Update MINA to
On Feb 29, 2008, at 6:07 AM, David Jencks wrote:
jdillon
sandbox/g1.1-activemq4
sandbox/repository (did this make it into the wiki? I'm planning to
propose using http://maven.apache.org/developers/release/releasing.html
as the basis for releasing g. stuff, is this relevant?)
I've cleaned
[
https://issues.apache.org/jira/browse/GSHELL-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-63.
--
Resolution: Fixed
Added a while ago... {{org.apache.geronimo.gshell.console.PromptReader}}
Expose a
[
https://issues.apache.org/jira/browse/XBEAN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dain Sundstrom reassigned XBEAN-60:
---
Assignee: Dain Sundstrom
Support multiple namespaces
---
Does any know where the spring.handlers and spring.schemas files are
actually used?
The reason I ask is because I'm working on XBEAN-60, where Kohsuke is
having problems using the maven plugin with multiple namespaces
because these files get blindly overwritten, but I can see any place
[
https://issues.apache.org/jira/browse/XBEAN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573476#action_12573476
]
Dain Sundstrom commented on XBEAN-71:
-
Is this still a problem for you?
The trunk poms
[
https://issues.apache.org/jira/browse/XBEAN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dain Sundstrom reassigned XBEAN-71:
---
Assignee: Dain Sundstrom
qdox dies because it cannot resolve javax/servlet/ServletContext
StaticRecipeTest fails
--
Key: XBEAN-102
URL: https://issues.apache.org/jira/browse/XBEAN-102
Project: XBean
Issue Type: Bug
Affects Versions: 3.4
Reporter: Alan Cabrera
83 matches
Mail list logo
