[jira] Commented: (GERONIMO-4990) Add serialVersionUID to serializable spec classes from javadoc
[ https://issues.apache.org/jira/browse/GERONIMO-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848037#action_12848037 ] Delos Dai commented on GERONIMO-4990: - geronimo-jaxws_2.2_spec updated in rev 925968 javax.xml.ws.WebServicePermission Add serialVersionUID to serializable spec classes from javadoc -- Key: GERONIMO-4990 URL: https://issues.apache.org/jira/browse/GERONIMO-4990 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs Affects Versions: 3.0 Reporter: David Jencks Assignee: Delos Dai Fix For: 3.0 The javadoc for the spec jars seems to generally include serialVersionUID values for serializable classes. Not all of our spec jars have specified these according to the javadoc. We should review the javadoc for all the specs and add serialVersionUID where they are missing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5196) Add a own authenticator for Spnego login
Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- 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: 925985
Geronimo Revision: 925985 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/unit-test-reports
[INFO] Compiling 6 source files to
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.web.deployment.GenericToSpecificPlanConverterTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.561 sec
Running org.apache.geronimo.web25.deployment.security.SecurityConfigTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 sec
Running org.apache.geronimo.web25.deployment.security.SpecSecurityParsingTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec
Running org.apache.geronimo.web25.deployment.SchemaConversionTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.409 sec
Running org.apache.geronimo.web.deployment.WebAppDConfigTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.056 sec
Results :
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle:
org.apache.geronimo.modules.geronimo-web-2.5-builder
[INFO] OSGi bundle is resolved:
org.apache.geronimo.modules.geronimo-web-2.5-builder
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-web-2.5-builder/3.0-SNAPSHOT/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing
org/apache/geronimo/modules/geronimo-web-2.5-builder/3.0-SNAPSHOT/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, J2EE :: Deployer
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from ops4j.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [dependency:unpack {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/plugins/j2ee/j2ee-deployer/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration {execution: default-validate-configuration}]
[INFO] [car:prepare-plan {execution: default-prepare-plan}]
[INFO] Generated:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/work/plan.xml
[INFO] [car:verify-no-dependency-change {execution:
default-verify-no-dependency-change}]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
[jira] Created: (GERONIMO-5197) Generic Header based authentication support in geronimo
Generic Header based authentication support in geronimo --- Key: GERONIMO-5197 URL: https://issues.apache.org/jira/browse/GERONIMO-5197 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Geronimo should provide a generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4990) Add serialVersionUID to serializable spec classes from javadoc
[ https://issues.apache.org/jira/browse/GERONIMO-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848060#action_12848060 ] Delos Dai commented on GERONIMO-4990: - geronimo-jaxb_2.2_spec updated in rev 925998 javax.xml.bind.JAXBPermission Add serialVersionUID to serializable spec classes from javadoc -- Key: GERONIMO-4990 URL: https://issues.apache.org/jira/browse/GERONIMO-4990 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs Affects Versions: 3.0 Reporter: David Jencks Assignee: Delos Dai Fix For: 3.0 The javadoc for the spec jars seems to generally include serialVersionUID values for serializable classes. Not all of our spec jars have specified these according to the javadoc. We should review the javadoc for all the specs and add serialVersionUID where they are missing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Discussion: Possible fixes for GERONIMO-5180
I will apply the fix to this issue tomorrow to g 2.1 branch. On Thu, Mar 18, 2010 at 7:04 PM, Ashish Jain ashja...@gmail.com wrote: I tried fixing this up by making FileKeystoreInstance serializable however I hit another issue java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableE xception: org.apache.geronimo.kernel.basic.ProxyMethodInterceptor at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:172) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(RMIConnecti onImpl_Stub.java:400) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection. invoke(RMIConnector.java:984) This prompts me to even make ProxyMethodInterceptor serializable and all the inner classes too. So as to not make such major modification which I am sure will keep affecting one class after other. I wish we can use another approach which is similar to #1 but not same. We can add a method to KeystoreManager interface something like initializeKeystores and do a kernel invoke of this method instead of previous one where we were doing a getAttribute on a method which does not return anything The newly added method initializeKeystores will in turn calls up getKeystores. This will help us attain the goal of adding the newly created keystores through Java provided keytool as Gbean in geronimo. Thanks Ashish On Tue, Mar 16, 2010 at 6:18 PM, Ashish Jain ashja...@gmail.com wrote: Thanks Jack and Joe for your choices. I will go ahead and implement the option #1. On Mon, Mar 15, 2010 at 9:17 PM, Jack Cai greensi...@gmail.com wrote: Interesting... Since the problem is really that FileKeystoreInstance is not seriazable, I don't see why changing the getter return type would help if the received objects are still instances of FileKeystoreInstance. Anyway, I agree with Joe - Option 1 looks more elegant. -Jack On Mon, Mar 15, 2010 at 1:25 PM, Ashish Jain ashja...@gmail.com wrote: The serialization problem is popping up due to the return type associated with getKeystores(). But in the case of getKeystores1() there is no return variable. So it helps in overcoming this problem. On Mon, Mar 15, 2010 at 8:18 AM, Jack Cai greensi...@gmail.com wrote: I still don't quite understand Option 2. So what would be stored in this new attribute keystores1? If it still contains an instance of FileKeystoreInstance, then there is still a serialization problem. -Jack On Sat, Mar 13, 2010 at 5:20 PM, Ashish Jain ashja...@gmail.comwrote: Hi Joe, Thanks for your comments. The intent of using option #2 was to make use of getAttribute and also since modifying the KeystoreManager interface will not have any effect on any existing functionalities. However as you pointed out a get method w/o any return types may be misleading. Thanks Ashish On Fri, Mar 12, 2010 at 8:46 PM, Joe Bohn joe.b...@earthlink.netwrote: I don't know much about the details of the problem but it seems to me that you would either make the class serializable (option #1) or exclude it from serialization if it is not necessary. I don't see how this would impact any existing functions. So I guess I would vote for #1. I don't understand why you would want to have a get* method that doesn't return anything - but perhaps I'm missing the point of option #2. Joe Ashish Jain wrote: Hi ALL, I have opened up a JIRA GERONIMO-5180 on the unlockKeystore command failure if keystore is created with keytool.exe. I was trying to fix this issue which requires some changes in the class declaration or interface. Following code is being utilized to fix up the issue KeystoreInstance[] keystores=(KeystoreInstance[])kernel.getAttribute(abstractName,keystores); where abstractName is obtained through org.apache.geronimo.management.geronimo.KeystoreManager. However I hit the following exception: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableE xception: org.apache.geronimo.security.keystore.FileKeystoreInstance at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:172) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(RMIConnecti onImpl_Stub.java:400) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection. invoke(RMIConnector.java:984) There are 2 ways to fix this up. 1) Make the class org.apache.geronimo.security.keystore.FileKeystoreInstance serializable. 2) add a new variable in FileKeystoreManager and add a new method in KeystoreManager which does not return anything and just gives a call to getKeystores(). For example getKeystores1() as the new method in
[jira] Created: (GERONIMO-5198) MultiParentClassLoader caching not found resources
MultiParentClassLoader caching not found resources -- Key: GERONIMO-5198 URL: https://issues.apache.org/jira/browse/GERONIMO-5198 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.2 Environment: Linux 64 bit Reporter: Marco Laponder We have extended the default classpath with a directory by specifying in the deployment plan an org.apache.geronimo.system.sharedlib.SharedLib gbean. So we are able to read application specific files from this directory. It is possbile for out application the resource can not be found at a given time, but the resource exists at a later time because it has been added to the directory. However when geronimo doesn't find the resource its add its name to the 'resourcesNotFound' map in the MultiParentClassLoader.java:571 in the 2.2 branch. The result of this caching is that we cannot find the resource after it has been placed in the direcotry. Would it be possible to configure this behaviour, clear the not found cache or is there an other solution to this problem ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4535) Alternate Node Discovery for Plugin Based Farming
[ https://issues.apache.org/jira/browse/GERONIMO-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4535: - Assignee: Shawn Jiang Alternate Node Discovery for Plugin Based Farming - Key: GERONIMO-4535 URL: https://issues.apache.org/jira/browse/GERONIMO-4535 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.2 Reporter: Chance Yeoman Assignee: Shawn Jiang Priority: Trivial Provide an alternative node discovery mechanism for cases where multicast is not an option. Geographically separated nodes that are able to connect to the admin server by configured IP or DNS host name should be able to participate in a farm as if they were on the same LAN as the admin server. Refer to discussions on Pulling Geronimo Configuration: http://www.nabble.com/Re%3A-Pulling-Geronimo-Configuration-td21962048s134.html http://www.nabble.com/Pulling-Geronimo-Configuration-td21936891s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4535) Alternate Node Discovery for Plugin Based Farming
[ https://issues.apache.org/jira/browse/GERONIMO-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4535. --- Resolution: Fixed Fix Version/s: 2.2.1 Resolved this JIRA with a WADI based plugin farm implementation: A, Refactored geronimo-farm module to only include the commone classes that a plugin based farm needs as well as a multi-cast discovery implementation. B, added geronimo-clustering-wadi/src/main/java/org/apache/geronimo/clustering/wadi/BasicWADISessionManagerHolder.java so that one can start a WADISessionManager by defining a GBean in deployment plan directly. C, added 4 maven module: 1, geronimo-farm-wadi It's Jar module that includes implementions of major wadi based node discovery logic. 2, plugin-farm-wadi It's a config that defines the GBeans a plugin based farm controller needs. 3, plugin-farm-member-wadi It's a config that defines the GBeans a plugin based farm member needs. 4, geronimo-plugin-farm-node-wadi It's a customized assembly that includes the minimum set of plugins for plugin based farm member. Alternate Node Discovery for Plugin Based Farming - Key: GERONIMO-4535 URL: https://issues.apache.org/jira/browse/GERONIMO-4535 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.2 Reporter: Chance Yeoman Assignee: Shawn Jiang Priority: Trivial Fix For: 2.2.1 Provide an alternative node discovery mechanism for cases where multicast is not an option. Geographically separated nodes that are able to connect to the admin server by configured IP or DNS host name should be able to participate in a farm as if they were on the same LAN as the admin server. Refer to discussions on Pulling Geronimo Configuration: http://www.nabble.com/Re%3A-Pulling-Geronimo-Configuration-td21962048s134.html http://www.nabble.com/Pulling-Geronimo-Configuration-td21936891s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5105) Create JACC 1.4 spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMO-5105: --- Assignee: Delos Dai Create JACC 1.4 spec jar - Key: GERONIMO-5105 URL: https://issues.apache.org/jira/browse/GERONIMO-5105 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Delos Dai Fix For: 3.0 Create a new spec jar for the JACC 1.4 spec level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Pulling Geronimo Configuration
Added WADI based plugin farm to 22 branch with this JIRA. https://issues.apache.org/jira/browse/GERONIMO-4535 https://issues.apache.org/jira/browse/GERONIMO-4535 On Tue, Feb 17, 2009 at 4:04 AM, Chance Yeoman cyeo...@cait.org wrote: Hi Gianny, I'll take a shot at it. I am brand new to the WADI API, but at first glance it seems that it would be a very flexible approach. I'll look at the NetworkConnectorMonitor to get a better feel for how it should be used. Thanks, Chance - Original Message - From: Gianny Damour gianny.dam...@optusnet.com.au To: dev@geronimo.apache.org Sent: Thursday, February 12, 2009 4:02:51 AM GMT -06:00 US/Canada Central Subject: Re: Pulling Geronimo Configuration On 12/02/2009, at 9:46 AM, David Jencks wrote: I think it would be great to get node discovery based on WADI working. Unfortunately I was in too much of a hurry when I implemented the plugin based farming to look into how to do this. Where is your ejb client failover code? Hi David, The code is located in the project plugins/openejb/geronimo-openejb-clustering-wadi The interesting class is NetworkConnectorMonitor where the method registerListenerForMembershipUpdates provides to joining peers the list of OpenEJB deployments currently running along with the network connector URIs EJB clients can used to access the EJB server running these deployments. Reading the code once again, it actually uses the geronimo-clustering API to track joining/leaving SessionManagers. So, if a BasicWADISessionManager is installed on admin and farm nodes the same type of approach may be used. I can certainly work on swapping the current node discovery implementation with a WADI implementation. Chance, do you want to give it a shot? Thanks, Gianny thanks david jencks -- Shawn
[jira] Closed: (GERONIMO-5179) Create a new customized ActiveMQ 4.1.2 build for Geronimo 2.1.5
[ https://issues.apache.org/jira/browse/GERONIMO-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-5179. -- Resolution: Fixed Create a new customized ActiveMQ 4.1.2 build for Geronimo 2.1.5 --- Key: GERONIMO-5179 URL: https://issues.apache.org/jira/browse/GERONIMO-5179 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.5 Reporter: Ivan Assignee: Ivan Fix For: 2.1.5 1. Merge changes of AMQ-2346 to fix a occasional failed JMS TCK case. 2. Merge changes of AMQ-1779 to fix a dead lock issue, but it seems that it cause some new ejb TCK cases failed :-( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5194) Patch for geronimo-jcdi spec
[ https://issues.apache.org/jira/browse/GERONIMO-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire reassigned GERONIMO-5194: -- Assignee: Rick McGuire Patch for geronimo-jcdi spec Key: GERONIMO-5194 URL: https://issues.apache.org/jira/browse/GERONIMO-5194 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Assignee: Rick McGuire Fix For: 3.0 Attachments: jcdi.patch Update geronimo-jcdi for updating AnnotationLiteral code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5194) Patch for geronimo-jcdi spec
[ https://issues.apache.org/jira/browse/GERONIMO-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-5194. Resolution: Fixed Committed revision 926014. Thanks Gurkan! Patch for geronimo-jcdi spec Key: GERONIMO-5194 URL: https://issues.apache.org/jira/browse/GERONIMO-5194 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Assignee: Rick McGuire Fix For: 3.0 Attachments: jcdi.patch Update geronimo-jcdi for updating AnnotationLiteral code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5196) Add a own authenticator for Spnego login
[ https://issues.apache.org/jira/browse/GERONIMO-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848075#action_12848075 ] Ashish Jain commented on GERONIMO-5196: --- New code is available @ https://issues.apache.org/bugzilla/show_bug.cgi?id=48685 . Details on the attachment Updated version of the patch against Tomcat 6.0.26 . Using this code users can specify SPNEGO as the auth-method in web.xml. Add a own authenticator for Spnego login Key: GERONIMO-5196 URL: https://issues.apache.org/jira/browse/GERONIMO-5196 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 It should be possible to use a custom authenticator for Spnego login. This includes the ability to have a different authentication method for web.xml. This is an improvement over GERONIMO-5129. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 926041
Geronimo Revision: 926041 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324
[jira] Created: (GERONIMO-5199) GShell equivalent for server startup with secure option, command unlock keystore and command redeploy for farming
GShell equivalent for server startup with secure option, command unlock keystore and command redeploy for farming - Key: GERONIMO-5199 URL: https://issues.apache.org/jira/browse/GERONIMO-5199 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Gshell equivalents for server startup with secure option, command unlock keystore and command redeploy for farming are required. Refer GERONIMO-5027, GERONIMO-5148 and GERONIMO-5156. -- 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: 926061
Geronimo Revision: 926061 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/unit-test-reports
[INFO] Compiling 6 source files to
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.web.deployment.GenericToSpecificPlanConverterTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.576 sec
Running org.apache.geronimo.web25.deployment.security.SecurityConfigTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.104 sec
Running org.apache.geronimo.web25.deployment.security.SpecSecurityParsingTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.096 sec
Running org.apache.geronimo.web25.deployment.SchemaConversionTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.422 sec
Running org.apache.geronimo.web.deployment.WebAppDConfigTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.076 sec
Results :
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle:
org.apache.geronimo.modules.geronimo-web-2.5-builder
[INFO] OSGi bundle is resolved:
org.apache.geronimo.modules.geronimo-web-2.5-builder
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/j2ee/geronimo-web-2.5-builder/target/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-web-2.5-builder/3.0-SNAPSHOT/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing
org/apache/geronimo/modules/geronimo-web-2.5-builder/3.0-SNAPSHOT/geronimo-web-2.5-builder-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, J2EE :: Deployer
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from ops4j.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-web-2.5-builder:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [dependency:unpack {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/plugins/j2ee/j2ee-deployer/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration {execution: default-validate-configuration}]
[INFO] [car:prepare-plan {execution: default-prepare-plan}]
[INFO] Generated:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/work/plan.xml
[INFO] [car:verify-no-dependency-change {execution:
default-verify-no-dependency-change}]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/target/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/j2ee/j2ee-deployer/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
Re: Any idea why the 2.1.5 daily build binaries are not transfered correctly?
I did have to kill a few scp processes a few days ago so that might have caused it. But looks like the files are uploaded fine now. Jarek On Sun, Mar 21, 2010 at 10:10 PM, Rex Wang rwo...@gmail.com wrote: The G 2.1.5 daily builds are damaged when publish to http://people.apache.org/builds/geronimo/server/binaries/2.1 But from the log, it build successfully. geronimo-jetty6-javaee5-2.1.5-SNAPSHOT-bin.zip 21-Mar-2010 07:15 26M Automated test builds geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT-bin.zip 21-Mar-2010 06:39 12M Automated test builds -- Lei Wang (Rex) rwonly AT apache.org
Google Summer of Code
Hi all, The Google Summer of Code program is starting up. If you are interested please see http://community.apache.org/gsoc.html for more information on becoming a mentor and/or submitting a project idea. Does anyone have a cool project idea for GSoC? Jarek
[jira] Commented: (GERONIMO-5095) Create JAX-RS spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848246#action_12848246 ] Bryant Luk commented on GERONIMO-5095: -- I think the 1.0 api spec is mostly done now. I don't have access to the TCK but if someone can run that in Apache to report results / fix anything, that would be great. I'll start work on the 1.1 spec since that's mostly a few additions here and there. Create JAX-RS spec jar --- Key: GERONIMO-5095 URL: https://issues.apache.org/jira/browse/GERONIMO-5095 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 926209
Geronimo Revision: 926209 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324
[jira] Commented: (GERONIMO-5095) Create JAX-RS spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848283#action_12848283 ] Bryant Luk commented on GERONIMO-5095: -- JAX-RS 1.1 is at http://svn.apache.org/repos/asf/cxf/sandbox/geronimo-jaxrs_1.1_spec/ . If someone would kindly run the API check on that API JAR, that would be great too. Feel free to modify whatever you want. Create JAX-RS spec jar --- Key: GERONIMO-5095 URL: https://issues.apache.org/jira/browse/GERONIMO-5095 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, specs Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rex Wang Fix For: 3.0 -- 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: 926255
Geronimo Revision: 926255 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100322/unit-test-reports
[mkdir] Created dir:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15/META-INF
[copy] Copying 2 files to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15/META-INF
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15.rar
[mkdir] Created dir:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-notx/META-INF
[copy] Copying 2 files to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-notx/META-INF
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-notx.rar
[mkdir] Created dir:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-localtx/META-INF
[copy] Copying 2 files to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-localtx/META-INF
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-localtx.rar
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-ear.ear
[mkdir] Created dir:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-10-noger/META-INF
[copy] Copying 1 file to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-10-noger/META-INF
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-10-noger.rar
[mkdir] Created dir:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-noger/META-INF
[copy] Copying 1 file to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-noger/META-INF
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-rar-15-noger.rar
[jar] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-ear-noger.ear
[INFO] Executed tasks
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 23 source files to
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/test-classes
[WARNING]
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/src/test/java/org/apache/geronimo/connector/deployment/MockRARDeployable.java:[67,22]
[deprecation] getModuleDTDVersion() in
javax.enterprise.deploy.model.DeployableObject has been deprecated
[WARNING]
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/src/test/java/org/apache/geronimo/connector/deployment/RAR_1_0DConfigBeanTest.java:[113,43]
[deprecation] toURL() in java.io.File has been deprecated
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/geronimo-connector-builder-1_6/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.connector.deployment.RAR_1_5DConfigBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running org.apache.geronimo.connector.deployment.ConnectorModuleBuilderTest
Tests run: 12, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 4.218 sec
FAILURE!
Running org.apache.geronimo.connector.deployment.RAR_1_0DConfigBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.apache.geronimo.connector.deployment.MessageDestinationTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.096 sec
Running org.apache.geronimo.connector.deployment.PlanParsingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.164 sec
Running org.apache.geronimo.connector.deployment.annotation.AnnotationHelperTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.185 sec
Running org.apache.geronimo.connector.deployment.SchemaConversionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Results :
Tests in error:
testBuildEar(org.apache.geronimo.connector.deployment.ConnectorModuleBuilderTest)
testBuildUnpackedModule
[BUILD] branches/2.2: Failed for Revision: 926396
Geronimo Revision: 926396 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100322/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-transaction -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT 2) org.apache.geronimo.components:geronimo-transaction:jar:2.1.4-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-transaction:jar:2.2.1-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324
Re: Any idea why the 2.1.5 daily build binaries are not transfered correctly?
Yep, thanks so much, Jarek :-) 2010/3/22 Jarek Gawor jga...@gmail.com I did have to kill a few scp processes a few days ago so that might have caused it. But looks like the files are uploaded fine now. Jarek On Sun, Mar 21, 2010 at 10:10 PM, Rex Wang rwo...@gmail.com wrote: The G 2.1.5 daily builds are damaged when publish to http://people.apache.org/builds/geronimo/server/binaries/2.1 But from the log, it build successfully. geronimo-jetty6-javaee5-2.1.5-SNAPSHOT-bin.zip 21-Mar-2010 07:15 26M Automated test builds geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT-bin.zip 21-Mar-2010 06:39 12M Automated test builds -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[jira] Updated: (GERONIMO-5147) deploy.sh exits with non-zero status because of stty echo
[ https://issues.apache.org/jira/browse/GERONIMO-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-5147: --- Affects Version/s: 3.0 2.1.4 Fix Version/s: 3.0 2.2.1 2.1.5 deploy.sh exits with non-zero status because of stty echo - Key: GERONIMO-5147 URL: https://issues.apache.org/jira/browse/GERONIMO-5147 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1.4, 2.2, 3.0 Environment: Ubuntu 9.10, but probably not restricted to. Reporter: Kees van Veen Fix For: 2.1.5, 2.2.1, 3.0 Attachments: deploy.sh.patch The fix for issue https://issues.apache.org/jira/browse/GERONIMO-4589 has introduced 'stty echo' at the end of the $GERONIMO_HOME/bin/deploy.sh script. When this command is run with input/output redirected, the deploy.sh script exits with a non-zero status, as the stty echo then fails. As issue 4589 reports, the 'stty echo' only seems necessary when an exception occurred in the previous java command. Not clear is why only stty echo would be sufficient: it may repair the echo status of the terminal, but probably other settings may need to be reset as well, which would make 'stty sane' (or both) more appropriate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
{DISCUSS} Remove Spnego Support from Geronimo 2.1.5?
Will Tomcat community plan to apply our fixes to their code base soon? If not, because this Friday we will ship release candidate build of G 2.1.5, I prefer to remove Spnego support this time. The related JIRAs that need to revert are: GERONIMO - 5128 GERONIMO - 5129 Thoughts? -- Lei Wang (Rex) rwonly AT apache.org
Re: Will your project feature at ApacheCon North America 2010?
Apologies for the broadcast message... In thinking about ApacheCon 2010, I began to wonder if there is interest in creating an Enterprise Java track for the conference. I think there is the potential for a lot of interesting content. Many of our projects are busy implementing JSR specs for Java EE6. Also, the OSGi Alliance EEG has created several EE-focuse specifications with more on the way. I'm sure each of our projects have a number of internal developments which we're also interested in sharing. I'm guessing that some of our projects have already initiated their own track programs. Which I think is fine. I don't think it's a conflict to have technology specific tracks. However, if you're interested in joining forces, let me know. I think it would help foster greater interactions between our projects and also result in a very interesting conference track. To help to start aggregating potential presentations, I've created a Wiki page -- http://cwiki.apache.org/confluence/display/GMOxPMGT/ApacheCon+NA+2010+--+Enterprise+Java+Track At this point, we do not need to identify specific presentations. But we do need to insure that there is sufficient interest. If I've left out any projects who you think might be interested in participating, please feel free to pass this along... --kevan On Mar 15, 2010, at 7:22 PM, Nóirín Shirley for the ApacheCon 2010 Planning Team wrote: Dear PMC, ApacheCon 2010 North America is just around the corner, and it's time to roll out a program for this event! We'll be at the Westin Peachtree Plaza in Atlanta, GA, from 1st-5th November. Will you be there? If you'd like your project to be featured in the main conference tracks, please discuss it with your project community. A schedule is not needed at this time, but you have a coherent vision for a one day (6 sessions) program. We are particularly interested in programs that fit current themes, from Servers to Cloud Computing, from Search to NoSQL, as well as Innovation and Emerging Technologies. You'll also need to identify a track program organizer, who will be responsible for liaising with the planners, as well as collecting the session descriptions, speaker bios, and other programming information. Your track organizer should email planners-2010...@apachecon.com with your project's intent to participate, before Sunday, March 21st. Projects will be notified by the end of March as to whether their proposal has been accepted, and full programming should be completed by April 16th. Note that the planning committee will review the proposed tracks, and may offer feedback or specify necessary changes to ensure the success of the event. All accepted speakers (not co-presenters) qualify for general conference admission and a minimum of two nights lodging at the conference hotel. Additional hotel nights and travel assistance are possible, depending on the number of presentations given and type of assistance needed. If you think main track programming isn't for you, don't worry! You should expect to hear from us shortly about opportunities to present Training Sessions, as well as evening Meetups and other events. Looking forward to seeing you in Atlanta! Your ApacheCon 2010 NA Planning Team - To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org For additional commands, e-mail: private-h...@incubator.apache.org
Re: {DISCUSS} Remove Spnego Support from Geronimo 2.1.5?
On Mar 22, 2010, at 10:34 PM, Rex Wang wrote: Will Tomcat community plan to apply our fixes to their code base soon? If not, because this Friday we will ship release candidate build of G 2.1.5, I prefer to remove Spnego support this time. The related JIRAs that need to revert are: GERONIMO - 5128 GERONIMO - 5129 Thoughts? I think that's reasonable. I'd rather not start adding additional function that hasn't also been applied to Tomcat. So, unless the patch is accepted soon, I'd be in favor of reverting the updates. --kevan
[jira] Updated: (GERONIMO-5197) Generic Header based authentication support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5197: --- Fix Version/s: (was: 2.1.5) Wish List Move to wish list since we won't include this in the upcoming G 2.1.5 release. Generic Header based authentication support in geronimo --- Key: GERONIMO-5197 URL: https://issues.apache.org/jira/browse/GERONIMO-5197 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Tomcat Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.1, 3.0, Wish List Geronimo should provide a generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
