[BUILD] 2.2: Failed for Revision: 618196
Geronimo Revision: 618196 built with tests included See the full build-0300.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/build-0300.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/unit-test-reports 3) org.apache.openejb:openejb-loader:jar:3.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=openejb-loader \ -Dversion=3.0-beta-2 -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.openejb -DartifactId=openejb-loader \ -Dversion=3.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT 2) org.apache.openejb:openejb-loader:jar:3.0-beta-2 4) org.apache.openejb:openejb-server:jar:3.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=openejb-server \ -Dversion=3.0-beta-2 -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.openejb -DartifactId=openejb-server \ -Dversion=3.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT 2) org.apache.openejb:openejb-server:jar:3.0-beta-2 5) org.apache.openejb:openejb-client:jar:3.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=openejb-client \ -Dversion=3.0-beta-2 -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.openejb -DartifactId=openejb-client \ -Dversion=3.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT 2) org.apache.openejb:openejb-client:jar:3.0-beta-2 6) org.apache.openejb:openejb-ejbd:jar:3.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=openejb-ejbd \ -Dversion=3.0-beta-2 -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.openejb -DartifactId=openejb-ejbd \ -Dversion=3.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT 2) org.apache.openejb:openejb-ejbd:jar:3.0-beta-2 7) org.apache.openejb:openejb-jee:jar:3.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=openejb-jee \ -Dversion=3.0-beta-2 -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.openejb -DartifactId=openejb-jee \ -Dversion=3.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT 2) org.apache.openejb:openejb-jee:jar:3.0-beta-2 -- 7 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-openejb:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), java.net (http://download.java.net/maven/1/), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238
Re: [VOTE] Release specs
+1 Guillaume Nodet wrote: Third try ... Tags are here: http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-activation_1.1_spec-1.0.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-saaj_1.3_spec-1.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/specs-1.4/ Staging repo is http://people.apache.org/~gnodet/staging/geronimo-specs/ I'm calling a single vote, as it is imho easier, but if there is any concern, I can create other vote threads if needed. [ ] +1 release these specs [ ] -1 another problem ? FYI, I won't be able for the next two weeks, so I won't be able to close the votes and move the specs to their final location. Hopefully someone can do it (provided that this vote is ok).
Re: [VOTE] Release specs
+1 Jay Guillaume Nodet wrote: Third try ... Tags are here: http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-activation_1.1_spec-1.0.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-saaj_1.3_spec-1.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/specs-1.4/ Staging repo is http://people.apache.org/~gnodet/staging/geronimo-specs/ I'm calling a single vote, as it is imho easier, but if there is any concern, I can create other vote threads if needed. [ ] +1 release these specs [ ] -1 another problem ? FYI, I won't be able for the next two weeks, so I won't be able to close the votes and move the specs to their final location. Hopefully someone can do it (provided that this vote is ok).
Re: svn commit: r618286 - /geronimo/server/branches/2.1/pom.xml
On Feb 4, 2008, at 9:04 AM, [EMAIL PROTECTED] wrote: Author: jbohn Date: Mon Feb 4 06:03:58 2008 New Revision: 618286 URL: http://svn.apache.org/viewvc?rev=618286view=rev Log: stick with openejb snapshot until beta-2 is released Modified: geronimo/server/branches/2.1/pom.xml Modified: geronimo/server/branches/2.1/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/pom.xml?rev=618286r1=618285r2=618286view=diff = = = = = = = = == --- geronimo/server/branches/2.1/pom.xml (original) +++ geronimo/server/branches/2.1/pom.xml Mon Feb 4 06:03:58 2008 @@ -69,7 +69,7 @@ !-- Having a single well named property makes automatic updating for the weekly build much easier. -- -openejbVersion3.0-beta-2/openejbVersion +openejbVersion3.0.0-SNAPSHOT/openejbVersion Oops. Thanks Joe. --kevan
[BUILD] 2.1: Failed for Revision: 618375
Geronimo Revision: 618375 built with tests included See the full build-1400.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-1400.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository
[jira] Commented: (GERONIMO-3746) Plugin Progress Bar Not Updating
[ https://issues.apache.org/jira/browse/GERONIMO-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565459#action_12565459 ] Joseph Leong commented on GERONIMO-3746: Update: Basic-Auth screen was being caused by the output buffer being flushed on the page include. Turning off flushing fixed issue. Plugin Progress Bar Not Updating Key: GERONIMO-3746 URL: https://issues.apache.org/jira/browse/GERONIMO-3746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Joseph Leong Assignee: Kevan Miller Attachments: GERONIMO-3746-2.patch, GERONIMO-3746.patch When installing any plugin from the repository, the progress bar fails to update correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [BUILD] 2.1: Failed for Revision: 618261
I can also see them here: https://maven-repository.dev.java.net/repository/com.sun.xml.bind/ However, it seems that there was some sort of update shortly at 00:27 on 2/4 and since then all downloads fail if you don't already have them in your local repo. I've found references to a maven-2 repo for java.net as well. However, changing to that reference (instead of the maven-1 repo we reference) doesn't help. This is failing for both openejb geronimo builds. I assume something went wrong with the update to the repository last evening that is causing the problem. Joe Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan, I can see some of them here - https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/poms/ - -- dims Kevan Miller wrote: | | On Feb 4, 2008, at 8:03 AM, [EMAIL PROTECTED] wrote: | | Geronimo Revision: 618261 built with tests included | | See the full build-0800.log file at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-0800.log | | | | See the unit test reports at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports | | | apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), | codehaus-snapshots (http://snapshots.repository.codehaus.org), | apache-incubator | (http://people.apache.org/repo/m2-incubating-repository/), | module-local (file:///home/geronimo/geronimo/2.1/repository/) | | | [INFO] | | [INFO] Trace | org.apache.maven.lifecycle.LifecycleExecutionException: Missing: | -- | 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 | | I'm not seeing any of the jaxb-* 2.0.5 artifacts. They were working | yesterday: | Downloading: | http://download.java.net/maven/1//com.sun.xml.bind/poms/jaxb-impl-2.0.5.pom | 656b downloaded | But I'm not seeing anything on the java.net repos now. I assume there's | some config messed up. Anybody know what's up? | --kevan | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHp0w/gNg6eWEDv1kRArDtAJ4m+8yrqK6YVTUq7kzpQnfOpHioZACfYe8e MmnP46pDmYSIh3Ttk/Q75Io= =CWIe -END PGP SIGNATURE-
Re: [BUILD] 2.1: Failed for Revision: 618261
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan, I can see some of them here - https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/poms/ - -- dims Kevan Miller wrote: | | On Feb 4, 2008, at 8:03 AM, [EMAIL PROTECTED] wrote: | | Geronimo Revision: 618261 built with tests included | | See the full build-0800.log file at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-0800.log | | | | See the unit test reports at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports | | | apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), | codehaus-snapshots (http://snapshots.repository.codehaus.org), | apache-incubator | (http://people.apache.org/repo/m2-incubating-repository/), | module-local (file:///home/geronimo/geronimo/2.1/repository/) | | | [INFO] | | [INFO] Trace | org.apache.maven.lifecycle.LifecycleExecutionException: Missing: | -- | 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 | | I'm not seeing any of the jaxb-* 2.0.5 artifacts. They were working | yesterday: | Downloading: | http://download.java.net/maven/1//com.sun.xml.bind/poms/jaxb-impl-2.0.5.pom | 656b downloaded | But I'm not seeing anything on the java.net repos now. I assume there's | some config messed up. Anybody know what's up? | --kevan | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHp0w/gNg6eWEDv1kRArDtAJ4m+8yrqK6YVTUq7kzpQnfOpHioZACfYe8e MmnP46pDmYSIh3Ttk/Q75Io= =CWIe -END PGP SIGNATURE-
[jira] Commented: (GERONIMO-3801) Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version.
[ https://issues.apache.org/jira/browse/GERONIMO-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565323#action_12565323 ] Rick McGuire commented on GERONIMO-3801: Committed revision 618250. Thanks SangjinI guess I wasn't observant enough to notice there were warnings in the build. Merge Mina 1.1.5 AsyncHttpClient into Mina 2.0 based version. - Key: GERONIMO-3801 URL: https://issues.apache.org/jira/browse/GERONIMO-3801 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: AsyncHttpClient Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Attachments: GERONIMO-3801.patch The recent changes that have been made to the AsyncHttpClient based on Mina 1.1.5 need to be merged into the sandbox branch based on the 2.0 Mina API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Build of trunk failed due to org.apache.maven.plugin.enforcer.RequireJavaVersion
Hi Dan and welcome aboard!
At the moment you need to build with a 1.5 jre. I'm using 1.5.0_14 but
any 1.5 should work. There's a check included in the root pom to
require 1.5 or higher but not 1.6.
HTH,
Joe
Dan Becker wrote:
Hello folks,
This is my first post here, but I thought this might be a quickie for the
Geronimo community.
I am attempting to build the trunk of Geronimo using the command mvn
install from my local trunk checkout. A number fo poms are downloaded, and
then my build runs into a problem (most likely
a newbie maven setup problem, did not see similar problem on list):
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireJavaVersion failed
wit
h message: Detected JDK Version: 1.6.0-4 is not in the allowed range
[1.5,1.6).
Environment:
java version 1.6.0_04
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
Maven 2.0.7
svn 1.4.6
Windows XP (Build 2600.xpsp.0501011-1528: Service Pack 2)
Any pointers for how to resolve the Java version issue or some other setup
item I may have forgotten?
Thanks, Dan Becker
[BUILD] 2.1: Failed for Revision: 618261
Geronimo Revision: 618261 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-0800.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository
[jira] Updated: (GERONIMO-2994) Apache Roller plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Petersson updated GERONIMO-2994: -- Attachment: roller_4_0_plugin_080204.patch Roller plugin updates for Geronimo v2.1 Adding roller_4_0_plugin_080204.patch Changes === * Setting properties so that everything roller related is contained within the server. In particular var stuff like cash, indexing, and other stuff will now reside within server var/roller-data/xxx dirs. * Moving roller themes dir from war file to server var/roller-data/themes to make it easy to add extra themes to roller (also needed for the upcoming roller-themes plugin module). Apache Roller plugin - Key: GERONIMO-2994 URL: https://issues.apache.org/jira/browse/GERONIMO-2994 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.2 Reporter: Peter Petersson Assignee: David Jencks Priority: Minor Attachments: geronimo-plugins.xml, geronimo-plugins.xml, geronimo-plugins_070602.xml, geronimo-web.xml, geronimo-web.xml, plan.xml, PluginInstallerGBean.patch, pom.xml, pom.xml, roller-custom.properties, roller-custom.properties, roller-custom.properties, roller-derbydb-plan-g1_2.xml, roller-mysql-db-plan-1-2.xml, roller070409.patch, roller12_070602.zip, roller_4_0_plugin_080103.patch, roller_4_0_plugin_080204.patch, roller_g20_svn_070602.patch, roller_maven_ant_task_070902_0.patch, roller_maven_ant_task_070918_0.patch, roller_plugin.patch, roller_plugin_070717.patch, roller_plugin_070803.patch, roller_plugin_070918.patch, roller_plugin_070921.patch, roller_plugin_patch_070724.txt Have been working on getting Apache Roller running under Geronimo I finally got to the point where the roller application seems to be running smoothly in Geronimo v1.2 (current snapshot). It would be great to eventually see this application as a plugin in G so here are pointers to resources and attached plans. Apache Roller v3.1 Resources (soon to be released) Apache roller home: http://rollerweblogger.org/project/ The bundle: http://people.apache.org/~snoopdave/apache-roller-3.1/ (until it will be available directly via roller home) Required jars: https://roller.dev.java.net/servlets/ProjectDocumentList?expandFolder=6959folderID=0 Path to database create scripts can be found in the bundle above under: apache-roller-3.1/webapp/roller/WEB-INF/dbscripts/ I have tested with the derby database and mysql 5. There is currently a issue with G v1.2 and hibernates v3.1 (used by roller 3.1) property loader that gets a FATAL [HibernateRollerImpl] Error initializing Hibernate java.lang.ClassCastException: java.util.HashSet at org.hibernate.util.PropertiesHelper.resolvePlaceHolders(PropertiesHelper.java:88) Hibernate is expecting a String value (This issue is fixed in hibernate 3.2 with a instanceOf check) Fortunately David Jencks hit this problem in trunk and suggested turning off the activemq and activemq-broker modules in config.xml, to test things out, and after that everything was running smothly :). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.2: Failed for Revision: 618286
Geronimo Revision: 618286 built with tests included See the full build-0900.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/build-0900.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository
Re: [BUILD] 2.1: Failed for Revision: 618261
Grrr I wish Sun would get this fixed (I'm not even sure if they are aware of the problem yet). One possible work-around for now would be to include the items from java.net (jaxb*, jstl, ??) in geronimo/repository. However, I'm not sure if that is worth it yet at this point ... and it wouldn't solve the issue for those of us that build OpenEjb locally (unless you build Geronimo first to populate the local repo). Thoughts? In the meantime I've put the jars from my local repo here if anybody needs them: http://people.apache.org/~jbohn/repo/ Joe Joe Bohn wrote: I can also see them here: https://maven-repository.dev.java.net/repository/com.sun.xml.bind/ However, it seems that there was some sort of update shortly at 00:27 on 2/4 and since then all downloads fail if you don't already have them in your local repo. I've found references to a maven-2 repo for java.net as well. However, changing to that reference (instead of the maven-1 repo we reference) doesn't help. This is failing for both openejb geronimo builds. I assume something went wrong with the update to the repository last evening that is causing the problem. Joe Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan, I can see some of them here - https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/poms/ - -- dims Kevan Miller wrote: | | On Feb 4, 2008, at 8:03 AM, [EMAIL PROTECTED] wrote: | | Geronimo Revision: 618261 built with tests included | | See the full build-0800.log file at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-0800.log | | | | See the unit test reports at | http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports | | | apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), | codehaus-snapshots (http://snapshots.repository.codehaus.org), | apache-incubator | (http://people.apache.org/repo/m2-incubating-repository/), | module-local (file:///home/geronimo/geronimo/2.1/repository/) | | | [INFO] | | [INFO] Trace | org.apache.maven.lifecycle.LifecycleExecutionException: Missing: | -- | 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 | | I'm not seeing any of the jaxb-* 2.0.5 artifacts. They were working | yesterday: | Downloading: | http://download.java.net/maven/1//com.sun.xml.bind/poms/jaxb-impl-2.0.5.pom | 656b downloaded | But I'm not seeing anything on the java.net repos now. I assume there's | some config messed up. Anybody know what's up? | --kevan | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHp0w/gNg6eWEDv1kRArDtAJ4m+8yrqK6YVTUq7kzpQnfOpHioZACfYe8e MmnP46pDmYSIh3Ttk/Q75Io= =CWIe -END PGP SIGNATURE-
Re: [BUILD] 2.1: Failed for Revision: 618261
On Feb 4, 2008, at 8:03 AM, [EMAIL PROTECTED] wrote: Geronimo Revision: 618261 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/build-0800.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository ), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/ ), module-local (file:///home/geronimo/geronimo/2.1/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 I'm not seeing any of the jaxb-* 2.0.5 artifacts. They were working yesterday: Downloading: http://download.java.net/maven/1//com.sun.xml.bind/poms/jaxb-impl-2.0.5.pom 656b downloaded But I'm not seeing anything on the java.net repos now. I assume there's some config messed up. Anybody know what's up? --kevan
Re: Build of trunk failed due to org.apache.maven.plugin.enforcer.RequireJavaVersion
Hi Dan,
I believe our build only works with java 1.5 at the moment.
Also, in an unrelated issue, it looks like Sun may have broken a
maven repository that we rely on for the jaxb jars.
Hopefully the repo issue will be solved soon.
thanks
david jencks
On Feb 4, 2008, at 10:48 AM, Dan Becker wrote:
Hello folks,
This is my first post here, but I thought this might be a quickie
for the
Geronimo community.
I am attempting to build the trunk of Geronimo using the command mvn
install from my local trunk checkout. A number fo poms are
downloaded, and
then my build runs into a problem (most likely
a newbie maven setup problem, did not see similar problem on list):
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0:
org.apache.maven.plugin.enforcer.RequireJavaVersion failed
wit
h message: Detected JDK Version: 1.6.0-4 is not in the allowed range
[1.5,1.6).
Environment:
java version 1.6.0_04
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
Maven 2.0.7
svn 1.4.6
Windows XP (Build 2600.xpsp.0501011-1528: Service Pack 2)
Any pointers for how to resolve the Java version issue or some
other setup
item I may have forgotten?
Thanks, Dan Becker
--
View this message in context: http://www.nabble.com/Build-of-trunk-
failed-due-to-org.apache.maven.plugin.enforcer.RequireJavaVersion-
tp15273467s134p15273467.html
Sent from the Apache Geronimo - Dev mailing list archive at
Nabble.com.
Build of trunk failed due to org.apache.maven.plugin.enforcer.RequireJavaVersion
Hello folks,
This is my first post here, but I thought this might be a quickie for the
Geronimo community.
I am attempting to build the trunk of Geronimo using the command mvn
install from my local trunk checkout. A number fo poms are downloaded, and
then my build runs into a problem (most likely
a newbie maven setup problem, did not see similar problem on list):
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireJavaVersion failed
wit
h message: Detected JDK Version: 1.6.0-4 is not in the allowed range
[1.5,1.6).
Environment:
java version 1.6.0_04
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
Maven 2.0.7
svn 1.4.6
Windows XP (Build 2600.xpsp.0501011-1528: Service Pack 2)
Any pointers for how to resolve the Java version issue or some other setup
item I may have forgotten?
Thanks, Dan Becker
--
View this message in context:
http://www.nabble.com/Build-of-trunk-failed-due-to-org.apache.maven.plugin.enforcer.RequireJavaVersion-tp15273467s134p15273467.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Updated: (GERONIMO-3746) Plugin Progress Bar Not Updating
[ https://issues.apache.org/jira/browse/GERONIMO-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3746: --- Attachment: GERONIMO-3746-3.patch Patch 3: *Fixes Basic-Auth Issue *If an Exception Is Thrown, An Indicating Message Will Appear As Well As A Back Button To Bring User Back To Plugin Home. Issues Remaining: CSRF Issue that occurs when a user tries to initiate the install process a second time around Plugin Progress Bar Not Updating Key: GERONIMO-3746 URL: https://issues.apache.org/jira/browse/GERONIMO-3746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Joseph Leong Assignee: Kevan Miller Attachments: GERONIMO-3746-2.patch, GERONIMO-3746-3.patch, GERONIMO-3746.patch When installing any plugin from the repository, the progress bar fails to update correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
toby cabot updated GERONIMO-3806:
-
Component/s: deployment
Regression: [Regression]
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.2
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Vamsavardhana Reddy
Priority: Minor
Attachments: bug3806-patch.txt
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3746) Plugin Progress Bar Not Updating
[ https://issues.apache.org/jira/browse/GERONIMO-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565547#action_12565547 ] Joseph Leong commented on GERONIMO-3746: Update: Added an indicator message on the progress page to list an exception, if one is caught and a back button to bring the user back to the plugin install home page. Plugin Progress Bar Not Updating Key: GERONIMO-3746 URL: https://issues.apache.org/jira/browse/GERONIMO-3746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Joseph Leong Assignee: Kevan Miller Attachments: GERONIMO-3746-2.patch, GERONIMO-3746.patch When installing any plugin from the repository, the progress bar fails to update correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Fwd: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync
Can someone please fix this... --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: February 4, 2008 1:09:31 PM PST To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/maven/server/binaries/2.1: Operation not permitted
[jira] Created: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Vamsavardhana Reddy
Priority: Minor
Fix For: 2.0.2, 2.1
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue, jms/OutboundEventQueue]
defined in plan file, reason - corresponding entry in deployment descriptor
missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory, mail/MailSession,
jms/TopicConnectionFactory] defined in plan file, reason - corresponding entry
in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the refMap
variable does not get completely emptied out, since the specific session bean
will only contain a subset of the resource-env-refs that are defined in the
plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean delivery problem
[
https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525
]
beniamin edited comment on GERONIMO-3783 at 2/4/08 1:02 PM:
I've edited deployment plan and finally have RAs like below:
{noformat}
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageReceiversMDB/resourceadapter-name
config-property-setting
name=UseInboundSessiontrue/config-property-setting
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMRConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
/xa-transaction
single-pool
max-size20/max-size
blocking-timeout-milliseconds5000/blocking-timeout-milliseconds
select-one-assume-match/
/single-pool
/connectionmanager
/connectiondefinition-instance
/connection-definition
/outbound-resourceadapter
/resourceadapter
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageSender/resourceadapter-name
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMSConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
/xa-transaction
single-pool
max-size20/max-size
blocking-timeout-milliseconds5000/blocking-timeout-milliseconds
select-one-assume-match/
/single-pool
/connectionmanager
/connectiondefinition-instance
/connection-definition
/outbound-resourceadapter
/resourceadapter
{noformat}
It's not working if {{maxSessions}} not equals {{maxMessagesPerSessions}}
was (Author: beniamin):
I've edited deployment plan and finally have RAs like below:
pre
resourceadapter
resourceadapter-instance
resourceadapter-nameMessageReceiversMDB/resourceadapter-name
config-property-setting
name=UseInboundSessiontrue/config-property-setting
nam:workmanager
xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2;
nam:gbean-linkDefaultWorkManager/nam:gbean-link
/nam:workmanager
/resourceadapter-instance
outbound-resourceadapter
connection-definition
connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface
connectiondefinition-instance
nameMRConnectionFactory/name
connectionmanager
xa-transaction
transaction-caching/
[jira] Issue Comment Edited: (GERONIMO-3746) Plugin Progress Bar Not Updating
[ https://issues.apache.org/jira/browse/GERONIMO-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565556#action_12565556 ] jleong edited comment on GERONIMO-3746 at 2/4/08 3:00 PM: Patch 3: *Fixes Basic-Auth Issue *If an Exception Is Thrown, An Indicating Message Will Appear As Well As A Back Button To Bring User Back To Plugin Home. Issues Remaining: CSRF Issue that occurs when a user tries to initiate the install process a second time around *Note, Applying Patch 3 will also apply the changes from Patch 2, thus making Patch 2 unnecessary to apply with this. was (Author: jleong): Patch 3: *Fixes Basic-Auth Issue *If an Exception Is Thrown, An Indicating Message Will Appear As Well As A Back Button To Bring User Back To Plugin Home. Issues Remaining: CSRF Issue that occurs when a user tries to initiate the install process a second time around Plugin Progress Bar Not Updating Key: GERONIMO-3746 URL: https://issues.apache.org/jira/browse/GERONIMO-3746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Joseph Leong Assignee: Kevan Miller Attachments: GERONIMO-3746-2.patch, GERONIMO-3746-3.patch, GERONIMO-3746.patch When installing any plugin from the repository, the progress bar fails to update correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
toby cabot updated GERONIMO-3806:
-
Attachment: bug3806-patch.txt
Here's a patch that quiets the messages in my case (and adds a couple of debug
messages that I found helpful). With this patch applied and log4j screwed down
to DEBUG I get:
16:36:46,764 DEBUG [ResourceRefBuilder] trying to resolve JobCF, type
reva.job.ra.ConnectionFactory, resourceRef null
16:36:46,766 DEBUG [ResourceRefBuilder] initial 0 unresolved 0 refmap 0
16:36:47,004 DEBUG [ResourceRefBuilder] trying to resolve JobCF, type
reva.job.ra.ConnectionFactory, resourceRef null
16:36:47,005 DEBUG [ResourceRefBuilder] initial 0 unresolved 0 refmap 0
... and no warnings.
Someone who understands the operation of the buildNaming() method better than I
do should inspect the code but I believe (from inspection) that it shouldn't
break the case that GERONIMO-3248 solved.
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Vamsavardhana Reddy
Priority: Minor
Fix For: 2.0.2, 2.1
Attachments: bug3806-patch.txt
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525 ] Tomasz Mazan commented on GERONIMO-3783: I've edited deployment plan and finally have RAs like below: resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter resourceadapter resourceadapter-instance resourceadapter-nameMessageSender/resourceadapter-name nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMSConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter It's not working if codemaxSessions/code not equals codemaxMessagesPerSessions/code MessageDrivenBean delivery problem -- Key: GERONIMO-3783 URL: https://issues.apache.org/jira/browse/GERONIMO-3783 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1 Environment: Windows XP Professional, 2GB ram, Java6SE, Geronimo 2.1-snapshot (2008-01-02) Reporter: Tomasz Mazan Priority: Critical Attachments: mdb-issue.zip MessageDrivenBean that listens on the Queue receive (and process) some messages and then stop receiving any new message until next module's restart. After restart a few next messages are delivered to MDB, and it stops again. Some additional information I put here http://www.nabble.com/Strange-plug-with-delivering-messages-to-MDB-td14923100s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.2: Failed for Revision: 618410
Geronimo Revision: 618410 built with tests included See the full build-1500.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/build-1500.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository
[jira] Issue Comment Edited: (GERONIMO-3783) MessageDrivenBean delivery problem
[ https://issues.apache.org/jira/browse/GERONIMO-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565525#action_12565525 ] beniamin edited comment on GERONIMO-3783 at 2/4/08 1:00 PM: I've edited deployment plan and finally have RAs like below: pre resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter resourceadapter resourceadapter-instance resourceadapter-nameMessageSender/resourceadapter-name nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMSConnectionFactory/name connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size20/max-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds select-one-assume-match/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter /pre It's not working if codemaxSessions/code not equals codemaxMessagesPerSessions/code was (Author: beniamin): I've edited deployment plan and finally have RAs like below: resourceadapter resourceadapter-instance resourceadapter-nameMessageReceiversMDB/resourceadapter-name config-property-setting name=UseInboundSessiontrue/config-property-setting nam:workmanager xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:gbean-linkDefaultWorkManager/nam:gbean-link /nam:workmanager /resourceadapter-instance outbound-resourceadapter connection-definition connectionfactory-interfacejavax.jms.ConnectionFactory/connectionfactory-interface connectiondefinition-instance nameMRConnectionFactory/name connectionmanager xa-transaction transaction-caching/
[jira] Commented: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565545#action_12565545
]
toby cabot commented on GERONIMO-3806:
--
The fix for GERONIMO-3248 causes two warnings in the log when a webapp has a
resource-ref in web.xml to a resource adapter in the same .ear:
16:24:19,032 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [] defined in plan file, reason - corresponding entry in deployment
descriptor missing.
16:24:19,311 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [] defined in plan file, reason - corresponding entry in deployment
descriptor missing.
This worked OK prior to r572902.
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Vamsavardhana Reddy
Priority: Minor
Fix For: 2.0.2, 2.1
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-99) Show how to run gshell from java service wrapper
Show how to run gshell from java service wrapper Key: GSHELL-99 URL: https://issues.apache.org/jira/browse/GSHELL-99 Project: GShell Issue Type: New Feature Security Level: public (Regular issues) Reporter: David Jencks Assignee: Jason Dillon Some people like to run e.g. geronimo using JSW. It would be helpful to demonstrate how to e.g. run geronimo using JSW + GShell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Build of trunk failed due to org.apache.maven.plugin.enforcer.RequireJavaVersion
Dan Becker wrote:
This is my first post here, but I thought this might be a quickie for the
Geronimo community.
I am attempting to build the trunk of Geronimo using the command mvn
install from my local trunk checkout. A number fo poms are downloaded,
and then my build runs into a problem (most likely
a newbie maven setup problem, did not see similar problem on list):
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireJavaVersion
failed wit
h message: Detected JDK Version: 1.6.0-4 is not in the allowed range
[1.5,1.6).
Thanks for your help folks. You are indeed correct that the build must be
done with JDK 1.5 or greater, but not 1.6. I was thrown off by the error
message with the range [1.5,1.6). I guess the round paren excludes the 1.6
endpoint. Anyway, I am now progressing.
Thanks, Dan Becker
--
View this message in context:
http://www.nabble.com/Build-of-trunk-failed-due-to-org.apache.maven.plugin.enforcer.RequireJavaVersion-tp15273467s134p15277978.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Updated: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
toby cabot updated GERONIMO-3806:
-
Fix Version/s: (was: 2.0.2)
(was: 2.1)
Patch Info: [Patch Available]
Affects Version/s: (was: 2.0-M6)
2.0.2
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.2
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Vamsavardhana Reddy
Priority: Minor
Attachments: bug3806-patch.txt
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] 2.0: Failed for Revision: 618502
Geronimo Revision: 618502 built with tests included See the full build-2000.log file at http://geronimo.apache.org/maven/server/binaries/2.0/20080204/build-2000.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.0/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.0/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.0.3-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.0.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.0/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.0.3-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.0.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.0/repository
Re: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync
Let me know if it's still complaining. Jarek On Feb 4, 2008 4:24 PM, Jason Dillon [EMAIL PROTECTED] wrote: Can someone please fix this... --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: February 4, 2008 1:09:31 PM PST To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/maven/server/binaries/2.1: Operation not permitted
[jira] Created: (GERONIMO-3807) ERROR's logged during plugin installation for non-existent plugins
ERROR's logged during plugin installation for non-existent plugins -- Key: GERONIMO-3807 URL: https://issues.apache.org/jira/browse/GERONIMO-3807 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1 Reporter: Kevan Miller Fix For: 2.1 I brought up the console screen to install plugins and had a number of ERROR's logged of the following form: 21:36:07,628 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT 21:36:07,722 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/j2ee-system/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT 21:36:07,723 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/xmlbeans/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT ... Presumably because the 2.2-SNAPSHOT plugins were registered in ~/.m2/repository/geronimo-plugins.xml, but they are not in my repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r618102 - /geronimo/server/branches/2.1/plugins/clustering/wadi-clustering/pom.xml
After quick scan of the WADI code, it looks like it has a lot of dependencies on the concurrent library. So we'll definitely need that dependency at runtime. And to be more specific, I did not see any references to ConcurrentReaderHashMap but a few references to CopyOnWriteArrayList. Jarek On Feb 3, 2008 10:52 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Feb 3, 2008, at 5:34 PM, Gianny Damour wrote: Hi Kevan, concurrent is a WADI runtime dependency. The server starts fine because wadi-clustering is not started by default and, assuming this was the case, this dependency is only used when an invocation is contextualized. So, could you please rollback this change? A bit more info on the problem with the concurrent library. The doc that I've found on the concurrent library is here -- http://g.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html As described there, the concurrent classes have been released to the public domain. However, two classes are copyright Sun and appear to be covered by the following license agreement: http://g.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/sun-u.c.license.pdf The problem with that license is: You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. This limitation is, I'm pretty sure, going to be against Apache Policy. It would be classified as a category x license (i.e. the licensed artifacts can't be included in an Apache distribution). See http://people.apache.org/~rubys/3party.html for more information on 3rd party licensing. So, things we can do: 1) validate the above on legal-discuss. I could always be wrong. 2) leave out concurrent jar, but require users to download the jar if they want to use wadi 3) update wadi to use JSE 5 concurrent support 4) Remove the CopyOnWriteArrayList and ConcurrentReaderHashMap classes from the concurrent jar. If wadi (and internal concurrent implementation) doesn't use those classes, everything should be OK. We included the library in at least our 1.1.1 release (it's not in our 2.0.x releases). Unfortunately, that doesn't help us. Just means that we were wrong back then... If anybody has any additional thoughts or ideas, let us know. We'll have to resolve this issue prior to a 2.1 release. --kevan
[BUILD] 2.2: Failed for Revision: 618512
Geronimo Revision: 618512 built with tests included See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/build-2100.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080204/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.xml.bind -DartifactId=jaxb-xjc \ -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) com.sun.xml.bind:jaxb-xjc:jar:2.0.5 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository
[jira] Commented: (GERONIMO-3808) NPE during server shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565632#action_12565632 ] Joe Bohn commented on GERONIMO-3808: Yes, I've been seeing these now too. I haven't picked up every build but I know that I didn't see them with rev. 616128 of trunk but then later saw them with rev. 616888. NPE during server shutdown -- Key: GERONIMO-3808 URL: https://issues.apache.org/jira/browse/GERONIMO-3808 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.1 Anybody else seeing these exceptions during server shutdown? java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.listBindings(ContextFlyweight.java:92) at org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:88) at org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:71) at org.apache.xbean.naming.context.AbstractContext.isEmpty(AbstractContext.java:449) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:138) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:123) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:387) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:377) at org.apache.geronimo.gjndi.KernelContextGBean.removeBinding(KernelContextGBean.java:206) at org.apache.geronimo.gjndi.KernelContextGBean$ContextLifecycleListener.stopping(KernelContextGBean.java:103) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppingEvent(BasicLifecycleMonitor.java:188) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$400(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppingEvent(BasicLifecycleMonitor.java:258) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:167) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3809) shutdown from admin console does not work
shutdown from admin console does not work - Key: GERONIMO-3809 URL: https://issues.apache.org/jira/browse/GERONIMO-3809 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.1 Reporter: Kevan Miller Fix For: 2.1.1 Attempted to shutdown the server using the admin console. After clicking shutdown, then the shutdown button, receiving a shutdown verify prompt, and pressing OK. Nothing happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3808) NPE during server shutdown
NPE during server shutdown -- Key: GERONIMO-3808 URL: https://issues.apache.org/jira/browse/GERONIMO-3808 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Kevan Miller Fix For: 2.1 Anybody else seeing these exceptions during server shutdown? java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.listBindings(ContextFlyweight.java:92) at org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:88) at org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:71) at org.apache.xbean.naming.context.AbstractContext.isEmpty(AbstractContext.java:449) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:138) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:123) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:387) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:377) at org.apache.geronimo.gjndi.KernelContextGBean.removeBinding(KernelContextGBean.java:206) at org.apache.geronimo.gjndi.KernelContextGBean$ContextLifecycleListener.stopping(KernelContextGBean.java:103) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppingEvent(BasicLifecycleMonitor.java:188) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$400(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppingEvent(BasicLifecycleMonitor.java:258) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:167) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync
Thx :-) --jason On Feb 4, 2008, at 6:58 PM, Jarek Gawor wrote: Let me know if it's still complaining. Jarek On Feb 4, 2008 4:24 PM, Jason Dillon [EMAIL PROTECTED] wrote: Can someone please fix this... --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: February 4, 2008 1:09:31 PM PST To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/maven/server/binaries/2.1: Operation not permitted
[jira] Assigned: (GERONIMO-3809) shutdown from admin console does not work
[ https://issues.apache.org/jira/browse/GERONIMO-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3809: - Assignee: Jarek Gawor shutdown from admin console does not work - Key: GERONIMO-3809 URL: https://issues.apache.org/jira/browse/GERONIMO-3809 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.1 Reporter: Kevan Miller Assignee: Jarek Gawor Fix For: 2.1.1 Attempted to shutdown the server using the admin console. After clicking shutdown, then the shutdown button, receiving a shutdown verify prompt, and pressing OK. Nothing happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
[ https://issues.apache.org/jira/browse/GERONIMO-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565634#action_12565634 ] Erik B. Craig commented on GERONIMO-3810: - Fixed in rev. 618493 for 2.1 branch Fixed in rev. 618526 for trunk. mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
[ https://issues.apache.org/jira/browse/GERONIMO-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3810. - Resolution: Fixed mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3809) shutdown from admin console does not work
[ https://issues.apache.org/jira/browse/GERONIMO-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3809. --- Resolution: Fixed Fix Version/s: (was: 2.1.1) 2.1 Committed a fix to trunk (revision 618525) and branches/2.1 (revision 618527). shutdown from admin console does not work - Key: GERONIMO-3809 URL: https://issues.apache.org/jira/browse/GERONIMO-3809 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.1 Reporter: Kevan Miller Assignee: Jarek Gawor Fix For: 2.1 Attempted to shutdown the server using the admin console. After clicking shutdown, then the shutdown button, receiving a shutdown verify prompt, and pressing OK. Nothing happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3811) EjbServer portlet
EjbServer portlet - Key: GERONIMO-3811 URL: https://issues.apache.org/jira/browse/GERONIMO-3811 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: OpenEJB Environment: All Reporter: Manu T George Assignee: Manu T George A portlet to show information about the OpenEJB container integrated in Geronimo. It should also allow configuration of some parameters like pool size etc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
