[jira] Commented: (GSHELL-113) GroupNodeTest is failing in gshell-core due to missing XPP3 depend
[ https://issues.apache.org/jira/browse/GSHELL-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598576#action_12598576 ] Jason Dillon commented on GSHELL-113: - Um, that is very odd... as the xstream 1.3 dependency does include xpp3:xpp3_min, is that not sufficient? GroupNodeTest is failing in gshell-core due to missing XPP3 depend -- Key: GSHELL-113 URL: https://issues.apache.org/jira/browse/GSHELL-113 Project: GShell Issue Type: Bug Security Level: public(Regular issues) Components: Build Affects Versions: 1.0-alpha-1, 1.0-alpha-2 Environment: MacOSX 10.5.2 w/ Sun 1.5.0_13 Reporter: Donald Woods Assignee: Donald Woods Fix For: 1.0-alpha-2 The following gshell-core test was failing when I tried to build the 1.0-alpha-1 tag on MacOSX with a clean repo - Tests in error: testDeserializeLinks(org.apache.geronimo.gshell.layout.model.GroupNodeTest) Tests run: 33, Failures: 0, Errors: 1, Skipped: 0 Test report showed - java.lang.IllegalArgumentException: XPP3 pull parser library not present. Solution, was to include the same xpp3-1.1.3.4.O depend as the Geronimo 2.1.x servers with scope=test. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 658571
Geronimo Revision: 658571 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 32 seconds
[INFO] Finished at: Wed May 21 03:40:24 EDT 2008
[INFO] Final Memory: 383M/1004M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/logs-0300-tomcat/test.log
[INFO] [site:attach-descriptor]
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:39.429
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:39.638)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:39.694)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.776)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:56.290)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.348)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.647)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.139)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.833)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:37.754)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:43.317)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[jira] Created: (GERONIMO-4038) Change the yoko version to the 1.0 release
Change the yoko version to the 1.0 release -- Key: GERONIMO-4038 URL: https://issues.apache.org/jira/browse/GERONIMO-4038 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: CORBA Affects Versions: 2.2 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: 2.2 Now that there's a published 1.0 release of yoko, Geronimo trunk should be using the 1.0 release rather than the snapshot version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4038) Change the yoko version to the 1.0 release
[ https://issues.apache.org/jira/browse/GERONIMO-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-4038. -- Resolution: Fixed Committed revision 658639. Change the yoko version to the 1.0 release -- Key: GERONIMO-4038 URL: https://issues.apache.org/jira/browse/GERONIMO-4038 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.2 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: 2.2 Now that there's a published 1.0 release of yoko, Geronimo trunk should be using the 1.0 release rather than the snapshot version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (GERONIMO-4038) Change the yoko version to the 1.0 release
IMO, we should update branches/2.1, also, and remove the build of yoko from branches/2.1/repository. --kevan On May 21, 2008, at 7:51 AM, Rick McGuire (JIRA) wrote: [ https://issues.apache.org/jira/browse/GERONIMO-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-4038. -- Resolution: Fixed Committed revision 658639. Change the yoko version to the 1.0 release -- Key: GERONIMO-4038 URL: https://issues.apache.org/jira/browse/GERONIMO-4038 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.2 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: 2.2 Now that there's a published 1.0 release of yoko, Geronimo trunk should be using the 1.0 release rather than the snapshot version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 658672
Geronimo Revision: 658672 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 2 seconds
[INFO] Finished at: Wed May 21 09:39:28 EDT 2008
[INFO] Final Memory: 371M/1004M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/logs-0900-tomcat/test.log
[INFO] [site:attach-descriptor]
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:38.636
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.716)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:40.064)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.336)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:01:03.485)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.056)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:32.245)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:30.325)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.277)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:41.015)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:43.901)
[INFO] enterprise-testsuite/jpa-tests RUNNING
Samples release process
I've been stuck attempting to use the maven-release-plugin for samples
for a few reasons. I would like go ahead and create a branch for this
release which will later be converted to a tag (the old fashioned way).
Are there any strong objects? (Note: I'm asking because of this sentence
in our release process doc - ...most smaller projects such as specs,
plugins, components, and most likely tools should avoid the complexity
of branches unless clearly necessary and agreed upon. )
Here are the problems that I'm having using the release-plugin/process:
1) There is a version property defined in the root pom to match the
release version. The maven-release-plugin will not change this version
property (just the version element in the root pom) during mvn
release:prepare
I attempted to remove the version property but it appears this is used
to generate the directory to scan by the jasper builder as I get the
following error when I attempt to remove it.
[ERROR] BUILD ERROR
[INFO]
[INFO] Could not scan directory for TLD files:
jar:file:/Users/bohn/geronimo-samples-2.1/samples/CustomerService/CustomerService-jetty/target/repository/org/apache/geronimo/samples/CustomerService-jetty/${version}/CustomerService-jetty-${version}.car/CustomerService-ejb-2.1-SNAPSHOT.jar!/META-INF
Illegal character in path at index 153:
file:/Users/bohn/geronimo-samples-2.1/samples/CustomerService/CustomerService-jetty/target/repository/org/apache/geronimo/samples/CustomerService-jetty/${version}/CustomerService-jetty-${version}.car/CustomerService-ejb-2.1-SNAPSHOT.jar
Attempting to change this version property manually prior to release
didn't work either. Apparently, the maven-release does a build prior to
the svn changes (which fails with a manual change) and after the svn
changes (which fails without the manual change).
BTW, we have this same version property defined in the server root pom.
2) When using the maven-release-plugin I have to specify the release
and the new snapshot version. The release default is fine because we
are currently using 2.1-SNAPSHOT and so the release will be 2.1.
However, I must manually specify the development release to
2.1.1-SNAPSHOT or it will default to 2.2-SNAPSHOT. This isn't a big
problem but it is annoying (especially since I have to enter that value
78 times ... once for each artifact). Newer versions of the
maven-release-plugin have parms to override these versions on the
command line but the version included in genesis 1.4 does not.
3) This isn't necessary a problem but it doesn't seem right to me. When
The scm entries are updated for a tag with the name:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-2.1
I understand why this based upon the release-plugin structure. However
the name doesn't seem intuitive to me. I think a structure that matches
our server structure makes much more sense. So I would prefer:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/2.1.0 (with or
without the .0)
I think this makes much more sense and more clearly matches the samples
to the server (and we indicated on earlier threads that we wanted to
keep these in sync).
4) I'm becoming more and more of the opinion that we should merge the
samples svn back into the server svn. I see little advantage in keeping
these independent and a lot of problems in doing so. If I can convince
folks that is the right thing to do then it doesn't make much sense to
get the samples releasing with the maven-release-plugin while the server
is still released manually.
Some reasons I think the samples should be merged back into the server svn.
- The samples are tied to a particular server release.
- It's important to have samples available ASAP with a server release.
Tying these together would ensure that they are available in conjunction
with the server release (you can't do any better than that).
- The samples are versioned to match the server and this would make it a
no-brainer to keep them in sync.
- Samples could take advantage of the dependency management in server
root pom to ensure that everything is in sync with the server. As it
stands now dependency versions for samples are spread across numerous
poms and managed independently from the server.
- We have had 0 success to date releasing samples independently of the
server.
Regarding #4 ... I would get 2.1 samples and 2.1.1 samples released
independently and then suggest we merge the samples under the server svn
in branches/2.1 and trunk. We don't need to decide #4 right away since
we still have to get 2.1 possibly 2.1.1 out the door. The only
advantage I can think of in keeping them independent is the ability to
build samples without building the server but as I mentioned in another
post I don't believe this is possible anyway at the moment.
Joe
Re: Samples release process
On May 21, 2008, at 10:57 AM, Joe Bohn wrote:
I've been stuck attempting to use the maven-release-plugin for
samples for a few reasons. I would like go ahead and create a
branch for this release which will later be converted to a tag (the
old fashioned way). Are there any strong objects? (Note: I'm asking
because of this sentence in our release process doc - ...most
smaller projects such as specs, plugins, components, and most likely
tools should avoid the complexity of branches unless clearly
necessary and agreed upon. )
Here are the problems that I'm having using the release-plugin/
process:
1) There is a version property defined in the root pom to match the
release version. The maven-release-plugin will not change this
version property (just the version element in the root pom) during
mvn release:prepare
I attempted to remove the version property but it appears this is
used to generate the directory to scan by the jasper builder as I
get the following error when I attempt to remove it.
[ERROR] BUILD ERROR
[INFO]
[INFO] Could not scan directory for TLD files: jar:file:/Users/bohn/
geronimo-samples-2.1/samples/CustomerService/CustomerService-jetty/
target/repository/org/apache/geronimo/samples/CustomerService-jetty/$
{version}/CustomerService-jetty-${version}.car/CustomerService-
ejb-2.1-SNAPSHOT.jar!/META-INF Illegal character in path at index
153: file:/Users/bohn/geronimo-samples-2.1/samples/CustomerService/
CustomerService-jetty/target/repository/org/apache/geronimo/samples/
CustomerService-jetty/${version}/CustomerService-jetty-$
{version}.car/CustomerService-ejb-2.1-SNAPSHOT.jar
Attempting to change this version property manually prior to release
didn't work either. Apparently, the maven-release does a build
prior to the svn changes (which fails with a manual change) and
after the svn changes (which fails without the manual change).
BTW, we have this same version property defined in the server root
pom.
This is a problem we'll have to solve to release the server with the
release plugin. I thought I'd dealt with it successfully in the
apacheds plugin release but maybe not
2) When using the maven-release-plugin I have to specify the
release and the new snapshot version. The release default is fine
because we are currently using 2.1-SNAPSHOT and so the release will
be 2.1. However, I must manually specify the development release to
2.1.1-SNAPSHOT or it will default to 2.2-SNAPSHOT. This isn't a big
problem but it is annoying (especially since I have to enter that
value 78 times ... once for each artifact). Newer versions of the
maven-release-plugin have parms to override these versions on the
command line but the version included in genesis 1.4 does not.
I think there's a configuration setting so you only have to specify it
once. You can set this on the command line although I think its
better to include in the samples root pom (or the next version of
genesis).
-DautoVersionSubmodules=true
3) This isn't necessary a problem but it doesn't seem right to me.
When The scm entries are updated for a tag with the name:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-2.1
I understand why this based upon the release-plugin structure.
However the name doesn't seem intuitive to me. I think a structure
that matches our server structure makes much more sense. So I would
prefer:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/2.1.0 (with
or without the .0)
I think this makes much more sense and more clearly matches the
samples to the server (and we indicated on earlier threads that we
wanted to keep these in sync).
While it isn't what we've been doing by hand I am 100% in favor of
following maven default behavior unless it breaks stuff. We don't
need to look different from everyone else.
4) I'm becoming more and more of the opinion that we should merge
the samples svn back into the server svn. I see little advantage in
keeping these independent and a lot of problems in doing so. If I
can convince folks that is the right thing to do then it doesn't
make much sense to get the samples releasing with the maven-release-
plugin while the server is still released manually.
Some reasons I think the samples should be merged back into the
server svn.
- The samples are tied to a particular server release.
- It's important to have samples available ASAP with a server
release. Tying these together would ensure that they are available
in conjunction with the server release (you can't do any better than
that).
- The samples are versioned to match the server and this would make
it a no-brainer to keep them in sync.
- Samples could take advantage of the dependency management in
server root pom to ensure that everything is in sync with the
server. As it stands now
Re: Google Analytics
Could you add me to the list? My email: [EMAIL PROTECTED] David Blevins wrote: Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David -- View this message in context: http://www.nabble.com/Google-Analytics-tp17246856s134p17364320.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Google Analytics
Added Jay Helen Wang wrote: Could you add me to the list? My email: [EMAIL PROTECTED] David Blevins wrote: Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David
[jira] Created: (GSHELL-114) The LoginHandler default realm should be configurable
The LoginHandler default realm should be configurable - Key: GSHELL-114 URL: https://issues.apache.org/jira/browse/GSHELL-114 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Affects Versions: 1.0-alpha-1 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GSHELL-114) The LoginHandler default realm should be configurable
[ https://issues.apache.org/jira/browse/GSHELL-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved GSHELL-114. Resolution: Fixed Sending src/main/java/org/apache/geronimo/gshell/remote/server/handler/LoginHandler.java Transmitting file data . Committed revision 658740. The LoginHandler default realm should be configurable - Key: GSHELL-114 URL: https://issues.apache.org/jira/browse/GSHELL-114 Project: GShell Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.0-alpha-1 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4039) Unable to include 2 versions of a jar in a server
Unable to include 2 versions of a jar in a server - Key: GERONIMO-4039 URL: https://issues.apache.org/jira/browse/GERONIMO-4039 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Priority: Blocker Fix For: 2.2 The car-maven-plugin is copying the same jar into two different jars in the geronimo repo when assembling a server where 2 plugins specify 2 versions of the same jar. The specific example in rev 658755 is that the cxf plugin specifies org.apache.ws.commons/XmlSchema/1.2/jar and axis2 specifies version 1.3.1. There are jars at both these locations in the geronimo repo but they are both the 1.3.1 jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4040) Tutorials - AJAX with JSF
Tutorials - AJAX with JSF - Key: GERONIMO-4040 URL: https://issues.apache.org/jira/browse/GERONIMO-4040 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4041) Tutorials - AJAX with JSF
Tutorials - AJAX with JSF - Key: GERONIMO-4041 URL: https://issues.apache.org/jira/browse/GERONIMO-4041 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4042) Tutorials - AJAX with JSF
Tutorials - AJAX with JSF - Key: GERONIMO-4042 URL: https://issues.apache.org/jira/browse/GERONIMO-4042 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4043) Tutorials - AJAX with JSF
Tutorials - AJAX with JSF - Key: GERONIMO-4043 URL: https://issues.apache.org/jira/browse/GERONIMO-4043 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4036) Warning message after running gsh geronimo/stop-server
[
https://issues.apache.org/jira/browse/GERONIMO-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Warner reassigned GERONIMO-4036:
--
Assignee: Jason Warner
Warning message after running gsh geronimo/stop-server
--
Key: GERONIMO-4036
URL: https://issues.apache.org/jira/browse/GERONIMO-4036
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands
Affects Versions: 2.1.2, 2.1.x, 2.2
Environment: Windows
Reporter: YunFeng Ma
Assignee: Jason Warner
Fix For: 2.1.2
About 10 seconds after running geronimo/stop-server successfully, got the
following warning messages in the gsh console:
{noformat}
[EMAIL PROTECTED]:/ 2008-5-20 13:51:12 ClientCommunicatorAdmin restart
Warning: Failed to restart: java.io.IOException: Failed to get a RMI stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused: connect]
2008-5-20 13:51:13 RMIConnector RMIClientCommunicatorAdmin-doStop
Warning: Failed to call the method close():java.rmi.ConnectException:
Connection refused to host: 9.186.117.32; nested exception is:
java.net.ConnectException: Connection refused: connect
2008-5-20 13:51:13 ClientCommunicatorAdmin Checker-run
Warning: Failed to check connection: java.net.ConnectException: Connection
refused: connect
2008-5-20 13:51:13 ClientCommunicatorAdmin Checker-run
Warning: stopping
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4043) Tutorials - Using JSP Immediate Expressions to access JSF
[ https://issues.apache.org/jira/browse/GERONIMO-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4043: Description: Geronimo v2.1 documentation, Tutorials section. Develop an Using JSP Immediate Expressions to access JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application was: Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application Summary: Tutorials - Using JSP Immediate Expressions to access JSF (was: Tutorials - AJAX with JSF) Tutorials - Using JSP Immediate Expressions to access JSF - Key: GERONIMO-4043 URL: https://issues.apache.org/jira/browse/GERONIMO-4043 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an Using JSP Immediate Expressions to access JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4042) Tutorials - User Interface development with JSF
[ https://issues.apache.org/jira/browse/GERONIMO-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4042: Description: Geronimo v2.1 documentation, Tutorials section. Develop a User Interface development with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html was: Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application Summary: Tutorials - User Interface development with JSF (was: Tutorials - AJAX with JSF) Tutorials - User Interface development with JSF --- Key: GERONIMO-4042 URL: https://issues.apache.org/jira/browse/GERONIMO-4042 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a User Interface development with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4043) Tutorials - Using JSP Immediate Expressions to access JSF
[ https://issues.apache.org/jira/browse/GERONIMO-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4043: Description: Geronimo v2.1 documentation, Tutorials section. Develop an Using JSP Immediate Expressions to access JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html was: Geronimo v2.1 documentation, Tutorials section. Develop an Using JSP Immediate Expressions to access JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application Tutorials - Using JSP Immediate Expressions to access JSF - Key: GERONIMO-4043 URL: https://issues.apache.org/jira/browse/GERONIMO-4043 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an Using JSP Immediate Expressions to access JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4041) Tutorials - Stateful Session Bean
[ https://issues.apache.org/jira/browse/GERONIMO-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4041: Description: Geronimo v2.1 documentation, Tutorials section. Develop an Stateful Session Bean tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html was: Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application Summary: Tutorials - Stateful Session Bean (was: Tutorials - AJAX with JSF) Tutorials - Stateful Session Bean - Key: GERONIMO-4041 URL: https://issues.apache.org/jira/browse/GERONIMO-4041 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an Stateful Session Bean tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4044) Tutorials - Message Driven Bean
Tutorials - Message Driven Bean --- Key: GERONIMO-4044 URL: https://issues.apache.org/jira/browse/GERONIMO-4044 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a Message Driven Bean tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4045) Tutorials - Container Managed Persistence with JPA
Tutorials - Container Managed Persistence with JPA -- Key: GERONIMO-4045 URL: https://issues.apache.org/jira/browse/GERONIMO-4045 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a CMP with JPA tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4046) Tutorials - Bean Managed Persistence with JPA
Tutorials - Bean Managed Persistence with JPA - Key: GERONIMO-4046 URL: https://issues.apache.org/jira/browse/GERONIMO-4046 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a BMP with JPA tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4047) Tutorials - Building JAX-WS EJB stateless session bean web services
Tutorials - Building JAX-WS EJB stateless session bean web services --- Key: GERONIMO-4047 URL: https://issues.apache.org/jira/browse/GERONIMO-4047 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Building JAX-WS EJB stateless session bean web services addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4048) Tutorials - RESTFUL Web Services
Tutorials - RESTFUL Web Services Key: GERONIMO-4048 URL: https://issues.apache.org/jira/browse/GERONIMO-4048 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for RESTFUL Web Services addressing the following common topics (use this list as a guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4049) Tutorials - SAAJ Web Services
Tutorials - SAAJ Web Services - Key: GERONIMO-4049 URL: https://issues.apache.org/jira/browse/GERONIMO-4049 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for SAAJ Web Services addressing the following common topics (use this list as a guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4051) Tutorials - WS Addressing
Tutorials - WS Addressing - Key: GERONIMO-4051 URL: https://issues.apache.org/jira/browse/GERONIMO-4051 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for WS Addressing addressing the following common topics (use this list as the intial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4050) Tutorials
Tutorials - Key: GERONIMO-4050 URL: https://issues.apache.org/jira/browse/GERONIMO-4050 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for MTOM Web Services addressing the following common topics (use this list as a guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4052) Tutorials - Securing your applications
Tutorials - Securing your applications -- Key: GERONIMO-4052 URL: https://issues.apache.org/jira/browse/GERONIMO-4052 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Securing your applications addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4053) Tutorials - Using Java Persistence API in application client
Tutorials - Using Java Persistence API in application client Key: GERONIMO-4053 URL: https://issues.apache.org/jira/browse/GERONIMO-4053 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Using Java Persistence API in application client addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4055) Tutorials - JAX-WS web service and client using annotations
Tutorials - JAX-WS web service and client using annotations --- Key: GERONIMO-4055 URL: https://issues.apache.org/jira/browse/GERONIMO-4055 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for JAX-WS web service and client using annotations addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4054) Working with JSF and JPA
Working with JSF and JPA Key: GERONIMO-4054 URL: https://issues.apache.org/jira/browse/GERONIMO-4054 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Working with JSF and JPA addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4050) Tutorials - MTOM Web Services
[ https://issues.apache.org/jira/browse/GERONIMO-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4050: Summary: Tutorials - MTOM Web Services (was: Tutorials) Tutorials - MTOM Web Services - Key: GERONIMO-4050 URL: https://issues.apache.org/jira/browse/GERONIMO-4050 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for MTOM Web Services addressing the following common topics (use this list as a guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4057) Tutorials - Clone your server environment with plugins
Tutorials - Clone your server environment with plugins -- Key: GERONIMO-4057 URL: https://issues.apache.org/jira/browse/GERONIMO-4057 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Cloning your server environment with plugins addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4056) Tutorials - Create your own custom server with Geronimo framework
Tutorials - Create your own custom server with Geronimo framework - Key: GERONIMO-4056 URL: https://issues.apache.org/jira/browse/GERONIMO-4056 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Creating your own custom server with Geronimo framework addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4058) Tutorials - Convert your current applications into plugins
Tutorials - Convert your current applications into plugins -- Key: GERONIMO-4058 URL: https://issues.apache.org/jira/browse/GERONIMO-4058 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Converting your current applications into plugins addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4054) Tutorials - Working with JSF and JPA
[ https://issues.apache.org/jira/browse/GERONIMO-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4054: Summary: Tutorials - Working with JSF and JPA (was: Working with JSF and JPA) Tutorials - Working with JSF and JPA Key: GERONIMO-4054 URL: https://issues.apache.org/jira/browse/GERONIMO-4054 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Working with JSF and JPA addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 658634
Geronimo Revision: 658634 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080521/build-0800.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20080521 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 38 seconds [INFO] Finished at: Wed May 21 08:37:14 EDT 2008 [INFO] Final Memory: 303M/1010M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080521/logs-0800-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080521/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 77.036 sec FAILURE! -- [INFO] Running org.apache.geronimo.testsuite.testset.JaxWSTest [INFO] Tests run: 7, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 0.418 sec FAILURE! -- [INFO] Running org.apache.geronimo.testsuite.testset.ClientJAXWSTest [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec FAILURE! Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20080521/samples-0800.log Build status: FAILED
[jira] Created: (GERONIMO-4059) Bank app error screen returns to page creating duplicate header.
Bank app error screen returns to page creating duplicate header. Key: GERONIMO-4059 URL: https://issues.apache.org/jira/browse/GERONIMO-4059 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 2.2 Environment: Ubuntu 7.10, Firefox Reporter: Joseph Leong Assignee: Joseph Leong Priority: Trivial In the Bank Sample application, when a user reaches the error screen and attempts to return to the homepage the header is duplicated and starts to create an inlay of headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4059) Bank app error screen returns to page creating duplicate header.
[ https://issues.apache.org/jira/browse/GERONIMO-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-4059: --- Attachment: GERONIMO-4059.patch Redirects to the jsp page instead of the html which creates the additional header inlays. -Joseph Leong Bank app error screen returns to page creating duplicate header. Key: GERONIMO-4059 URL: https://issues.apache.org/jira/browse/GERONIMO-4059 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.2 Environment: Ubuntu 7.10, Firefox Reporter: Joseph Leong Assignee: Joseph Leong Priority: Trivial Attachments: GERONIMO-4059.patch In the Bank Sample application, when a user reaches the error screen and attempts to return to the homepage the header is duplicated and starts to create an inlay of headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3965) Custom LoginModule uses wrong classloader
[ https://issues.apache.org/jira/browse/GERONIMO-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598762#action_12598762 ] Kory Markevich commented on GERONIMO-3965: -- Could you give a quick rundown on how to use this? I couldn't figure it out just looking at the diffs. Custom LoginModule uses wrong classloader - Key: GERONIMO-3965 URL: https://issues.apache.org/jira/browse/GERONIMO-3965 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.0.2, 2.1 Environment: Windows XP, JDK 1.5 Reporter: Kory Markevich Assignee: David Jencks Fix For: 2.0.x, 2.1.x, 2.2 When specifying a custom LoginModule implementation in a geronimo-application.xml file, the class cannot be loaded if it is in the EAR. Debugging, the classloader being used belongs to OpenEJB rather than the one for the application. I have tried both versions 2.0.2 and 2.1. This bug was discovered and discussed in the mailing lists (http://www.nabble.com/Custom-LoginModule-classloading-issue-in-gernimo-2.0.2-td14404472s134.html) but I couldn't find any JIRA's for it. Note that the workaround discussed in the thread cannot be used in our application, though I tried it anyway and couldn't get it working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4060) Installation and Configuration - Available configuration files
Installation and Configuration - Available configuration files -- Key: GERONIMO-4060 URL: https://issues.apache.org/jira/browse/GERONIMO-4060 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Installation and Configuration There is a need to document all the [Available configuration files|http://cwiki.apache.org/GMOxDOC21/installation-and-configuration.html#Installationandconfiguration-Availableconfigurationfiles] in the Installation and Configuration section. The purpose of this section is to identify all the configuration files, provide an initial overview as well as a link to separate page with all the details. Additional children pages (and JIRA sub-tasks) should be created to cover the specific configuration files. geronimo_home/var/config * artifact_aliases.properties * client_artifact_aliases.properties * config-substitutions.properties * config.xml * jsr88-configurer-config.xml * offline-deployer-config.xml geronimo_home/var/log * client-log4j.properties * deployer-log4j.properties * server-log4j.properties geronimo_home/var/security * groups.properties * users.properties -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3965) Custom LoginModule uses wrong classloader
[ https://issues.apache.org/jira/browse/GERONIMO-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598764#action_12598764 ] David Jencks commented on GERONIMO-3965: 1. build one of the geronimo versions from svn or find a snapshot from one of the auto-builds 2. make sure the login module class is available in the plugin/module where the security realm using it is defined 3. enjoy :-) You shouldn't have to do anything special for this to work. The trunk testsuite/enterprise-testsuite/sec-tests client test relies on this working for the ejb module's fake login module when calling in through the ejbd protocol. Custom LoginModule uses wrong classloader - Key: GERONIMO-3965 URL: https://issues.apache.org/jira/browse/GERONIMO-3965 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.0.2, 2.1 Environment: Windows XP, JDK 1.5 Reporter: Kory Markevich Assignee: David Jencks Fix For: 2.0.x, 2.1.x, 2.2 When specifying a custom LoginModule implementation in a geronimo-application.xml file, the class cannot be loaded if it is in the EAR. Debugging, the classloader being used belongs to OpenEJB rather than the one for the application. I have tried both versions 2.0.2 and 2.1. This bug was discovered and discussed in the mailing lists (http://www.nabble.com/Custom-LoginModule-classloading-issue-in-gernimo-2.0.2-td14404472s134.html) but I couldn't find any JIRA's for it. Note that the workaround discussed in the thread cannot be used in our application, though I tried it anyway and couldn't get it working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4061) Deployment plans - geronimo-application.xml
Deployment plans - geronimo-application.xml --- Key: GERONIMO-4061 URL: https://issues.apache.org/jira/browse/GERONIMO-4061 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-application.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4062) Deployment plans - geronimo-application-client.xml
Deployment plans - geronimo-application-client.xml -- Key: GERONIMO-4062 URL: https://issues.apache.org/jira/browse/GERONIMO-4062 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-application-client.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 658813
Geronimo Revision: 658813 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 32 minutes 36 seconds
[INFO] Finished at: Wed May 21 15:37:57 EDT 2008
[INFO] Final Memory: 382M/991M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/logs-1500-tomcat/test.log
[INFO] [site:attach-descriptor]
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:37.472
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.781)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:39.075)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:44.781)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:46.441)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.328)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.441)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.454)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.088)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:36.686)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:43.455)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[jira] Created: (GERONIMO-4063) Deployment plans - geronimo-ra.xml
Deployment plans - geronimo-ra.xml -- Key: GERONIMO-4063 URL: https://issues.apache.org/jira/browse/GERONIMO-4063 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-ra.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4064) Deployment plans - geronimo-web.xml
Deployment plans - geronimo-web.xml --- Key: GERONIMO-4064 URL: https://issues.apache.org/jira/browse/GERONIMO-4064 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-web.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4065) Deployment plans - datasources
Deployment plans - datasources -- Key: GERONIMO-4065 URL: https://issues.apache.org/jira/browse/GERONIMO-4065 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - datasources There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4063) Deployment plans - geronimo-ra.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4063: Description: Geronimo 2.1 Documentation - Deployment plans - geronimo-ra.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html was: Geronimo 2.1 Documentation - Deployment plans - geronimo-ra.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples Deployment plans - geronimo-ra.xml -- Key: GERONIMO-4063 URL: https://issues.apache.org/jira/browse/GERONIMO-4063 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-ra.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4062) Deployment plans - geronimo-application-client.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4062: Description: Geronimo 2.1 Documentation - Deployment plans - geronimo-application-client.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html was: Geronimo 2.1 Documentation - Deployment plans - geronimo-application-client.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples Deployment plans - geronimo-application-client.xml -- Key: GERONIMO-4062 URL: https://issues.apache.org/jira/browse/GERONIMO-4062 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-application-client.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4061) Deployment plans - geronimo-application.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4061: Description: Geronimo 2.1 Documentation - Deployment plans - geronimo-application.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html was: Geronimo 2.1 Documentation - Deployment plans - geronimo-application.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples Deployment plans - geronimo-application.xml --- Key: GERONIMO-4061 URL: https://issues.apache.org/jira/browse/GERONIMO-4061 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-application.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4064) Deployment plans - geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4064: Description: Geronimo 2.1 Documentation - Deployment plans - geronimo-web.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html was: Geronimo 2.1 Documentation - Deployment plans - geronimo-web.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples Deployment plans - geronimo-web.xml --- Key: GERONIMO-4064 URL: https://issues.apache.org/jira/browse/GERONIMO-4064 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - geronimo-web.xml Suggested topics to cover * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4065) Deployment plans - datasources
[ https://issues.apache.org/jira/browse/GERONIMO-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hernan Cunico updated GERONIMO-4065: Description: Geronimo 2.1 Documentation - Deployment plans - datasources There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html was: Geronimo 2.1 Documentation - Deployment plans - datasources There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples Deployment plans - datasources -- Key: GERONIMO-4065 URL: https://issues.apache.org/jira/browse/GERONIMO-4065 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - datasources There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4066) Deployment plans - messaging
Deployment plans - messaging Key: GERONIMO-4066 URL: https://issues.apache.org/jira/browse/GERONIMO-4066 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - messaging There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples See http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4067) Deployment plans - Security
Deployment plans - Security --- Key: GERONIMO-4067 URL: https://issues.apache.org/jira/browse/GERONIMO-4067 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.1, 2.1 Reporter: Hernan Cunico Geronimo 2.1 Documentation - Deployment plans - Security There is no specific deployment plan name for this resource type but still it can be covered following the same guidelines as for the application specific plans. The idea is to cover all the alternatives for deploying this type of resource. Suggested basic structure. * Deployment plan overview _(include packaging)_ * Review of standard corresponding deployment descriptor * Review of XML Schemas _(some schemas are documented here http://geronimo.apache.org/apache-geronimo-v21-xml-schemas.html)_ * Dep plan break down _(environment, dependencies, references, etc.)_ * Samples See http://cwiki.apache.org/GMOxDOC21/deployment.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4059) Bank app error screen returns to page creating duplicate header.
[ https://issues.apache.org/jira/browse/GERONIMO-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-4059: - Assignee: Jarek Gawor (was: Joseph Leong) Bank app error screen returns to page creating duplicate header. Key: GERONIMO-4059 URL: https://issues.apache.org/jira/browse/GERONIMO-4059 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.2 Environment: Ubuntu 7.10, Firefox Reporter: Joseph Leong Assignee: Jarek Gawor Priority: Trivial Attachments: GERONIMO-4059.patch In the Bank Sample application, when a user reaches the error screen and attempts to return to the homepage the header is duplicated and starts to create an inlay of headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4059) Bank app error screen returns to page creating duplicate header.
[ https://issues.apache.org/jira/browse/GERONIMO-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4059. --- Resolution: Fixed Fixed committed to trunk (revision 658867) and branches/2.1 (revision 658869). Thanks for the patch! Bank app error screen returns to page creating duplicate header. Key: GERONIMO-4059 URL: https://issues.apache.org/jira/browse/GERONIMO-4059 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.2 Environment: Ubuntu 7.10, Firefox Reporter: Joseph Leong Assignee: Jarek Gawor Priority: Trivial Attachments: GERONIMO-4059.patch In the Bank Sample application, when a user reaches the error screen and attempts to return to the homepage the header is duplicated and starts to create an inlay of headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-262) Update 2.1.0 update site
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell closed GERONIMODEVTOOLS-262. -- Resolution: Fixed Update 2.1.0 update site Key: GERONIMODEVTOOLS-262 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-262 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 658962
Geronimo Revision: 658962 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 31 minutes 5 seconds
[INFO] Finished at: Wed May 21 21:38:22 EDT 2008
[INFO] Final Memory: 386M/1003M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080521/logs-2100-tomcat/test.log
[INFO] [site:attach-descriptor]
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:37.448
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.369)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:39.954)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:48.569)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:50.022)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.166)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.129)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.907)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.593)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:37.112)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:43.970)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[jira] Closed: (GERONIMO-4039) Unable to include 2 versions of a jar in a server
[ https://issues.apache.org/jira/browse/GERONIMO-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4039. -- Resolution: Fixed Fixed in rev 658985. we were resolving to what maven figured out even if the version was specified explicitly. Unable to include 2 versions of a jar in a server - Key: GERONIMO-4039 URL: https://issues.apache.org/jira/browse/GERONIMO-4039 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Priority: Blocker Fix For: 2.2 The car-maven-plugin is copying the same jar into two different jars in the geronimo repo when assembling a server where 2 plugins specify 2 versions of the same jar. The specific example in rev 658755 is that the cxf plugin specifies org.apache.ws.commons/XmlSchema/1.2/jar and axis2 specifies version 1.3.1. There are jars at both these locations in the geronimo repo but they are both the 1.3.1 jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Samples release process
On May 21, 2008, at 11:19 AM, David Jencks wrote:
On May 21, 2008, at 10:57 AM, Joe Bohn wrote:
I've been stuck attempting to use the maven-release-plugin for
samples for a few reasons. I would like go ahead and create a
branch for this release which will later be converted to a tag (the
old fashioned way). Are there any strong objects? (Note: I'm asking
because of this sentence in our release process doc - ...most
smaller projects such as specs, plugins, components, and most
likely tools should avoid the complexity of branches unless clearly
necessary and agreed upon. )
Here are the problems that I'm having using the release-plugin/
process:
1) There is a version property defined in the root pom to match the
release version. The maven-release-plugin will not change this
version property (just the version element in the root pom) during
mvn release:prepare
I attempted to remove the version property but it appears this is
used to generate the directory to scan by the jasper builder as I
get the following error when I attempt to remove it.
[ERROR] BUILD ERROR
[INFO]
[INFO] Could not scan directory for TLD files: jar:file:/Users/bohn/
geronimo-samples-2.1/samples/CustomerService/CustomerService-jetty/
target/repository/org/apache/geronimo/samples/CustomerService-jetty/
${version}/CustomerService-jetty-${version}.car/CustomerService-
ejb-2.1-SNAPSHOT.jar!/META-INF Illegal character in path at index
153: file:/Users/bohn/geronimo-samples-2.1/samples/CustomerService/
CustomerService-jetty/target/repository/org/apache/geronimo/samples/
CustomerService-jetty/${version}/CustomerService-jetty-$
{version}.car/CustomerService-ejb-2.1-SNAPSHOT.jar
Attempting to change this version property manually prior to
release didn't work either. Apparently, the maven-release does a
build prior to the svn changes (which fails with a manual change)
and after the svn changes (which fails without the manual change).
BTW, we have this same version property defined in the server root
pom.
This is a problem we'll have to solve to release the server with the
release plugin. I thought I'd dealt with it successfully in the
apacheds plugin release but maybe not
yup, this was due to someone trying hard to mess up the c-m-p by
including part of the environment element that it generates
correctly. After I removed them (in trunk) the ${version} property is
not needed.
2) When using the maven-release-plugin I have to specify the
release and the new snapshot version. The release default is fine
because we are currently using 2.1-SNAPSHOT and so the release will
be 2.1. However, I must manually specify the development release to
2.1.1-SNAPSHOT or it will default to 2.2-SNAPSHOT. This isn't a
big problem but it is annoying (especially since I have to enter
that value 78 times ... once for each artifact). Newer versions of
the maven-release-plugin have parms to override these versions on
the command line but the version included in genesis 1.4 does not.
I think there's a configuration setting so you only have to specify
it once. You can set this on the command line although I think its
better to include in the samples root pom (or the next version of
genesis).
-DautoVersionSubmodules=true
3) This isn't necessary a problem but it doesn't seem right to me.
When The scm entries are updated for a tag with the name:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-2.1
I understand why this based upon the release-plugin structure.
However the name doesn't seem intuitive to me. I think a structure
that matches our server structure makes much more sense. So I
would prefer:
- http://svn.apache.org/repos/asf/geronimo/samples/tags/2.1.0 (with
or without the .0)
I think this makes much more sense and more clearly matches the
samples to the server (and we indicated on earlier threads that we
wanted to keep these in sync).
While it isn't what we've been doing by hand I am 100% in favor of
following maven default behavior unless it breaks stuff. We don't
need to look different from everyone else.
4) I'm becoming more and more of the opinion that we should merge
the samples svn back into the server svn. I see little advantage
in keeping these independent and a lot of problems in doing so. If
I can convince folks that is the right thing to do then it doesn't
make much sense to get the samples releasing with the maven-release-
plugin while the server is still released manually.
Some reasons I think the samples should be merged back into the
server svn.
- The samples are tied to a particular server release.
- It's important to have samples available ASAP with a server
release. Tying these together would ensure that they are available
in conjunction with the server release (you can't do any better
than
