Re: When i start greonimo1.1 server , i see some warning messages like setErrorHandler
Ahmed,
I can reproduce your problem in the j2ee-tomcat assembly. It appears
that a recent change (20 May) to the config.xml file in revision 407883
has introduced the problem.
To work around the issue place an XML comment out the following in the
var\config.xml file (near line 73):
The message about the error handler is a warning from Xerces that it
encountered a validation (in the config.xml file) error but Geronimo
didn't have an error handler registered. That is another issue we need
to look into, as it wasn't clear in the message from Xerces what file
had the error. Once you apply the workaround above, this warning
shouldn't appear.
Regards,
John
ahmed wrote:
Hi Everybody ,
I have downloaded Geronimo1.1 source recently and was
able to build successfully .
But when i start the server i get below warning message
saying , setErrorHandler( ) , i have pasted the warning messages also.
Can somebody help me , what is wrong ,
Thanks in advance !!!
Booting Geronimo Kernel (in Java 1.4.2_09)...
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not
set, which is probably not what is desired. Parser will use a default
ErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.
Error: URI=null Line=65: cvc-complex-type.2.4.b: The content of
element 'referen
ce' is not complete. One of '{"
http://geronimo.apache.org/xml/ns/attributes-1.1";
:pattern}' is expected.
Starting Geronimo Application Server v1.1-SNAPSHOT
[] 100% 35s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
1527 0.0.0.0 Derby Connector
4242 0.0.0.0 Remote Login Listener
8009 0.0.0.0 Tomcat Connector AJP
8080 0.0.0.0 Tomcat Connector HTTP
8443 0.0.0.0 Tomcat Connector HTTPS
0.0.0.0 JMX Remoting Connector
61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules:
EAR: geronimo/webconsole-tomcat/1.1-SNAPSHOT/car
RAR: geronimo/activemq/1.1-SNAPSHOT/car
RAR: geronimo/system-database/1.1-SNAPSHOT/car
WAR: geronimo/remote-deploy-tomcat/1.1-SNAPSHOT/car
WAR: geronimo/welcome-tomcat/1.1-SNAPSHOT/car
Web Applications:
http://vidyarao:8080/
http://vidyarao:8080/console
http://vidyarao:8080/console-standard
http://vidyarao:8080/remote-deploy
Geronimo Application Server started
With Thanks and Regards,
When i start greonimo1.1 server , i see some warning messages like setErrorHandler
Hi Everybody ,
I have downloaded Geronimo1.1 source recently and was able to build successfully .
But when i start the server i get below warning message saying , setErrorHandler( ) , i have pasted the warning messages also.
Can somebody help me , what is wrong ,
Thanks in advance !!!
Booting Geronimo Kernel (in Java 1.4.2_09)...Warning: validation was turned on but an org.xml.sax.ErrorHandler was notset, which is probably not what is desired. Parser will use a defaultErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.Error: URI=null Line=65: cvc-complex-type.2.4.b: The content of element 'reference' is not complete. One of '{"
http://geronimo.apache.org/xml/ns/attributes-1.1":pattern}' is expected.Starting Geronimo Application Server v1.1-SNAPSHOT[] 100% 35s Startup complete Listening on Ports:
1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4242 0.0.0.0 Remote Login Listener 8009
0.0.0.0 Tomcat Connector AJP 8080 0.0.0.0 Tomcat Connector HTTP 8443 0.0.0.0 Tomcat Connector HTTPS 0.0.0.0
JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules: EAR: geronimo/webconsole-tomcat/1.1-SNAPSHOT/car RAR: geronimo/activemq/1.1-SNAPSHOT/car RAR: geronimo/system-database/1.1-SNAPSHOT/car WAR: geronimo/remote-deploy-tomcat/1.1-SNAPSHOT/car
WAR: geronimo/welcome-tomcat/1.1-SNAPSHOT/car
Web Applications: http://vidyarao:8080/ http://vidyarao:8080/console
http://vidyarao:8080/console-standard http://vidyarao:8080/remote-deploy
Geronimo Application Server started
With Thanks and Regards,
Re: Re-migration to m2 - status and discussion.
On 5/29/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote: Please ignore this patch. The earlier patch should work. The problem is the parent pom.xml. It creates conflicts. It will be easier if this was deleted and the new pom.xml was added. The problem mentioned below was caused by wrong geronimoVersion! I am running a full build, i.e moduels, m2-plugins, openejb and configs (non jetty and non client). Here are the results - Hi Anita, Excellent results! I'm really impressed by your pace and determination. I've been quite busy lately and couldn't help much, but seems things are getting straighten out and thus I'll soon be able to apply the patches (after they're approved). The results are so encouraging that I'm wondering whether there's anything left to be done wrt the migration. ;) Thanks! Keep'em comming. Anita Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Updated: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=all ] Anita Kulshreshtha updated GERONIMO-1740: - Attachment: openejb.patch m2-plugins.patch deploy-tool.patch > Plugin migration to Maven 2: geronimo-packaging-plugin > -- > > Key: GERONIMO-1740 > URL: http://issues.apache.org/jira/browse/GERONIMO-1740 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Components: buildsystem > Versions: 1.x > Reporter: Jacek Laskowski > Assignee: Anita Kulshreshtha > Attachments: configs.patch, configs.patch, configs.patch, deploy-tool.patch, > deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, > geronimo.patch, m2-plugins.patch, m2-plugins.patch, m2-plugins.patch, > m2-plugins.patch, m2-plugins.patch, modules.patch, modules.patch, > modules.patch, modules.patch, modules.patch, openejb.patch, pom.patch, > pom.patch, pom.patch, pom.xml > > It's a task to keep track of the progress of the plugin build migration to > Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=all ] Anita Kulshreshtha updated GERONIMO-1740: - Attachment: pom.patch modules.patch configs.patch Here is list of patches to build modules, m2-plugins. openejb and configs(non jetty and non client) G rev 409296, openejb rev 2659 1. pom.xml (from parent directory) 2. modules.patch 3. configs.patch 4. m2-plugins.patch 5. openejb.patch 6. deploy-tool.patch Please see above for the commands to use. > Plugin migration to Maven 2: geronimo-packaging-plugin > -- > > Key: GERONIMO-1740 > URL: http://issues.apache.org/jira/browse/GERONIMO-1740 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Components: buildsystem > Versions: 1.x > Reporter: Jacek Laskowski > Assignee: Anita Kulshreshtha > Attachments: configs.patch, configs.patch, configs.patch, deploy-tool.patch, > deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, > geronimo.patch, m2-plugins.patch, m2-plugins.patch, m2-plugins.patch, > m2-plugins.patch, m2-plugins.patch, modules.patch, modules.patch, > modules.patch, modules.patch, modules.patch, openejb.patch, pom.patch, > pom.patch, pom.patch, pom.xml > > It's a task to keep track of the progress of the plugin build migration to > Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Please try out the upgrade jar
Toby, Thanks for pointing this out. I've fixed it in 1.1, will port to trunk soon. See http://issues.apache.org/jira/browse/GERONIMO-2068 thanks david jencks On May 26, 2006, at 3:29 PM, toby cabot wrote: David, Thanks for providing this tool, it's a big help. I had some problems on a test geronimo-application.xml file that includes some gbean references (for hooking up to security gbeans). The file looks like: = http://geronimo.apache.org/xml/ns/j2ee/ application" configId="hello" parentId="geronimo/j2ee-security/1.0.1-SNAPSHOT/car"> class="org.apache.geronimo.security.realm.GenericSecurityRealm"> hello-realm hello-login-chain name>geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo name>geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e class="org.apache.geronimo.security.jaas.JaasLoginModuleUse"> REQUIRED hello-login class="org.apache.geronimo.security.jaas.LoginModuleGBean"> name="loginModuleClass">reva.common.auth.TrivialLoginModuleattribute> true usersURI=var/security/demo_users.properties groupsURI=var/security/demo_groups.properties hello-realm = The problem seems to be the application/gbean/reference/gbean-name elements, as the error I get at offline deploy time looks like: Deployer operation failed: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type. 2.4a: Expected elements '[EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ deployment-1.1' instead of '[EMAIL PROTECTED]://geronimo.apache.org/ xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1] Descriptor: http://geronimo.apache.org/xml/ ns/deployment-1.1"> default hello 1-default car geronimo j2ee-security 1.0.1-SNAPSHOT car class="org.apache.geronimo.security.realm.GenericSecurityRealm"> hello-realm hello-login-chain name>geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- system/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfoname> name>geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee- security/1.0.1-SNAPSHOT/ car,J2EEServer=geronimo,j2eeType=JaasLoginService,name=JaasLoginServic e class="org.apache.geronimo.security.jaas.JaasLoginModuleUse"> REQUIRED hello-login class="org.apache.geronimo.security.jaas.LoginModuleGBean"> name="loginModuleClass">reva.common.auth.TrivialLoginModuledep:attribute> true usersURI=var/security/ demo_users.properties groupsURI=var/security/demo_groups.propertiesdep:attribute> hello-realm org.apache.geronimo.common.DeploymentException: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: [error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.1' instead of 'gbean- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1' here in element [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/deployment-1.1, error: cvc-complex-type.2.4a: Expected elements '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deploymen
[jira] Commented: (GERONIMO-2068) Upgrade tool should deal with gbean-name element in gbean refs.
[ http://issues.apache.org/jira/browse/GERONIMO-2068?page=comments#action_12413733 ] David Jencks commented on GERONIMO-2068: Fixed in 1.1 in rev 410129. > Upgrade tool should deal with gbean-name element in gbean refs. > --- > > Key: GERONIMO-2068 > URL: http://issues.apache.org/jira/browse/GERONIMO-2068 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: deployment > Versions: 1.2, 1.1 > Reporter: David Jencks > Assignee: David Jencks > Fix For: 1.2, 1.1 > > Upgrade tool does nothing to stuff like: > class="org.apache.geronimo.security.realm.GenericSecurityRealm"> > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo > > > It should extract the name component and include some advice in a comment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2068) Upgrade tool should deal with gbean-name element in gbean refs.
Upgrade tool should deal with gbean-name element in gbean refs. --- Key: GERONIMO-2068 URL: http://issues.apache.org/jira/browse/GERONIMO-2068 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions: 1.2, 1.1 Reporter: David Jencks Assigned to: David Jencks Fix For: 1.2, 1.1 Upgrade tool does nothing to stuff like: geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo It should extract the name component and include some advice in a comment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Stable branch for ActiveMQ 4.0.x patch releases
Here's a handy svn command to reapply changes committed on one branch
to a another one:
svn merge -r 409741:409742
https://svn.apache.org/repos/asf/incubator/activemq/trunk/
I used the above command on in the 4.0 branch directory to apply the
revision 409742 change I had done to the trunk back on the 4.0 branch.
Regards,
Hiram
On 5/29/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
ok the branch has been created.
On 5/26/06, Bruce Snyder <[EMAIL PROTECTED]> wrote:
> On 5/26/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>
> > > If you don't think we should merge bug fixes from
> > > branches/activemq-4.0.x to the trunk, how do you propose we get bug
> > > fixes into the next major release?
> > >
> >
> > Bug fixes needs to be merged manually into trunk and all other
> > branches manually by the person committing the fix. So the net effect
> > is that we constantly merging in bug fixes to both the stable and
> > trunk branch at concurrently. We don't wait to 'roll up' all the bug
> > fixes on the stable branch so they are merged into trunk.
>
> +1 Sounds good to me.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://incubator.apache.org/activemq/
> Apache ServiceMix - http://incubator.apache.org/servicemix/
> Castor - http://castor.org/
>
--
Regards,
Hiram
--
Regards,
Hiram
Re: Stable branch for ActiveMQ 4.0.x patch releases
ok the branch has been created.
On 5/26/06, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 5/26/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> > If you don't think we should merge bug fixes from
> > branches/activemq-4.0.x to the trunk, how do you propose we get bug
> > fixes into the next major release?
> >
>
> Bug fixes needs to be merged manually into trunk and all other
> branches manually by the person committing the fix. So the net effect
> is that we constantly merging in bug fixes to both the stable and
> trunk branch at concurrently. We don't wait to 'roll up' all the bug
> fixes on the stable branch so they are merged into trunk.
+1 Sounds good to me.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://incubator.apache.org/activemq/
Apache ServiceMix - http://incubator.apache.org/servicemix/
Castor - http://castor.org/
--
Regards,
Hiram
Re: Re-migration to m2 - status and discussion.
Prasad, Please ignore this patch. The earlier patch should work. The problem is the parent pom.xml. It creates conflicts. It will be easier if this was deleted and the new pom.xml was added. The problem mentioned below was caused by wrong geronimoVersion! I am running a full build, i.e moduels, m2-plugins, openejb and configs (non jetty and non client). Here are the results - Thanks Anita er-1.2-SNAPSHOT.car [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Geronimo ... SUCCESS [2.516s] [INFO] Geronimo Modules ... SUCCESS [0.047s] [INFO] Geronimo :: Activation . SUCCESS [3.719s] [INFO] Geronimo :: Kernel . SUCCESS [2:07.969s] [INFO] Geronimo :: Common . SUCCESS [8.390s] [INFO] Geronimo :: Util ... SUCCESS [13.719s] [INFO] Geronimo :: System . SUCCESS [8.297s] [INFO] Geronimo :: Management API . SUCCESS [3.062s] [INFO] Geronimo :: J2EE ... SUCCESS [5.813s] [INFO] Geronimo :: Core ... SUCCESS [4.656s] [INFO] Geronimo :: Security ... SUCCESS [30.297s] [INFO] Geronimo :: Naming . SUCCESS [5.125s] [INFO] Geronimo :: Web Services ... SUCCESS [3.062s] [INFO] Geronimo :: Axis ... SUCCESS [7.547s] [INFO] Geronimo :: J2EE Schema SUCCESS [51.672s] [INFO] Geronimo :: Deployment . SUCCESS [6.969s] [INFO] Geronimo :: Deploy :: Common Config SUCCESS [1.453s] [INFO] Geronimo :: Service :: Builder . SUCCESS [14.828s] [INFO] Geronimo :: Security :: Builder SUCCESS [8.109s] [INFO] Geronimo :: J2EE :: Builder SUCCESS [21.453s] [INFO] Geronimo :: Naming :: Builder .. SUCCESS [12.954s] [INFO] Geronimo :: Axis :: Builder SUCCESS [20.843s] [INFO] Geronimo :: Transaction SUCCESS [31.938s] [INFO] Geronimo :: Client . SUCCESS [1.625s] [INFO] Geronimo :: Test :: DDBeans SUCCESS [5.532s] [INFO] Geronimo :: Connector .. SUCCESS [5.734s] [INFO] Geronimo :: Connector :: Builder ... SUCCESS [13.563s] [INFO] Geronimo :: Client Builder . SUCCESS [9.625s] [INFO] Geronimo :: Configuration Converter SUCCESS [2.343s] [INFO] Geronimo :: Web :: Builder . SUCCESS [10.672s] [INFO] Geronimo :: Deploy :: JSR-88 ... SUCCESS [7.203s] [INFO] Geronimo :: Deploy :: CLI Tool . SUCCESS [4.453s] [INFO] Geronimo :: Derby .. SUCCESS [2.266s] [INFO] Geronimo :: Directory .. SUCCESS [21.281s] [INFO] Geronimo :: Deploy :: Hot Deployer . SUCCESS [2.531s] [INFO] Geronimo :: Installer :: Processing SUCCESS [1.750s] [INFO] Geronimo :: JMX Remoting ... SUCCESS [3.500s] [INFO] Geronimo :: Mail ... SUCCESS [3.719s] [INFO] Geronimo :: Scripts SUCCESS [8.187s] [INFO] Geronimo :: Timer .. SUCCESS [1:16.297s] [INFO] Geronimo :: Tomcat . SUCCESS [49.328s] [INFO] Geronimo :: Tomcat :: Builder .. SUCCESS [30.079s] [INFO] Geronimo :: Upgrade SUCCESS [4.890s] [INFO] Geronimo Plugins ... SUCCESS [0.063s] [INFO] Geronimo :: Maven2 Packaging Plugin SUCCESS [10.968s] [INFO] OpenEJB SUCCESS [0.188s] [INFO] OpenEJB :: Core SUCCESS [44.312s] [INFO] OpenEJB :: PK Generation :: Builder SUCCESS [9.641s] [INFO] OpenEJB :: Builder . SUCCESS [37.937s] [INFO] Geronimo Configs ... SUCCESS [0.156s] [INFO] Geronimo Configuration for performing service deployments SUCCESS [5.016s] [INFO] System Configuration for the J2EE Server ... SUCCESS [20.109s] [INFO] RMI Naming configuration ... SUCCESS [1.547s] [INFO] Server Configuration for the J2EE Server ...
[jira] Updated: (GERONIMO-1740) Plugin migration to Maven 2: geronimo-packaging-plugin
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=all ] Anita Kulshreshtha updated GERONIMO-1740: - Attachment: m2-plugins.patch deploy-tool.patch The new patches are exactly same as above, but have been built for the trunk and have ^M removed. > Plugin migration to Maven 2: geronimo-packaging-plugin > -- > > Key: GERONIMO-1740 > URL: http://issues.apache.org/jira/browse/GERONIMO-1740 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Components: buildsystem > Versions: 1.x > Reporter: Jacek Laskowski > Assignee: Anita Kulshreshtha > Attachments: configs.patch, configs.patch, deploy-tool.patch, > deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, > m2-plugins.patch, m2-plugins.patch, m2-plugins.patch, m2-plugins.patch, > modules.patch, modules.patch, modules.patch, modules.patch, pom.patch, > pom.patch, pom.xml > > It's a task to keep track of the progress of the plugin build migration to > Maven2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2067) Configs migration to M2
[ http://issues.apache.org/jira/browse/GERONIMO-2067?page=all ] Anita Kulshreshtha updated GERONIMO-2067: - Attachment: newconfigs.patch > Configs migration to M2 > --- > > Key: GERONIMO-2067 > URL: http://issues.apache.org/jira/browse/GERONIMO-2067 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Components: buildsystem > Versions: 1.2 > Environment: All > Reporter: Anita Kulshreshtha > Assignee: Anita Kulshreshtha > Fix For: 1.2 > Attachments: newconfigs.patch > > To build these configurations use packaging plugin GERONIMO-1740. This patch > builds non openejb and non jetty configurations. > This patch is for the new trunk, and has been edited using emcas to rempve ^M. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2067) Configs migration to M2
Configs migration to M2 --- Key: GERONIMO-2067 URL: http://issues.apache.org/jira/browse/GERONIMO-2067 Project: Geronimo Type: Sub-task Security: public (Regular issues) Components: buildsystem Versions: 1.2 Environment: All Reporter: Anita Kulshreshtha Assigned to: Anita Kulshreshtha Fix For: 1.2 Attachments: newconfigs.patch To build these configurations use packaging plugin GERONIMO-1740. This patch builds non openejb and non jetty configurations. This patch is for the new trunk, and has been edited using emcas to rempve ^M. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2066) Openejb migration to M2
[ http://issues.apache.org/jira/browse/GERONIMO-2066?page=all ] Anita Kulshreshtha updated GERONIMO-2066: - Attachment: openejb.patch > Openejb migration to M2 > --- > > Key: GERONIMO-2066 > URL: http://issues.apache.org/jira/browse/GERONIMO-2066 > Project: Geronimo > Type: Sub-task > Security: public(Regular issues) > Environment: All > Reporter: Anita Kulshreshtha > Attachments: openejb.patch > > The attached patch provides a local openejb build for Geronimo using > o.a.g.modules groupId. > This is to ensure that the latest openejb jars are available. The results for > rev 2659 are below : > Path: . > URL: https://svn.codehaus.org/openejb/branches/v2_1/openejb2 > Repository UUID: 2b0c1533-c60b-0410-b8bd-89f67432e5c6 > Revision: 2659 > Node Kind: directory > Schedule: normal > Last Changed Author: gdamour > Last Changed Rev: 2659 > Last Changed Date: 2006-05-27 08:00:16 -0400 (Sat, 27 May 2006) > Properties Last Updated: 2006-05-26 19:05:28 -0400 (Fri, 26 May 2006) > Todo - fix the test failures. > > > APSHOT\openejb-builder-2.1-SNAPSHOT.jar > [INFO] > [INFO] > [INFO] > > [INFO] Reactor Summary: > [INFO] > > [INFO] OpenEJB SUCCESS > [3.953s] > [INFO] OpenEJB :: Core SUCCESS > [30.515s] > [INFO] OpenEJB :: PK Generation :: Builder SUCCESS > [9.297s] > [INFO] OpenEJB :: Builder . SUCCESS > [27.875s] > [INFO] > > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 1 minute 12 seconds > [INFO] Finished at: Mon May 29 08:11:40 EDT 2006 > [INFO] Final Memory: 17M/53M > [INFO] > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2066) Openejb migration to M2
Openejb migration to M2 --- Key: GERONIMO-2066 URL: http://issues.apache.org/jira/browse/GERONIMO-2066 Project: Geronimo Type: Sub-task Security: public (Regular issues) Environment: All Reporter: Anita Kulshreshtha The attached patch provides a local openejb build for Geronimo using o.a.g.modules groupId. This is to ensure that the latest openejb jars are available. The results for rev 2659 are below : Path: . URL: https://svn.codehaus.org/openejb/branches/v2_1/openejb2 Repository UUID: 2b0c1533-c60b-0410-b8bd-89f67432e5c6 Revision: 2659 Node Kind: directory Schedule: normal Last Changed Author: gdamour Last Changed Rev: 2659 Last Changed Date: 2006-05-27 08:00:16 -0400 (Sat, 27 May 2006) Properties Last Updated: 2006-05-26 19:05:28 -0400 (Fri, 26 May 2006) Todo - fix the test failures. APSHOT\openejb-builder-2.1-SNAPSHOT.jar [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] OpenEJB SUCCESS [3.953s] [INFO] OpenEJB :: Core SUCCESS [30.515s] [INFO] OpenEJB :: PK Generation :: Builder SUCCESS [9.297s] [INFO] OpenEJB :: Builder . SUCCESS [27.875s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 minute 12 seconds [INFO] Finished at: Mon May 29 08:11:40 EDT 2006 [INFO] Final Memory: 17M/53M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [continuum] BUILD ERROR: Geronimo
Hi, I think that Continuum needs some help here. Can someone who has access to stan try to sort it out? (I think that deleting modules/console-web should do the trick). Thanks, Gianny continuum wrote: Online report : http://ci.gbuild.org/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/3625 Build statistics: State: Error Previous State: Error Started at: Mon, 29 May 2006 02:01:02 -0700 Finished at: Mon, 29 May 2006 02:01:27 -0700 Total time: 24s Build Trigger: Schedule Exit code: 0 Building machine hostname: stan.gbuild.org Operating system : Linux(unknown) Java version : 1.4.2_08(Sun Microsystems Inc.) Changes No files changed Build Error: Provider message: The svn command failed. Command output: --- svn: Failed to add directory 'modules/console-web': object of the same name already exists ---
Unassigned Patches: week of 05-29-2006
Project: Apache Geronimo Status: Open Assignee: Unassigned Geronimo Info: Patch Available Total: 25 items DATE UPDATED KEY SUMMARY Dec 18 2005 - GERONIMO-1381 - [Daytrader] Removed unused code Dec 22 2005 - GERONIMO-1400 - modularize daytrader deployment plan Jan 3 2006 - GERONIMO-1413 - Console needs to set JSP and Servlet contentType to UTF-8 Jan 8 2006 - GERONIMO-1260 - simplify construction of the combined deployment plan: deployment plan template and preprocessor Jan 9 2006 - GERONIMO-1163 - improve jmx debug console Jan 14 2006 - GERONIMO-1453 - GBeanOverride throws NullPointerException when more than one reference element specified Jan 19 2006 - GERONIMO-1498 - DriverDownloader.DriverInfo causes java.io.NotSerializableException during server shutdown Jan 19 2006 - GERONIMO-1499 - Daytrader: uncomment the drop table statements in daytrader.sql Jan 19 2006 - GERONIMO-1501 - Daytrader: remove hardcoded dependency versions in project.xml Jan 23 2006 - GERONIMO-1534 - Daytrader: ejb-ql-compiler-factory element is wrong for DB2 or Oracle db Jan 27 2006 - GERONIMO-1341 - POP3 Implementation Feb 21 2006 - GERONIMO-1396 - Provide consistent look and feel for table views in the web console across all portlets Feb 23 2006 - GERONIMO-1648 - Eliminate unnecessary config parent (import) dependencies Feb 25 2006 - GERONIMO-1652 - EJBModuleImpl.getEJBs() always return an empty array Mar 6 2006 - GERONIMO-1700 - Web Console prints a stack trace when attempting to deploy an application that is already deployed. Mar 6 2006 - GERONIMO-1701 - Improve the EJB Server portlet Mar 7 2006 - GERONIMO-1657 - CommandSupport doesn't bubble up the exception. Prints stacktrace. Mar 16 2006 - GERONIMO-1130 - Implement WebServer Manager (statistics gathering/reporting) management interface Mar 21 2006 - GERONIMO-1757 - rarRelativePath is not set correctly cause showplan.jsp displayswrong instruction Mar 24 2006 - GERONIMO-1764 - Daytrader createDB.sh script does not support cygwin users on Windows. Apr 6 2006 - GERONIMO-1783 - Welcome application i18n Apr 10 2006 - GERONIMO-1804 - The name of JNDI/RMI service provider is hardcoded in the sources. Apr 11 2006 - GERONIMO-1826 - Naming tests might not work on non-Sun VMs. Apr 12 2006 - GERONIMO-1833 - Non-public Sun classes dependencies in tests Apr 13 2006 - GERONIMO-1840 - NamingPropertiesTest is not compatible with non-Sun VMs.
