date:20090918

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try

2009-09-18 Thread Ivan

+1

2009/9/19 David Jencks 

> I've removed the leftover archetype scripts, fixed up the pom names so the
> NOTICE files look nicer, added license goo to the script sources in the
> unreleased archetype, as well as a script to remove the goo, and tried
> again.  I think this answers all the problems Kevan and Joe found except
> getting my key in to the appropriate KEYS file.
>
>
> For various reasons we are now using a forked copy of tomcat derived from
> the tomcat 6.0.20 release, built with maven, with maven dependencies, etc
> etc.
>
> The code changes from tomcat 6.0.20 are:
>
> r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line
>
> GERONIMO-4566 port fix for tomcats
> https://issues.apache.org/bugzilla/show_bug.cgi?id=47378
> 
> r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1 line
>
> GERONIMO-3451 "Restricted listeners property file not found" error logged
> during Tomcat server startup (Patch from Shawn Jiang)
> 
> r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line
>
> GERONIMO-4685 Some customizations of Tomcat properties. Server info is now:
> Apache Geronimo (Embedded Tomcat). Will want to merge in the future.
> 
> r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line
>
> GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in
> MapperListener.registerHost(). I would expect that this fix would be in
> 6.0.22. So prolly won't require merging in the future
> 
> r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line
>
> GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This includes
> revision numbers 784303 and 784304. Does not include 787519, which should
> already be in 6.0.20
> 
> r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line
>
> fill-in ServerInfo properties - but I can't add that to archetype as ant
> task will fail
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/geronimo-staging-035/
>
> site staged at:
>
>
> http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/
>
> svn tag at:
>
>
> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.20.0
>
> The structure is a still little weird but I still don't really want to
> spend time fixing it up.
>
>
> [ ] +1 go for it
> [ ] 0
> [ ] -1 whoa, hold on a minute
>
> Vote open 72 hours
>
> thanks
> david jencks
>
>


-- 
Ivan

[VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try

2009-09-18 Thread David Jencks

I've removed the leftover archetype scripts, fixed up the pom names so  
the NOTICE files look nicer, added license goo to the script sources  
in the unreleased archetype, as well as a script to remove the goo,  
and tried again.  I think this answers all the problems Kevan and Joe  
found except getting my key in to the appropriate KEYS file.



For various reasons we are now using a forked copy of tomcat derived  
from the tomcat 6.0.20 release, built with maven, with maven  
dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1  
line


GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378

r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1  
line


GERONIMO-3451 "Restricted listeners property file not found" error  
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Some customizations of Tomcat properties. Server info is  
now: Apache Geronimo (Embedded Tomcat). Will want to merge in the  
future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in  
MapperListener.registerHost(). I would expect that this fix would be  
in 6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This  
includes revision numbers 784303 and 784304. Does not include 787519,  
which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line

fill-in ServerInfo properties - but I can't add that to archetype as  
ant task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-035/

site staged at:

http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/

svn tag at:

https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.20.0

The structure is a still little weird but I still don't really want to  
spend time fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

[BUILD] trunk: Failed for Revision: 816840

2009-09-18 Thread gawor

Geronimo Revision: 816840 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

[BUILD] branches/2.2: Failed for Revision: 816816

2009-09-18 Thread gawor

Geronimo Revision: 816816 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/unit-test-reports
 
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT
2) org.apache.geronimo.configs:transaction:car:2.2-SNAPSHOT
3) org.apache.geronimo.framework:j2ee-security:car:2.2-SNAPSHOT
4) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT

from the specified remote repositories:
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/),
  jetty-snapshots.oss.sonatype.org 
(http://oss.sonatype.org/content/repositories/jetty-snapshots/),
  jpa-spec-staging 
(https://repository.apache.org/content/repositories/geronimo-staging-021/),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/activemq-staging-026/),
  jetty-releases.oss.sonatype.org 
(http://oss.sonatype.org/content/repositories/jetty-releases/),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  tomcat-fork-staging 
(https://repository.apache.org/content/repositories/geronimo-staging-023/)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT
2) org.apache.geronimo.configs:transaction:car:2.2-SNAPSHOT
3) org.apache.geronimo.framework:j2ee-security:car:2.2-SNAPSHOT
4) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT

from the specified remote repositories:
  amq-staging 
(https://repository.apache.org/content/repositories

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

2009-09-18 Thread David Jencks



On Sep 18, 2009, at 11:40 AM, Kevan Miller wrote:

+1 I checked source, digital signature/checksums, and build. A few  
non-blocking issues:


1) KEYS -- I don't see your digital key in the KEYS file. Would also  
prefer that you sign your key with an apache.org email address,  
rather than yahoo. There are multiple KEYS files floating about svn  
and dists/geronimo, etc. Would be best, IMO, to use SVN geronimo/ 
KEYS and sync dists/geronimo/KEYS with that.


I'll work on this, I may need some coaching.  For instance I don't  
understand where you are saying the KEYS files are.




2) NOTICE file in geronimo-jpa jar Says:
JPA 1.0
Copyright 2003-2009 The Apache Software Foundation

It should say something like "Apache Geronimo Specs: JPA 1.0"


Maybe, but all the other specs are more like this one.



3) Could I convince you to include the SVN tag in your vote email?  
Letter of the law, IIUC, we're voting on the source-release files  
that you've prepared. But good to validate that actually corresponds  
to what's in svn...


Well, you can always look in the source archive for the root pom scm  
info if that's not correct please vote -1 :-)   Although this will  
always be more reliable than my flaky memory, I'll try to remember to  
do this in the future.


thanks
david jencks



And finally -- Thanks David!

--kevan

On Sep 15, 2009, at 4:05 PM, David Jencks wrote:

After some discussion with the openjpa folks it seems like its a  
good idea to re-release our jpa 1 spec with an aritfactId of  
geronimo-jpa_1.0_spec rather than the original 3.0 version number.   
We don't really have a plan for what to do when jpa actually gets a  
3.0 spec, but we don't have to deal with that for a bit.


This is the same as the previous geronimo-jpa_3.0_spec but with  
updated build, license files, release profile, and of course  
artifactId.  As an osgi bundle it imports what it exports.


Staged here:

https://repository.apache.org/content/repositories/geronimo-staging-021/

site staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/

[ ] +1 yes
[ ] 0 dunno
[ ] -1 no

Vote open 72 hours

many thanks
david jencks

[RESULT] [VOTE] release geronimo-jpa_1.0_spec 1.1.2

2009-09-18 Thread David Jencks

Vote passes with 4 +1 votes (dwoods,  djencks, jbohn, kmiller) and no  
other votes.


I'll promote the staging repo and move the site.

thanks!
david jencks

On Sep 15, 2009, at 1:05 PM, David Jencks wrote:

After some discussion with the openjpa folks it seems like its a  
good idea to re-release our jpa 1 spec with an aritfactId of  
geronimo-jpa_1.0_spec rather than the original 3.0 version number.   
We don't really have a plan for what to do when jpa actually gets a  
3.0 spec, but we don't have to deal with that for a bit.


This is the same as the previous geronimo-jpa_3.0_spec but with  
updated build, license files, release profile, and of course  
artifactId.  As an osgi bundle it imports what it exports.


Staged here:

https://repository.apache.org/content/repositories/geronimo-staging-021/

site staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/

[ ] +1 yes
[ ] 0 dunno
[ ] -1 no

Vote open 72 hours

many thanks
david jencks

[CANCELLED] [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

2009-09-18 Thread David Jencks


need to fix the legal goo issues Joe and Kevan found.

thanks
david jencks

On Sep 15, 2009, at 5:31 PM, David Jencks wrote:

For various reasons we are now using a forked copy of tomcat derived  
from the tomcat 6.0.20 release, built with maven, with maven  
dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1  
line


GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378

r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) |  
1 line


GERONIMO-3451 "Restricted listeners property file not found" error  
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Some customizations of Tomcat properties. Server info  
is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the  
future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE  
in MapperListener.registerHost(). I would expect that this fix would  
be in 6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This  
includes revision numbers 784303 and 784304. Does not include  
787519, which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1  
line


fill-in ServerInfo properties - but I can't add that to archetype as  
ant task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-023/

I forgot to include site generation stuff in the root pom before  
rolling the release.  I generated a site by applying rev 815573 to  
the checkout used for the release build.  The results are here:


http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/

The structure is a little weird but I don't really want to spend  
time fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

[jira] Created: (GERONIMO-4885) Configure default max heap and max permsize

2009-09-18 Thread Kevan Miller (JIRA)

Configure default max heap and max permsize
---

 Key: GERONIMO-4885
 URL: https://issues.apache.org/jira/browse/GERONIMO-4885
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2
Reporter: Kevan Miller
 Fix For: 2.2


It seems that the amount of PermGen space being used by Geronimo 2.2. I think 
users are more likely to run into OutOfMemoryErrors as a result. Even on small 
to medium size apps. Setting a default max heap and max perm size should help 
avoid this...

Looks like a 2.2 server is using the following:

50 MB heap
80 MB PermGen

I'd suggest setting the max for both options to 128M. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

With Latest G2.2 svn build (rev 816446) can't start through "gsh"

2009-09-18 Thread Quintin Beukes

Hey,

I have the G2.2 branch rev 816446 build, but can't start through gsh
geronimo/start-server anymore. I confirmed and it's still working on
previous builds. So it's not a system configuration problem as far as
I can see.

This is what I'm getting:
quin...@quintin-desktop bin $ sudo ./gsh --verbose --debug -c
"geronimo/start-server"
org.codehaus.plexus.classworlds.launcher.ConfigurationException: No
such property: version
at 
org.codehaus.plexus.classworlds.launcher.Configurator.filter(Configurator.java:574)
at 
org.codehaus.plexus.classworlds.launcher.Configurator.configure(Configurator.java:311)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.configure(Launcher.java:131)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:404)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.apache.geronimo.gshell.bootstrap.Launcher.main(Launcher.java:59)

Quintin Beukes

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

2009-09-18 Thread Kevan Miller

Unless there's a good reason against, I'm going to be -1 until there  
are license headers in the following:


build-archetype.sh
fixup.sh
mv-resource.sh
mydos2unix.sh
run.sh
svn-actions.sh

Similar non-blocking comments about the text in the jar NOTICE files  
and your digital signature. Everything else looks good. I checked  
source, build, sigs and checksums.


--kevan

On Sep 15, 2009, at 8:31 PM, David Jencks wrote:

For various reasons we are now using a forked copy of tomcat derived  
from the tomcat 6.0.20 release, built with maven, with maven  
dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1  
line


GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378

r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) |  
1 line


GERONIMO-3451 "Restricted listeners property file not found" error  
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Some customizations of Tomcat properties. Server info  
is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the  
future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE  
in MapperListener.registerHost(). I would expect that this fix would  
be in 6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This  
includes revision numbers 784303 and 784304. Does not include  
787519, which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1  
line


fill-in ServerInfo properties - but I can't add that to archetype as  
ant task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-023/

I forgot to include site generation stuff in the root pom before  
rolling the release.  I generated a site by applying rev 815573 to  
the checkout used for the release build.  The results are here:


http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/

The structure is a little weird but I don't really want to spend  
time fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

Re: [discuss] update Transaction.commit method signature in jta spec jar

2009-09-18 Thread Kevan Miller



On Sep 17, 2009, at 4:13 PM, Lin Sun wrote:



What do you think of adding the missing unchecked exception
"IllegalStateException" back to our JTA spec and release a newer
version of the JTA spec jar just to be the same as what is in the Java
doc?  I think it is good for us to be consistent with what is in the
JTA spec and we should be consistent in declaring the unchecked
exceptions (we currently declares the SecurityException but not the
IllegalStateException).


Been trying to find some motivation one way or another...

We can debate whether or not declaration of unchecked exceptions serve  
a useful purpose in this case. However, not sure if that really  
matters. In this instance, best to be accurate, IMO. So would support  
the update to our JTA spec.


--kevan

[BUILD] trunk: Failed for Revision: 816743

2009-09-18 Thread gawor

Geronimo Revision: 816743 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

Re: [discuss] update Transaction.commit method signature in jta spec jar

2009-09-18 Thread Lin Sun

Thanks.  If there is no objection by end of Sunday, I'll start this
work earlier next week.

Lin

On Fri, Sep 18, 2009 at 12:42 AM, Jack Cai  wrote:
> Agreed, since it won't hurt.
>
> -Jack
>
> On Fri, Sep 18, 2009 at 4:13 AM, Lin Sun  wrote:
>>
>> Hi,
>>
>> Recently, I opened GERONIMO-4683 in G about the Transaction.commit
>> signature is missing the IllegalStateException.  The reason why I
>> raised this JIRA is because in OSGi RFC 98 (Transaction in OSGi)
>> compliance test, we use Geronimo's JTA spec jar as the baseline.
>> During OSGi RFC 98 compliance test run with an implementation of RFC
>> 98, OSGi signature test currently checks strictly on exceptions throw
>> by each of the method to see if it is the same as the baseline's
>> signature, which is the Geronimo JTA spec jar.   If it is not the same
>> the test fail.   For example, below is what is specified by the JTA
>> java doc and G JTA spec.
>>
>>
>> G JTA spec jar - Transaction.java
>> public void commit()
>>throws HeuristicMixedException,
>>   HeuristicRollbackException,
>>   RollbackException,
>>   SecurityException,
>>   SystemException;
>>
>>
>> JTA 1.1 Java doc - Transaction.java
>> public void commit()
>>throws RollbackException,
>>   HeuristicMixedException,
>>   HeuristicRollbackException,
>>   SecurityException,
>>   IllegalStateException,
>>   SystemException
>>
>> What do you think of adding the missing unchecked exception
>> "IllegalStateException" back to our JTA spec and release a newer
>> version of the JTA spec jar just to be the same as what is in the Java
>> doc?  I think it is good for us to be consistent with what is in the
>> JTA spec and we should be consistent in declaring the unchecked
>> exceptions (we currently declares the SecurityException but not the
>> IllegalStateException).
>>
>> p.s. if you are interested and have access to, the related discussion
>> is OSGi alliance can be found here -
>> https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1447
>>
>> Thanks
>>
>> Lin
>
>

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

2009-09-18 Thread Kevan Miller

+1 I checked source, digital signature/checksums, and build. A few non- 
blocking issues:


1) KEYS -- I don't see your digital key in the KEYS file. Would also  
prefer that you sign your key with an apache.org email address, rather  
than yahoo. There are multiple KEYS files floating about svn and dists/ 
geronimo, etc. Would be best, IMO, to use SVN geronimo/KEYS and sync  
dists/geronimo/KEYS with that.


2) NOTICE file in geronimo-jpa jar Says:
 JPA 1.0
 Copyright 2003-2009 The Apache Software Foundation

 It should say something like "Apache Geronimo Specs: JPA 1.0"

3) Could I convince you to include the SVN tag in your vote email?  
Letter of the law, IIUC, we're voting on the source-release files that  
you've prepared. But good to validate that actually corresponds to  
what's in svn...


And finally -- Thanks David!

--kevan

On Sep 15, 2009, at 4:05 PM, David Jencks wrote:

After some discussion with the openjpa folks it seems like its a  
good idea to re-release our jpa 1 spec with an aritfactId of  
geronimo-jpa_1.0_spec rather than the original 3.0 version number.   
We don't really have a plan for what to do when jpa actually gets a  
3.0 spec, but we don't have to deal with that for a bit.


This is the same as the previous geronimo-jpa_3.0_spec but with  
updated build, license files, release profile, and of course  
artifactId.  As an osgi bundle it imports what it exports.


Staged here:

https://repository.apache.org/content/repositories/geronimo-staging-021/

site staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/

[ ] +1 yes
[ ] 0 dunno
[ ] -1 no

Vote open 72 hours

many thanks
david jencks

[BUILD] branches/2.2: Failed for Revision: 816729

2009-09-18 Thread gawor

Geronimo Revision: 816729 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

2009-09-18 Thread Joe Bohn



+1 ... with just one potential concern:

While not officially part of the binary distribution, I did notice that 
the build/management scripts in the tag root source don't include the AL 
header.  I'm never sure just how paranoid we need to be about the AL 
header for marginal parts like these.  Given that these are only used to 
create the image, I don't think it's a real concern (hence my +1). 
However, I thought I should mention it just in case somebody has some 
justification for why a header must be on those parts too.  I personally 
think it's probably safest just to add the header for the next release.


Joe


David Jencks wrote:
For various reasons we are now using a forked copy of tomcat derived 
from the tomcat 6.0.20 release, built with maven, with maven 
dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line

GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378


r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1 line

GERONIMO-3451 "Restricted listeners property file not found" error 
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Some customizations of Tomcat properties. Server info is 
now: Apache Geronimo (Embedded Tomcat). Will want to merge in the future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in 
MapperListener.registerHost(). I would expect that this fix would be in 
6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line

GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This 
includes revision numbers 784303 and 784304. Does not include 787519, 
which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line

fill-in ServerInfo properties - but I can't add that to archetype as ant 
task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-023/

I forgot to include site generation stuff in the root pom before rolling 
the release.  I generated a site by applying rev 815573 to the checkout 
used for the release build.  The results are here:


http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/ 



The structure is a little weird but I don't really want to spend time 
fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

2009-09-18 Thread Joe Bohn



+1 ... looks good to me.   Thanks David!

Joe

David Jencks wrote:
After some discussion with the openjpa folks it seems like its a good 
idea to re-release our jpa 1 spec with an aritfactId of 
geronimo-jpa_1.0_spec rather than the original 3.0 version number.  We 
don't really have a plan for what to do when jpa actually gets a 3.0 
spec, but we don't have to deal with that for a bit.


This is the same as the previous geronimo-jpa_3.0_spec but with updated 
build, license files, release profile, and of course artifactId.  As an 
osgi bundle it imports what it exports.


Staged here:

https://repository.apache.org/content/repositories/geronimo-staging-021/

site staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/ 



[ ] +1 yes
[ ] 0 dunno
[ ] -1 no

Vote open 72 hours

many thanks
david jencks

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

2009-09-18 Thread David Jencks


+1

david jencks

On Sep 15, 2009, at 5:31 PM, David Jencks wrote:

For various reasons we are now using a forked copy of tomcat derived  
from the tomcat 6.0.20 release, built with maven, with maven  
dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1  
line


GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378

r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) |  
1 line


GERONIMO-3451 "Restricted listeners property file not found" error  
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Some customizations of Tomcat properties. Server info  
is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the  
future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE  
in MapperListener.registerHost(). I would expect that this fix would  
be in 6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This  
includes revision numbers 784303 and 784304. Does not include  
787519, which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1  
line


fill-in ServerInfo properties - but I can't add that to archetype as  
ant task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-023/

I forgot to include site generation stuff in the root pom before  
rolling the release.  I generated a site by applying rev 815573 to  
the checkout used for the release build.  The results are here:


http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/

The structure is a little weird but I don't really want to spend  
time fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

2009-09-18 Thread David Jencks

You can try removing the dependency and building to find out for  
sure :-)
IIRC there's some slight amount of annotation processing to recognize  
injected ejbs and entity managers and such that uses these classes.


thanks
david jencks

On Sep 17, 2009, at 9:37 AM, Donald Woods wrote:

Yep, saw that, and wondered why our Tomcat artifacts depend on the  
JPA Spec?



-Donald


David Jencks wrote:
I forgot to note that this artifact depends on the geronimo- 
jpa_1.0_spec artifact also currently under vote, so this vote  
depends on that vote.

thanks
david jencks
On Sep 15, 2009, at 5:31 PM, David Jencks wrote:
For various reasons we are now using a forked copy of tomcat  
derived from the tomcat 6.0.20 release, built with maven, with  
maven dependencies, etc etc.


The code changes from tomcat 6.0.20 are:

r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) |  
1 line


GERONIMO-4566 port fix for tomcats 
https://issues.apache.org/bugzilla/show_bug.cgi?id=47378

r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009)  
| 1 line


GERONIMO-3451 "Restricted listeners property file not found" error  
logged during Tomcat server startup (Patch from Shawn Jiang)


r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Some customizations of Tomcat properties. Server  
info is now: Apache Geronimo (Embedded Tomcat). Will want to merge  
in the future.


r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes  
NPE in MapperListener.registerHost(). I would expect that this fix  
would be in 6.0.22. So prolly won't require merging in the future


r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1  
line


GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This  
includes revision numbers 784303 and 784304. Does not include  
787519, which should already be in 6.0.20


r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1  
line


fill-in ServerInfo properties - but I can't add that to archetype  
as ant task will fail


Staging repo:

https://repository.apache.org/content/repositories/geronimo-staging-023/

I forgot to include site generation stuff in the root pom before  
rolling the release.  I generated a site by applying rev 815573 to  
the checkout used for the release build.  The results are here:


http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/

The structure is a little weird but I don't really want to spend  
time fixing it up.



[ ] +1 go for it
[ ] 0
[ ] -1 whoa, hold on a minute

Vote open 72 hours

thanks
david jencks

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

2009-09-18 Thread David Jencks


+1
david jencks

On Sep 15, 2009, at 1:05 PM, David Jencks wrote:

After some discussion with the openjpa folks it seems like its a  
good idea to re-release our jpa 1 spec with an aritfactId of  
geronimo-jpa_1.0_spec rather than the original 3.0 version number.   
We don't really have a plan for what to do when jpa actually gets a  
3.0 spec, but we don't have to deal with that for a bit.


This is the same as the previous geronimo-jpa_3.0_spec but with  
updated build, license files, release profile, and of course  
artifactId.  As an osgi bundle it imports what it exports.


Staged here:

https://repository.apache.org/content/repositories/geronimo-staging-021/

site staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/

[ ] +1 yes
[ ] 0 dunno
[ ] -1 no

Vote open 72 hours

many thanks
david jencks

[jira] Commented: (GERONIMO-4874) Improve the console filter performance

2009-09-18 Thread Jarek Gawor (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757193#action_12757193
 ] 

Jarek Gawor commented on GERONIMO-4874:
---

Maybe I'm not understanding this, but how do you handle the case where the 
 keyword is broken apart in two or more separate buffers. That is, for 
example, the first .write() call passes a buffer that ends with ""?


> Improve the console filter performance
> --
>
> Key: GERONIMO-4874
> URL: https://issues.apache.org/jira/browse/GERONIMO-4874
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
> Environment: All
>Reporter: Jack Cai
>Priority: Minor
> Attachments: GERONIMO-4874.patch, GERONIMO-4874_0918.patch
>
>
> Current console filter for blocking XSRF attack does not scale well as it 
> need to read all the output into a string and then do some text replacement. 
> This will use a lot of memory in extreme cases. See the discussion [1].
> [1] http://www.nabble.com/XSRFHandler-question-td24545409s134.html

-- 
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: 816617

2009-09-18 Thread gawor

Geronimo Revision: 816617 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

[jira] Resolved: (GERONIMO-4603) PropertiesLoginManager is hardwired to properties-login login module

2009-09-18 Thread Ivan (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan resolved GERONIMO-4603.


   Resolution: Fixed
Fix Version/s: (was: 2.1.5)
   3.0

Commit changes to trunkAt revision: 816624  and 2.2 At revision: 816623

> PropertiesLoginManager is hardwired to properties-login login module
> 
>
> Key: GERONIMO-4603
> URL: https://issues.apache.org/jira/browse/GERONIMO-4603
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.2
>Reporter: David Jencks
>Assignee: Ivan
> Fix For: 2.2, 3.0
>
>
> In production you want to replace the toy properties login realm with 
> something else such as an ldap realm.  However the admin console has a 
> hardwired dependency on the properties-login gbean.
> We should make the reference from PropertiesLoginManager multi-valued and 
> scan through it for properties login modules so you can edit any such 
> properties files.
> Workaround for replacing server-security-config with something with a real 
> security realm is to include the properties login module as a dummy, not used 
> in a security realm:
> 
>  class="org.apache.geronimo.security.jaas.LoginModuleGBean">
>  name="loginModuleClass">org.apache.geronimo.security.realm.providers.PropertiesFileLoginModule
> 
> usersURI=var/security/users.properties
> groupsURI=var/security/groups.properties
> 
> geronimo-admin
> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[BUILD] branches/2.2: Failed for Revision: 816591

2009-09-18 Thread gawor

Geronimo Revision: 816591 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/build-0800.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

[jira] Updated: (GERONIMO-4874) Improve the console filter performance

2009-09-18 Thread Jack Cai (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jack Cai updated GERONIMO-4874:
---

Attachment: GERONIMO-4874_0918.patch

I did build 2.1 branch with the patch. Everything passed, including the console 
test suite.

I made a minor correction to the patch. Please help to review this new one.

> Improve the console filter performance
> --
>
> Key: GERONIMO-4874
> URL: https://issues.apache.org/jira/browse/GERONIMO-4874
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
> Environment: All
>Reporter: Jack Cai
>Priority: Minor
> Attachments: GERONIMO-4874.patch, GERONIMO-4874_0918.patch
>
>
> Current console filter for blocking XSRF attack does not scale well as it 
> need to read all the output into a string and then do some text replacement. 
> This will use a lot of memory in extreme cases. See the discussion [1].
> [1] http://www.nabble.com/XSRFHandler-question-td24545409s134.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-4222) Database pool unusable after database unavailable for awhile

2009-09-18 Thread Jack Cai (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jack Cai reassigned GERONIMO-4222:
--

Assignee: Jack Cai

> Database pool unusable after database unavailable for awhile
> 
>
> Key: GERONIMO-4222
> URL: https://issues.apache.org/jira/browse/GERONIMO-4222
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.0.2, 2.1.3, 2.1.4
> Environment: Red Hat Enterprise Linux Server v5.2
> WAS-CE v2.0.0.1, based on Geronimo v2.0.2
>Reporter: David Frahm
>Assignee: Jack Cai
> Fix For: Wish List
>
> Attachments: before and after wasce restart.txt, PGtrial.patch, 
> stacktrace.txt, tranql-connector-postgresql-common-1.1.jar
>
>
> I have frequent trouble with my database pool to an AS/400.  The database is 
> taken down every night for backup, and at least once a week the connection 
> pool is unusable after the database comes back up.  Restarting the connection 
> pool makes everything work again. 
> We are new to Geronimo/WAS-CE -- just this one app on one server -- so I 
> don't have anything to compare to.  However, we have had this same issue with 
> a couple 1.x/1.1.x versions before we upgraded to v2.  Also, there are 
> several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble.
> Configuration Info
> Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver)
> Pool Min Size: 0
> Pool Max Size: 100
> Blocking Timeout: 5000
> Idle Timeout: 15

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMODEVTOOLS-593) "tptp.runtime-TPTP-4.6.0.zip " download URL is incorrect in build.xml

2009-09-18 Thread viola.lu (JIRA)

"tptp.runtime-TPTP-4.6.0.zip " download URL is incorrect in build.xml
-

 Key: GERONIMODEVTOOLS-593
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-593
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.2.0
 Environment: OS:Suse
Reporter: viola.lu
Assignee: Delos Dai
Priority: Minor


1.Build GEP, and when download tptp.runtime-TPTP-4.6.0.zip, Errors exist:
Embedded error: The following error occurred while executing this line:
/var/gep22src/eclipse/build.xml:63: Error while expanding 
/root/.m2/repository/eclipse-downloads/tptp.runtime-TPTP-4.6.0.zip
Negative seek offset


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-4884) Using the default port number may cause unexpected build failure

2009-09-18 Thread Siqi Du (JIRA)

Using the default port number may cause unexpected build failure


 Key: GERONIMO-4884
 URL: https://issues.apache.org/jira/browse/GERONIMO-4884
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2
Reporter: Siqi Du
Priority: Minor
 Fix For: 2.2
 Attachments: fix_unittest.patch

When a geronimo is running

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4884) Using the default port number may cause unexpected build failure

2009-09-18 Thread Siqi Du (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siqi Du updated GERONIMO-4884:
--

Attachment: fix_unittest.patch

> Using the default port number may cause unexpected build failure
> 
>
> Key: GERONIMO-4884
> URL: https://issues.apache.org/jira/browse/GERONIMO-4884
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Siqi Du
>Priority: Minor
> Fix For: 2.2
>
> Attachments: fix_unittest.patch
>
>
> When a geronimo is running

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4875) "edit" button shows under "Created" label when i create a new view

2009-09-18 Thread Siqi Du (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siqi Du updated GERONIMO-4875:
--

Attachment: fix_view_layout.patch

The missing info is not supported in 2.2, so just remove this 2 columns.

> "edit" button shows under "Created"  label  when  i create a new view
> -
>
> Key: GERONIMO-4875
> URL: https://issues.apache.org/jira/browse/GERONIMO-4875
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
> Environment: jdk6
> windows xp sp2
>Reporter: Bin He
>Priority: Minor
> Attachments: fix_view_layout.patch
>
>
> Start server
> Click monitoring porlet
> Create a new view and you can see that  the "edit" button is under "Created" 
> label.and there is nothing under "Modified" label and "Actions" label.
> In geronomo 2114 and geronimo 2115 ,under "Created" and "Modified" is  some 
> time ,under "Actions" is the Edit button.

-- 
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: 816495

2009-09-18 Thread gawor

Geronimo Revision: 816495 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090918/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-jaspi -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT
2) org.apache.geronimo.components:geronimo-jaspi:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-security:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try

[VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try

[BUILD] trunk: Failed for Revision: 816840

[BUILD] branches/2.2: Failed for Revision: 816816

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

[RESULT] [VOTE] release geronimo-jpa_1.0_spec 1.1.2

[CANCELLED] [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

[jira] Created: (GERONIMO-4885) Configure default max heap and max permsize

With Latest G2.2 svn build (rev 816446) can't start through "gsh"

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

Re: [discuss] update Transaction.commit method signature in jta spec jar

[BUILD] trunk: Failed for Revision: 816743

Re: [discuss] update Transaction.commit method signature in jta spec jar

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

[BUILD] branches/2.2: Failed for Revision: 816729

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

[jira] Commented: (GERONIMO-4874) Improve the console filter performance

[BUILD] trunk: Failed for Revision: 816617

[jira] Resolved: (GERONIMO-4603) PropertiesLoginManager is hardwired to properties-login login module

[BUILD] branches/2.2: Failed for Revision: 816591

[jira] Updated: (GERONIMO-4874) Improve the console filter performance

[jira] Assigned: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

[jira] Created: (GERONIMODEVTOOLS-593) "tptp.runtime-TPTP-4.6.0.zip " download URL is incorrect in build.xml

[jira] Created: (GERONIMO-4884) Using the default port number may cause unexpected build failure

[jira] Updated: (GERONIMO-4884) Using the default port number may cause unexpected build failure

[jira] Updated: (GERONIMO-4875) "edit" button shows under "Created" label when i create a new view

[BUILD] trunk: Failed for Revision: 816495

31 matches

Site Navigation

Mail list logo

Footer information