[BUILD] trunk: Failed for Revision: 930806
Geronimo Revision: 930806 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/unit-test-reports [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots
SNAPSHOT versions in current trunk
Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT felix bundlerepository: 1.5.0-snapshot felix karaf console: 1.5.0-snapshot felix framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.blueprint org.apache.aries.blueprint.api org.apache.aries.blueprint.core org.apache.aries.blueprint.cm All of the Geronimo specs have new versions, which can be released prior to creating the new release. To the best of my knowledge, all of these are in a state where they can be released. geronimo-osgi-registry geronimo-osgi-locator geronimo-activation_1.1_spec geronimo-annotation_1.1_spec geronimo-atinject_1.0_spec geronimo-cpp_1.0_spec geronimo-ejb_3.1_spec geronimo-interceptor_1.1_spec geronimo-jaxb_2.0_spec geronimo-j2ee-connector_1.6_spec geronimo-javaee-deployment_1.1MR3_spec geronimo-jacc_1.1_spec geronimo-jaspic_1.0_spec geronimo-javamail_1.4_spec geronimo-jaxr_1.0_spec geronimo-jaxrpc_1.1_spec geronimo-jaxrs_1.1_spec geronimo-jaxws_2.2_spec geronimo-jcdi_1.0_spec geronimo-jsp_2.2_spec geronimo-el_2.2_spec geronimo-servlet_1.1_spec geronimo-jpa_2.0_spec geronimo-validation_1.0_spec geronimo-annotation_1.1_spec geronimo-ws-metadata_2.0_spec geronimo-saaj_1.3_spec geronimo-stax-api_1.2_spec The geronimo schema projects: geronimo-schema-jee5 geronimo-schema-j2ee_1.4 geronimo-schema-javaee_6 The geronimo components releases geronimo-connector geronimo-transaction geronimo-jaspi Servicemix bundles org.apache.servicemix.bundles.jdt-core
Re: SNAPSHOT versions in current trunk
Sorry about this...hit the wrong key sequence in Thunderbird and sent this out in draft status. Still working on pulling together the list of snapshots in Geronimo 3.0...the complete list and discussion will be coming later. Rick On 4/5/2010 6:56 AM, Rick McGuire wrote: Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT felix bundlerepository: 1.5.0-snapshot felix karaf console: 1.5.0-snapshot felix framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.blueprint org.apache.aries.blueprint.api org.apache.aries.blueprint.core org.apache.aries.blueprint.cm All of the Geronimo specs have new versions, which can be released prior to creating the new release. To the best of my knowledge, all of these are in a state where they can be released. geronimo-osgi-registry geronimo-osgi-locator geronimo-activation_1.1_spec geronimo-annotation_1.1_spec geronimo-atinject_1.0_spec geronimo-cpp_1.0_spec geronimo-ejb_3.1_spec geronimo-interceptor_1.1_spec geronimo-jaxb_2.0_spec geronimo-j2ee-connector_1.6_spec geronimo-javaee-deployment_1.1MR3_spec geronimo-jacc_1.1_spec geronimo-jaspic_1.0_spec geronimo-javamail_1.4_spec geronimo-jaxr_1.0_spec geronimo-jaxrpc_1.1_spec geronimo-jaxrs_1.1_spec geronimo-jaxws_2.2_spec geronimo-jcdi_1.0_spec geronimo-jsp_2.2_spec geronimo-el_2.2_spec geronimo-servlet_1.1_spec geronimo-jpa_2.0_spec geronimo-validation_1.0_spec geronimo-annotation_1.1_spec geronimo-ws-metadata_2.0_spec geronimo-saaj_1.3_spec geronimo-stax-api_1.2_spec The geronimo schema projects: geronimo-schema-jee5 geronimo-schema-j2ee_1.4 geronimo-schema-javaee_6 The geronimo components releases geronimo-connector geronimo-transaction geronimo-jaspi Servicemix bundles org.apache.servicemix.bundles.jdt-core
[BUILD] branches/2.2: Failed for Revision: 930842
Geronimo Revision: 930842 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/build-0800.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/unit-test-reports
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 13 resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 9 source files to
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.tomcat.StatTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.23 sec
Running org.apache.geronimo.tomcat.TomcatServerGBeanTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.588 sec
Running org.apache.geronimo.tomcat.JACCSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.5 sec
Running org.apache.geronimo.tomcat.ContainerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.057 sec
Running org.apache.geronimo.tomcat.ApplicationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.152 sec
Running org.apache.geronimo.tomcat.BasicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.281 sec
Running org.apache.geronimo.tomcat.JAASSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.407 sec
Results :
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-tomcat6/2.2.1-SNAPSHOT/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Tomcat
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479
SNAPSHOT dependencies in Geronimo 3.0
Ok, the completed email that I accidentally sent out earlier. Since we're targetting an M1 release of Geroinimo 3.0, we need to be taking a close look at the snapshot dependencies we have in the release. Here is what I believe is the complete list of current snapshot dependencies. We have way fewer external snapshot dependencies than I actually believed, so this might not be too bad, even if we need to release some of these from external. It helps a little that we're already using released versions of OpenJPA and jetty8. Here's a breakdown by category: non-Geronimo controlled releases: Tomcat 7 (which we currently have an external release for because we have some patches that have not be accepted by the Tomcat community), openejb, pax logging, xbean, myfaces, and felix. It should be easy to push out an xbean release, openejb just had a release, and might be reluctant to push a new one so soon after the last one. I'm not sure if the latest release can be used for Geronimo or not. I suspect not, since there has been a bit of recent work on getting openejb to run in 3.0. myfaces and pax logging I'm not sure about. Does anybody have connections to these communities strong enough to ask about a release? What is the current state of the felix and karaf projects? Would it be possible to get new releases in the next couple of weeks? Another big category is Aries, which is currently attempting to put out their first release. There's a good chance this will happen in time for the 3.0 milestone release. This is probably the biggest dependency, since a major goal of this milestone is to get feedback on the OSGi application features. And finally, we have one servicemix bundle dependency that's in snapshot state. Hopefully, we can get a release pushed for this. As a fallback, we could just add another subproject to geronimo-bundles to cover this. Geronimo specs: We need new releases of almost all of these to pick up the new OSGi support. We probably should put these up for a vote by early next week at the latest. Do we need to have a separate vote for each spec, or can we do a group vote on this? Also, the javamail uber jar will need a release vote. Geronimo components: We need releases for connector, transaction, and jaspic. In taking a look at these, I discovered that these jars a building using the java ee 5 versions of apis and providers (e.g., stax, jaxb). I suspect these really should be upgraded. Also, the dependencies tend to be non-bundle versions of a lot of the jars. I suspect these should really be using the bundle versions. Geronimo bundles: The framework has bundle versions of a number of common components. This is part of the Geronimo build tree, and thus these are not released separately. However, these bundle versions look like they should be getting used in other places (e.g., components, possibly xbean). This seems to argue that they should be moved out the geronimo tree to possibly components or maybe their own top-level tree as peers to components/external etc. Here is what I believe is the current list of snapshot dependencies. Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT Felix: main bundlerepository: 1.5.0-SNAPSHOT karaf main: 1.5.0-SNAPSHOT karaf console: 1.5.0-SNAPSHOT karaf client: 1.5.0-SNAPSHOT framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.jmx org.apache.aries.blueprint org.apache.aries.blueprint.api org.apache.aries.blueprint.core org.apache.aries.blueprint.cm All of the Geronimo specs have new versions, which can be released prior to creating the new release. To the best of my knowledge, all of these are in a state where they can be released. geronimo-osgi-registry geronimo-osgi-locator geronimo-activation_1.1_spec geronimo-annotation_1.1_spec geronimo-atinject_1.0_spec geronimo-cpp_1.0_spec geronimo-ejb_3.1_spec geronimo-interceptor_1.1_spec geronimo-jaxb_2.0_spec geronimo-j2ee-connector_1.6_spec geronimo-javaee-deployment_1.1MR3_spec geronimo-jacc_1.1_spec geronimo-jaspic_1.0_spec geronimo-javamail_1.4_spec geronimo-jaxr_1.0_spec geronimo-jaxrpc_1.1_spec geronimo-jaxrs_1.1_spec geronimo-jaxws_2.2_spec geronimo-jcdi_1.0_spec geronimo-jsp_2.2_spec
components dependencies
This is sort of related to the earlier email I sent out about the snapshot dependencies. In looking at the dependencies of the subprojects in the geronimo components tree, I find what appear to be a few problems we should probably correct: geronimo-schema-javaee_6: This is ok as it stands, but should we move the latest verions of the java 1.4 and java 5 schemas into the components tree rather than leaving them in the restricted TCK tree? geronimo-jaspi: This is building with the 2.1 version of the jaxb specs and the older release of the stax api spec. It also has dependencies on non-bundle versions of sxc-jaxb, woodstox, and the jaxb-impl. The jaxb-impl is also at the 2.1.7 level rather than the 2.2 level used by the server. This is a fairly simple update, but would have dependencies on geronimo bundles components, which really suggests those should be moved out of the server tree as separately buildable components. I suspect it would make the bootstrapping process easier if they could be handled that way. On the downside, this creates another level of release artifacts that require voting and a release process. geronimo-jaspi-openid: Building with the older version of the jaspic spec jar and servlet 2.5 spec. Should this be using the java ee 6 api versions? This is also using the 1.0-SNAPSHOT version of the geronimo-jaspic build, rather than the current 1.1-SNAPSHOT version. geronimo-connector/geronimo-transaction: The connector 1.6 spec version is the 1.0-EA-SNAPSHOT. This should be updated to the latest spec snapshot. Thoughts on updating this? The issue of the use of the geronimo bundles probably needs to be resolved ASAP so we can get release votes out for those components in the very near future. Rick
[BUILD] trunk: Failed for Revision: 930855
Geronimo Revision: 930855 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/unit-test-reports [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots
Re: components dependencies
For geronimo-schema-java1.4 and java 5 schemas, I wish somebody could double-check the descriptions in the license and notice files in the geronimo-schema-javaee_6 before moving them out. I have mentioned it in the past, and Donald gave me some suggestions to refer to the OpenJPA project. I do update them from my understanding. But ... Anyway, if we are OK with the current descriptions, I would move 1.4 and 1.5 out as soon as possible. 2010/4/5 Rick McGuire rick...@gmail.com This is sort of related to the earlier email I sent out about the snapshot dependencies. In looking at the dependencies of the subprojects in the geronimo components tree, I find what appear to be a few problems we should probably correct: geronimo-schema-javaee_6: This is ok as it stands, but should we move the latest verions of the java 1.4 and java 5 schemas into the components tree rather than leaving them in the restricted TCK tree? geronimo-jaspi: This is building with the 2.1 version of the jaxb specs and the older release of the stax api spec. It also has dependencies on non-bundle versions of sxc-jaxb, woodstox, and the jaxb-impl. The jaxb-impl is also at the 2.1.7 level rather than the 2.2 level used by the server. This is a fairly simple update, but would have dependencies on geronimo bundles components, which really suggests those should be moved out of the server tree as separately buildable components. I suspect it would make the bootstrapping process easier if they could be handled that way. On the downside, this creates another level of release artifacts that require voting and a release process. geronimo-jaspi-openid: Building with the older version of the jaspic spec jar and servlet 2.5 spec. Should this be using the java ee 6 api versions? This is also using the 1.0-SNAPSHOT version of the geronimo-jaspic build, rather than the current 1.1-SNAPSHOT version. geronimo-connector/geronimo-transaction: The connector 1.6 spec version is the 1.0-EA-SNAPSHOT. This should be updated to the latest spec snapshot. Thoughts on updating this? The issue of the use of the geronimo bundles probably needs to be resolved ASAP so we can get release votes out for those components in the very near future. Rick -- Ivan
Re: components dependencies
On Apr 5, 2010, at 9:23 AM, Ivan wrote: For geronimo-schema-java1.4 and java 5 schemas, I wish somebody could double-check the descriptions in the license and notice files in the geronimo-schema-javaee_6 before moving them out. I have mentioned it in the past, and Donald gave me some suggestions to refer to the OpenJPA project. I do update them from my understanding. But ... Anyway, if we are OK with the current descriptions, I would move 1.4 and 1.5 out as soon as possible. IIRC, I took a quick look at the ee6 schema license/notice files and they looked good. Would definitely re-review prior to release. Are we going to/do we need to release 1.4 and 1.5 schema's? Originally the 1.4 and 1.5 schemas had license restrictions which prohibited us including in our svn. If all xsd's have been fixed, then we can move them out. It would be good to do this, but if we don't need to re-release them, it's not absolutely imperative, IMO. --kevan
Re: components dependencies
Thanks, Kevan. I am afraid that we may still need to release an OSGI style 1.4 and 1.5 for Geronimo 3.0. 2010/4/5 Kevan Miller kevan.mil...@gmail.com On Apr 5, 2010, at 9:23 AM, Ivan wrote: For geronimo-schema-java1.4 and java 5 schemas, I wish somebody could double-check the descriptions in the license and notice files in the geronimo-schema-javaee_6 before moving them out. I have mentioned it in the past, and Donald gave me some suggestions to refer to the OpenJPA project. I do update them from my understanding. But ... Anyway, if we are OK with the current descriptions, I would move 1.4 and 1.5 out as soon as possible. IIRC, I took a quick look at the ee6 schema license/notice files and they looked good. Would definitely re-review prior to release. Are we going to/do we need to release 1.4 and 1.5 schema's? Originally the 1.4 and 1.5 schemas had license restrictions which prohibited us including in our svn. If all xsd's have been fixed, then we can move them out. It would be good to do this, but if we don't need to re-release them, it's not absolutely imperative, IMO. --kevan -- Ivan
Re: components dependencies
On 4/5/2010 10:02 AM, Kevan Miller wrote: On Apr 5, 2010, at 9:23 AM, Ivan wrote: For geronimo-schema-java1.4 and java 5 schemas, I wish somebody could double-check the descriptions in the license and notice files in the geronimo-schema-javaee_6 before moving them out. I have mentioned it in the past, and Donald gave me some suggestions to refer to the OpenJPA project. I do update them from my understanding. But ... Anyway, if we are OK with the current descriptions, I would move 1.4 and 1.5 out as soon as possible. IIRC, I took a quick look at the ee6 schema license/notice files and they looked good. Would definitely re-review prior to release. Are we going to/do we need to release 1.4 and 1.5 schema's? Originally the 1.4 and 1.5 schemas had license restrictions which prohibited us including in our svn. If all xsd's have been fixed, then we can move them out. It would be good to do this, but if we don't need to re-release them, it's not absolutely imperative, IMO. --kevan We needed to update these to get the osgi package imports/exports sorted out, so we definitely need to re-released them. I'm not sure if the xsd's have been changed nor not. Rick
Re: 3.0 Milestone Release?
A few thoughts: 1) Yes, I think it would be good to have a milestone release to show some of the Aries + Java EE 6 stuff. 2) I am concerned about the number of snapshot dependencies and the time would take to release them all for the milestone. So we should start releasing stuff now... but at the same time we should consider what happens if we can't get everything released in time. That is, should we consider removing certain components from the release or releasing the milestone with some snapshot dependencies. In general, I have no problem with either options. This is a milestone release so it doesn't have to be perfect. 3) Things that I think we should get done before/for the milestone: a) make sure the testsuites are running, b) figure out how to deal with the endorsed libraries in maven. Jarek On Mon, Mar 29, 2010 at 3:42 PM, Kevan Miller kevan.mil...@gmail.com wrote: I'm curious to hear the community's thoughts about starting to pull together a 3.0 Milestone release. I think there's been a lot of progress on trunk and that it would be valuable to start pulling things together for a release. If anything, just planning for a release starts to identify hat parts are missing and what needs to be done. Also, gives users a chance to start focusing on what features they are going to need... Thoughts? --kevan
Re: SNAPSHOT dependencies in Geronimo 3.0
Rick, There are a few more snapshot dependencies in trunk: org.apache.ws.scout, org.apache.juddi, org.apache.activemq, org.apache.portals.pluto and also a few more Aries modules: org.apache.aries.web.*, org.apache.aries.application.*, org.apache.aries.jpa.* Jarek On Mon, Apr 5, 2010 at 8:43 AM, Rick McGuire rick...@gmail.com wrote: Ok, the completed email that I accidentally sent out earlier. Since we're targetting an M1 release of Geroinimo 3.0, we need to be taking a close look at the snapshot dependencies we have in the release. Here is what I believe is the complete list of current snapshot dependencies. We have way fewer external snapshot dependencies than I actually believed, so this might not be too bad, even if we need to release some of these from external. It helps a little that we're already using released versions of OpenJPA and jetty8. Here's a breakdown by category: non-Geronimo controlled releases: Tomcat 7 (which we currently have an external release for because we have some patches that have not be accepted by the Tomcat community), openejb, pax logging, xbean, myfaces, and felix. It should be easy to push out an xbean release, openejb just had a release, and might be reluctant to push a new one so soon after the last one. I'm not sure if the latest release can be used for Geronimo or not. I suspect not, since there has been a bit of recent work on getting openejb to run in 3.0. myfaces and pax logging I'm not sure about. Does anybody have connections to these communities strong enough to ask about a release? What is the current state of the felix and karaf projects? Would it be possible to get new releases in the next couple of weeks? Another big category is Aries, which is currently attempting to put out their first release. There's a good chance this will happen in time for the 3.0 milestone release. This is probably the biggest dependency, since a major goal of this milestone is to get feedback on the OSGi application features. And finally, we have one servicemix bundle dependency that's in snapshot state. Hopefully, we can get a release pushed for this. As a fallback, we could just add another subproject to geronimo-bundles to cover this. Geronimo specs: We need new releases of almost all of these to pick up the new OSGi support. We probably should put these up for a vote by early next week at the latest. Do we need to have a separate vote for each spec, or can we do a group vote on this? Also, the javamail uber jar will need a release vote. Geronimo components: We need releases for connector, transaction, and jaspic. In taking a look at these, I discovered that these jars a building using the java ee 5 versions of apis and providers (e.g., stax, jaxb). I suspect these really should be upgraded. Also, the dependencies tend to be non-bundle versions of a lot of the jars. I suspect these should really be using the bundle versions. Geronimo bundles: The framework has bundle versions of a number of common components. This is part of the Geronimo build tree, and thus these are not released separately. However, these bundle versions look like they should be getting used in other places (e.g., components, possibly xbean). This seems to argue that they should be moved out the geronimo tree to possibly components or maybe their own top-level tree as peers to components/external etc. Here is what I believe is the current list of snapshot dependencies. Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT Felix: main bundlerepository: 1.5.0-SNAPSHOT karaf main: 1.5.0-SNAPSHOT karaf console: 1.5.0-SNAPSHOT karaf client: 1.5.0-SNAPSHOT framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.jmx org.apache.aries.blueprint org.apache.aries.blueprint.api org.apache.aries.blueprint.core org.apache.aries.blueprint.cm All of the Geronimo specs have new versions, which can be released prior to creating the new release. To the best of my knowledge, all of these are in a state where they can be released. geronimo-osgi-registry geronimo-osgi-locator geronimo-activation_1.1_spec geronimo-annotation_1.1_spec geronimo-atinject_1.0_spec geronimo-cpp_1.0_spec geronimo-ejb_3.1_spec
[BUILD] branches/2.2: Failed for Revision: 930915
Geronimo Revision: 930915 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/build-1400.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/unit-test-reports
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 13 resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 9 source files to
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.tomcat.StatTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.507 sec
Running org.apache.geronimo.tomcat.TomcatServerGBeanTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.551 sec
Running org.apache.geronimo.tomcat.JACCSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.228 sec
Running org.apache.geronimo.tomcat.ContainerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.708 sec
Running org.apache.geronimo.tomcat.ApplicationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.154 sec
Running org.apache.geronimo.tomcat.BasicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.27 sec
Running org.apache.geronimo.tomcat.JAASSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.163 sec
Results :
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-tomcat6/2.2.1-SNAPSHOT/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Tomcat
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479
Re: SNAPSHOT dependencies in Geronimo 3.0
The geronimo-cpp_1.0_spec has never been near a tck. It's needed for pluto 2. I thought I'd requested the tck on jcp-open but don't seem to have. I guess we should? thanks david jencks On Apr 5, 2010, at 5:43 AM, Rick McGuire wrote: Ok, the completed email that I accidentally sent out earlier. Since we're targetting an M1 release of Geroinimo 3.0, we need to be taking a close look at the snapshot dependencies we have in the release. Here is what I believe is the complete list of current snapshot dependencies. We have way fewer external snapshot dependencies than I actually believed, so this might not be too bad, even if we need to release some of these from external. It helps a little that we're already using released versions of OpenJPA and jetty8. Here's a breakdown by category: non-Geronimo controlled releases: Tomcat 7 (which we currently have an external release for because we have some patches that have not be accepted by the Tomcat community), openejb, pax logging, xbean, myfaces, and felix. It should be easy to push out an xbean release, openejb just had a release, and might be reluctant to push a new one so soon after the last one. I'm not sure if the latest release can be used for Geronimo or not. I suspect not, since there has been a bit of recent work on getting openejb to run in 3.0. myfaces and pax logging I'm not sure about. Does anybody have connections to these communities strong enough to ask about a release? What is the current state of the felix and karaf projects? Would it be possible to get new releases in the next couple of weeks? Another big category is Aries, which is currently attempting to put out their first release. There's a good chance this will happen in time for the 3.0 milestone release. This is probably the biggest dependency, since a major goal of this milestone is to get feedback on the OSGi application features. And finally, we have one servicemix bundle dependency that's in snapshot state. Hopefully, we can get a release pushed for this. As a fallback, we could just add another subproject to geronimo-bundles to cover this. Geronimo specs: We need new releases of almost all of these to pick up the new OSGi support. We probably should put these up for a vote by early next week at the latest. Do we need to have a separate vote for each spec, or can we do a group vote on this? Also, the javamail uber jar will need a release vote. Geronimo components: We need releases for connector, transaction, and jaspic. In taking a look at these, I discovered that these jars a building using the java ee 5 versions of apis and providers (e.g., stax, jaxb). I suspect these really should be upgraded. Also, the dependencies tend to be non-bundle versions of a lot of the jars. I suspect these should really be using the bundle versions. Geronimo bundles: The framework has bundle versions of a number of common components. This is part of the Geronimo build tree, and thus these are not released separately. However, these bundle versions look like they should be getting used in other places (e.g., components, possibly xbean). This seems to argue that they should be moved out the geronimo tree to possibly components or maybe their own top-level tree as peers to components/external etc. Here is what I believe is the current list of snapshot dependencies. Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT Felix: main bundlerepository: 1.5.0-SNAPSHOT karaf main: 1.5.0-SNAPSHOT karaf console: 1.5.0-SNAPSHOT karaf client: 1.5.0-SNAPSHOT framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.jmx org.apache.aries.blueprint org.apache.aries.blueprint.api org.apache.aries.blueprint.core org.apache.aries.blueprint.cm All of the Geronimo specs have new versions, which can be released prior to creating the new release. To the best of my knowledge, all of these are in a state where they can be released. geronimo-osgi-registry geronimo-osgi-locator geronimo-activation_1.1_spec geronimo-annotation_1.1_spec geronimo-atinject_1.0_spec geronimo-cpp_1.0_spec geronimo-ejb_3.1_spec geronimo-interceptor_1.1_spec geronimo-jaxb_2.0_spec
Re: components dependencies
On Apr 5, 2010, at 6:06 AM, Rick McGuire wrote: This is sort of related to the earlier email I sent out about the snapshot dependencies. In looking at the dependencies of the subprojects in the geronimo components tree, I find what appear to be a few problems we should probably correct: geronimo-schema-javaee_6: This is ok as it stands, but should we move the latest verions of the java 1.4 and java 5 schemas into the components tree rather than leaving them in the restricted TCK tree? geronimo-jaspi: This is building with the 2.1 version of the jaxb specs and the older release of the stax api spec. It also has dependencies on non-bundle versions of sxc-jaxb, woodstox, and the jaxb-impl. The jaxb-impl is also at the 2.1.7 level rather than the 2.2 level used by the server. This is a fairly simple update, but would have dependencies on geronimo bundles components, which really suggests those should be moved out of the server tree as separately buildable components. I suspect it would make the bootstrapping process easier if they could be handled that way. On the downside, this creates another level of release artifacts that require voting and a release process. geronimo-jaspi-openid: Building with the older version of the jaspic spec jar and servlet 2.5 spec. Should this be using the java ee 6 api versions? This is also using the 1.0-SNAPSHOT version of the geronimo-jaspic build, rather than the current 1.1-SNAPSHOT version. I'm not sure we want to push the jaspi support into java 6 and the latest apis as it might inhibit people using it with java 5 projects. I don't feel too strongly about it though. david jencks geronimo-connector/geronimo-transaction: The connector 1.6 spec version is the 1.0-EA-SNAPSHOT. This should be updated to the latest spec snapshot. Thoughts on updating this? The issue of the use of the geronimo bundles probably needs to be resolved ASAP so we can get release votes out for those components in the very near future. Rick
Re: SNAPSHOT dependencies in Geronimo 3.0
On Apr 5, 2010, at 9:46 AM, Jarek Gawor wrote: Rick, There are a few more snapshot dependencies in trunk: org.apache.ws.scout, org.apache.juddi, I think I got these projects to osgi-enable their latest releases so they may be usable. I also don't think we need to build the geronimo jaxr and uddi support for the milestone. I'm sure we won't get the latest juddi to work in an ee server by may. org.apache.activemq, this may be tough to get to a release. Maybe we can use 5.3.1 more chance of that. org.apache.portals.pluto Portals is working on releasing this more or less now. I expect a vote this week. and also a few more Aries modules: org.apache.aries.web.*, org.apache.aries.application.*, org.apache.aries.jpa.* Jarek On Mon, Apr 5, 2010 at 8:43 AM, Rick McGuire rick...@gmail.com wrote: Ok, the completed email that I accidentally sent out earlier. Since we're targetting an M1 release of Geroinimo 3.0, we need to be taking a close look at the snapshot dependencies we have in the release. Here is what I believe is the complete list of current snapshot dependencies. We have way fewer external snapshot dependencies than I actually believed, so this might not be too bad, even if we need to release some of these from external. It helps a little that we're already using released versions of OpenJPA and jetty8. Here's a breakdown by category: non-Geronimo controlled releases: Tomcat 7 (which we currently have an external release for because we have some patches that have not be accepted by the Tomcat community), openejb, pax logging, xbean, myfaces, and felix. It should be easy to push out an xbean release, openejb just had a release, and might be reluctant to push a new one so soon after the last one. I'm not sure if the latest release can be used for Geronimo or not. I suspect not, since there has been a bit of recent work on getting openejb to run in 3.0. myfaces and pax logging I'm not sure about. Does anybody have connections to these communities strong enough to ask about a release? What is the current state of the felix and karaf projects? Would it be possible to get new releases in the next couple of weeks? Another big category is Aries, which is currently attempting to put out their first release. There's a good chance this will happen in time for the 3.0 milestone release. This is probably the biggest dependency, since a major goal of this milestone is to get feedback on the OSGi application features. And finally, we have one servicemix bundle dependency that's in snapshot state. Hopefully, we can get a release pushed for this. As a fallback, we could just add another subproject to geronimo-bundles to cover this. Geronimo specs: We need new releases of almost all of these to pick up the new OSGi support. We probably should put these up for a vote by early next week at the latest. Do we need to have a separate vote for each spec, or can we do a group vote on this? Also, the javamail uber jar will need a release vote. Geronimo components: We need releases for connector, transaction, and jaspic. In taking a look at these, I discovered that these jars a building using the java ee 5 versions of apis and providers (e.g., stax, jaxb). I suspect these really should be upgraded. Also, the dependencies tend to be non-bundle versions of a lot of the jars. I suspect these should really be using the bundle versions. Geronimo bundles: The framework has bundle versions of a number of common components. This is part of the Geronimo build tree, and thus these are not released separately. However, these bundle versions look like they should be getting used in other places (e.g., components, possibly xbean). This seems to argue that they should be moved out the geronimo tree to possibly components or maybe their own top-level tree as peers to components/external etc. Here is what I believe is the current list of snapshot dependencies. Tomcat: 7.0.0.0-SNAPSHOT. This is a version build in the geronimo external, so we release this largely concurrent with the server release. openejb: 3.1.3-SNAPSHOT: I believe we've had some patches and modifications above and beyond the most recent openejb release. xbean: 3.7-SNAPSHOT: The Geronimo community controls the release of this. transaction manager: 3.0-SNAPSHOT : Under the control of the Geronimo community. pax logging: 1.4.1-SNAPSHOT: I'm not sure what the release procedures are in the PAX community or how often they make new release available. myfaces: 2.0.0-SNAPSHOT Felix: main bundlerepository: 1.5.0-SNAPSHOT karaf main: 1.5.0-SNAPSHOT karaf console: 1.5.0-SNAPSHOT karaf client: 1.5.0-SNAPSHOT framework: 2.1.0-SNAPSHOT Aries: all at 0.1-incubating-SNAPSHOT level org.apache.aries.jndi.core org.apache.aries.jndi.url org.apache.aries.jmx org.apache.aries.blueprint
[BUILD] branches/2.2: Failed for Revision: 930983
Geronimo Revision: 930983 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/build-2000.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100405/unit-test-reports
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@6dc06dc0
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.tomcat.JACCSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.654 sec
Running org.apache.geronimo.tomcat.StatTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.263 sec
Running org.apache.geronimo.tomcat.JAASSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.373 sec
Running org.apache.geronimo.tomcat.ApplicationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.319 sec
Running org.apache.geronimo.tomcat.TomcatServerGBeanTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.327 sec
Running org.apache.geronimo.tomcat.BasicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.3 sec
Running org.apache.geronimo.tomcat.ContainerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.17 sec
Results :
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/tomcat/geronimo-tomcat6/target/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-tomcat6/2.2.1-SNAPSHOT/geronimo-tomcat6-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Tomcat
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@76fe76fe
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@6dc06dc0
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@6dc06dc0
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@76fe76fe
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@6dc06dc0
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@6dc06dc0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6/src/main/history/dependencies.added.xml
Removed dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/tomcat/tomcat6
OSGi requirements
Will Geronimo 3.0 support all the specifications in the OSGi Service Platform Enterprise Specification ?? Or only a subset ?? -- Thanks, Tim McConnell
[BUILD] trunk: Failed for Revision: 930992
Geronimo Revision: 930992 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100405/unit-test-reports [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-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.aries -DartifactId=org.apache.aries.util -Dversion=0.1-incubating-20100312.185411-2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT 2) org.apache.felix.karaf:org.apache.felix.karaf.client:jar:1.5.0-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.bundles:karaf-client:jar:1.5.0-SNAPSHOT_1-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots
Pluto jar problem in Geronimo 2.1
Hi All
In Geronimo 2.1.4, when I use Geronimo Database pool wizard in
ServicesDatabase Pools and provide Database Type as SQL Server, I found
Driver Connection Properties like this:
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port}
When I checked
G_Home\repository\org\apache\geronimo\plugins\sysdb-console-tomcat\2.1.4\sysdb-console-tomcat-2.1.4.car\META-INF\plan.xml.
It is defined for Sql server here like this:
gbean name=Database28
class=org.apache.geronimo.console.databasemanager.wizard.DatabaseDriverGBean
attribute name=nameSQL Server/attribute
attribute
name=URLPrototypejdbc:sqlserver://{Host}:{Port};DatabaseName={Database}/attribute
attribute
name=driverClassNamecom.microsoft.sqlserver.jdbc.SQLServerDriver/attribute
attribute name=defaultPort1433/attribute
attribute name=specificfalse/attribute
attribute name=RARNameorg.tranql/tranql-connector-ra//rar/attribute
/gbean
Full JDBC URL and other properties are missing in Driver Connection
Properties in this case. This seems to me Apache Pluto plugin problem.
Whenever the input parameter contains semicolon, there will be some issues
while handlering those parameters. I also tried with other Database types
which have semi colon in URLPrototype (for example all the DataDirect
database types) and got same result as SQL Server database type. It Seems
that Pluto would ignore those parameters after the semicolon. There is one
Jira also opened for this issue.
https://issues.apache.org/jira/browse/PLUTO-579
In G 2.1.4 , we are using Pluto Version 1.1.6-G643117. PLUTO-579 fix is not
included in this version of Pluto.
I have built Pluto with PLUTO-579, and use the jar file in G 2.1.4. I can
clearly see all the parameters and full JDBC URL in Driver Connection
Properties.
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port};DatabaseName={Database}
Host:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Database:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Port:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Do we have any plan to include PLUTO-579 in Geronimo 2.1.5?
Thanks and Regards,
Amit
[jira] Closed: (GERONIMO-5036) [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18
[ https://issues.apache.org/jira/browse/GERONIMO-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5036. -- Resolution: Fixed Closing it because geronimo 2.1.5 has upgraded openejb to 3.0.2 [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18 Key: GERONIMO-5036 URL: https://issues.apache.org/jira/browse/GERONIMO-5036 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: JVM-compatibility, OpenEJB Affects Versions: 2.1.4, 2.2 Environment: Windows XP Reporter: Johannes Weberhofer Assignee: Kevan Miller Priority: Critical Fix For: 2.1.5, 2.2.1 After Upgrading to Sun JDK 1.6.0 u18 the above mentioned warning occures. The bug is filed in OPENEJB-1131, a fix has been provided in the openejb3 svn for ClassLoaderUtil.java with revision number 98 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Pluto jar problem in Geronimo 2.1
Rex, you might want to take a look at this one.
It would be much better if the patch is included in G2.1.5 because it's
feature-related.
Jeff
On Mon, Apr 5, 2010 at 7:54 PM, Amit Puri puri.a...@gmail.com wrote:
Hi All
In Geronimo 2.1.4, when I use Geronimo Database pool wizard in
ServicesDatabase Pools and provide Database Type as SQL Server, I found
Driver Connection Properties like this:
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port}
When I checked
G_Home\repository\org\apache\geronimo\plugins\sysdb-console-tomcat\2.1.4\sysdb-console-tomcat-2.1.4.car\META-INF\plan.xml.
It is defined for Sql server here like this:
gbean name=Database28
class=org.apache.geronimo.console.databasemanager.wizard.DatabaseDriverGBean
attribute name=nameSQL Server/attribute
attribute
name=URLPrototypejdbc:sqlserver://{Host}:{Port};DatabaseName={Database}/attribute
attribute
name=driverClassNamecom.microsoft.sqlserver.jdbc.SQLServerDriver/attribute
attribute name=defaultPort1433/attribute
attribute name=specificfalse/attribute
attribute name=RARNameorg.tranql/tranql-connector-ra//rar/attribute
/gbean
Full JDBC URL and other properties are missing in Driver Connection
Properties in this case. This seems to me Apache Pluto plugin problem.
Whenever the input parameter contains semicolon, there will be some issues
while handlering those parameters. I also tried with other Database types
which have semi colon in URLPrototype (for example all the DataDirect
database types) and got same result as SQL Server database type. It Seems
that Pluto would ignore those parameters after the semicolon. There is one
Jira also opened for this issue.
https://issues.apache.org/jira/browse/PLUTO-579
In G 2.1.4 , we are using Pluto Version 1.1.6-G643117. PLUTO-579 fix is not
included in this version of Pluto.
I have built Pluto with PLUTO-579, and use the jar file in G 2.1.4. I can
clearly see all the parameters and full JDBC URL in Driver Connection
Properties.
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port};DatabaseName={Database}
Host:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Database:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Port:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Do we have any plan to include PLUTO-579 in Geronimo 2.1.5?
Thanks and Regards,
Amit
Re: Pluto jar problem in Geronimo 2.1
The patch in PLUTO-579 seems not be applied in pluto. I have checked this
with Ivan, and Ivan has pulled the workaround in Geronimo-4836 into G 2.1.5.
please verify.
-Rex
2010/4/6 chi runhua chirun...@gmail.com
Rex, you might want to take a look at this one.
It would be much better if the patch is included in G2.1.5 because it's
feature-related.
Jeff
On Mon, Apr 5, 2010 at 7:54 PM, Amit Puri puri.a...@gmail.com wrote:
Hi All
In Geronimo 2.1.4, when I use Geronimo Database pool wizard in
ServicesDatabase Pools and provide Database Type as SQL Server, I found
Driver Connection Properties like this:
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port}
When I checked
G_Home\repository\org\apache\geronimo\plugins\sysdb-console-tomcat\2.1.4\sysdb-console-tomcat-2.1.4.car\META-INF\plan.xml.
It is defined for Sql server here like this:
gbean name=Database28
class=org.apache.geronimo.console.databasemanager.wizard.DatabaseDriverGBean
attribute name=nameSQL Server/attribute
attribute
name=URLPrototypejdbc:sqlserver://{Host}:{Port};DatabaseName={Database}/attribute
attribute
name=driverClassNamecom.microsoft.sqlserver.jdbc.SQLServerDriver/attribute
attribute name=defaultPort1433/attribute
attribute name=specificfalse/attribute
attribute name=RARNameorg.tranql/tranql-connector-ra//rar/attribute
/gbean
Full JDBC URL and other properties are missing in Driver Connection
Properties in this case. This seems to me Apache Pluto plugin problem.
Whenever the input parameter contains semicolon, there will be some issues
while handlering those parameters. I also tried with other Database types
which have semi colon in URLPrototype (for example all the DataDirect
database types) and got same result as SQL Server database type. It Seems
that Pluto would ignore those parameters after the semicolon. There is one
Jira also opened for this issue.
https://issues.apache.org/jira/browse/PLUTO-579
In G 2.1.4 , we are using Pluto Version 1.1.6-G643117. PLUTO-579 fix is
not included in this version of Pluto.
I have built Pluto with PLUTO-579, and use the jar file in G 2.1.4. I can
clearly see all the parameters and full JDBC URL in Driver Connection
Properties.
Driver Connection Properties-
Typical JDBC URL:
jdbc:sqlserver://{Host}:{Port};DatabaseName={Database}
Host:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Database:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Port:
A property used to connect to SQL Server. May be optional (see JDBC
driver documentation).
Do we have any plan to include PLUTO-579 in Geronimo 2.1.5?
Thanks and Regards,
Amit
--
Lei Wang (Rex)
rwonly AT apache.org
About G3.0 Java EE 6 Samples
Hi All, We prepared some samples regarding Jave EE 6 new features, so far including these: 1. WebFragment Description: This sample demonstrate define new features of servlet 3.0 like web-fragment.xml and use jars with web-fragment.xml _ 2. JPASample Description: This sample demonstrate Criteria API in JPA 2.O. It includes CRUD operations for messages. Also provide rank query for messages. It's also a war-based EJB application,all EJB classes are under WEB-INF/classes directory of the web project. _ 3. MultipartFile Description: This file upload system demonstrate Part attribute in servlet 3.0. _ 4. Converter Description: This is a simple example demonstrate JSF2.0 with AJAX. _ 5. Calculator Description: This is a simple example demonstrate Singleton Session Bean of EJB3.1 _ 6. CustomerDB Description: This example demonstrate RESTful Service. _ 7. helloWorld Description: This example demonstrate annotations for servlets,filters and listeners in servlet 3.0. _ 8. JSPResource Description: This example demonstrate a servlet 3.0 feature.Resource under META-INF/resources of jar file can be used as they are in the root directory if the jar file is put inside application's WEB-INF/lib directory. _ 9. Cviewer Description: This example demonstrate a servlet 3.0 feature.We can programmatically register servlets,filters . _ 10. embeddedEJBTimer Description: This is a simple example demonstrate EJB3.1 feature:get a EJB Container from Embedded API. I would like to contribute them to G samples trunk. However, I have some rough idea about how to deal with them in samples trunk code base: 1. Do we need to name a Java EE 6 subproject under samples directory and put all of these into the subproject like this? . |-- LICENSE |-- NOTICE |-- buildutil |-- geronimo-samples-archetype |-- pom.xml |-- samples | |-- DataCDInfo | |-- all-samples | |-- app-per-port | |-- async-http | |-- bank | |-- calculator | |-- csa-activemq | |-- customer | |-- dbtester | |-- inventory | |-- jaxws-calculator | |-- jms-mdb | |-- jsp-examples | |-- ldap-sample-app | |-- myphonebook | |-- mytime | |-- pom.xml | |-- sample-datasource | |-- sendmail | |-- servlet-examples | |-- timereport *| `--JavaEE6 ||--Converter ||--...* `-- src `-- site Or just add them directly under samples? As you can see that some Java EE 6 samples are based on existing ones(such as calculator). I personally prefer the former, since it gives user a clear view about where to look for Java EE 6 samples. 2. Shall we turn all of these samples into OSGi bundles? or just make Java EE 6 ones as bundles and keep existing ones unchanged? Please let me know your thoughts. Best regards, Forrest
[jira] Updated: (GERONIMO-5159) Add pause when startup.bat fails on Windows
[ https://issues.apache.org/jira/browse/GERONIMO-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5159: -- Attachment: (was: GERONIMO-5159-refined.patch) Add pause when startup.bat fails on Windows Key: GERONIMO-5159 URL: https://issues.apache.org/jira/browse/GERONIMO-5159 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.4, 2.2 Environment: Windows Reporter: Jack Cai Assignee: Jack Cai Priority: Trivial Fix For: 2.1.5 Attachments: GERONIMO-5159-refined2.patch When starting Geronimo in a separate command prompt (with startup.bat or geronimo.bat start), the new command prompt will close immediately after an error occurs, leaving no chance for the user to take a look at the console output. An improvement could be made to pause the prompt when an exception occurs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5159) Add pause when startup.bat fails on Windows
[ https://issues.apache.org/jira/browse/GERONIMO-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5159: -- Attachment: GERONIMO-5159-refined2.patch Missing %% for windows environment viable tag, so repatch it again, and commit fix for 2.1 at revision 931016, 2.2 at revision 931017, trunk at revision 931018. Add pause when startup.bat fails on Windows Key: GERONIMO-5159 URL: https://issues.apache.org/jira/browse/GERONIMO-5159 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.4, 2.2 Environment: Windows Reporter: Jack Cai Assignee: Jack Cai Priority: Trivial Fix For: 2.1.5 Attachments: GERONIMO-5159-refined2.patch When starting Geronimo in a separate command prompt (with startup.bat or geronimo.bat start), the new command prompt will close immediately after an error occurs, leaving no chance for the user to take a look at the console output. An improvement could be made to pause the prompt when an exception occurs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5037) Support Servlet 3.0 annotation and fragment web file
[ https://issues.apache.org/jira/browse/GERONIMO-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12853752#action_12853752 ] Ivan commented on GERONIMO-5037: Commit first step changes to trunk at revision: 931020, including support for web-fragment.xml/annotation scanning, sorting and merging. Some features are still on going, like excluded jar files, ServletContainerInitializer, etc. Also, TCK may required to validate the codes logic ... Support Servlet 3.0 annotation and fragment web file Key: GERONIMO-5037 URL: https://issues.apache.org/jira/browse/GERONIMO-5037 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: web Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Support Servlet 3.0 annotation and fragment web file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 931024
Geronimo Revision: 931024 built with tests included
See the full build-0200.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100406/build-0200.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100406/unit-test-reports
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.1/plugins/console/console-filter/src/test/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.1/plugins/console/console-filter/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.1/plugins/console/console-filter/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.1/plugins/console/console-filter/target/console-filter-2.1.5-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: console-filter-2.1.5-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.1/plugins/console/console-filter/target/console-filter-2.1.5-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/console-filter/2.1.5-SNAPSHOT/console-filter-2.1.5-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Pluto
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/2.1/plugins/pluto/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/pluto/2.1.5-SNAPSHOT/pluto-2.1.5-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Plugins, Pluto :: Core
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 4 source files to
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/src/main/java/org/apache/geronimo/pluto/impl/PortalURLParserImpl.java:[28,21]
package javax.portlet does not exist
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/src/main/java/org/apache/geronimo/pluto/impl/PortalURLParserImpl.java:[29,21]
package javax.portlet does not exist
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/src/main/java/org/apache/geronimo/pluto/impl/PortalURLParserImpl.java:[186,57]
cannot find symbol
symbol : class WindowState
location: class org.apache.geronimo.pluto.impl.PortalURLParserImpl
/home/geronimo/geronimo/2.1/plugins/pluto/geronimo-pluto/src/main/java/org/apache/geronimo/pluto/impl/PortalURLParserImpl.java:[191,57]
cannot find symbol
symbol : class PortletMode
location: class org.apache.geronimo.pluto.impl.PortalURLParserImpl
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
