Re: [Discussion] Time to release an updated maven-eclipsepde-plugin?
Thanks, Donald & Kevan! BTW, could you help to review the RC for GEP 2.1.6 and 3.0M1? 2010/7/10 Donald Woods > +1 Sounds like needed updates. > > > -Donald > > > On 7/9/10 4:37 AM, Delos wrote: > > As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins > > to maven dependencies and add them into artifact dependency list. So > > without it, GEP can't be compiled successfully. The plugin is in version > > 1.0. But now, some new requirements come out that the plugin didn't take > > into account before. I'm afraid we have to update the plugin > > to accommodate new requirements. > > > > 1) Eclipse on Mac > > There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse > > 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only > > recognize carbon eclipse on Mac, so we have to fix it to make GEP build > > successfully on Mac. You may see details in > > > > 2)Optional bundles > > There are some optional required bundles in MANIFEST.MF for some > > extended functions, such as TPTP and Free Aires Tools. They're > > not mandatory for GEP and actually GEP don't need these bundles in build > > process. They're marked as "optional" because user may get these extra > > plugins by themselves for some advanced functions. So these optional > > bundles shouldn't block the build process of GEP. Unfortunately, current > > maven-eclipsepde-plugin does block GEP build process because of these > > optional bundles. > > > > Because of these new requirements, I suggest we release an updated > > maven-eclipsepde-plugin with version 1.1. Any objection? > > > > -- > > Best Regards, > > > > Delos > -- Best Regards, Delos
[BUILD] trunk: Failed for Revision: 962735
Geronimo Revision: 962735 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), 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.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] Commented: (GERONIMO-5444) Add slight delay during async startup of ActiveMQ
[ https://issues.apache.org/jira/browse/GERONIMO-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886893#action_12886893 ] Kevan Miller commented on GERONIMO-5444: I totally agree, in general. However, this is not normal processing. ActiveMQ broker start up is a synchronous operation. The start() call will block until the broker is fully started. So, in a default configuration, the broker will be completely started (and there is never any delay processing). To support Master-Slave/shared file system broker configurations, we have an asynchronous start mode. For a "slave" broker, the start() call may block forever (i.e. the broker may be a "slave" forever). So, we need an asynchronous method of starting the Broker service, without blocking the Geronimo server startup. So, we start a thread to perform broker start asynchronously. This code adds a "delay" to give the broker service enough time to start, but won't block forever. In Master-Slave configurations, you need to configure "clients" to use multiple brokers (i.e. they may not be connecting to a broker on the same Geronimo server). They should be configured to use multicast protocols or failover protocols (configured with multiple broker uri's or use new AMQ support for dynamic failover uri's). If they delay time expires, this almost certainly means our broker is a "slave" broker. JMS clients will then be connecting to the "master" running in a different geronimo server. > Add slight delay during async startup of ActiveMQ > - > > Key: GERONIMO-5444 > URL: https://issues.apache.org/jira/browse/GERONIMO-5444 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2.1 >Reporter: Kevan Miller > Fix For: 2.2.1, 3.0 > > > If ActiveMQ is being started asynchronously (e.g. for a master-slave shared > file system configuration), JMS clients may be started prior to the actual > start of the server. We should allow the doStart of the ActiveMQ service to > have a delay, giving time for the service to start, if this server ends up > being the Master. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Discussion] Time to release an updated maven-eclipsepde-plugin?
+1 Sounds like needed updates. -Donald On 7/9/10 4:37 AM, Delos wrote: > As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins > to maven dependencies and add them into artifact dependency list. So > without it, GEP can't be compiled successfully. The plugin is in version > 1.0. But now, some new requirements come out that the plugin didn't take > into account before. I'm afraid we have to update the plugin > to accommodate new requirements. > > 1) Eclipse on Mac > There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse > 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only > recognize carbon eclipse on Mac, so we have to fix it to make GEP build > successfully on Mac. You may see details in > > 2)Optional bundles > There are some optional required bundles in MANIFEST.MF for some > extended functions, such as TPTP and Free Aires Tools. They're > not mandatory for GEP and actually GEP don't need these bundles in build > process. They're marked as "optional" because user may get these extra > plugins by themselves for some advanced functions. So these optional > bundles shouldn't block the build process of GEP. Unfortunately, current > maven-eclipsepde-plugin does block GEP build process because of these > optional bundles. > > Because of these new requirements, I suggest we release an updated > maven-eclipsepde-plugin with version 1.1. Any objection? > > -- > Best Regards, > > Delos
[jira] Commented: (GERONIMO-5444) Add slight delay during async startup of ActiveMQ
[ https://issues.apache.org/jira/browse/GERONIMO-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886862#action_12886862 ] Mark Struberg commented on GERONIMO-5444: - is there any started() or ready() 'event' (callback, etc) which can listen to? I always feel really uncomfortable when I hear the word 'delays' ;) > Add slight delay during async startup of ActiveMQ > - > > Key: GERONIMO-5444 > URL: https://issues.apache.org/jira/browse/GERONIMO-5444 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2.1 >Reporter: Kevan Miller > Fix For: 2.2.1, 3.0 > > > If ActiveMQ is being started asynchronously (e.g. for a master-slave shared > file system configuration), JMS clients may be started prior to the actual > start of the server. We should allow the doStart of the ActiveMQ service to > have a delay, giving time for the service to start, if this server ends up > being the Master. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5444) Add slight delay during async startup of ActiveMQ
Add slight delay during async startup of ActiveMQ - Key: GERONIMO-5444 URL: https://issues.apache.org/jira/browse/GERONIMO-5444 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.2.1 Reporter: Kevan Miller Fix For: 2.2.1, 3.0 If ActiveMQ is being started asynchronously (e.g. for a master-slave shared file system configuration), JMS clients may be started prior to the actual start of the server. We should allow the doStart of the ActiveMQ service to have a delay, giving time for the service to start, if this server ends up being the Master. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 962639
Geronimo Revision: 962639 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), 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.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
Re: [Discussion] Time to release an updated maven-eclipsepde-plugin?
On Jul 9, 2010, at 4:37 AM, Delos wrote: > As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to > maven dependencies and add them into artifact dependency list. So without it, > GEP can't be compiled successfully. The plugin is in version 1.0. But now, > some new requirements come out that the plugin didn't take into account > before. I'm afraid we have to update the plugin to accommodate new > requirements. > > 1) Eclipse on Mac > There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6, > only cocoa is supported. But maven-eclipsepde-plugin can only recognize > carbon eclipse on Mac, so we have to fix it to make GEP build successfully on > Mac. You may see details in > > 2)Optional bundles > There are some optional required bundles in MANIFEST.MF for some extended > functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP > and actually GEP don't need these bundles in build process. They're marked as > "optional" because user may get these extra plugins by themselves for some > advanced functions. So these optional bundles shouldn't block the build > process of GEP. Unfortunately, current maven-eclipsepde-plugin does block GEP > build process because of these optional bundles. > > Because of these new requirements, I suggest we release an updated > maven-eclipsepde-plugin with version 1.1. Any objection? No objections from me. Sounds like a good plan. Thanks Delos! --kevan
Re: [VOTE] Geronimo Eclipse Plugin 2.1.6 RC1
+1 Helios support would be great to have... And the error log view fix is much needed. -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/VOTE-Geronimo-Eclipse-Plugin-2-1-6-RC1-tp951788p955028.html Sent from the Development mailing list archive at Nabble.com.
Re: meaning of property-name="local" in Farming
I'm having the same problem. Did you find a solution? Thanks in advance. -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/meaning-of-property-name-local-in-Farming-tp365612p954672.html Sent from the Development mailing list archive at Nabble.com.
[BUILD] trunk: Failed for Revision: 962513
Geronimo Revision: 962513 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 4 seconds
[INFO] Finished at: Fri Jul 09 09:44:36 EDT 2010
[INFO] Final Memory: 456M/983M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/logs-0900-tomcat/
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@120e76d}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.Connec
[jira] Updated: (GERONIMO-5439) Put the sample apps in the testsuite
[ https://issues.apache.org/jira/browse/GERONIMO-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guang Zhe Wang updated GERONIMO-5439: - Description: Put the sample apps in the testsuite to make test the samples automatically. (was: Put the sample apps in the testsuite to make test the samples automately.) > Put the sample apps in the testsuite > > > Key: GERONIMO-5439 > URL: https://issues.apache.org/jira/browse/GERONIMO-5439 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 3.0-M1 >Reporter: Guang Zhe Wang > Fix For: 3.0-M1 > > Original Estimate: 168h > Remaining Estimate: 168h > > Put the sample apps in the testsuite to make test the samples automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Future directions towards better osgi integration
For the item 3, especially for the classloader archetecture, I found that it is difficult to totally depend on the bundle classloader. Also, I am not sure scan all the jar files in the lib folder is reasonable, even we could build the import/export packages list, we might also have problems while reading resources from jar files in the lib folders via classloader (the same issue with service api in jdk). I am thinking to add a proxy classloader to separate the web application from the native bundle classloader. Aslo, we could hack the classloader in this proxy classloader to load those classes directly from the bundle hosts the library jars/ejb/ra, which means the import/export will not be used. In this way, maybe we could make those java ee applications live more happier in osgi world. 2010/7/8 David Jencks > > On Jul 6, 2010, at 4:13 PM, David Jencks wrote: > > > What we have now in trunk more or less works OK but does not really take > good advantage of many osgi standard features, instead often duplicating > some functionality with stuff ported from earlier geronimo versions. Here > are a few ideas on how we might be more osgi friendly. > > > > > > 1. use osgi jndi to back up our java: jndi namespace. Right now we're > constructing our own references that poke around in the geronimo kernel > gbean registry to find the target. This is very similar to what the osgi: > namespace does in the osgi service registry. I think we can bind jndi links > to the osgi jndi name and get into the service registry that way. We're > already binding connection factories in the service registry, we can do > admin objects and ejbs pretty easily too. I'm experimenting with this in > connector. > > > > 2. Use karaf features instead of our plugin dependency management. > Currently these are very similar, our addition is to unpack stuff from > bundles on installation if requested. We can do this independently of the > features functionality, and we can talk to karaf about whether this unpack > idea would be good there. > > > > 3. Build ee artifacts into eba's. Although it isn't really counter-spec > to through everything except app clients in an ear into one > bundle/classloader, it doesn't seem ideal. I think one bundle per module > (and possibly one additional bundle per @DataSource annotation) will be more > flexible. BTW we have a problem currently in getting the app and global > jndi contexts onto the app client. If we deploy each rar and datasource > into a separate bundle we can just start these on the app client too so the > jndi stuff will be avaliable. > > > > 4. Replace gbeans with some combination of blueprint, blueprint namespace > handlers, and whatever else is needed. The plugins that use plain gbeans > can be converted to blueprint pretty easily. Our use of gbeans to wrap EE > application components is less straightforward. We may be able to generate > fairly simple blueprint plans in a special namespace that will give access > to the appropriate bundles containing the container classes. This will take > some investigation. I wonder if processing the xml into a neutral data tree > like the openejb info tree would be a useful approach. > > > > I've worried that (4) will take months and break everything from when it > starts to when it's complete. However I am now starting to think that if we > do 1-3 first there's a small chance that (4) can be done plugin-by-plugin > without completely breaking the server. > > > > 5. Figure out how to support jsr-77 (ee management) without gbeans. One > of the basic functions of gbeans was to support jsr-77 directly. Without > them we'll have to figure out what mbeans to register and how to do it. > Since the jsr-77 mbean structure is often totally nuts, this will probably > simplify the working code a bit, but will add another layer of goo. On the > other hand we can presumably make it optional. > > Another point. currently we use our directed acyclic graph of plugins > to determine which gbeans are visible to references in a plugin. This > mechanism is just not going to be present in the future. We can think about > trying to use subsystems or something else, but for now we might be able to > just make all the gbean refeences global, which will simplify stuff a lot. > It may break systems that have multiple possible services satisfying a > reference, but we'll have to find a way to deal with that anyway. > > thanks > david jencks > > > > > > thanks > > david jencks > > > > -- Ivan
Re: [Discussion] Time to release an updated maven-eclipsepde-plugin?
Sorry, I missed the JIRA number in #1. You may find details about #1 in https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649 2010/7/9 Delos > As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to > maven dependencies and add them into artifact dependency list. So without > it, GEP can't be compiled successfully. The plugin is in version 1.0. But > now, some new requirements come out that the plugin didn't take into account > before. I'm afraid we have to update the plugin to accommodate new > requirements. > > 1) Eclipse on Mac > There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse > 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only > recognize carbon eclipse on Mac, so we have to fix it to make GEP build > successfully on Mac. You may see details in > > 2)Optional bundles > There are some optional required bundles in MANIFEST.MF for some extended > functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP > and actually GEP don't need these bundles in build process. They're marked > as "optional" because user may get these extra plugins by themselves for > some advanced functions. So these optional bundles shouldn't block the build > process of GEP. Unfortunately, current maven-eclipsepde-plugin does block > GEP build process because of these optional bundles. > > Because of these new requirements, I suggest we release an updated > maven-eclipsepde-plugin with version 1.1. Any objection? > > -- > Best Regards, > > Delos > -- Best Regards, Delos
[Discussion] Time to release an updated maven-eclipsepde-plugin?
As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list. So without it, GEP can't be compiled successfully. The plugin is in version 1.0. But now, some new requirements come out that the plugin didn't take into account before. I'm afraid we have to update the plugin to accommodate new requirements. 1) Eclipse on Mac There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only recognize carbon eclipse on Mac, so we have to fix it to make GEP build successfully on Mac. You may see details in 2)Optional bundles There are some optional required bundles in MANIFEST.MF for some extended functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP and actually GEP don't need these bundles in build process. They're marked as "optional" because user may get these extra plugins by themselves for some advanced functions. So these optional bundles shouldn't block the build process of GEP. Unfortunately, current maven-eclipsepde-plugin does block GEP build process because of these optional bundles. Because of these new requirements, I suggest we release an updated maven-eclipsepde-plugin with version 1.1. Any objection? -- Best Regards, Delos
[BUILD] trunk: Failed for Revision: 962428
Geronimo Revision: 962428 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 49 seconds
[INFO] Finished at: Fri Jul 09 03:40:15 EDT 2010
[INFO] Final Memory: 470M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100709/logs-0300-tomcat/
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@d92dbb}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host:
