[jira] Created: (GERONIMO-4598) Versions missing in plugins: as a result many plugins cannot be added to framework server
Versions missing in plugins: as a result many plugins cannot be added to framework server - Key: GERONIMO-4598 URL: https://issues.apache.org/jira/browse/GERONIMO-4598 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Plugins Affects Versions: 2.1.4 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.4 Some plugins are missing versions in thieir geronimo-plugin.xml dependencies. As a result when you try to install these plugins into the framework server geronimo can't figure out which version to use and installation fails. Jetty and console-jetty are a couple obvious examples. Applying the patch does not AFAICT change the contents of the server nor the relationship between the plugins. It only makes sure all geronimo-plugin.xml dependencies have versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4598) Versions missing in plugins: as a result many plugins cannot be added to framework server
[ https://issues.apache.org/jira/browse/GERONIMO-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4598: --- Attachment: GERONIMO-4598.diff patch defaults the car-maven-plugin to use dependencies and changes all plugins that don't use maven dependencies to have explicit versions. It also sets the default plugin repository to the 2.1.4 repo that has already been set up, http://geronimo.apache.org/plugins/geronimo-2.1.4. Versions missing in plugins: as a result many plugins cannot be added to framework server - Key: GERONIMO-4598 URL: https://issues.apache.org/jira/browse/GERONIMO-4598 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.4 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.4 Attachments: GERONIMO-4598.diff Some plugins are missing versions in thieir geronimo-plugin.xml dependencies. As a result when you try to install these plugins into the framework server geronimo can't figure out which version to use and installation fails. Jetty and console-jetty are a couple obvious examples. Applying the patch does not AFAICT change the contents of the server nor the relationship between the plugins. It only makes sure all geronimo-plugin.xml dependencies have versions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Making plugins work better for 2.1.4
On Mar 20, 2009, at 12:38 PM, Joe Bohn wrote: Hi David, Do you have a patch that you can attach here (or better to a JIRA) so that others can see the proposed changes? It is very late. I'm basically just waiting for the openjpa release to make it to the ibiblio mirrors so that I can create the RC. If this is really minor and doesn't break anything then I supposed it could perhaps squeek in ... if it is ready to go later today or tomorrow. I opened https://issues.apache.org/jira/browse/GERONIMO-4598 and attached a patch. With the patch (after I've changed the default plugin repo back to my local maven repo) I can use gshell to install console-jetty onto the framework server, which was failing before. Since this AFAICT doesn't change the contents of the server nor how the plugins are wired together I think its safe to apply. We should probably also apply it to 2.1 equivalent work should have happened a long time ago for 2.2/trunk when I made the geronimo dependencies follow transitive maven dependencies. thanks david jencks Joe David Jencks wrote: I'm well aware this is last minute... Recently a user has discovered that installing plugins into the framework server pretty much doesn't work for 2.1.3. I think this is because we're generating some geronimo-plugin.xml without dependency versions. My preliminary investigation looks like we can easily change this with 4 changed lines in a couple poms. I'm trying to figure out what if anything obvious this breaks. IMO we should also point to the actual 2.1.4 plugin repo http://geronimo.apache.org/plugins/geronimo-2.1.4/ rather than the local maven repo as the default plugin repo. If these don't break anything obvious (e.g. testsuite) what else would we need to test to get this into 2.1.4? thanks david jencks
[jira] Resolved: (GERONIMO-4593) Upgrade to OpenJPA 1.2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4593. Resolution: Fixed Updated in branches/2.1.4 rev. 756943 Updated in branches/2.1 rev 756945 Updated in trunk in rev 756946 Upgrade to OpenJPA 1.2.1 Key: GERONIMO-4593 URL: https://issues.apache.org/jira/browse/GERONIMO-4593 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.1.4, 2.1.5, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 Upgrade to OpenJPA 1.2.1 when released -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4593) Upgrade to OpenJPA 1.2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4593: --- Affects Version/s: 2.2 2.1.5 Fix Version/s: 2.2 2.1.5 Upgrade to OpenJPA 1.2.1 Key: GERONIMO-4593 URL: https://issues.apache.org/jira/browse/GERONIMO-4593 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.1.4, 2.1.5, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 Upgrade to OpenJPA 1.2.1 when released -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Making plugins work better for 2.1.4
David, I applied the patch and checked out a few things. Everything looks good to me. In fact, these changes seem to have improved the overall plugin install process even from the console (at least it appeared to me that the plugins were installed much more quickly). Please go ahead and integrate these changes into branches/2.1.4 and branches/2.1. Thanks! Joe David Jencks wrote: On Mar 20, 2009, at 12:38 PM, Joe Bohn wrote: Hi David, Do you have a patch that you can attach here (or better to a JIRA) so that others can see the proposed changes? It is very late. I'm basically just waiting for the openjpa release to make it to the ibiblio mirrors so that I can create the RC. If this is really minor and doesn't break anything then I supposed it could perhaps squeek in ... if it is ready to go later today or tomorrow. I opened https://issues.apache.org/jira/browse/GERONIMO-4598 and attached a patch. With the patch (after I've changed the default plugin repo back to my local maven repo) I can use gshell to install console-jetty onto the framework server, which was failing before. Since this AFAICT doesn't change the contents of the server nor how the plugins are wired together I think its safe to apply. We should probably also apply it to 2.1 equivalent work should have happened a long time ago for 2.2/trunk when I made the geronimo dependencies follow transitive maven dependencies. thanks david jencks Joe David Jencks wrote: I'm well aware this is last minute... Recently a user has discovered that installing plugins into the framework server pretty much doesn't work for 2.1.3. I think this is because we're generating some geronimo-plugin.xml without dependency versions. My preliminary investigation looks like we can easily change this with 4 changed lines in a couple poms. I'm trying to figure out what if anything obvious this breaks. IMO we should also point to the actual 2.1.4 plugin repo http://geronimo.apache.org/plugins/geronimo-2.1.4/ rather than the local maven repo as the default plugin repo. If these don't break anything obvious (e.g. testsuite) what else would we need to test to get this into 2.1.4? thanks david jencks
[jira] Closed: (GERONIMO-4598) Versions missing in plugins: as a result many plugins cannot be added to framework server
[ https://issues.apache.org/jira/browse/GERONIMO-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4598. -- Resolution: Fixed Fix Version/s: 2.1.5 2.1.4 rev 756973 2.1 rev 756974 Versions missing in plugins: as a result many plugins cannot be added to framework server - Key: GERONIMO-4598 URL: https://issues.apache.org/jira/browse/GERONIMO-4598 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.4 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.4, 2.1.5 Attachments: GERONIMO-4598.diff Some plugins are missing versions in thieir geronimo-plugin.xml dependencies. As a result when you try to install these plugins into the framework server geronimo can't figure out which version to use and installation fails. Jetty and console-jetty are a couple obvious examples. Applying the patch does not AFAICT change the contents of the server nor the relationship between the plugins. It only makes sure all geronimo-plugin.xml dependencies have versions. -- 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: 757108
Geronimo Revision: 757108 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090321/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090321
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes 33 seconds
[INFO] Finished at: Sat Mar 21 21:40:28 EDT 2009
[INFO] Final Memory: 639M/1002M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090321/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.955
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.115)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.249)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.145)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.921)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:27.172)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:20.357)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:44.920)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:49.940)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:51.128)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.739)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.346)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.299)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.324)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.453)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.937)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.283)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.872)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.971)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.466) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:31.205)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test
