[jira] Closed: (GERONIMODEVTOOLS-174) "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-174. -- Resolution: Cannot Reproduce Assignee: Delos Dai (was: Tim McConnell) Can't reproduce it in GEP 2.2. So close it > "Distribution of configuration failed" when attempting to deploy using > Geronimo 2.0 adapter > --- > > Key: GERONIMODEVTOOLS-174 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Tom Mutdosch >Assignee: Delos Dai > Fix For: 2.2.0 > > > Using the following Geronimo 2.0 runtime server and adapter: > (*) Server: > http://people.apache.org/dist/geronimo/eclipse/unstable/servers/geronimo-tomcat6-jee5-2.0-SNAPSHOT-bin.zip > > (*)Server plugins: > http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070621.1204-deployable.zip > > Using eclipse WTP, I create a simple Dynamic Web Project targeting Geronimo > with a single HTML file. When I do a Run on Server I get the following error > in an error dialog and my page does not run. > Error: > Distribution of configuration failed. See log for details. > Cannot deploy the requested application module because no deployer is able to > handle it. This can happen if you have omitted the J2EE deployment > descriptor, disabled a deployer module, or if, for example, you are trying to > deploy an EJB module on a minimal Geronimo server that does not have EJB > support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > org.apache.geronimo.common.DeploymentException: Cannot deploy the requested > application module because no deployer is able to handle it. This can happen > if you have omitted the J2EE deployment descriptor, disabled a deployer > module, or if, for example, you are trying to deploy an EJB module on a > minimal Geronimo server that does not have EJB support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:239) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) > at > org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) > at > org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) > at > com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) > at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423) > at > javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260) > at java.security.AccessController.doPrivileged(AccessController.java:275) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) > at > sun.re
[jira] Updated: (GERONIMO-4527) Geronimo 2.0.x branch does not build after updating OpenEJB to released version (3.0)
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh updated GERONIMO-4527: Description: Because of a number of changes that have occurred in dependencies of Geronimo it will no longer build. In particular, after changing the dependency on OpenEJB from 3.0-beta-1 to 3.0, the build stopped working. Due to changes in the group/artifact names of the artifacts for XBeans - OpenEJB 3.0 no longer builds. There is now a new snapshot version of OpenEJB (3.0.1-SNAPSHOT). These changes include the new snapshot version of OpenEJB rather than the unbuildable 3.0 version. was:Because of a number of changes that have occurred in dependencies of Geronimo it will no longer build. Summary: Geronimo 2.0.x branch does not build after updating OpenEJB to released version (3.0) (was: Geronimo 2.0.x branch does not build with tests) Sorry for any confusion. This issue sprung up as a result of removing the dependency to the beta version of OpenEJB locally. > Geronimo 2.0.x branch does not build after updating OpenEJB to released > version (3.0) > - > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Fix For: 2.0.3 > > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. > In particular, after changing the dependency on OpenEJB from 3.0-beta-1 to > 3.0, the build stopped working. > Due to changes in the group/artifact names of the artifacts for XBeans - > OpenEJB 3.0 no longer builds. There is now a new snapshot version of OpenEJB > (3.0.1-SNAPSHOT). These changes include the new snapshot version of OpenEJB > rather than the unbuildable 3.0 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670248#action_12670248 ] Jarek Gawor commented on GERONIMO-4527: --- I understand. It was just confusing as the name of the bug implies the branch does not build as it. But it only does not build if you locally updated to openejb 3.0. > Geronimo 2.0.x branch does not build with tests > --- > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Fix For: 2.0.3 > > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670246#action_12670246 ] Jay D. McHugh commented on GERONIMO-4527: - I have been trying to get 2.0 ready for release - including removing dependencies on beta versions. When I moved it to point it at OpenEJB 3.0 (rather than 3.0-beta-1), the build stopped working. If you switch away from the beta version, does the build still work for you? > Geronimo 2.0.x branch does not build with tests > --- > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Fix For: 2.0.3 > > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670244#action_12670244 ] Jarek Gawor commented on GERONIMO-4527: --- You mean it doesn't build if you update to OpenEJB 3.0.1-SNAPSHOT? The branches/2.0 builds fine without any changes... > Geronimo 2.0.x branch does not build with tests > --- > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Fix For: 2.0.3 > > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh resolved GERONIMO-4527. - Resolution: Fixed Fix Version/s: 2.0.3 Changes committed to branches/2.0 Sending modules/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java Sending modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java Sending modules/geronimo-openejb-builder/src/main/java/org/apache/geronimo/openejb/deployment/EjbRefBuilder.java Sendingpom.xml Transmitting file data Committed revision 740608. > Geronimo 2.0.x branch does not build with tests > --- > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Fix For: 2.0.3 > > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
[ https://issues.apache.org/jira/browse/GERONIMO-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh updated GERONIMO-4527: Attachment: geronimo-4527.diff Put all of the changes here so that there would be an easily reviewable set of changes if anyone cared to see what was changed to fix the build. > Geronimo 2.0.x branch does not build with tests > --- > > Key: GERONIMO-4527 > URL: https://issues.apache.org/jira/browse/GERONIMO-4527 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core, kernel, OpenEJB >Affects Versions: 2.0.3 >Reporter: Jay D. McHugh >Assignee: Jay D. McHugh > Attachments: geronimo-4527.diff > > > Because of a number of changes that have occurred in dependencies of Geronimo > it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4527) Geronimo 2.0.x branch does not build with tests
Geronimo 2.0.x branch does not build with tests --- Key: GERONIMO-4527 URL: https://issues.apache.org/jira/browse/GERONIMO-4527 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: core, kernel, OpenEJB Affects Versions: 2.0.3 Reporter: Jay D. McHugh Assignee: Jay D. McHugh Because of a number of changes that have occurred in dependencies of Geronimo it will no longer build. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-174) "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-174: --- Fix Version/s: (was: 2.1.3) 2.2.0 > "Distribution of configuration failed" when attempting to deploy using > Geronimo 2.0 adapter > --- > > Key: GERONIMODEVTOOLS-174 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Tom Mutdosch >Assignee: Tim McConnell > Fix For: 2.2.0 > > > Using the following Geronimo 2.0 runtime server and adapter: > (*) Server: > http://people.apache.org/dist/geronimo/eclipse/unstable/servers/geronimo-tomcat6-jee5-2.0-SNAPSHOT-bin.zip > > (*)Server plugins: > http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070621.1204-deployable.zip > > Using eclipse WTP, I create a simple Dynamic Web Project targeting Geronimo > with a single HTML file. When I do a Run on Server I get the following error > in an error dialog and my page does not run. > Error: > Distribution of configuration failed. See log for details. > Cannot deploy the requested application module because no deployer is able to > handle it. This can happen if you have omitted the J2EE deployment > descriptor, disabled a deployer module, or if, for example, you are trying to > deploy an EJB module on a minimal Geronimo server that does not have EJB > support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > org.apache.geronimo.common.DeploymentException: Cannot deploy the requested > application module because no deployer is able to handle it. This can happen > if you have omitted the J2EE deployment descriptor, disabled a deployer > module, or if, for example, you are trying to deploy an EJB module on a > minimal Geronimo server that does not have EJB support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:239) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) > at > org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) > at > org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) > at > com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) > at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423) > at > javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260) > at java.security.AccessController.doPrivileged(AccessController.java:275) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) &
[jira] Updated: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3450: --- Fix Version/s: (was: 2.0.x) 2.0.1 > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 2.0.1, 2.1 > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: FYI: Geronimo 2.0 Docs - Japanese Translation completed.
Excellent ... thank you! Joe 石田 剛 wrote: > Hello, Geronimo-devs. > > We, The Japan Apache Geronimo Users Group , are proud to announce that > we've completed all the Geronimo 2.0 documents translation. Now it's on > the Geronimo Wiki. > > http://cwiki.apache.org/GMOxDOC20ja/documentation.html > > Everything was done on a voluntary basis, so it took a little time. > We'd like to say big "thank-you !" to all the original doc authors. > Surely it was fun and interesting as the original docs were so good. > We're looking forward the 2.1 docs growing up ! > > contact: [EMAIL PROTECTED] > > Regards. > > > > GANBARE! NIPPON! Win your ticket to Olympic Games 2008. > <http://pr.mail.yahoo.co.jp/ganbare-nippon/>
Re: FYI: Geronimo 2.0 Docs - Japanese Translation completed.
Outstanding! Regards, Alan On May 28, 2008, at 8:43 AM, 石田 剛 wrote: Hello, Geronimo-devs. We, The Japan Apache Geronimo Users Group , are proud to announce that we've completed all the Geronimo 2.0 documents translation. Now it's on the Geronimo Wiki. http://cwiki.apache.org/GMOxDOC20ja/documentation.html Everything was done on a voluntary basis, so it took a little time. We'd like to say big "thank-you !" to all the original doc authors. Surely it was fun and interesting as the original docs were so good. We're looking forward the 2.1 docs growing up ! contact: [EMAIL PROTECTED] Regards. GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
FYI: Geronimo 2.0 Docs - Japanese Translation completed.
Hello, Geronimo-devs. We, The Japan Apache Geronimo Users Group , are proud to announce that we've completed all the Geronimo 2.0 documents translation. Now it's on the Geronimo Wiki. http://cwiki.apache.org/GMOxDOC20ja/documentation.html Everything was done on a voluntary basis, so it took a little time. We'd like to say big "thank-you !" to all the original doc authors. Surely it was fun and interesting as the original docs were so good. We're looking forward the 2.1 docs growing up ! contact: [EMAIL PROTECTED] Regards. - GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
Oracle 10g RAC / Geronimo 2.0
Hi, I need to access an Oracle Rac (cluster) from Geronimo. For that, I need to setup a datasource with a few additional properties to specify the hosts part of the cluster. However, I also need to setup an Oracle specific connection pool that manages the fail overs (the swithc between the rac servers). In the web console, the connection pools are limited to using the standard connection pool. Is there another way to specify the connection pool class and its properties? Thanks Xav -- View this message in context: http://www.nabble.com/Oracle-10g-RAC---Geronimo-2.0-tp16827659s134p16827659.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Geronimo 2.0: customize EJB-Container settings
Hi I opened a JIRA and attached an initial patch for a new portlet for displaying information regarding the different ejb containers and the ejbs deployed in them. The JIRA is http://issues.apache.org/jira/browse/GERONIMO-3811. Currently to after changing the properties like pool size etc the portlet prompts you to restart the server as openejb doesn't support dynamic changes of these settings. Suggestions welcome Thanks Manu On Thu, Jan 31, 2008 at 8:16 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Jan 31, 2008, at 7:36 AM, Manu George wrote: > > > Hi, > > > > What does the community think about having a portlet in the admin > > console for configuring openejb related stuff as well as displaying > > the different containers etc deployed in Geronimo. I think this may > > improve the usability of Geronimo. If there is interest I would like > > to investigate it further. > > Is that a trick question? ;-) Sounds like a great idea. I'd certainly > be interested in seeing console support. Doubt that I'd be able to > help out, though... > > --kevan > >
Re: Geronimo 2.0: customize EJB-Container settings
On Jan 31, 2008, at 7:36 AM, Manu George wrote: Hi, What does the community think about having a portlet in the admin console for configuring openejb related stuff as well as displaying the different containers etc deployed in Geronimo. I think this may improve the usability of Geronimo. If there is interest I would like to investigate it further. Is that a trick question? ;-) Sounds like a great idea. I'd certainly be interested in seeing console support. Doubt that I'd be able to help out, though... --kevan
Re: Geronimo 2.0: customize EJB-Container settings
;>
> >>>>> OpenEjbSystem
> >>>>>
> >>>>>
> >>>>> >>>>> class="org.apache.geronimo.openejb.EjbContainer">
> >>>>> Default CMP Container
> >>>>> CMP_ENTITY
> >>>>>
> >>>>> OpenEjbSystem
> >>>>>
> >>>>>
> >>>>>
> >>>>> To override the PoolSize attribute of DefaultStatefulContainer,
> >>>>> you
> >>>>> need to update the org.apache.geronimo.configs/openejb//car
> >>>>> confiiguration as follows in var/config/config.xm:
> >>>>>
> >>>>>
> >>>>>
> >>>>> ${OpenEJBPort + PortOffset} >>>>> attribute>
> >>>>> ${ServerHostname}
> >>>>>
> >>>>>
> >>>>>
> >>>>>PoolSize=100 >>>>> attribute>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Properties declared there are passed "as-is" to OpenEJB; hence,
> >>>>> you
> >>>>> can use the same property names defined by OpenEJB.
> >>>>>
> >>>>> Thanks,
> >>>>> Gianny
> >>>>>
> >>>>>
> >>>>> On 25/01/2008, at 6:19 AM, the666pack wrote:
> >>>>>
> >>>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> Can anybody tell me how i can customize the EJB-Container
> >>>>>> settings in
> >>>>>> Geronimo?
> >>>>>>
> >>>>>> I dont find an entry in the admin-console and i dont have an idea
> >>>>>> which
> >>>>>> files i can search for change.
> >>>>>>
> >>>>>> Basically i would like to set values like Bean-Pool Size or
> >>>>>> Maximum
> >>>>>> Cache
> >>>>>> Size as well as Timeout values.
> >>>>>>
> >>>>>> I hope someone can help,
> >>>>>>
> >>>>>> thank you,
> >>>>>>
> >>>>>> Mario
> >>>>>> --
> >>>>>> View this message in context: http://www.nabble.com/
> >>>>>> Geronimo-2.0%3A-
> >>>>>> customize-EJB-Container-settings-tp15072400s134p15072400.html
> >>>>>> Sent from the Apache Geronimo - Users mailing list archive at
> >>>>>> Nabble.com.
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> View this message in context: http://www.nabble.com/Geronimo-2.0%
> >>>> 3A-
> >>>> customize-EJB-Container-settings-tp15072400s134p15106943.html
> >>>> Sent from the Apache Geronimo - Users mailing list archive at
> >>>> Nabble.com.
> >>>>
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context: http://www.nabble.com/Geronimo-2.0%
> >> 3A-customize-EJB-Container-settings-tp15072400s134p15119677.html
> >> Sent from the Apache Geronimo - Users mailing list archive at
> >> Nabble.com.
> >>
> >
>
>
[jira] Closed: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh closed GERONIMO-3450. --- > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 2.0.x, 2.1 > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh resolved GERONIMO-3450. - Resolution: Invalid See Ramesh's comment. > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 2.0.x, 2.1 > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Geronimo 2.0 Stateless EJB Web Service
http://www.nabble.com/file/p14623694/jaxws-calculator-ejb.zip jaxws-calculator-ejb.zip When trying to deploy the ejb web services (see attached code) to geronimo 2.0, the following exception was thrown: ... at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(Configuratio nUtil.java:514) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationMan ager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleCon figurationManager.java:530) ... 45 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronim o.samples/jaxws-calculator/1.0-SNAPSHOT/car failed to start due to the following reasons: The service EJBModule=org.apache.geronimo.samples/jaxws-calculator/1.0-SNAPSHOT/car,J2EEApplicatio n=null,StatelessSessionBean=CalculatorBean,j2eeType=WSLink,name=CalculatorBean did not start for an unknown reason at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(Configuratio nUtil.java:477) ... 47 more Do you have any ideas? Do you have a working example for Stateless EJB Web Service? Please advise. Thanks, Derek -- View this message in context: http://www.nabble.com/Geronimo-2.0-Stateless-EJB-Web-Service-tp14623694s134p14623694.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Updated: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-3450: -- Fix Version/s: (was: 1.1.2) (was: 1.1.x) 2.1 2.0.x > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 2.0.x, 2.1 > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: A presentation on "Java EE 5.0 App Development on Geronimo 2.0 simplified using Eclipse + WTP 2.0"
I hope the presentation is also under AL 2.0 :o) Vamsi On 9/8/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > > On 9/7/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote: > > Just in case someone is interested in doing Java EE 5 app development > using > > Eclipse + WTP and looking for some instructions, here is some: > > > http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse > > Hey Shiva, > > That's awesome! I'm presenting the very same topic on the upcoming > Java Developers Day 2007 in Krakow and the presentation of yours is of > great help. Thanks! > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl >
Re: A presentation on "Java EE 5.0 App Development on Geronimo 2.0 simplified using Eclipse + WTP 2.0"
On 9/7/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote: > Just in case someone is interested in doing Java EE 5 app development using > Eclipse + WTP and looking for some instructions, here is some: > http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse Hey Shiva, That's awesome! I'm presenting the very same topic on the upcoming Java Developers Day 2007 in Krakow and the presentation of yours is of great help. Thanks! Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: A presentation on "Java EE 5.0 App Development on Geronimo 2.0 simplified using Eclipse + WTP 2.0"
Wow, that's really quick. Thanks Hernan! - Shiva On 9/7/07, Hernan Cunico <[EMAIL PROTECTED]> wrote: > > You wanted a new location, you got it ;-) > > There is a new section on the cwiki for presentations ( > http://cwiki.apache.org/geronimo) > > Shiva, here is the direct link to your material > > > http://cwiki.apache.org/geronimo/java-ee-50-app-development-on-geronimo-simplified-using-eclipse.html > > > I'll be trying to consolidate all the available presentations here. Folks, > if you are presenting at conferences it would be great you upload your > material here too so we'll have a sort of repository for all the > presentations and additional materials. > > Cheers! > Hernan > > Shiva Kumar H R wrote: > > Just in case someone is interested in doing Java EE 5 app development > > using Eclipse + WTP and looking for some instructions, here is some: > > > http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse > > > > Hernan, > > Request you to move this page to a more appropriate location. > > > > - Shiva >
Re: A presentation on "Java EE 5.0 App Development on Geronimo 2.0 simplified using Eclipse + WTP 2.0"
You wanted a new location, you got it ;-) There is a new section on the cwiki for presentations (http://cwiki.apache.org/geronimo) Shiva, here is the direct link to your material http://cwiki.apache.org/geronimo/java-ee-50-app-development-on-geronimo-simplified-using-eclipse.html I'll be trying to consolidate all the available presentations here. Folks, if you are presenting at conferences it would be great you upload your material here too so we'll have a sort of repository for all the presentations and additional materials. Cheers! Hernan Shiva Kumar H R wrote: Just in case someone is interested in doing Java EE 5 app development using Eclipse + WTP and looking for some instructions, here is some: http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse Hernan, Request you to move this page to a more appropriate location. - Shiva
A presentation on "Java EE 5.0 App Development on Geronimo 2.0 simplified using Eclipse + WTP 2.0"
Just in case someone is interested in doing Java EE 5 app development using Eclipse + WTP and looking for some instructions, here is some: http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse Hernan, Request you to move this page to a more appropriate location. - Shiva
[jira] Commented: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523995 ] Ramesh B commented on GERONIMO-3450: Hi Kevan, Many thanks for the help... i've been struggling with this for days. The reason why i had filtered org.apache.pluto was this comes by default with geronimo and i didn't want to use these jars. I had added these jars seperately in the web-inf/lib folder of the war. The pluto portal has successfully deployed after implementing your suggestion. thanks again for the help. Regards, Ramesh B. > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 1.1.2, 1.1.x > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-174) "Distribution of configuration failed" when attempting to deploy using Geronimo 2.0 adapter
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-174: --- Affects Version/s: (was: 2.0) 2.1.x Fix Version/s: 2.1.x Assignee: Tim McConnell > "Distribution of configuration failed" when attempting to deploy using > Geronimo 2.0 adapter > --- > > Key: GERONIMODEVTOOLS-174 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.x >Reporter: Tom Mutdosch >Assignee: Tim McConnell > Fix For: 2.1.x > > > Using the following Geronimo 2.0 runtime server and adapter: > (*) Server: > http://people.apache.org/dist/geronimo/eclipse/unstable/servers/geronimo-tomcat6-jee5-2.0-SNAPSHOT-bin.zip > > (*)Server plugins: > http://people.apache.org/dist/geronimo/eclipse/unstable/g-eclipse-plugin-2.0.0-v20070621.1204-deployable.zip > > Using eclipse WTP, I create a simple Dynamic Web Project targeting Geronimo > with a single HTML file. When I do a Run on Server I get the following error > in an error dialog and my page does not run. > Error: > Distribution of configuration failed. See log for details. > Cannot deploy the requested application module because no deployer is able to > handle it. This can happen if you have omitted the J2EE deployment > descriptor, disabled a deployer module, or if, for example, you are trying to > deploy an EJB module on a minimal Geronimo server that does not have EJB > support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > org.apache.geronimo.common.DeploymentException: Cannot deploy the requested > application module because no deployer is able to handle it. This can happen > if you have omitted the J2EE deployment descriptor, disabled a deployer > module, or if, for example, you are trying to deploy an EJB module on a > minimal Geronimo server that does not have EJB support installed. > (moduleFile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\geronimo-deployer1127.tmpdir\geronimoTestEAR.zip) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:239) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) > at > org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) > at > org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:863) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) > at > com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) > at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423) > at > javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260) > at java.security.AccessController.doPrivileged(AccessController.java:275) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) > at > sun.reflect
[jira] Commented: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523901 ] Kevan Miller commented on GERONIMO-3450: Ramesh I'm not sure I understand what you mean by 1). Where are your adding the jars? You're declaring pluto dependencies, but then you're filtering pluto from your parent ClassLoaders: org.apache.pluto org.springframework So, I'm a little confused... Anyway, to the heart of the matter... You need to filter spring resources as well as spring classes: org.apache.pluto org.springframework META-INF/spring > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 1.1.2, 1.1.x > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh B updated GERONIMO-3450: --- Attachment: geronimo.log The log of error generated > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 1.1.2, 1.1.x > > Attachments: geronimo-web.xml, geronimo.log > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh B updated GERONIMO-3450: --- Attachment: geronimo-web.xml The Geronimo-web.xml that i'm using for deployment. > Unable to Run Pluto 1.1 on Geronimo 2.0 > --- > > Key: GERONIMO-3450 > URL: https://issues.apache.org/jira/browse/GERONIMO-3450 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0-M2 > Environment: Operating System : Windows 2k3 > Pluto Version: 1.1.0 > Geronimo with Jetty Version 2.0.1 >Reporter: Ramesh B > Fix For: 1.1.2, 1.1.x > > Attachments: geronimo-web.xml > > > Hi, > I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on > geronimo with jetty 2.0.1. > For this I have done the following steps: > 1) I've added the following additional jars to common libs before deployment: > * pluto-container-1.1.0.jar > * pluto-descriptor-api-1.1.0.jar > * pluto-descriptor-impl-1.1.0.jar > * pluto-taglib-1.1.0.jar > * xalan 2.6.0 > 2) I've modified the castor.properties for pluto/web-inf/classes and set all > parameters to false. > 3) i've added a geronimo-web.xml to the /web-inf folder. > I created a war of the pluto folder. however while deploying it it gives the > following error: > 3582: 11:02:34,501 ERROR [log] Nested in > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from ServletContext resource > [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is > java.lang.IllegalArgumentException: Class > [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the > NamespaceHandler interface: > After throwing this error on the console it shows as successfully deployed > and successfully running. > However when i'm trying to access the pluto portal, it says service > unavailable. > Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0
Unable to Run Pluto 1.1 on Geronimo 2.0 --- Key: GERONIMO-3450 URL: https://issues.apache.org/jira/browse/GERONIMO-3450 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.0-M2 Environment: Operating System : Windows 2k3 Pluto Version: 1.1.0 Geronimo with Jetty Version 2.0.1 Reporter: Ramesh B Fix For: 1.1.2, 1.1.x Hi, I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on geronimo with jetty 2.0.1. For this I have done the following steps: 1) I've added the following additional jars to common libs before deployment: * pluto-container-1.1.0.jar * pluto-descriptor-api-1.1.0.jar * pluto-descriptor-impl-1.1.0.jar * pluto-taglib-1.1.0.jar * xalan 2.6.0 2) I've modified the castor.properties for pluto/web-inf/classes and set all parameters to false. 3) i've added a geronimo-web.xml to the /web-inf folder. I created a war of the pluto folder. however while deploying it it gives the following error: 3582: 11:02:34,501 ERROR [log] Nested in org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the NamespaceHandler interface: After throwing this error on the console it shows as successfully deployed and successfully running. However when i'm trying to access the pluto portal, it says service unavailable. Please help me with this problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Fwd: Re: building geronimo-2.0-rc1]
It does appear that File.toURL() produces a URL with spaces, while
File.toURI().toURL() correctly encodes the spaces with %20. Seems
very odd that File.toURL() doesn't do that internally, but eh...
--jason
On Aug 23, 2007, at 3:48 PM, Anita Kulshreshtha wrote:
I am seeing this error on trunk:
http://issues.apache.org/jira/browse/GERONIMO-3424
I had to change buildsupport-maven-plugin to NOP (edit
CopyXMLBeansSchemaMojo.groovy) to be able to build from C:\Documents
And Settings\...
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
Problem occurs when there is a space in the M2REPO directory, in this
case
"C:\Documents And Settings\...". Work around is to use an M2REPO dir
without any spaces in it. We will still have to investigate the
cause.
Vamsi
On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
The entire log is here
http://rifers.org/paste/show/5314
Cheers
Prasad
On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
I have begun to see this same error at another location now.
On windows, run mvn from server/testsuite directory and you will
get
this
[INFO] [selenium:start-server {execution: start-server}]
[INFO] Starting Selenium server...
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-
1.7.0.jar
[INFO]
--
--
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
http://rifers.org/paste/show/5312
Cheers
Prasad
On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
This should now be fixed in Rev565885.
Should this be pulled into 2.0.1?
-Donald
Prasad Kashyap wrote:
The changes that Donald Woods is doing (svn commit: r565837)
is
supposed to fix this.
However, as you can see from the latest build error, this
needs to
be
fixed further.
Cheers
Prasad
On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I
get it
from? I don't see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1
(and
modifying plugin.xml and the pom file) works. A new release
would
be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying
around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and
copied
it
over the
released alpha-1.jar from 8/8 and my builds starting
working
again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask
them
to
fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0
also.
I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2
repo
without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]>
wrote:
Is anyone else seeing this in geronimo-welcome.. I
am
building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-
src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
Illegal character in path at index 18:
file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
--
--
[INFO] Trace
java.lang.IllegalArgumentException
=== message truncated ===
_
Re: [Fwd: Re: building geronimo-2.0-rc1]
I'm fairly sure that these are all being caused by the Groovy
integration for Maven...
Though I'm not sure why it happens or how to fix it at the moment
though. I did some investigation a while ago and it looked like the
ClassWorlds CL inside of Maven muck was not encoding spaces
correctly, or maybe its being tickled in some way to induce it. I
think this is related to this issue too:
http://jira.codehaus.org/browse/MGROOVY-64
:-\
--jason
On Aug 23, 2007, at 3:48 PM, Anita Kulshreshtha wrote:
I am seeing this error on trunk:
http://issues.apache.org/jira/browse/GERONIMO-3424
I had to change buildsupport-maven-plugin to NOP (edit
CopyXMLBeansSchemaMojo.groovy) to be able to build from C:\Documents
And Settings\...
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
Problem occurs when there is a space in the M2REPO directory, in this
case
"C:\Documents And Settings\...". Work around is to use an M2REPO dir
without any spaces in it. We will still have to investigate the
cause.
Vamsi
On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
The entire log is here
http://rifers.org/paste/show/5314
Cheers
Prasad
On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
I have begun to see this same error at another location now.
On windows, run mvn from server/testsuite directory and you will
get
this
[INFO] [selenium:start-server {execution: start-server}]
[INFO] Starting Selenium server...
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-
1.7.0.jar
[INFO]
--
--
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
http://rifers.org/paste/show/5312
Cheers
Prasad
On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
This should now be fixed in Rev565885.
Should this be pulled into 2.0.1?
-Donald
Prasad Kashyap wrote:
The changes that Donald Woods is doing (svn commit: r565837)
is
supposed to fix this.
However, as you can see from the latest build error, this
needs to
be
fixed further.
Cheers
Prasad
On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I
get it
from? I don't see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1
(and
modifying plugin.xml and the pom file) works. A new release
would
be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying
around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and
copied
it
over the
released alpha-1.jar from 8/8 and my builds starting
working
again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask
them
to
fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0
also.
I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2
repo
without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]>
wrote:
Is anyone else seeing this in geronimo-welcome.. I
am
building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-
src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
Illegal character in path at index 18:
file:/C:/Documents and
Se
Re: [Fwd: Re: building geronimo-2.0-rc1]
I am seeing this error on trunk:
http://issues.apache.org/jira/browse/GERONIMO-3424
I had to change buildsupport-maven-plugin to NOP (edit
CopyXMLBeansSchemaMojo.groovy) to be able to build from C:\Documents
And Settings\...
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> Problem occurs when there is a space in the M2REPO directory, in this
> case
> "C:\Documents And Settings\...". Work around is to use an M2REPO dir
> without any spaces in it. We will still have to investigate the
> cause.
>
> Vamsi
>
> On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> >
> > The entire log is here
> > http://rifers.org/paste/show/5314
> >
> > Cheers
> > Prasad
> >
> > On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> > > I have begun to see this same error at another location now.
> > >
> > > On windows, run mvn from server/testsuite directory and you will
> get
> > this
> > >
> > > [INFO] [selenium:start-server {execution: start-server}]
> > > [INFO] Starting Selenium server...
> > > [INFO]
> >
>
> > > [ERROR] FATAL ERROR
> > > [INFO]
> >
>
> > > [INFO] null
> > > Illegal character in path at index 18: file:/C:/Documents and
> > >
> Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-
> > 1.7.0.jar
> > > [INFO]
> >
>
> > > [INFO] Trace
> > > java.lang.IllegalArgumentException
> > > at java.net.URI.create(URI.java:842)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:39)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > >
> > >
> > > http://rifers.org/paste/show/5312
> > >
> > > Cheers
> > > Prasad
> > >
> > >
> > >
> > >
> > > On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> > > > This should now be fixed in Rev565885.
> > > >
> > > > Should this be pulled into 2.0.1?
> > > >
> > > >
> > > > -Donald
> > > >
> > > > Prasad Kashyap wrote:
> > > > > The changes that Donald Woods is doing (svn commit: r565837)
> is
> > > > > supposed to fix this.
> > > > >
> > > > > However, as you can see from the latest build error, this
> needs to
> > be
> > > > > fixed further.
> > > > >
> > > > > Cheers
> > > > > Prasad
> > > > >
> > > > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> > > > >> So, how is this Jedi hand waving thingy?
> > > > >>
> > > > >> What is the file that needs to be replaced and where do I
> get it
> > from? I don't see any on my repo with that timestamp.
> > > > >>
> > > > >> What other files need to be modified
> > > > >>
> > > > >> Cheers!
> > > > >> Hernan
> > > > >>
> > > > >> Anita Kulshreshtha wrote:
> > > > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1
> (and
> > > > >>> modifying plugin.xml and the pom file) works. A new release
> would
> > be
> > > > >>> nice otherwise we can put it in the repo.
> > > > >>>
> > > > >>> Thanks
> > > > >>> Anita
> > > > >>>
> > > > >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> > > > >>>
> > > > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > > > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying
> around
> > > > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and
> copied
> > it
> > > > >>>> over the
> > > > >>>> released alpha-1.jar from 8/8 and my builds starting
> working
> > again on
> > > > >>>> WinXP
> > > > >>>>
> > > > >>>> Sh
Re: [Fwd: Re: building geronimo-2.0-rc1]
Raymond,
It didn't help in this case.
public static void main(String[] args) throws MalformedURLException,
URISyntaxException {
Object temp = new URL("file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
").toURI();
System.out.println(temp);
}
This method threw the same exception.
Moreover the failing code is not in Geronimo.
Vamsi
On 8/24/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I ran into a similar problem before. Some classloaders doesn't encode the
> spaces for URL. The trick we did is to use new URL(uri).toURI() instead of
> URI.create(uri).
>
> Thanks,
> Raymond
>
> - Original Message -
> *From:* Vamsavardhana Reddy <[EMAIL PROTECTED]>
> *To:* dev@geronimo.apache.org
> *Sent:* Thursday, August 23, 2007 12:15 PM
> *Subject:* Re: [Fwd: Re: building geronimo-2.0-rc1]
>
> Problem occurs when there is a space in the M2REPO directory, in this case
> "C:\Documents And Settings\...". Work around is to use an M2REPO dir
> without any spaces in it. We will still have to investigate the cause.
>
> Vamsi
>
> On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> >
> > The entire log is here
> > http://rifers.org/paste/show/5314
> >
> > Cheers
> > Prasad
> >
> > On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED] > wrote:
> > > I have begun to see this same error at another location now.
> > >
> > > On windows, run mvn from server/testsuite directory and you will get
> > this
> > >
> > > [INFO] [selenium:start-server {execution: start-server}]
> > > [INFO] Starting Selenium server...
> > > [INFO]
> >
> > > [ERROR] FATAL ERROR
> > > [INFO]
> >
> > > [INFO] null
> > > Illegal character in path at index 18: file:/C:/Documents and
> > > Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-
> > 1.7.0.jar
> > > [INFO]
> >
> > > [INFO] Trace
> > > java.lang.IllegalArgumentException
> > > at java.net.URI.create(URI.java:842)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke (
> > NativeMethodAccessorImpl.java:39)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > >
> > >
> > > http://rifers.org/paste/show/5312
> > >
> > > Cheers
> > > Prasad
> > >
> > >
> > >
> > >
> > > On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> > > > This should now be fixed in Rev565885.
> > > >
> > > > Should this be pulled into 2.0.1?
> > > >
> > > >
> > > > -Donald
> > > >
> > > > Prasad Kashyap wrote:
> > > > > The changes that Donald Woods is doing (svn commit: r565837) is
> > > > > supposed to fix this.
> > > > >
> > > > > However, as you can see from the latest build error, this needs to
> > be
> > > > > fixed further.
> > > > >
> > > > > Cheers
> > > > > Prasad
> > > > >
> > > > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> > > > >> So, how is this Jedi hand waving thingy?
> > > > >>
> > > > >> What is the file that needs to be replaced and where do I get it
> > from? I don't see any on my repo with that timestamp.
> > > > >>
> > > > >> What other files need to be modified
> > > > >>
> > > > >> Cheers!
> > > > >> Hernan
> > > > >>
> > > > >> Anita Kulshreshtha wrote:
> > > > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> > > > >>> modifying plugin.xml and the pom file) works. A new release
> > would be
> > > > >>> nice otherwise we can put it in the repo.
> > > > >>>
> > > > >>> Thanks
> > > > >>> Anita
> > > > >>>
> > > > >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> > > > >>>
> > > >
Re: [Fwd: Re: building geronimo-2.0-rc1]
t;mailto:[EMAIL PROTECTED]>>> wrote: > > > > >> So, how is this Jedi hand waving thingy? > > > > >> > > > > >> What is the file that needs to be replaced and where do I > > get it from? I don't see any on my repo with that timestamp. > > > > >> > > > > >> What other files need to be modified > > > > >> > > > > >> Cheers! > > > > >> Hernan > > > > >> > > > > >> Anita Kulshreshtha wrote: > > > > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 > > (and > > > > >>> modifying plugin.xml and the pom file) works. A new release > > would be > > > > >>> nice otherwise we can put it in the repo. > > > > >>> > > > > >>> Thanks > > > > >>> Anita > > > > >>> > > > > >>> --- Donald Woods < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > >>> > > > > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame. > > > > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around > > > > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar ) and > > copied it > > > > >>>> over the > > > > >>>> released alpha-1.jar from 8/8 and my builds starting > > working again on > > > > >>>> WinXP > > > > >>>> > > > > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask > > them to > > > > >>>> fix it > > > > >>>> before we release 2.0.1? > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> -Donald > > > > >>>> > > > > >>>> Anita Kulshreshtha wrote: > > > > >>>>> I have not been so lucky. I have tried branches/2.0.0 > > also. I > > > > >>>> have > > > > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 > > repo without > > > > >>>> any > > > > >>>>> success (The trunk builds fine). > > > > >>>>> > > > > >>>>> Thanks > > > > >>>>> Anita > > > > >>>>> > > > > >>>>> --- Vamsavardhana Reddy < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > mailto:[EMAIL PROTECTED]>>> wrote: > > > > >>>>> > > > > >>>>>> I am not exactly building from geronimo-2.0-src.zip, but > > from > > > > >>>>>> branches\2.0.0. If that still counts as if I built from > > src > > > > >>>> zip... I > > > > >>>>>> have > > > > >>>>>> not run into this problem. I have tried after removing > > > > >>>>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so > > that it > > > > >>>>>> downloads a > > > > >>>>>> fresh. > > > > >>>>>> > > > > >>>>>> --vamsi > > > > >>>>>> > > > > >>>>>> > > > > >>>>>> On 8/9/07, Anita Kulshreshtha < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > >>>>>>>Is anyone else seeing this in geronimo-welco
Re: [Fwd: Re: building geronimo-2.0-rc1]
> > >> Cheers! > > > > > >> Hernan > > > > > >> > > > > > >> Anita Kulshreshtha wrote: > > > > > >>> yup, copying alpha-1-20070806.170854-1.jar over > alpha-1 > > > (and > > > > > >>> modifying plugin.xml and the pom file) works. A new > release > > > would be > > > > > >>> nice otherwise we can put it in the repo. > > > > > >>> > > > > > >>> Thanks > > > > > >>> Anita > > > > > >>> > > > > > >>> --- Donald Woods <[EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > >>> > > > > > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame. > > > > > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying > around > > > > > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar ) > and > > > copied it > > > > > >>>> over the > > > > > >>>> released alpha-1.jar from 8/8 and my builds starting > > > working again on > > > > > >>>> WinXP > > > > > >>>> > > > > > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or > ask > > > them to > > > > > >>>> fix it > > > > > >>>> before we release 2.0.1? > > > > > >>>> > > > > > >>>> > > > > > >>>> > > > > > >>>> -Donald > > > > > >>>> > > > > > >>>> Anita Kulshreshtha wrote: > > > > > >>>>> I have not been so lucky. I have tried > branches/2.0.0 > > > also. I > > > > > >>>> have > > > > > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 > > > repo without > > > > > >>>> any > > > > > >>>>> success (The trunk builds fine). > > > > > >>>>> > > > > > >>>>> Thanks > > > > > >>>>> Anita > > > > > >>>>> > > > > > >>>>> --- Vamsavardhana Reddy < [EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > >>>>> > > > > > >>>>>> I am not exactly building from geronimo-2.0-src.zip, > but > > > from > > > > > >>>>>> branches\2.0.0. If that still counts as if I built > from > > > src > > > > > >>>> zip... I > > > > > >>>>>> have > > > > > >>>>>> not run into this problem. I have tried after > removing > > > > > >>>>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO > so > > > that it > > > > > >>>>>> downloads a > > > > > >>>>>> fresh. > > > > > >>>>>> > > > > > >>>>>> --vamsi > > > > > >>>>>> > > > > > >>>>>> > > > > > >>>>>> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > >>>>>>>Is anyone else seeing this in geronimo-welcome.. I > > > am building > > > > > >>>>>> from > > > > > >>> > > > > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip > > > < > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip> > > > > > >>>>>>> Thanks > > > > > >>>>>>> Anita > > > > > >>>>>>> > > > > > >>>>>>> Downloading: > > > > > >>>>>>> > > &
Re: [Fwd: Re: building geronimo-2.0-rc1]
> >>> --- Donald Woods <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> > > > >>>
> > > > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > > > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> > > > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar ) and
> > copied it
> > > > >>>> over the
> > > > >>>> released alpha-1.jar from 8/8 and my builds starting
> > working again on
> > > > >>>> WinXP
> > > > >>>>
> > > > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask
> > them to
> > > > >>>> fix it
> > > > >>>> before we release 2.0.1?
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> -Donald
> > > > >>>>
> > > > >>>> Anita Kulshreshtha wrote:
> > > > >>>>> I have not been so lucky. I have tried branches/2.0.0
> > also. I
> > > > >>>> have
> > > > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2
> > repo without
> > > > >>>> any
> > > > >>>>> success (The trunk builds fine).
> > > > >>>>>
> > > > >>>>> Thanks
> > > > >>>>> Anita
> > > > >>>>>
> > > > >>>>> --- Vamsavardhana Reddy < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> > > > >>>>>
> > > > >>>>>> I am not exactly building from geronimo-2.0-src.zip, but
> > from
> > > > >>>>>> branches\2.0.0. If that still counts as if I built from
> > src
> > > > >>>> zip... I
> > > > >>>>>> have
> > > > >>>>>> not run into this problem. I have tried after removing
> > > > >>>>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
> > that it
> > > > >>>>>> downloads a
> > > > >>>>>> fresh.
> > > > >>>>>>
> > > > >>>>>> --vamsi
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> > > > >>>>>>>Is anyone else seeing this in geronimo-welcome.. I
> > am building
> > > > >>>>>> from
> > > > >>>
> > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> >
> > <http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip>
> > > > >>>>>>> Thanks
> > > > >>>>>>> Anita
> > > > >>>>>>>
> > > > >>>>>>> Downloading:
> > > > >>>>>>>
> > > > >>>>
> > http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> > > > >>>>>>> -tomcat6/2.0-alpha-1/jspc- compiler-tomcat6-2.0-alpha-1.jar
> > > > >>>>>>> 4K downloaded
> > > > >>>>>>> [INFO] [jspc:compile {execution: default}]
> > > > >>>>>>> [INFO]
> > > > >>>>>>>
> > > > >>>
> >
> > > > >>>>>>> [ERROR] FATAL ERROR
> > > > >>>>>>> [INFO]
> > > > >>>>>>>
> > > > >>>
> >
> > > > >>>>>>> [INFO] null
> > > > >
Re: [Fwd: Re: building geronimo-2.0-rc1]
how do we set the .m2 repo to different directory? I can't find the config file
to set this up.
Cheers!
Hernan
Vamsavardhana Reddy wrote:
Problem occurs when there is a space in the M2REPO directory, in this
case "C:\Documents And Settings\...". Work around is to use an M2REPO
dir without any spaces in it. We will still have to investigate the cause.
Vamsi
On 8/24/07, *Prasad Kashyap* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
The entire log is here
http://rifers.org/paste/show/5314
Cheers
Prasad
On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> I have begun to see this same error at another location now.
>
> On windows, run mvn from server/testsuite directory and you will
get this
>
> [INFO] [selenium:start-server {execution: start-server}]
> [INFO] Starting Selenium server...
> [INFO]
> [ERROR] FATAL ERROR
> [INFO]
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
>
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
> [INFO] Trace
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>
> http://rifers.org/paste/show/5312 <http://rifers.org/paste/show/5312>
>
> Cheers
> Prasad
>
>
>
>
> On 8/14/07, Donald Woods <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > This should now be fixed in Rev565885.
> >
> > Should this be pulled into 2.0.1?
> >
> >
> > -Donald
> >
> > Prasad Kashyap wrote:
> > > The changes that Donald Woods is doing (svn commit: r565837) is
> > > supposed to fix this.
> > >
> > > However, as you can see from the latest build error, this
needs to be
> > > fixed further.
> > >
> > > Cheers
> > > Prasad
> > >
> > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > >> So, how is this Jedi hand waving thingy?
> > >>
> > >> What is the file that needs to be replaced and where do I
get it from? I don't see any on my repo with that timestamp.
> > >>
> > >> What other files need to be modified
> > >>
> > >> Cheers!
> > >> Hernan
> > >>
> > >> Anita Kulshreshtha wrote:
> > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1
(and
> > >>> modifying plugin.xml and the pom file) works. A new release
would be
> > >>> nice otherwise we can put it in the repo.
> > >>>
> > >>> Thanks
> > >>> Anita
> > >>>
> > >>> --- Donald Woods <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > >>>
> > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar ) and
copied it
> > >>>> over the
> > >>>> released alpha-1.jar from 8/8 and my builds starting
working again on
> > >>>> WinXP
> > >>>>
> > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask
them to
> > >>>> fix it
> > >>>> before we release 2.0.1?
> > >>>>
> > >>>>
> > >>>>
> > >>>> -Donald
> > >>>>
> > >>>> Anita Kulshreshtha wrote:
> > >>>>> I have not been so lucky. I have tried branches/2.0.0
also. I
> > >>>> have
> &g
Re: [Fwd: Re: building geronimo-2.0-rc1]
Hi,
I ran into a similar problem before. Some classloaders doesn't encode the
spaces for URL. The trick we did is to use new URL(uri).toURI() instead of
URI.create(uri).
Thanks,
Raymond
- Original Message -
From: Vamsavardhana Reddy
To: dev@geronimo.apache.org
Sent: Thursday, August 23, 2007 12:15 PM
Subject: Re: [Fwd: Re: building geronimo-2.0-rc1]
Problem occurs when there is a space in the M2REPO directory, in this case
"C:\Documents And Settings\...". Work around is to use an M2REPO dir without
any spaces in it. We will still have to investigate the cause.
Vamsi
On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
The entire log is here
http://rifers.org/paste/show/5314
Cheers
Prasad
On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED] > wrote:
> I have begun to see this same error at another location now.
>
> On windows, run mvn from server/testsuite directory and you will get this
>
> [INFO] [selenium:start-server {execution: start-server}]
> [INFO] Starting Selenium server...
> [INFO]
> [ERROR] FATAL ERROR
> [INFO]
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
>
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
> [INFO] Trace
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>
> http://rifers.org/paste/show/5312
>
> Cheers
> Prasad
>
>
>
>
> On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> > This should now be fixed in Rev565885.
> >
> > Should this be pulled into 2.0.1?
> >
> >
> > -Donald
> >
> > Prasad Kashyap wrote:
> > > The changes that Donald Woods is doing (svn commit: r565837) is
> > > supposed to fix this.
> > >
> > > However, as you can see from the latest build error, this needs to be
> > > fixed further.
> > >
> > > Cheers
> > > Prasad
> > >
> > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> > >> So, how is this Jedi hand waving thingy?
> > >>
> > >> What is the file that needs to be replaced and where do I get it
from? I don't see any on my repo with that timestamp.
> > >>
> > >> What other files need to be modified
> > >>
> > >> Cheers!
> > >> Hernan
> > >>
> > >> Anita Kulshreshtha wrote:
> > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> > >>> modifying plugin.xml and the pom file) works. A new release would be
> > >>> nice otherwise we can put it in the repo.
> > >>>
> > >>> Thanks
> > >>> Anita
> > >>>
> > >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> > >>>
> > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar ) and copied
it
> > >>>> over the
> > >>>> released alpha-1.jar from 8/8 and my builds starting working again
on
> > >>>> WinXP
> > >>>>
> > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
> > >>>> fix it
> > >>>> before we release 2.0.1?
> > >>>>
> > >>>>
> > >>>>
> > >>>> -Donald
> > >>>>
> > >>>> Anita Kulshreshtha wrote:
> > >>>>> I have not been so lucky. I have tried branches/2.0.0 also. I
> > >>>> have
> > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo
without
> > >&g
Re: [Fwd: Re: building geronimo-2.0-rc1]
Problem occurs when there is a space in the M2REPO directory, in this case
"C:\Documents And Settings\...". Work around is to use an M2REPO dir
without any spaces in it. We will still have to investigate the cause.
Vamsi
On 8/24/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
>
> The entire log is here
> http://rifers.org/paste/show/5314
>
> Cheers
> Prasad
>
> On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> > I have begun to see this same error at another location now.
> >
> > On windows, run mvn from server/testsuite directory and you will get
> this
> >
> > [INFO] [selenium:start-server {execution: start-server}]
> > [INFO] Starting Selenium server...
> > [INFO]
>
> > [ERROR] FATAL ERROR
> > [INFO]
>
> > [INFO] null
> > Illegal character in path at index 18: file:/C:/Documents and
> > Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-
> 1.7.0.jar
> > [INFO]
>
> > [INFO] Trace
> > java.lang.IllegalArgumentException
> > at java.net.URI.create(URI.java:842)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> >
> >
> > http://rifers.org/paste/show/5312
> >
> > Cheers
> > Prasad
> >
> >
> >
> >
> > On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> > > This should now be fixed in Rev565885.
> > >
> > > Should this be pulled into 2.0.1?
> > >
> > >
> > > -Donald
> > >
> > > Prasad Kashyap wrote:
> > > > The changes that Donald Woods is doing (svn commit: r565837) is
> > > > supposed to fix this.
> > > >
> > > > However, as you can see from the latest build error, this needs to
> be
> > > > fixed further.
> > > >
> > > > Cheers
> > > > Prasad
> > > >
> > > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> > > >> So, how is this Jedi hand waving thingy?
> > > >>
> > > >> What is the file that needs to be replaced and where do I get it
> from? I don't see any on my repo with that timestamp.
> > > >>
> > > >> What other files need to be modified
> > > >>
> > > >> Cheers!
> > > >> Hernan
> > > >>
> > > >> Anita Kulshreshtha wrote:
> > > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> > > >>> modifying plugin.xml and the pom file) works. A new release would
> be
> > > >>> nice otherwise we can put it in the repo.
> > > >>>
> > > >>> Thanks
> > > >>> Anita
> > > >>>
> > > >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> > > >>>
> > > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> > > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied
> it
> > > >>>> over the
> > > >>>> released alpha-1.jar from 8/8 and my builds starting working
> again on
> > > >>>> WinXP
> > > >>>>
> > > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them
> to
> > > >>>> fix it
> > > >>>> before we release 2.0.1?
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> -Donald
> > > >>>>
> > > >>>> Anita Kulshreshtha wrote:
> > > >>>>> I have not been so lucky. I have tried branches/2.0.0 also.
> I
> > > >>>> have
> > > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo
> without
> > > >>>> any
> > > >>>>> success (The trunk builds fine).
> > > >>>>>
> > > >>>>> Thanks
> >
Re: [Fwd: Re: building geronimo-2.0-rc1]
The entire log is here
http://rifers.org/paste/show/5314
Cheers
Prasad
On 8/23/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> I have begun to see this same error at another location now.
>
> On windows, run mvn from server/testsuite directory and you will get this
>
> [INFO] [selenium:start-server {execution: start-server}]
> [INFO] Starting Selenium server...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
> Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>
> http://rifers.org/paste/show/5312
>
> Cheers
> Prasad
>
>
>
>
> On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> > This should now be fixed in Rev565885.
> >
> > Should this be pulled into 2.0.1?
> >
> >
> > -Donald
> >
> > Prasad Kashyap wrote:
> > > The changes that Donald Woods is doing (svn commit: r565837) is
> > > supposed to fix this.
> > >
> > > However, as you can see from the latest build error, this needs to be
> > > fixed further.
> > >
> > > Cheers
> > > Prasad
> > >
> > > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> > >> So, how is this Jedi hand waving thingy?
> > >>
> > >> What is the file that needs to be replaced and where do I get it from? I
> > >> don't see any on my repo with that timestamp.
> > >>
> > >> What other files need to be modified
> > >>
> > >> Cheers!
> > >> Hernan
> > >>
> > >> Anita Kulshreshtha wrote:
> > >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> > >>> modifying plugin.xml and the pom file) works. A new release would be
> > >>> nice otherwise we can put it in the repo.
> > >>>
> > >>> Thanks
> > >>> Anita
> > >>>
> > >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> > >>>
> > >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> > >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> > >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
> > >>>> over the
> > >>>> released alpha-1.jar from 8/8 and my builds starting working again on
> > >>>> WinXP
> > >>>>
> > >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
> > >>>> fix it
> > >>>> before we release 2.0.1?
> > >>>>
> > >>>>
> > >>>>
> > >>>> -Donald
> > >>>>
> > >>>> Anita Kulshreshtha wrote:
> > >>>>> I have not been so lucky. I have tried branches/2.0.0 also. I
> > >>>> have
> > >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
> > >>>> any
> > >>>>> success (The trunk builds fine).
> > >>>>>
> > >>>>> Thanks
> > >>>>> Anita
> > >>>>>
> > >>>>> --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> > >>>>>
> > >>>>>> I am not exactly building from geronimo-2.0-src.zip, but from
> > >>>>>> branches\2.0.0. If that still counts as if I built from src
> > >>>> zip... I
> > >>>>>> have
> > >>>>>> not run into this problem. I have tried after removing
> > >>>>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> > >>>>>> downloads a
> > >>>>>> fresh.
> > >>>>>>
> > >>>>>> --vamsi
> > >>>>>>
> > >>>>>>
Re: [Fwd: Re: building geronimo-2.0-rc1]
I have begun to see this same error at another location now.
On windows, run mvn from server/testsuite directory and you will get this
[INFO] [selenium:start-server {execution: start-server}]
[INFO] Starting Selenium server...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
http://rifers.org/paste/show/5312
Cheers
Prasad
On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote:
> This should now be fixed in Rev565885.
>
> Should this be pulled into 2.0.1?
>
>
> -Donald
>
> Prasad Kashyap wrote:
> > The changes that Donald Woods is doing (svn commit: r565837) is
> > supposed to fix this.
> >
> > However, as you can see from the latest build error, this needs to be
> > fixed further.
> >
> > Cheers
> > Prasad
> >
> > On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> >> So, how is this Jedi hand waving thingy?
> >>
> >> What is the file that needs to be replaced and where do I get it from? I
> >> don't see any on my repo with that timestamp.
> >>
> >> What other files need to be modified
> >>
> >> Cheers!
> >> Hernan
> >>
> >> Anita Kulshreshtha wrote:
> >>> yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> >>> modifying plugin.xml and the pom file) works. A new release would be
> >>> nice otherwise we can put it in the repo.
> >>>
> >>> Thanks
> >>> Anita
> >>>
> >>> --- Donald Woods <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> >>>> I still had a copy of the last alpha-1-SNAPSHOT laying around
> >>>> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
> >>>> over the
> >>>> released alpha-1.jar from 8/8 and my builds starting working again on
> >>>> WinXP
> >>>>
> >>>> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
> >>>> fix it
> >>>> before we release 2.0.1?
> >>>>
> >>>>
> >>>>
> >>>> -Donald
> >>>>
> >>>> Anita Kulshreshtha wrote:
> >>>>> I have not been so lucky. I have tried branches/2.0.0 also. I
> >>>> have
> >>>>> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
> >>>> any
> >>>>> success (The trunk builds fine).
> >>>>>
> >>>>> Thanks
> >>>>> Anita
> >>>>>
> >>>>> --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> >>>>>
> >>>>>> I am not exactly building from geronimo-2.0-src.zip, but from
> >>>>>> branches\2.0.0. If that still counts as if I built from src
> >>>> zip... I
> >>>>>> have
> >>>>>> not run into this problem. I have tried after removing
> >>>>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> >>>>>> downloads a
> >>>>>> fresh.
> >>>>>>
> >>>>>> --vamsi
> >>>>>>
> >>>>>>
> >>>>>> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> >>>>>>>Is anyone else seeing this in geronimo-welcome.. I am building
> >>>>>> from
> >>> http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> >>>>>>> Thanks
> >>>>>>> Anita
> >>>>>>>
> >>>>>>> Downloading:
> >>>>>>>
> >>>> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> >>>>>>> -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
On Aug 18, 2007, at 11:59 PM, Rodrigo Rodrigues da Silva wrote: Donald, thanks for your help, but it didn't work out. If it were the problem, wouldn't have worked on windows before, I guess. Well, about Linux distros I've tested on ubuntu feisty and debian etch. none worked. I'm able to login, list-modules, to a remote linux box without a problem (using G 2.0.1 Mac OS X -> SLES). I didn't need to make any updates to my config.xml. I did run into a problem deploying a WAR. Donald, I recall you had a remote-deploy jira recently. Would that explain the following? Uploading 1 file(s) to server unknown protocol: localhost Error: Unable to distribute HelloWorld.war: java.io.FileNotFoundException: /Users/kevan/HelloWorld.war (No such file or directory) /Users/kevan/HelloWorld.war (No such file or directory) --kevan
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Donald,
thanks for your help, but it didn't work out. If it were the problem,
wouldn't have worked on windows before, I guess. Well, about Linux distros
I've tested on ubuntu feisty and debian etch. none worked.
thanks,
Rodrigo
On 8/15/07, Donald Woods <[EMAIL PROTECTED]> wrote:
>
> Have you updated the config.xml, to allow access to the remote deployer,
> which
> was recently changed to only listen to localhost:8080 ?
>
> In config.xml, replace -
> name="org.apache.geronimo.configs
> /geronimo-gbean-deployer/${version}/car"/>
>
> with -
> name="org.apache.geronimo.configs/geronimo-gbean-deployer/${version}/car">
>
> name="remoteDeployAddress">YOUR_HOSTNAME:8080
>
>
>
> and see if that helps (which I forgot that I had already done on my
> machines)
>
> -Donald
>
>
>
> Rodrigo Rodrigues da Silva wrote:
> > Hi,
> >
> > I tried out 2.0-rc1 release (as posted by David to
> > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could
> > reproduce bug GERONIMO-3191, which had been considered as closed.
> > I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a
> > Windows Vista Machine I ran the following command:
> >
> > deploy --host 192.168.0.11 <http://192.168.0.11> --user system
> > --password manager --port 1099 login
> >
> > which returned:
> >
> > Error: Unable to connect to server at
> > deployer:geronimo:jmx://192.168.0.11 – no such object in table
> >
> > if I run it from the server Linux machine, it works.
> >
> > I haven't ever been able to access remote linux servers (specially from
> > Eclipse) but this specific situation has been tested only on this
> release.
> >
> > I was wondering if anyone could reproduce it since I may have commited
> > some configuration mistake. hope it helps.
> >
> > thanks,
> > Rodrigo
> >
> > On 8/9/07, * David Jencks* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> > I'd recommend trying with the about to be released unless someone
> > finds a major problem 2.0 release you can find here
> >
> http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
> > <
> http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/>
> > apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
> >
> > You won't have this exact problem because the
> > JaasLoginServiceRemotingServer gbean isn't in the latest version.
> >
> > If you wish to continue with 2.0-M6 the problem is that the
> > JaasLoginServiceRemotingServer can't figure out what ip address to
> > bind onto. Have you perhaps changed var/config/config-
> > substitutions.properties? Or perhaps your hostnames aren't quite
> > right? something seems to expect your computer to be named
> "testing"
> >
> > thanks
> > david jencks
> >
> > On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote:
> >
> > > Hi!
> > >
> > > I just download the last version of geronimo
> > > (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server
> > with
> > > geronimo.sh:
> > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./
> > > geronimo.sh run
> > >
> > > but fails at 16%:
> > > [> ] 16% 4s Startup failed
> > >
> > > The stack trace start with this log (the complete log is
> attached)
> > > 7:22:37,995 ERROR [GBeanInstanceState] Error while starting;
> > GBean is
> > > now in the FAILED state:
> > > abstractName="org.apache.geronimo.configs
> /j2ee-security/2.0-M6/car?
> > > ServiceModule=org.apache.geronimo.configs/j2ee-se
> > >
> >
> curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer"
> > >
> > > This is my first contact with geronimo, maybe I am doing
> something
> > > wrong.
> > >
> > > Some useful information of my java environment:
> > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo
> > > $JAVA_HOME
> > > /home/fsousa/opt/java/jdk1.5.0_12
> > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java
> -version
> > > java version "1.5.0_12"
>
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Have you updated the config.xml, to allow access to the remote deployer, which
was recently changed to only listen to localhost:8080 ?
In config.xml, replace -
name="org.apache.geronimo.configs/geronimo-gbean-deployer/${version}/car"/>
with -
name="org.apache.geronimo.configs/geronimo-gbean-deployer/${version}/car">
YOUR_HOSTNAME:8080
and see if that helps (which I forgot that I had already done on my
machines)
-Donald
Rodrigo Rodrigues da Silva wrote:
Hi,
I tried out 2.0-rc1 release (as posted by David to
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could
reproduce bug GERONIMO-3191, which had been considered as closed.
I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a
Windows Vista Machine I ran the following command:
deploy --host 192.168.0.11 <http://192.168.0.11> --user system
--password manager --port 1099 login
which returned:
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.0.11 – no such object in table
if I run it from the server Linux machine, it works.
I haven't ever been able to access remote linux servers (specially from
Eclipse) but this specific situation has been tested only on this release.
I was wondering if anyone could reproduce it since I may have commited
some configuration mistake. hope it helps.
thanks,
Rodrigo
On 8/9/07, * David Jencks* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
<http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/>
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have this exact problem because the
JaasLoginServiceRemotingServer gbean isn't in the latest version.
If you wish to continue with 2.0-M6 the problem is that the
JaasLoginServiceRemotingServer can't figure out what ip address to
bind onto. Have you perhaps changed var/config/config-
substitutions.properties? Or perhaps your hostnames aren't quite
right? something seems to expect your computer to be named "testing"
thanks
david jencks
On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote:
> Hi!
>
> I just download the last version of geronimo
> (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server
with
> geronimo.sh:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./
> geronimo.sh run
>
> but fails at 16%:
> [> ] 16% 4s Startup failed
>
> The stack trace start with this log (the complete log is attached)
> 7:22:37,995 ERROR [GBeanInstanceState] Error while starting;
GBean is
> now in the FAILED state:
> abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car?
> ServiceModule=org.apache.geronimo.configs/j2ee-se
>
curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer"
>
> This is my first contact with geronimo, maybe I am doing something
> wrong.
>
> Some useful information of my java environment:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo
> $JAVA_HOME
> /home/fsousa/opt/java/jdk1.5.0_12
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>
> --
> Filipe Sousa
>
--
Rodrigo Rodrigues da Silva
Engenharia de Computação - Coop8
http://www.coop8.rg.com.br
Grêmio Politécnico - Gestão Colabora
http://www.gremio.poli.usp.br
"Não importa como morre o home, importa como vive." Carijó, velho do rio.
"To the person with only a hammer, everything looks like a nail."
bussdriver
--
Rodrigo Rodrigues da Silva
Engenharia de Computação - Coop8
http://www.coop8.rg.com.br
Grêmio Politécnico - Gestão Colabora
http://www.gremio.poli.usp.br
"Não importa como morre o home, importa como vive." Carijó, velho do rio.
"To the person with only a hammer, everything looks like a nail."
bussdriver
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
I'm still not seeing this problem
My setup is -
SLES10 w/ Sun 1.5.0_11 and Geronimo 2.0
WinXP w/ Sun 1.5.0_11 and Geronimo 2.0
Both machines are on the same subnet and do not have IPv6 configured or
enabled on the Ethernet adapters.
From SLES, the following works:
deploy -host winxp list-modules
From WinXP, the following works:
deploy -host sles list-modules
Can you try disabling IPv6 if its not required for your setup?
-Donald
Peter Petersson wrote:
I can still not tell you whats wrong but I now think it is safe to say
that it is definitely not any firewall rules in the way (and I get the
same error as you do). I checked all my firewall rules "iptables -L" and
to be on the safe side I also turned on logging on iptables reject and
drop rules and as suspected nothing was found.
The other thing i did was turning on logging of rmi gc via
-Dsun.rmi.dgc.loglevel=VERBOSE but that didn't give me any information
ether.
Sun jdk build 1.5.0_06-b05, Ubuntu 7.10, G 1.1.1.
regards
Peter Petersson
Peter Petersson wrote:
Okey now I get exactly the same error as you
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.2.1:1099 -- no such object in table
regards
Peter Petersson
Rodrigo Rodrigues da Silva wrote:
Hi,
I tried out 2.0-rc1 release (as posted by David to
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could
reproduce bug GERONIMO-3191, which had been considered as closed.
I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From
a Windows Vista Machine I ran the following command:
deploy --host 192.168.0.11 <http://192.168.0.11> --user system
--password manager --port 1099 login
which returned:
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.0.11 – no such object in table
if I run it from the server Linux machine, it works.
I haven't ever been able to access remote linux servers (specially
from Eclipse) but this specific situation has been tested only on
this release.
I was wondering if anyone could reproduce it since I may have
commited some configuration mistake. hope it helps.
thanks,
Rodrigo
On 8/9/07, * David Jencks* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
<http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/>
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have this exact problem because the
JaasLoginServiceRemotingServer gbean isn't in the latest version.
If you wish to continue with 2.0-M6 the problem is that the
JaasLoginServiceRemotingServer can't figure out what ip address to
bind onto. Have you perhaps changed var/config/config-
substitutions.properties? Or perhaps your hostnames aren't quite
right? something seems to expect your computer to be named "testing"
thanks
david jencks
On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote:
> Hi!
>
> I just download the last version of geronimo
> (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the
server with
> geronimo.sh:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./
> geronimo.sh run
>
> but fails at 16%:
> [> ] 16% 4s Startup failed
>
> The stack trace start with this log (the complete log is attached)
> 7:22:37,995 ERROR [GBeanInstanceState] Error while starting;
GBean is
> now in the FAILED state:
> abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car?
> ServiceModule=org.apache.geronimo.configs/j2ee-se
>
curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer"
>
> This is my first contact with geronimo, maybe I am doing something
> wrong.
>
> Some useful information of my java environment:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo
> $JAVA_HOME
> /home/fsousa/opt/java/jdk1.5.0_12
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java
-version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>
> --
> Filipe Sousa
>
--
Rodrigo Rodrigues da Silva
Engenharia de Computação - Coop8
http://www.coop8.rg.com.br
Grêmio Politécnico - Gestão Colabora
http://www.gremio.poli.usp.br
"Não importa como morre o home, importa como vive." Carijó, velho do rio.
"To the person with only a hammer, everything looks like a nail."
bussdr
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
I can still not tell you whats wrong but I now think it is safe to say
that it is definitely not any firewall rules in the way (and I get the
same error as you do). I checked all my firewall rules "iptables -L" and
to be on the safe side I also turned on logging on iptables reject and
drop rules and as suspected nothing was found.
The other thing i did was turning on logging of rmi gc via
-Dsun.rmi.dgc.loglevel=VERBOSE but that didn't give me any information
ether.
Sun jdk build 1.5.0_06-b05, Ubuntu 7.10, G 1.1.1.
regards
Peter Petersson
Peter Petersson wrote:
Okey now I get exactly the same error as you
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.2.1:1099 -- no such object in table
regards
Peter Petersson
Rodrigo Rodrigues da Silva wrote:
Hi,
I tried out 2.0-rc1 release (as posted by David to
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could
reproduce bug GERONIMO-3191, which had been considered as closed.
I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From
a Windows Vista Machine I ran the following command:
deploy --host 192.168.0.11 <http://192.168.0.11> --user system
--password manager --port 1099 login
which returned:
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.0.11 – no such object in table
if I run it from the server Linux machine, it works.
I haven't ever been able to access remote linux servers (specially
from Eclipse) but this specific situation has been tested only on
this release.
I was wondering if anyone could reproduce it since I may have
commited some configuration mistake. hope it helps.
thanks,
Rodrigo
On 8/9/07, * David Jencks* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
<http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/>
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have this exact problem because the
JaasLoginServiceRemotingServer gbean isn't in the latest version.
If you wish to continue with 2.0-M6 the problem is that the
JaasLoginServiceRemotingServer can't figure out what ip address to
bind onto. Have you perhaps changed var/config/config-
substitutions.properties? Or perhaps your hostnames aren't quite
right? something seems to expect your computer to be named "testing"
thanks
david jencks
On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote:
> Hi!
>
> I just download the last version of geronimo
> (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the
server with
> geronimo.sh:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./
> geronimo.sh run
>
> but fails at 16%:
> [> ] 16% 4s Startup failed
>
> The stack trace start with this log (the complete log is attached)
> 7:22:37,995 ERROR [GBeanInstanceState] Error while starting;
GBean is
> now in the FAILED state:
> abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car?
> ServiceModule=org.apache.geronimo.configs/j2ee-se
>
curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer"
>
> This is my first contact with geronimo, maybe I am doing something
> wrong.
>
> Some useful information of my java environment:
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo
> $JAVA_HOME
> /home/fsousa/opt/java/jdk1.5.0_12
> [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java
-version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>
> --
> Filipe Sousa
>
--
Rodrigo Rodrigues da Silva
Engenharia de Computação - Coop8
http://www.coop8.rg.com.br
Grêmio Politécnico - Gestão Colabora
http://www.gremio.poli.usp.br
"Não importa como morre o home, importa como vive." Carijó, velho do rio.
"To the person with only a hammer, everything looks like a nail."
bussdriver
--
Rodrigo Rodrigues da Silva
Engenharia de Computação - Coop8
http://www.coop8.rg.com.br
Grêmio Politécnico - Gestão Colabora
http://www.gremio.poli.usp.br
"Não importa como morre o home, importa como vive." Carijó, velho do rio.
"To the person with only a hammer, everything looks like a nail."
bussdriver
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Okey now I get exactly the same error as you Error: Unable to connect to server at deployer:geronimo:jmx://192.168.2.1:1099 -- no such object in table regards Peter Petersson Rodrigo Rodrigues da Silva wrote: Hi, I tried out 2.0-rc1 release (as posted by David to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could reproduce bug GERONIMO-3191, which had been considered as closed. I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a Windows Vista Machine I ran the following command: deploy --host 192.168.0.11 <http://192.168.0.11> --user system --password manager --port 1099 login which returned: Error: Unable to connect to server at deployer:geronimo:jmx://192.168.0.11 – no such object in table if I run it from the server Linux machine, it works. I haven't ever been able to access remote linux servers (specially from Eclipse) but this specific situation has been tested only on this release. I was wondering if anyone could reproduce it since I may have commited some configuration mistake. hope it helps. thanks, Rodrigo On 8/9/07, * David Jencks* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: I'd recommend trying with the about to be released unless someone finds a major problem 2.0 release you can find here http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/ <http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/> apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/ You won't have this exact problem because the JaasLoginServiceRemotingServer gbean isn't in the latest version. If you wish to continue with 2.0-M6 the problem is that the JaasLoginServiceRemotingServer can't figure out what ip address to bind onto. Have you perhaps changed var/config/config- substitutions.properties? Or perhaps your hostnames aren't quite right? something seems to expect your computer to be named "testing" thanks david jencks On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote: > Hi! > > I just download the last version of geronimo > (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server with > geronimo.sh: > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./ > geronimo.sh run > > but fails at 16%: > [> ] 16% 4s Startup failed > > The stack trace start with this log (the complete log is attached) > 7:22:37,995 ERROR [GBeanInstanceState] Error while starting; GBean is > now in the FAILED state: > abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car? > ServiceModule=org.apache.geronimo.configs/j2ee-se > curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer" > > This is my first contact with geronimo, maybe I am doing something > wrong. > > Some useful information of my java environment: > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo > $JAVA_HOME > /home/fsousa/opt/java/jdk1.5.0_12 > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java -version > java version "1.5.0_12" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) > Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) > > -- > Filipe Sousa > -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Hi
I have looked at java security policy, firewall settings, sniffed the
traffic and more without finding out way the connection fails. As far as
I know IPv6 should normally not be a problem but I started to suspect it
had something to do with it. In my case it seems to have something to do
with the loopback interface.
Anyone else having problem with network access using this command?
deploy --host --user --password
--port 1099 login
or better yet a solution ? this may still be a configuration issue.
I will try to find out what is wrong and will get back if I find
something out.
regards
Peter
Rodrigo Rodrigues da Silva wrote:
Hi Peter,
rmi runs on IPv6 here as well. I am not a network expert also, don't
know if this should be a problem, as all ports opened by the java vm
are on IPv6. Here port 1527 (derby) runs on Ipv6, although I could
access derby from a remote machine with no hurt =]
tcp6 0 0 *:1099 *:*
LISTEN 6794/java
tcp6 0 0 *:1527 *:*
LISTEN 6794/java
thanks,
On 8/14/07, *Peter Petersson* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Rodrigo
As I am also running G on a Ubuntu system (although it's 7.10) I
thought I should give it a try and I get a similar problem
(although I am not really reproducing yours).
In my case I tried the "deploy login" command from a client also
running Ubuntu from within a local network and surprisingly it
failed with the following
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.2.1:1099 -- Connection refused to
host: 127.0.0.1 <http://127.0.0.1>; nested exception is:
As I am trying this via a local network connection and no firewall
rules should be in the way so I should not get "connection
refused" but I did so if this is suppose to work right out of the
box(?) we may have some weird problem and in my case this could be
related to some IPv6 problem as I found out that the rmiregistry
(port 1099) was running on IPv6
netstat -plt
:
tcp0 0 *:www
*:* LISTEN -
:
tcp6 0 0 *:rmiregistry
*:* LISTEN -
I don't know way this should be a problem (I am not a network
expert) but apparently something is wrong. However as in your case
from local machine it works fine.
I haven't upgraded to 2.0 yet on the server, so this test has been
done on G v1.1.1 and FYI all the address and port binds are the
defaults (in config.xml) so G and rmiregistry should bind to all
interfaces.
However In your case you get "no such object in table" which to me
looks like you actually got the initial connection on port 1099
but a failure in the object call (using some other port) so our
problems may not be related but anyhow It seem you are not
completely alone on this. You could try sniff the network traffic
with Wireshark (you can do a apt-get if you don't have it
already), you may whant to use some traffic filter for example
"tcp port 1099 || tcp port " to minimize the noise.
Sry I couldn't help you more with this, lets see what more the G
devs have to say about it ?
regards
Peter Petersson
Rodrigo Rodrigues da Silva wrote:
Hi,
I tried out 2.0-rc1 release (as posted by David to
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and
could reproduce bug GERONIMO-3191, which had been considered as
closed.
I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo.
From a Windows Vista Machine I ran the following command:
deploy --host 192.168.0.11 <http://192.168.0.11> --user system
--password manager --port 1099 login
which returned:
Error: Unable to connect to server at
deployer:geronimo:jmx://192.168.0.11 -- no such object in table
if I run it from the server Linux machine, it works.
I haven't ever been able to access remote linux servers
(specially from Eclipse) but this specific situation has been
tested only on this release.
I was wondering if anyone could reproduce it since I may have
commited some configuration mistake. hope it helps.
thanks,
Rodrigo
On 8/9/07, * David Jencks* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
<http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/>
apache/geronimo/assemblies
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Hi Peter, rmi runs on IPv6 here as well. I am not a network expert also, don't know if this should be a problem, as all ports opened by the java vm are on IPv6. Here port 1527 (derby) runs on Ipv6, although I could access derby from a remote machine with no hurt =] tcp6 0 0 *:1099 *:* LISTEN 6794/java tcp6 0 0 *:1527 *:*LISTEN 6794/java thanks, On 8/14/07, Peter Petersson <[EMAIL PROTECTED]> wrote: > > Hi Rodrigo > As I am also running G on a Ubuntu system (although it's 7.10) I thought I > should give it a try and I get a similar problem (although I am not really > reproducing yours). > In my case I tried the "deploy login" command from a client also running > Ubuntu from within a local network and surprisingly it failed with the > following > > Error: Unable to connect to server at > deployer:geronimo:jmx://192.168.2.1:1099 -- Connection refused to > host: 127.0.0.1; nested exception is: > > As I am trying this via a local network connection and no firewall rules > should be in the way so I should not get "connection refused" but I did so > if this is suppose to work right out of the box(?) we may have some weird > problem and in my case this could be related to some IPv6 problem as I found > out that the rmiregistry (port 1099) was running on IPv6 > >netstat -plt > : >tcp0 0 *:www *:* > LISTEN - > : >tcp6 0 0 *:rmiregistry *:* > LISTEN - > > I don't know way this should be a problem (I am not a network expert) but > apparently something is wrong. However as in your case from local machine it > works fine. > I haven't upgraded to 2.0 yet on the server, so this test has been done on > G v1.1.1 and FYI all the address and port binds are the defaults (in > config.xml) so G and rmiregistry should bind to all interfaces. > > However In your case you get "no such object in table" which to me looks > like you actually got the initial connection on port 1099 but a failure in > the object call (using some other port) so our problems may not be related > but anyhow It seem you are not completely alone on this. You could try sniff > the network traffic with Wireshark (you can do a apt-get if you don't have > it already), you may whant to use some traffic filter for example "tcp port > 1099 || tcp port " to minimize the noise. > > Sry I couldn't help you more with this, lets see what more the G devs have > to say about it ? > > regards >Peter Petersson > > > > > > Rodrigo Rodrigues da Silva wrote: > > Hi, > > I tried out 2.0-rc1 release (as posted by David to > [EMAIL PROTECTED]) and could reproduce bug GERONIMO-3191, which had > been considered as closed. > I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a > Windows Vista Machine I ran the following command: > > deploy --host 192.168.0.11 --user system --password manager --port 1099 > login > > which returned: > > Error: Unable to connect to server at > deployer:geronimo:jmx://192.168.0.11 – no such object in table > > if I run it from the server Linux machine, it works. > I haven't ever been able to access remote linux servers (specially from > Eclipse) but this specific situation has been tested only on this release. > > I was wondering if anyone could reproduce it since I may have commited > some configuration mistake. hope it helps. > > thanks, > Rodrigo > > On 8/9/07, David Jencks <[EMAIL PROTECTED]> wrote: > > > > I'd recommend trying with the about to be released unless someone > > finds a major problem 2.0 release you can find here > > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/ > > <http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/> > > apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/ > > > > You won't have this exact problem because the > > JaasLoginServiceRemotingServer gbean isn't in the latest version. > > > > If you wish to continue with 2.0-M6 the problem is that the > > JaasLoginServiceRemotingServer can't figure out what ip address to > > bind onto. Have you perhaps changed var/config/config- > > substitutions.properties? Or perhaps your hostnames aren't quite > > right? something seems to expect your computer to be named "testing" > > > > thanks > > david jencks > > > > On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote: > > > > > Hi! > > > > > > I jus
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Hi Rodrigo As I am also running G on a Ubuntu system (although it's 7.10) I thought I should give it a try and I get a similar problem (although I am not really reproducing yours). In my case I tried the "deploy login" command from a client also running Ubuntu from within a local network and surprisingly it failed with the following Error: Unable to connect to server at deployer:geronimo:jmx://192.168.2.1:1099 -- Connection refused to host: 127.0.0.1; nested exception is: As I am trying this via a local network connection and no firewall rules should be in the way so I should not get "connection refused" but I did so if this is suppose to work right out of the box(?) we may have some weird problem and in my case this could be related to some IPv6 problem as I found out that the rmiregistry (port 1099) was running on IPv6 netstat -plt : tcp0 0 *:www *:* LISTEN - : tcp6 0 0 *:rmiregistry *:* LISTEN - I don't know way this should be a problem (I am not a network expert) but apparently something is wrong. However as in your case from local machine it works fine. I haven't upgraded to 2.0 yet on the server, so this test has been done on G v1.1.1 and FYI all the address and port binds are the defaults (in config.xml) so G and rmiregistry should bind to all interfaces. However In your case you get "no such object in table" which to me looks like you actually got the initial connection on port 1099 but a failure in the object call (using some other port) so our problems may not be related but anyhow It seem you are not completely alone on this. You could try sniff the network traffic with Wireshark (you can do a apt-get if you don't have it already), you may whant to use some traffic filter for example "tcp port 1099 || tcp port " to minimize the noise. Sry I couldn't help you more with this, lets see what more the G devs have to say about it ? regards Peter Petersson Rodrigo Rodrigues da Silva wrote: Hi, I tried out 2.0-rc1 release (as posted by David to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could reproduce bug GERONIMO-3191, which had been considered as closed. I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a Windows Vista Machine I ran the following command: deploy --host 192.168.0.11 <http://192.168.0.11> --user system --password manager --port 1099 login which returned: Error: Unable to connect to server at deployer:geronimo:jmx://192.168.0.11 – no such object in table if I run it from the server Linux machine, it works. I haven't ever been able to access remote linux servers (specially from Eclipse) but this specific situation has been tested only on this release. I was wondering if anyone could reproduce it since I may have commited some configuration mistake. hope it helps. thanks, Rodrigo On 8/9/07, * David Jencks* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: I'd recommend trying with the about to be released unless someone finds a major problem 2.0 release you can find here http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/ <http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/> apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/ You won't have this exact problem because the JaasLoginServiceRemotingServer gbean isn't in the latest version. If you wish to continue with 2.0-M6 the problem is that the JaasLoginServiceRemotingServer can't figure out what ip address to bind onto. Have you perhaps changed var/config/config- substitutions.properties? Or perhaps your hostnames aren't quite right? something seems to expect your computer to be named "testing" thanks david jencks On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote: > Hi! > > I just download the last version of geronimo > (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server with > geronimo.sh: > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./ > geronimo.sh run > > but fails at 16%: > [> ] 16% 4s Startup failed > > The stack trace start with this log (the complete log is attached) > 7:22:37,995 ERROR [GBeanInstanceState] Error while starting; GBean is > now in the FAILED state: > abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car? > ServiceModule=org.apache.geronimo.configs/j2ee-se > curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer" > > This is my first contact with geronimo, maybe I am doing something
Re: [Fwd: Re: building geronimo-2.0-rc1]
I'm about to test it on 2.0
Do I still need the the transaction mgr manually added to the local repo or
that was just for 2.0.1? I would like to try it with a clean repo
Cheers!
Hernan
Donald Woods wrote:
This should now be fixed in Rev565885.
Should this be pulled into 2.0.1?
-Donald
Prasad Kashyap wrote:
The changes that Donald Woods is doing (svn commit: r565837) is
supposed to fix this.
However, as you can see from the latest build error, this needs to be
fixed further.
Cheers
Prasad
On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I get it
from? I don't see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
modifying plugin.xml and the pom file) works. A new release would be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
over the
released alpha-1.jar from 8/8 and my builds starting working again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
Is anyone else seeing this in geronimo-welcome.. I am building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
9)
at
org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at
org.apache.tools.ant.Project.setAntLib(Project.java:313)
at
org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at
org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
a:65)
at
org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
lassHelper.java:563)
at
groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
at
org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
143)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
Helper.java:114)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
tecodeAdapter.java:214)
at
org.codehaus.mojo.groovy.GroovyMojoSupport.ge
Re: [Fwd: Re: building geronimo-2.0-rc1]
This should now be fixed in Rev565885.
Should this be pulled into 2.0.1?
-Donald
Prasad Kashyap wrote:
The changes that Donald Woods is doing (svn commit: r565837) is
supposed to fix this.
However, as you can see from the latest build error, this needs to be
fixed further.
Cheers
Prasad
On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I get it from? I don't
see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
modifying plugin.xml and the pom file) works. A new release would be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
over the
released alpha-1.jar from 8/8 and my builds starting working again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
Is anyone else seeing this in geronimo-welcome.. I am building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
9)
at
org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at
org.apache.tools.ant.Project.setAntLib(Project.java:313)
at
org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at
org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
a:65)
at
org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
lassHelper.java:563)
at
groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
at
org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
143)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
Helper.java:114)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
tecodeAdapter.java:214)
at
org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
roovy:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
Re: Geronimo 2.0 Release suspended due to security issue found before release
At this point, I am not really sure. We can always easily move them around. If you have or can envision a lot of CLI tests, we can create a separate testsuite for it. This separate testsuite won't have to start/stop selenium server too since it is cmdline. If you want to drop it under deployment-testsuite for now, that's fine too. Cheers Prasad On 8/14/07, Donald Woods <[EMAIL PROTECTED]> wrote: > > Where were you thinking? Should we start a new subdirectory for cmdline > tests? Or could it go under deployment-testsuite? > > -Donald > > > Prasad Kashyap wrote: > > Good catch Donald. Can you please throw in a small test(s) in our > > testsuite framework so that we can catch things like this ? There are > > a lot of tests there already that can act as a template/example and > > help you with your testcase. > > > > Let me know if you need more help. > > > > Cheers > > Prasad > > > > On 8/13/07, Donald Woods <[EMAIL PROTECTED]> wrote: > >> > >> Matt Hogstrom wrote: > >>> All, > >>> > >>> Earlier today one of the Geronimo committers discovered a bug in the > >>> command line deployer where a null user / password on the deployer > >>> command line will allow a user to deploy modules to a 2.0 server. This > >>> is an unacceptable security exposure and as such we have abandoned the > >>> release of Geronimo 2.0. > >>> > >>> Donald Woods is going to open a JIRA for this issue and Hernan will > >>> create a news item on our web page. > >> GERONIMO-3404 was opened for this. > >> > >>> At this point we need to discuss how to move forward with a 2.0 release. > >>> > >>> I think we should delete the tags/2.0.0 entry and replace it with a text > >>> file that notes the svn rev of the tree before deletion. The purpose of > >>> this is to avoid anyone from picking up that source tree and using it to > >>> build a server with a known security exposure. Unless there is > >>> disagreement I'd like to do that tomorrow allowing some time for > >>> discussion. We can always put it back. > >>> > >>> There are several options for the 2.0 release: > >>> > >>> 1. Use the branches/2.0 to spin up a new release as 2.0.1. > >>> If we do this there are a number of fixes that need to be verified, > >>> We'd need to close out the SNAPSHOT releases again, or at least revisit > >>> them. > >>> Respin and re-tck a new release. > >>> > >>> 2. Take the tags/2.0.0 to create a branches/2.0.1 > >>> This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT > >>> Copy the existing tag over and apply the security fixes. Repsin and > >>> release. > >>> > >>> Personally, I vote for option 2. Based on my experience, closing out > >>> the SNAPSHOTs is and introducing little changes will cause us to restart > >>> the release process. > >> +1 on option #2. > >> > >> > >>> I'd like to hear other people's input but having done the release > >>> several times option 2 is the fastest. I think option 1 will cause us > >>> to not release until September. > >>> > >>> > >> > > > > > >
Re: [Fwd: Re: building geronimo-2.0-rc1]
The changes that Donald Woods is doing (svn commit: r565837) is
supposed to fix this.
However, as you can see from the latest build error, this needs to be
fixed further.
Cheers
Prasad
On 8/14/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> So, how is this Jedi hand waving thingy?
>
> What is the file that needs to be replaced and where do I get it from? I
> don't see any on my repo with that timestamp.
>
> What other files need to be modified
>
> Cheers!
> Hernan
>
> Anita Kulshreshtha wrote:
> > yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
> > modifying plugin.xml and the pom file) works. A new release would be
> > nice otherwise we can put it in the repo.
> >
> > Thanks
> > Anita
> >
> > --- Donald Woods <[EMAIL PROTECTED]> wrote:
> >
> >> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> >> I still had a copy of the last alpha-1-SNAPSHOT laying around
> >> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
> >> over the
> >> released alpha-1.jar from 8/8 and my builds starting working again on
> >> WinXP
> >>
> >> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
> >> fix it
> >> before we release 2.0.1?
> >>
> >>
> >>
> >> -Donald
> >>
> >> Anita Kulshreshtha wrote:
> >>> I have not been so lucky. I have tried branches/2.0.0 also. I
> >> have
> >>> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
> >> any
> >>> success (The trunk builds fine).
> >>>
> >>> Thanks
> >>> Anita
> >>>
> >>> --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I am not exactly building from geronimo-2.0-src.zip, but from
> >>>> branches\2.0.0. If that still counts as if I built from src
> >> zip... I
> >>>> have
> >>>> not run into this problem. I have tried after removing
> >>>> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> >>>> downloads a
> >>>> fresh.
> >>>>
> >>>> --vamsi
> >>>>
> >>>>
> >>>> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> >>>>>Is anyone else seeing this in geronimo-welcome.. I am building
> >>>> from
> > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> >>>>> Thanks
> >>>>> Anita
> >>>>>
> >>>>> Downloading:
> >>>>>
> >> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> >>>>> -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> >>>>> 4K downloaded
> >>>>> [INFO] [jspc:compile {execution: default}]
> >>>>> [INFO]
> >>>>>
> >
> >>>>> [ERROR] FATAL ERROR
> >>>>> [INFO]
> >>>>>
> >
> >>>>> [INFO] null
> >>>>> Illegal character in path at index 18: file:/C:/Documents and
> >>>>> Settings/Anita/.m2
> >>>>> /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> >>>>> [INFO]
> >>>>>
> >
> >>>>> [INFO] Trace
> >>>>> java.lang.IllegalArgumentException
> >>>>> at java.net.URI.create(URI.java:842)
> >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>>> Method)
> >>>>> at
> >>>>>
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >>>>> java:39)
> >>>>> at
> >>>>>
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >>>>> sorImpl.java:25)
> >>>>> at java.lang.reflect.Method.invoke(Method.java:585)
> >>>>> at
> >>>>> org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> >>>>> at
> >>>>>
> >> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> >>>>> 9)
> >>>>>
Re: Geronimo 2.0 Release suspended due to security issue found before release
Where were you thinking? Should we start a new subdirectory for cmdline tests? Or could it go under deployment-testsuite? -Donald Prasad Kashyap wrote: > Good catch Donald. Can you please throw in a small test(s) in our > testsuite framework so that we can catch things like this ? There are > a lot of tests there already that can act as a template/example and > help you with your testcase. > > Let me know if you need more help. > > Cheers > Prasad > > On 8/13/07, Donald Woods <[EMAIL PROTECTED]> wrote: >> >> Matt Hogstrom wrote: >>> All, >>> >>> Earlier today one of the Geronimo committers discovered a bug in the >>> command line deployer where a null user / password on the deployer >>> command line will allow a user to deploy modules to a 2.0 server. This >>> is an unacceptable security exposure and as such we have abandoned the >>> release of Geronimo 2.0. >>> >>> Donald Woods is going to open a JIRA for this issue and Hernan will >>> create a news item on our web page. >> GERONIMO-3404 was opened for this. >> >>> At this point we need to discuss how to move forward with a 2.0 release. >>> >>> I think we should delete the tags/2.0.0 entry and replace it with a text >>> file that notes the svn rev of the tree before deletion. The purpose of >>> this is to avoid anyone from picking up that source tree and using it to >>> build a server with a known security exposure. Unless there is >>> disagreement I'd like to do that tomorrow allowing some time for >>> discussion. We can always put it back. >>> >>> There are several options for the 2.0 release: >>> >>> 1. Use the branches/2.0 to spin up a new release as 2.0.1. >>> If we do this there are a number of fixes that need to be verified, >>> We'd need to close out the SNAPSHOT releases again, or at least revisit >>> them. >>> Respin and re-tck a new release. >>> >>> 2. Take the tags/2.0.0 to create a branches/2.0.1 >>> This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT >>> Copy the existing tag over and apply the security fixes. Repsin and >>> release. >>> >>> Personally, I vote for option 2. Based on my experience, closing out >>> the SNAPSHOTs is and introducing little changes will cause us to restart >>> the release process. >> +1 on option #2. >> >> >>> I'd like to hear other people's input but having done the release >>> several times option 2 is the fastest. I think option 1 will cause us >>> to not release until September. >>> >>> >> > >
Re: [Fwd: Re: building geronimo-2.0-rc1]
I just checked it into the branches/2.0/repository and updated the build to
install and use it. If all looks well, I'll copy it into branches/2.0.1, too
-Donald
Hernan Cunico wrote:
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I get it from? I
don't see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
modifying plugin.xml and the pom file) works. A new release would be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
over the
released alpha-1.jar from 8/8 and my builds starting working again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
fix it before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
Is anyone else seeing this in geronimo-welcome.. I am building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
9)
at
org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at
org.apache.tools.ant.Project.setAntLib(Project.java:313)
at
org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at
org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
a:65)
at
org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
lassHelper.java:563)
at
groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
at
org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
143)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
Helper.java:114)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
tecodeAdapter.java:214)
at
org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
roovy:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke
Re: [Fwd: Re: building geronimo-2.0-rc1]
So, how is this Jedi hand waving thingy?
What is the file that needs to be replaced and where do I get it from? I don't
see any on my repo with that timestamp.
What other files need to be modified
Cheers!
Hernan
Anita Kulshreshtha wrote:
yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
modifying plugin.xml and the pom file) works. A new release would be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
over the
released alpha-1.jar from 8/8 and my builds starting working again on
WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
Is anyone else seeing this in geronimo-welcome.. I am building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
9)
at
org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at
org.apache.tools.ant.Project.setAntLib(Project.java:313)
at
org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at
org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
a:65)
at
org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
lassHelper.java:563)
at
groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
at
org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
143)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
Helper.java:114)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
tecodeAdapter.java:214)
at
org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
roovy:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Ref
lectionMetaMethod.java:52)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassH
elp
Re: Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Have you verified there is no firewall running on your Linux box and that the Windows machine can ping the Linux box with the IP address you are using? -Donald Rodrigo Rodrigues da Silva wrote: Hi, I tried out 2.0-rc1 release (as posted by David to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>) and could reproduce bug GERONIMO-3191, which had been considered as closed. I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a Windows Vista Machine I ran the following command: deploy --host 192.168.0.11 <http://192.168.0.11> --user system --password manager --port 1099 login which returned: Error: Unable to connect to server at deployer:geronimo:jmx://192.168.0.11 – no such object in table if I run it from the server Linux machine, it works. I haven't ever been able to access remote linux servers (specially from Eclipse) but this specific situation has been tested only on this release. I was wondering if anyone could reproduce it since I may have commited some configuration mistake. hope it helps. thanks, Rodrigo On 8/9/07, * David Jencks* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: I'd recommend trying with the about to be released unless someone finds a major problem 2.0 release you can find here http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/ <http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/> apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/ You won't have this exact problem because the JaasLoginServiceRemotingServer gbean isn't in the latest version. If you wish to continue with 2.0-M6 the problem is that the JaasLoginServiceRemotingServer can't figure out what ip address to bind onto. Have you perhaps changed var/config/config- substitutions.properties? Or perhaps your hostnames aren't quite right? something seems to expect your computer to be named "testing" thanks david jencks On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote: > Hi! > > I just download the last version of geronimo > (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server with > geronimo.sh: > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./ > geronimo.sh run > > but fails at 16%: > [> ] 16% 4s Startup failed > > The stack trace start with this log (the complete log is attached) > 7:22:37,995 ERROR [GBeanInstanceState] Error while starting; GBean is > now in the FAILED state: > abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car? > ServiceModule=org.apache.geronimo.configs/j2ee-se > curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer" > > This is my first contact with geronimo, maybe I am doing something > wrong. > > Some useful information of my java environment: > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6 /bin $ echo > $JAVA_HOME > /home/fsousa/opt/java/jdk1.5.0_12 > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java -version > java version "1.5.0_12" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) > Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) > > -- > Filipe Sousa > -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver smime.p7s Description: S/MIME Cryptographic Signature
Re: Geronimo 2.0 Release suspended due to security issue found before release
Good catch Donald. Can you please throw in a small test(s) in our testsuite framework so that we can catch things like this ? There are a lot of tests there already that can act as a template/example and help you with your testcase. Let me know if you need more help. Cheers Prasad On 8/13/07, Donald Woods <[EMAIL PROTECTED]> wrote: > > > Matt Hogstrom wrote: > > All, > > > > Earlier today one of the Geronimo committers discovered a bug in the > > command line deployer where a null user / password on the deployer > > command line will allow a user to deploy modules to a 2.0 server. This > > is an unacceptable security exposure and as such we have abandoned the > > release of Geronimo 2.0. > > > > Donald Woods is going to open a JIRA for this issue and Hernan will > > create a news item on our web page. > > GERONIMO-3404 was opened for this. > > > > > At this point we need to discuss how to move forward with a 2.0 release. > > > > I think we should delete the tags/2.0.0 entry and replace it with a text > > file that notes the svn rev of the tree before deletion. The purpose of > > this is to avoid anyone from picking up that source tree and using it to > > build a server with a known security exposure. Unless there is > > disagreement I'd like to do that tomorrow allowing some time for > > discussion. We can always put it back. > > > > There are several options for the 2.0 release: > > > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. > > If we do this there are a number of fixes that need to be verified, > > We'd need to close out the SNAPSHOT releases again, or at least revisit > > them. > > Respin and re-tck a new release. > > > > 2. Take the tags/2.0.0 to create a branches/2.0.1 > > This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT > > Copy the existing tag over and apply the security fixes. Repsin and > > release. > > > > Personally, I vote for option 2. Based on my experience, closing out > > the SNAPSHOTs is and introducing little changes will cause us to restart > > the release process. > > +1 on option #2. > > > > > > I'd like to hear other people's input but having done the release > > several times option 2 is the fastest. I think option 1 will cause us > > to not release until September. > > > > > >
Can't remote access geronimo 2.0 on Linux (GERONIMO-3191)
Hi, I tried out 2.0-rc1 release (as posted by David to [EMAIL PROTECTED]) and could reproduce bug GERONIMO-3191, which had been considered as closed. I have a Ubuntu Linux 7.04 with sun-jdk-1.5.0 running geronimo. From a Windows Vista Machine I ran the following command: deploy --host 192.168.0.11 --user system --password manager --port 1099 login which returned: Error: Unable to connect to server at deployer:geronimo:jmx://192.168.0.11 – no such object in table if I run it from the server Linux machine, it works. I haven't ever been able to access remote linux servers (specially from Eclipse) but this specific situation has been tested only on this release. I was wondering if anyone could reproduce it since I may have commited some configuration mistake. hope it helps. thanks, Rodrigo On 8/9/07, David Jencks <[EMAIL PROTECTED]> wrote: > > I'd recommend trying with the about to be released unless someone > finds a major problem 2.0 release you can find here > http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/ > <http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/> > apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/ > > You won't have this exact problem because the > JaasLoginServiceRemotingServer gbean isn't in the latest version. > > If you wish to continue with 2.0-M6 the problem is that the > JaasLoginServiceRemotingServer can't figure out what ip address to > bind onto. Have you perhaps changed var/config/config- > substitutions.properties? Or perhaps your hostnames aren't quite > right? something seems to expect your computer to be named "testing" > > thanks > david jencks > > On Aug 9, 2007, at 9:39 AM, Filipe Sousa wrote: > > > Hi! > > > > I just download the last version of geronimo > > (geronimo-tomcat6-jee5-2.0-M6) and I'm trying to start the server with > > geronimo.sh: > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ ./ > > geronimo.sh run > > > > but fails at 16%: > > [> ] 16% 4s Startup failed > > > > The stack trace start with this log (the complete log is attached) > > 7:22:37,995 ERROR [GBeanInstanceState] Error while starting; GBean is > > now in the FAILED state: > > abstractName="org.apache.geronimo.configs/j2ee-security/2.0-M6/car? > > ServiceModule=org.apache.geronimo.configs/j2ee-se > > curity/2.0-M6/car,j2eeType=GBean,name=JaasLoginServiceRemotingServer" > > > > This is my first contact with geronimo, maybe I am doing something > > wrong. > > > > Some useful information of my java environment: > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ echo > > $JAVA_HOME > > /home/fsousa/opt/java/jdk1.5.0_12 > > [EMAIL PROTECTED] ~/opt/geronimo-tomcat6-jee5-2.0-M6/bin $ java -version > > java version "1.5.0_12" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) > > Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode) > > > > -- > > Filipe Sousa > > > > -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver -- Rodrigo Rodrigues da Silva Engenharia de Computação - Coop8 http://www.coop8.rg.com.br Grêmio Politécnico - Gestão Colabora http://www.gremio.poli.usp.br "Não importa como morre o home, importa como vive." Carijó, velho do rio. "To the person with only a hammer, everything looks like a nail." bussdriver
Re: Geronimo 2.0 Release suspended due to security issue found before release
Verified that the fixes address the security bug Donald has identified. No
regression is observed in case of GERONIMO-2266 and GERONIMO-2267. I
suggest others verify any scenarios they can think of for possible
regression.
Vamsi
On 8/14/07, David Jencks <[EMAIL PROTECTED]> wrote:
>
> I've now fixed GERONIMO-3407 in trunk, rev 565657. I added new
> methods to ContextManager and removed direct use of LoginContext.
> Among other things this may make implementing jaspi slightly easier.
>
> New methods are:
> public static LoginContext login(String realm, CallbackHandler
> callbackHandler) throws LoginException {
> Subject subject = new Subject();
> LoginContext loginContext = new LoginContext(realm, subject,
> callbackHandler);
> loginContext.login();
> SubjectId id = ContextManager.registerSubject(subject);
> IdentificationPrincipal principal = new
> IdentificationPrincipal(id);
> subject.getPrincipals().add(principal);
> return loginContext;
> }
>
> public static void logout(LoginContext loginContext) throws
> LoginException {
> Subject subject = loginContext.getSubject();
> ContextManager.unregisterSubject(subject);
> loginContext.logout();
> }
>
>
> This revision needs to be ported to branches/2.0 and wherever 2.0.1 is.
>
> thanks
> david jencks
>
> On Aug 13, 2007, at 6:27 PM, David Jencks wrote:
>
> > I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev
> > 565599. It might be a good idea for this to get a review before we
> > port it to branches/2.0 and possibly branches/2.0.x.
> >
> > I haven't decided how to fix GERONIMO-3407 yet, and could be talked
> > out of it for 2.0.1. The problem would manifest itself as geronimo
> > not working if anyone tried to use a login module with REQUISITE
> > or (I think) SUFFICIENT flags. I don't think there's any security
> > exposure, it just that you effectively couldn't log in with such a
> > login configuration.
> >
> > On a completely unrelated issue I can't build modules/geronimo-axis-
> > builder in trunk as part of the main build, I get a complaint from
> > javac. I don't have problems building it by itself. Anyone else
> > see this?
> >
> > thanks
> > david jencks
> > On Aug 13, 2007, at 5:03 PM, David Jencks wrote:
> >
> >> So before we all jump onto option 2 maybe we should consider just
> >> how big a change this set of bugs is causing and comparatively how
> >> much branches/2.0 has changed since 2.0.0 was cut.
> >>
> >> It looks like there have been about 15 commits to branches/2.0
> >> that aren't version changes, many of them simple fixes that make
> >> things like the plugin installer actually usable. On the other
> >> hand so far I've modified 16 files working on this security fix
> >> (admittedly most of them either simple fixes and/or documentation)
> >> and still have to figure out a solution to
> >> SubjectRegistrationLoginModule not working (GERONIMO-3407)
> >>
> >> If we go with (2) I would like some of the changes to branches/
> >> 2.0 to be merged in, especially rev 563592. I think r563662 and
> >> r563782 would be good also.
> >>
> >> thanks
> >> david jencks
> >>
> >> On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote:
> >>
> >>> All,
> >>>
> >>> Earlier today one of the Geronimo committers discovered a bug in
> >>> the command line deployer where a null user / password on the
> >>> deployer command line will allow a user to deploy modules to a
> >>> 2.0 server. This is an unacceptable security exposure and as
> >>> such we have abandoned the release of Geronimo 2.0.
> >>>
> >>> Donald Woods is going to open a JIRA for this issue and Hernan
> >>> will create a news item on our web page.
> >>>
> >>> At this point we need to discuss how to move forward with a 2.0
> >>> release.
> >>>
> >>> I think we should delete the tags/2.0.0 entry and replace it with
> >>> a text file that notes the svn rev of the tree before deletion.
> >>> The purpose of this is to avoid anyone from picking up that
> >>> source tree and using it to build a server with a known security
> >>> exposure. Unless there is disagreement I'd like to do that
> >>> tomorrow allowing some time for discussion. We can always put it
> >>&g
Re: Geronimo 2.0 Release suspended due to security issue found before release
I've now fixed GERONIMO-3407 in trunk, rev 565657. I added new
methods to ContextManager and removed direct use of LoginContext.
Among other things this may make implementing jaspi slightly easier.
New methods are:
public static LoginContext login(String realm, CallbackHandler
callbackHandler) throws LoginException {
Subject subject = new Subject();
LoginContext loginContext = new LoginContext(realm, subject,
callbackHandler);
loginContext.login();
SubjectId id = ContextManager.registerSubject(subject);
IdentificationPrincipal principal = new
IdentificationPrincipal(id);
subject.getPrincipals().add(principal);
return loginContext;
}
public static void logout(LoginContext loginContext) throws
LoginException {
Subject subject = loginContext.getSubject();
ContextManager.unregisterSubject(subject);
loginContext.logout();
}
This revision needs to be ported to branches/2.0 and wherever 2.0.1 is.
thanks
david jencks
On Aug 13, 2007, at 6:27 PM, David Jencks wrote:
I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev
565599. It might be a good idea for this to get a review before we
port it to branches/2.0 and possibly branches/2.0.x.
I haven't decided how to fix GERONIMO-3407 yet, and could be talked
out of it for 2.0.1. The problem would manifest itself as geronimo
not working if anyone tried to use a login module with REQUISITE
or (I think) SUFFICIENT flags. I don't think there's any security
exposure, it just that you effectively couldn't log in with such a
login configuration.
On a completely unrelated issue I can't build modules/geronimo-axis-
builder in trunk as part of the main build, I get a complaint from
javac. I don't have problems building it by itself. Anyone else
see this?
thanks
david jencks
On Aug 13, 2007, at 5:03 PM, David Jencks wrote:
So before we all jump onto option 2 maybe we should consider just
how big a change this set of bugs is causing and comparatively how
much branches/2.0 has changed since 2.0.0 was cut.
It looks like there have been about 15 commits to branches/2.0
that aren't version changes, many of them simple fixes that make
things like the plugin installer actually usable. On the other
hand so far I've modified 16 files working on this security fix
(admittedly most of them either simple fixes and/or documentation)
and still have to figure out a solution to
SubjectRegistrationLoginModule not working (GERONIMO-3407)
If we go with (2) I would like some of the changes to branches/
2.0 to be merged in, especially rev 563592. I think r563662 and
r563782 would be good also.
thanks
david jencks
On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote:
All,
Earlier today one of the Geronimo committers discovered a bug in
the command line deployer where a null user / password on the
deployer command line will allow a user to deploy modules to a
2.0 server. This is an unacceptable security exposure and as
such we have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
will create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0
release.
I think we should delete the tags/2.0.0 entry and replace it with
a text file that notes the svn rev of the tree before deletion.
The purpose of this is to avoid anyone from picking up that
source tree and using it to build a server with a known security
exposure. Unless there is disagreement I'd like to do that
tomorrow allowing some time for discussion. We can always put it
back.
There are several options for the 2.0 release:
1. Use the branches/2.0 to spin up a new release as 2.0.1.
If we do this there are a number of fixes that need to be
verified, We'd need to close out the SNAPSHOT releases again, or
at least revisit them.
Respin and re-tck a new release.
2. Take the tags/2.0.0 to create a branches/2.0.1
This would mean that we need to update branches/2.0 to 2.0.2-
SNAPSHOT
Copy the existing tag over and apply the security fixes.
Repsin and release.
Personally, I vote for option 2. Based on my experience, closing
out the SNAPSHOTs is and introducing little changes will cause us
to restart the release process.
I'd like to hear other people's input but having done the release
several times option 2 is the fastest. I think option 1 will
cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
On 8/14/07, David Jencks <[EMAIL PROTECTED]> wrote: > > I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev > 565599. It might be a good idea for this to get a review before we > port it to branches/2.0 and possibly branches/2.0.x. We may also want to make sure GERONIMO-2266, GERONIMO-2267 and any similar ones do not recur. I haven't decided how to fix GERONIMO-3407 yet, and could be talked > out of it for 2.0.1. The problem would manifest itself as geronimo > not working if anyone tried to use a login module with REQUISITE or > (I think) SUFFICIENT flags. I don't think there's any security > exposure, it just that you effectively couldn't log in with such a > login configuration. > > On a completely unrelated issue I can't build modules/geronimo-axis- > builder in trunk as part of the main build, I get a complaint from > javac. I don't have problems building it by itself. Anyone else see > this? > > thanks > david jencks > On Aug 13, 2007, at 5:03 PM, David Jencks wrote: > > > So before we all jump onto option 2 maybe we should consider just > > how big a change this set of bugs is causing and comparatively how > > much branches/2.0 has changed since 2.0.0 was cut. > > > > It looks like there have been about 15 commits to branches/2.0 that > > aren't version changes, many of them simple fixes that make things > > like the plugin installer actually usable. On the other hand so > > far I've modified 16 files working on this security fix (admittedly > > most of them either simple fixes and/or documentation) and still > > have to figure out a solution to SubjectRegistrationLoginModule not > > working (GERONIMO-3407) > > > > If we go with (2) I would like some of the changes to branches/2.0 > > to be merged in, especially rev 563592. I think r563662 and > > r563782 would be good also. > > > > thanks > > david jencks > > > > On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote: > > > >> All, > >> > >> Earlier today one of the Geronimo committers discovered a bug in > >> the command line deployer where a null user / password on the > >> deployer command line will allow a user to deploy modules to a 2.0 > >> server. This is an unacceptable security exposure and as such we > >> have abandoned the release of Geronimo 2.0. > >> > >> Donald Woods is going to open a JIRA for this issue and Hernan > >> will create a news item on our web page. > >> > >> At this point we need to discuss how to move forward with a 2.0 > >> release. > >> > >> I think we should delete the tags/2.0.0 entry and replace it with > >> a text file that notes the svn rev of the tree before deletion. > >> The purpose of this is to avoid anyone from picking up that source > >> tree and using it to build a server with a known security > >> exposure. Unless there is disagreement I'd like to do that > >> tomorrow allowing some time for discussion. We can always put it > >> back. > >> > >> There are several options for the 2.0 release: > >> > >> 1. Use the branches/2.0 to spin up a new release as 2.0.1. > >> If we do this there are a number of fixes that need to be > >> verified, We'd need to close out the SNAPSHOT releases again, or > >> at least revisit them. > >> Respin and re-tck a new release. > >> > >> 2. Take the tags/2.0.0 to create a branches/2.0.1 > >> This would mean that we need to update branches/2.0 to 2.0.2- > >> SNAPSHOT > >> Copy the existing tag over and apply the security fixes. Repsin > >> and release. > >> > >> Personally, I vote for option 2. Based on my experience, closing > >> out the SNAPSHOTs is and introducing little changes will cause us > >> to restart the release process. > >> > >> I'd like to hear other people's input but having done the release > >> several times option 2 is the fastest. I think option 1 will > >> cause us to not release until September. > > > >
Re: Geronimo 2.0 Release suspended due to security issue found before release
David, Though there are a few other minor fixes (that may not come in the way of TCK, for e.g. R565355) that I would have wanted in 2.0.1, I felt that this may not be the right time to bring up those as we may not "any" additional delays in getting 2.0.1 out, perhaps we may have to think about a 2.0.2 out of the current branches\2.0 and save these for then. As always, it is RMs call. Vamsi On 8/14/07, David Jencks <[EMAIL PROTECTED]> wrote: > > So before we all jump onto option 2 maybe we should consider just how > big a change this set of bugs is causing and comparatively how much > branches/2.0 has changed since 2.0.0 was cut. > > It looks like there have been about 15 commits to branches/2.0 that > aren't version changes, many of them simple fixes that make things > like the plugin installer actually usable. On the other hand so far > I've modified 16 files working on this security fix (admittedly most > of them either simple fixes and/or documentation) and still have to > figure out a solution to SubjectRegistrationLoginModule not working > (GERONIMO-3407) > > If we go with (2) I would like some of the changes to branches/2.0 > to be merged in, especially rev 563592. I think r563662 and r563782 > would be good also. > > thanks > david jencks > > On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote: > > > All, > > > > Earlier today one of the Geronimo committers discovered a bug in > > the command line deployer where a null user / password on the > > deployer command line will allow a user to deploy modules to a 2.0 > > server. This is an unacceptable security exposure and as such we > > have abandoned the release of Geronimo 2.0. > > > > Donald Woods is going to open a JIRA for this issue and Hernan will > > create a news item on our web page. > > > > At this point we need to discuss how to move forward with a 2.0 > > release. > > > > I think we should delete the tags/2.0.0 entry and replace it with a > > text file that notes the svn rev of the tree before deletion. The > > purpose of this is to avoid anyone from picking up that source tree > > and using it to build a server with a known security exposure. > > Unless there is disagreement I'd like to do that tomorrow allowing > > some time for discussion. We can always put it back. > > > > There are several options for the 2.0 release: > > > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. > > If we do this there are a number of fixes that need to be > > verified, We'd need to close out the SNAPSHOT releases again, or at > > least revisit them. > > Respin and re-tck a new release. > > > > 2. Take the tags/2.0.0 to create a branches/2.0.1 > > This would mean that we need to update branches/2.0 to 2.0.2- > > SNAPSHOT > > Copy the existing tag over and apply the security fixes. Repsin > > and release. > > > > Personally, I vote for option 2. Based on my experience, closing > > out the SNAPSHOTs is and introducing little changes will cause us > > to restart the release process. > > > > I'd like to hear other people's input but having done the release > > several times option 2 is the fastest. I think option 1 will cause > > us to not release until September. > >
Re: [Fwd: Re: building geronimo-2.0-rc1]
yup, copying alpha-1-20070806.170854-1.jar over alpha-1 (and
modifying plugin.xml and the pom file) works. A new release would be
nice otherwise we can put it in the repo.
Thanks
Anita
--- Donald Woods <[EMAIL PROTECTED]> wrote:
> The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
> I still had a copy of the last alpha-1-SNAPSHOT laying around
> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it
> over the
> released alpha-1.jar from 8/8 and my builds starting working again on
> WinXP
>
> Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to
> fix it
> before we release 2.0.1?
>
>
>
> -Donald
>
> Anita Kulshreshtha wrote:
> > I have not been so lucky. I have tried branches/2.0.0 also. I
> have
> > tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
> any
> > success (The trunk builds fine).
> >
> > Thanks
> > Anita
> >
> > --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> >
> >> I am not exactly building from geronimo-2.0-src.zip, but from
> >> branches\2.0.0. If that still counts as if I built from src
> zip... I
> >> have
> >> not run into this problem. I have tried after removing
> >> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> >> downloads a
> >> fresh.
> >>
> >> --vamsi
> >>
> >>
> >> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> >>>Is anyone else seeing this in geronimo-welcome.. I am building
> >> from
> >
>
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> >>> Thanks
> >>> Anita
> >>>
> >>> Downloading:
> >>>
> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> >>> -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> >>> 4K downloaded
> >>> [INFO] [jspc:compile {execution: default}]
> >>> [INFO]
> >>>
> >
>
> >>> [ERROR] FATAL ERROR
> >>> [INFO]
> >>>
> >
>
> >>> [INFO] null
> >>> Illegal character in path at index 18: file:/C:/Documents and
> >>> Settings/Anita/.m2
> >>> /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> >>> [INFO]
> >>>
> >
>
> >>> [INFO] Trace
> >>> java.lang.IllegalArgumentException
> >>> at java.net.URI.create(URI.java:842)
> >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> Method)
> >>> at
> >>>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >>> java:39)
> >>> at
> >>>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >>> sorImpl.java:25)
> >>> at java.lang.reflect.Method.invoke(Method.java:585)
> >>> at
> >>> org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> >>> at
> >>>
> >>
> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> >>> 9)
> >>> at
> >>>
> org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> >>> at
> org.apache.tools.ant.Project.setAntLib(Project.java:313)
> >>> at
> >>> org.apache.tools.ant.Project.initProperties(Project.java:309)
> >>> at org.apache.tools.ant.Project.init(Project.java:295)
> >>> at
> >>>
> >>
> org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> >>> a:65)
> >>> at
> >>>
> org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> >>> at
> >>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> >> Method)
> >>> at
> >>>
> >>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> >>> orAccessorImpl.java:39)
> >>> at
> >>>
> >>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> >>> onstructorAccessorImpl.java:27)
> >>> at
> >>> java.lang.reflect.Constructor.newInstance(Constructo
Re: Geronimo 2.0 Release suspended due to security issue found before release
On Aug 13, 2007, at 9:27 PM, David Jencks wrote: I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev 565599. It might be a good idea for this to get a review before we port it to branches/2.0 and possibly branches/2.0.x. I'm looking things over now... May take me a bit... Easy to get this logic a bit twisted... I haven't decided how to fix GERONIMO-3407 yet, and could be talked out of it for 2.0.1. The problem would manifest itself as geronimo not working if anyone tried to use a login module with REQUISITE or (I think) SUFFICIENT flags. I don't think there's any security exposure, it just that you effectively couldn't log in with such a login configuration. Hmm. I was thinking the big issue was with the SUFFICIENT flag -- if a SUFFICIENT LoginModule succeeds, authentication does not proceed down the chain of LoginModules. Thus the SubjectLoginRegistrationModule might not be invoked. Likewise, if a REQUISITE LoginModule fails, the SubjectLoginRegistrationModule wouldn't be invoked. Since the login won't succeed, this doesn't seem like a big issue. Am I missing something? On a completely unrelated issue I can't build modules/geronimo-axis- builder in trunk as part of the main build, I get a complaint from javac. I don't have problems building it by itself. Anyone else see this? I'm not having a problem... --kevan
Re: Geronimo 2.0 Release suspended due to security issue found before release
I'll go ahead and update branches/2.0 to 2.0.2-SNAPSHOT as this needs to be done regardless. On Aug 13, 2007, at 8:03 PM, David Jencks wrote: So before we all jump onto option 2 maybe we should consider just how big a change this set of bugs is causing and comparatively how much branches/2.0 has changed since 2.0.0 was cut. It looks like there have been about 15 commits to branches/2.0 that aren't version changes, many of them simple fixes that make things like the plugin installer actually usable. On the other hand so far I've modified 16 files working on this security fix (admittedly most of them either simple fixes and/or documentation) and still have to figure out a solution to SubjectRegistrationLoginModule not working (GERONIMO-3407) If we go with (2) I would like some of the changes to branches/2.0 to be merged in, especially rev 563592. I think r563662 and r563782 would be good also. thanks david jencks On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2- SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 to option 2. Let's get 2.0.1 out of the door ASAP. Cheers Prasad On 8/13/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > All, > > Earlier today one of the Geronimo committers discovered a bug in the > command line deployer where a null user / password on the deployer > command line will allow a user to deploy modules to a 2.0 server. > This is an unacceptable security exposure and as such we have > abandoned the release of Geronimo 2.0. > > Donald Woods is going to open a JIRA for this issue and Hernan will > create a news item on our web page. > > At this point we need to discuss how to move forward with a 2.0 release. > > I think we should delete the tags/2.0.0 entry and replace it with a > text file that notes the svn rev of the tree before deletion. The > purpose of this is to avoid anyone from picking up that source tree > and using it to build a server with a known security exposure. > Unless there is disagreement I'd like to do that tomorrow allowing > some time for discussion. We can always put it back. > > There are several options for the 2.0 release: > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. >If we do this there are a number of fixes that need to be > verified, We'd need to close out the SNAPSHOT releases again, or at > least revisit them. >Respin and re-tck a new release. > > 2. Take the tags/2.0.0 to create a branches/2.0.1 >This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT >Copy the existing tag over and apply the security fixes. Repsin > and release. > > Personally, I vote for option 2. Based on my experience, closing out > the SNAPSHOTs is and introducing little changes will cause us to > restart the release process. > > I'd like to hear other people's input but having done the release > several times option 2 is the fastest. I think option 1 will cause > us to not release until September. >
Re: Geronimo 2.0 Release suspended due to security issue found before release
I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev 565599. It might be a good idea for this to get a review before we port it to branches/2.0 and possibly branches/2.0.x. I haven't decided how to fix GERONIMO-3407 yet, and could be talked out of it for 2.0.1. The problem would manifest itself as geronimo not working if anyone tried to use a login module with REQUISITE or (I think) SUFFICIENT flags. I don't think there's any security exposure, it just that you effectively couldn't log in with such a login configuration. On a completely unrelated issue I can't build modules/geronimo-axis- builder in trunk as part of the main build, I get a complaint from javac. I don't have problems building it by itself. Anyone else see this? thanks david jencks On Aug 13, 2007, at 5:03 PM, David Jencks wrote: So before we all jump onto option 2 maybe we should consider just how big a change this set of bugs is causing and comparatively how much branches/2.0 has changed since 2.0.0 was cut. It looks like there have been about 15 commits to branches/2.0 that aren't version changes, many of them simple fixes that make things like the plugin installer actually usable. On the other hand so far I've modified 16 files working on this security fix (admittedly most of them either simple fixes and/or documentation) and still have to figure out a solution to SubjectRegistrationLoginModule not working (GERONIMO-3407) If we go with (2) I would like some of the changes to branches/2.0 to be merged in, especially rev 563592. I think r563662 and r563782 would be good also. thanks david jencks On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2- SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
Matt, We could at least release/publish the transaction and connector bits, right? Jarek On 8/13/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > All, > > Earlier today one of the Geronimo committers discovered a bug in the > command line deployer where a null user / password on the deployer > command line will allow a user to deploy modules to a 2.0 server. > This is an unacceptable security exposure and as such we have > abandoned the release of Geronimo 2.0. > > Donald Woods is going to open a JIRA for this issue and Hernan will > create a news item on our web page. > > At this point we need to discuss how to move forward with a 2.0 release. > > I think we should delete the tags/2.0.0 entry and replace it with a > text file that notes the svn rev of the tree before deletion. The > purpose of this is to avoid anyone from picking up that source tree > and using it to build a server with a known security exposure. > Unless there is disagreement I'd like to do that tomorrow allowing > some time for discussion. We can always put it back. > > There are several options for the 2.0 release: > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. >If we do this there are a number of fixes that need to be > verified, We'd need to close out the SNAPSHOT releases again, or at > least revisit them. >Respin and re-tck a new release. > > 2. Take the tags/2.0.0 to create a branches/2.0.1 >This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT >Copy the existing tag over and apply the security fixes. Repsin > and release. > > Personally, I vote for option 2. Based on my experience, closing out > the SNAPSHOTs is and introducing little changes will cause us to > restart the release process. > > I'd like to hear other people's input but having done the release > several times option 2 is the fastest. I think option 1 will cause > us to not release until September. >
Re: Geronimo 2.0 Release suspended due to security issue found before release
So before we all jump onto option 2 maybe we should consider just how big a change this set of bugs is causing and comparatively how much branches/2.0 has changed since 2.0.0 was cut. It looks like there have been about 15 commits to branches/2.0 that aren't version changes, many of them simple fixes that make things like the plugin installer actually usable. On the other hand so far I've modified 16 files working on this security fix (admittedly most of them either simple fixes and/or documentation) and still have to figure out a solution to SubjectRegistrationLoginModule not working (GERONIMO-3407) If we go with (2) I would like some of the changes to branches/2.0 to be merged in, especially rev 563592. I think r563662 and r563782 would be good also. thanks david jencks On Aug 13, 2007, at 1:59 PM, Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2- SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 to option #2 Cheers! Anita --- Matt Hogstrom <[EMAIL PROTECTED]> wrote: > All, > > Earlier today one of the Geronimo committers discovered a bug in the > > command line deployer where a null user / password on the deployer > command line will allow a user to deploy modules to a 2.0 server. > This is an unacceptable security exposure and as such we have > abandoned the release of Geronimo 2.0. > > Donald Woods is going to open a JIRA for this issue and Hernan will > create a news item on our web page. > > At this point we need to discuss how to move forward with a 2.0 > release. > > I think we should delete the tags/2.0.0 entry and replace it with a > text file that notes the svn rev of the tree before deletion. The > purpose of this is to avoid anyone from picking up that source tree > and using it to build a server with a known security exposure. > Unless there is disagreement I'd like to do that tomorrow allowing > some time for discussion. We can always put it back. > > There are several options for the 2.0 release: > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. >If we do this there are a number of fixes that need to be > verified, We'd need to close out the SNAPSHOT releases again, or at > least revisit them. >Respin and re-tck a new release. > > 2. Take the tags/2.0.0 to create a branches/2.0.1 >This would mean that we need to update branches/2.0 to > 2.0.2-SNAPSHOT >Copy the existing tag over and apply the security fixes. Repsin > and release. > > Personally, I vote for option 2. Based on my experience, closing out > > the SNAPSHOTs is and introducing little changes will cause us to > restart the release process. > > I'd like to hear other people's input but having done the release > several times option 2 is the fastest. I think option 1 will cause > us to not release until September. > Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
Re: Geronimo 2.0 Release suspended due to security issue found before release
On Aug 13, 2007, at 4:59 PM, Matt Hogstrom wrote: 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2- SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. Agreed. --kevan
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 to option 2 Joe Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
Here is the link to the dev site home page with the latest update http://cwiki.apache.org/GMOxSITE/ within the next hour geronimo.apache.org should get updated. Cheers! Hernan Hernan Cunico wrote: +1 for option 2, it seems the quickest one. I just put the "News" out, it takes some time to get propagated. Cheers! Hernan Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 for option 2, it seems the quickest one. I just put the "News" out, it takes some time to get propagated. Cheers! Hernan Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
Re: Geronimo 2.0 Release suspended due to security issue found before release
On Aug 13, 2007, at 4:59 PM, Matt Hogstrom wrote: 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2- SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. +1 for option 2 Best wishes, Paul
Re: Geronimo 2.0 Release suspended due to security issue found before release
Matt Hogstrom wrote: All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. GERONIMO-3404 was opened for this. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. +1 on option #2. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September. smime.p7s Description: S/MIME Cryptographic Signature
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 for option 2
Re: Geronimo 2.0 Release suspended due to security issue found before release
+1 for option 2. Jarek On 8/13/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > All, > > Earlier today one of the Geronimo committers discovered a bug in the > command line deployer where a null user / password on the deployer > command line will allow a user to deploy modules to a 2.0 server. > This is an unacceptable security exposure and as such we have > abandoned the release of Geronimo 2.0. > > Donald Woods is going to open a JIRA for this issue and Hernan will > create a news item on our web page. > > At this point we need to discuss how to move forward with a 2.0 release. > > I think we should delete the tags/2.0.0 entry and replace it with a > text file that notes the svn rev of the tree before deletion. The > purpose of this is to avoid anyone from picking up that source tree > and using it to build a server with a known security exposure. > Unless there is disagreement I'd like to do that tomorrow allowing > some time for discussion. We can always put it back. > > There are several options for the 2.0 release: > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. >If we do this there are a number of fixes that need to be > verified, We'd need to close out the SNAPSHOT releases again, or at > least revisit them. >Respin and re-tck a new release. > > 2. Take the tags/2.0.0 to create a branches/2.0.1 >This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT >Copy the existing tag over and apply the security fixes. Repsin > and release. > > Personally, I vote for option 2. Based on my experience, closing out > the SNAPSHOTs is and introducing little changes will cause us to > restart the release process. > > I'd like to hear other people's input but having done the release > several times option 2 is the fastest. I think option 1 will cause > us to not release until September. >
Re: Geronimo 2.0 Release suspended due to security issue found before release
At this point, we will want to get a release out fast and address only those issues (like the security bug Donald has found and hopefully only this) that are blocker. +1 to option 2, create branches\2.0.1 from tags\2.0.0. Vamsi On 8/14/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > All, > > Earlier today one of the Geronimo committers discovered a bug in the > command line deployer where a null user / password on the deployer > command line will allow a user to deploy modules to a 2.0 server. > This is an unacceptable security exposure and as such we have > abandoned the release of Geronimo 2.0. > > Donald Woods is going to open a JIRA for this issue and Hernan will > create a news item on our web page. > > At this point we need to discuss how to move forward with a 2.0 release. > > I think we should delete the tags/2.0.0 entry and replace it with a > text file that notes the svn rev of the tree before deletion. The > purpose of this is to avoid anyone from picking up that source tree > and using it to build a server with a known security exposure. > Unless there is disagreement I'd like to do that tomorrow allowing > some time for discussion. We can always put it back. > > There are several options for the 2.0 release: > > 1. Use the branches/2.0 to spin up a new release as 2.0.1. >If we do this there are a number of fixes that need to be > verified, We'd need to close out the SNAPSHOT releases again, or at > least revisit them. >Respin and re-tck a new release. > > 2. Take the tags/2.0.0 to create a branches/2.0.1 >This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT >Copy the existing tag over and apply the security fixes. Repsin > and release. > > Personally, I vote for option 2. Based on my experience, closing out > the SNAPSHOTs is and introducing little changes will cause us to > restart the release process. > > I'd like to hear other people's input but having done the release > several times option 2 is the fastest. I think option 1 will cause > us to not release until September. >
Geronimo 2.0 Release suspended due to security issue found before release
All, Earlier today one of the Geronimo committers discovered a bug in the command line deployer where a null user / password on the deployer command line will allow a user to deploy modules to a 2.0 server. This is an unacceptable security exposure and as such we have abandoned the release of Geronimo 2.0. Donald Woods is going to open a JIRA for this issue and Hernan will create a news item on our web page. At this point we need to discuss how to move forward with a 2.0 release. I think we should delete the tags/2.0.0 entry and replace it with a text file that notes the svn rev of the tree before deletion. The purpose of this is to avoid anyone from picking up that source tree and using it to build a server with a known security exposure. Unless there is disagreement I'd like to do that tomorrow allowing some time for discussion. We can always put it back. There are several options for the 2.0 release: 1. Use the branches/2.0 to spin up a new release as 2.0.1. If we do this there are a number of fixes that need to be verified, We'd need to close out the SNAPSHOT releases again, or at least revisit them. Respin and re-tck a new release. 2. Take the tags/2.0.0 to create a branches/2.0.1 This would mean that we need to update branches/2.0 to 2.0.2-SNAPSHOT Copy the existing tag over and apply the security fixes. Repsin and release. Personally, I vote for option 2. Based on my experience, closing out the SNAPSHOTs is and introducing little changes will cause us to restart the release process. I'd like to hear other people's input but having done the release several times option 2 is the fastest. I think option 1 will cause us to not release until September.
[Fwd: Re: building geronimo-2.0-rc1]
The jspc-maven-plugin-2.0-alpha-1.jar is to blame.
I still had a copy of the last alpha-1-SNAPSHOT laying around
(jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it over the
released alpha-1.jar from 8/8 and my builds starting working again on WinXP
Should we place this in the repo for 2.0.1-SNAPSHOT or ask them to fix it
before we release 2.0.1?
-Donald
Anita Kulshreshtha wrote:
I have not been so lucky. I have tried branches/2.0.0 also. I have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
Is anyone else seeing this in geronimo-welcome.. I am building
from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
Thanks
Anita
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
4K downloaded
[INFO] [jspc:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Illegal character in path at index 18: file:/C:/Documents and
Settings/Anita/.m2
/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
9)
at
org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at
org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at
org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
a:65)
at
org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
lassHelper.java:563)
at
groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
at
groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
at
org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
143)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
Helper.java:114)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
tecodeAdapter.java:214)
at
org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
roovy:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Ref
lectionMetaMethod.java:52)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassH
elper.java:714)
at
groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:936)
at
groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:2183)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
:o) Vamsi On 8/13/07, Joe Bohn <[EMAIL PROTECTED]> wrote: > > My belated but very enthusiastic +1. > > Joe > > > Matt Hogstrom wrote: > > I have put together the release and its been a long journey to get here. > > > > If you have comments please put them on the corresponding [DISCUSS] > thread. > > > > [ ] +1 Release Geronimo 2.0 > > [ ] 0 No opinion > > [ ] -1 Do not release Geronimo 2.0 > > > > Vote will conclude on 0700 ET on Saturday August 11th. > > > > Binaries and source artifacts are at > > http://people.apache.org/~hogstrom/geronimo-2.0-rc1 > > > > > > Files are being uploaded as of the time of this writing. > > >
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
My belated but very enthusiastic +1. Joe Matt Hogstrom wrote: I have put together the release and its been a long journey to get here. If you have comments please put them on the corresponding [DISCUSS] thread. [ ] +1 Release Geronimo 2.0 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.0 Vote will conclude on 0700 ET on Saturday August 11th. Binaries and source artifacts are at http://people.apache.org/~hogstrom/geronimo-2.0-rc1 Files are being uploaded as of the time of this writing.
Re: [RESULT] Geronimo 2.0 (RC1) and txmanager 2.0.1 - Passes with 17 +1 votes
forgot to update the Subject line. Once again. The 2.0 release has passed with 17 +1's. w00t !! I'll push the binaries out this weekend and we can declare victory next week !! Great job all ! On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote: I have put together the release and its been a long journey to get here. If you have comments please put them on the corresponding [DISCUSS] thread. [ ] +1 Release Geronimo 2.0 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.0 Vote will conclude on 0700 ET on Saturday August 11th. Binaries and source artifacts are at http://people.apache.org/ ~hogstrom/geronimo-2.0-rc1 Files are being uploaded as of the time of this writing.
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
The 2.0 release has passed with 17 +1's. w00t !! I'll push the binaries out this weekend and we can declare victory next week !! Great job all ! On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote: I have put together the release and its been a long journey to get here. If you have comments please put them on the corresponding [DISCUSS] thread. [ ] +1 Release Geronimo 2.0 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.0 Vote will conclude on 0700 ET on Saturday August 11th. Binaries and source artifacts are at http://people.apache.org/ ~hogstrom/geronimo-2.0-rc1 Files are being uploaded as of the time of this writing.
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
+1 -- Thanks, Tim McConnell Matt Hogstrom wrote: I have put together the release and its been a long journey to get here. If you have comments please put them on the corresponding [DISCUSS] thread. [ ] +1 Release Geronimo 2.0 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.0 Vote will conclude on 0700 ET on Saturday August 11th. Binaries and source artifacts are at http://people.apache.org/~hogstrom/geronimo-2.0-rc1 Files are being uploaded as of the time of this writing.
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
+1 Vamsi On 8/8/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > I have put together the release and its been a long journey to get here. > > If you have comments please put them on the corresponding [DISCUSS] > thread. > > [ ] +1 Release Geronimo 2.0 > [ ] 0 No opinion > [ ] -1 Do not release Geronimo 2.0 > > Vote will conclude on 0700 ET on Saturday August 11th. > > Binaries and source artifacts are at http://people.apache.org/ > ~hogstrom/geronimo-2.0-rc1 > > > Files are being uploaded as of the time of this writing. >
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
+1 -Donald Matt Hogstrom wrote: I have put together the release and its been a long journey to get here. If you have comments please put them on the corresponding [DISCUSS] thread. [ ] +1 Release Geronimo 2.0 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.0 Vote will conclude on 0700 ET on Saturday August 11th. Binaries and source artifacts are at http://people.apache.org/~hogstrom/geronimo-2.0-rc1 Files are being uploaded as of the time of this writing. smime.p7s Description: S/MIME Cryptographic Signature
Re: building geronimo-2.0-rc1
I have tried it on another windows machine with same fate...
Thanks for responding
Anita
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> I see this same problem on Windows while building branches/2.0.0 and
> with a squeaky clean repo.
>
> I do not have this problem on Linux.
>
> Cheers
> Prasad
>
> On 8/10/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> > I have not been so lucky. I have tried branches/2.0.0 also. I
> have
> > tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
> any
> > success (The trunk builds fine).
> >
> > Thanks
> > Anita
> >
> > --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> >
> > > I am not exactly building from geronimo-2.0-src.zip, but from
> > > branches\2.0.0. If that still counts as if I built from src
> zip... I
> > > have
> > > not run into this problem. I have tried after removing
> > > jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> > > downloads a
> > > fresh.
> > >
> > > --vamsi
> > >
> > >
> > > On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> > > >
> > > >Is anyone else seeing this in geronimo-welcome.. I am
> building
> > > from
> > > >
> > >
> >
>
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> > > >
> > > > Thanks
> > > > Anita
> > > >
> > > > Downloading:
> > > >
> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> > > > -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> > > > 4K downloaded
> > > > [INFO] [jspc:compile {execution: default}]
> > > > [INFO]
> > > >
> > >
> >
>
> > > > [ERROR] FATAL ERROR
> > > > [INFO]
> > > >
> > >
> >
>
> > > > [INFO] null
> > > > Illegal character in path at index 18: file:/C:/Documents and
> > > > Settings/Anita/.m2
> > > > /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> > > > [INFO]
> > > >
> > >
> >
>
> > > > [INFO] Trace
> > > > java.lang.IllegalArgumentException
> > > > at java.net.URI.create(URI.java:842)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > Method)
> > > > at
> > > >
> > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > > > java:39)
> > > > at
> > > >
> > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > > > sorImpl.java:25)
> > > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > > at
> > > > org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> > > > at
> > > >
> > >
> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> > > > 9)
> > > > at
> > > >
> org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> > > > at
> org.apache.tools.ant.Project.setAntLib(Project.java:313)
> > > > at
> > > > org.apache.tools.ant.Project.initProperties(Project.java:309)
> > > > at org.apache.tools.ant.Project.init(Project.java:295)
> > > > at
> > > >
> > >
> org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> > > > a:65)
> > > > at
> > > >
> org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> > > > at
> > > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > > Method)
> > > >
> > > > at
> > > >
> > >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> > > > orAccessorImpl.java:39)
> > > > at
> > > >
> > >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> > > > onstructorAccessorImpl.java:27)
> > > > at
> > > > java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> > > > at
>
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
On Aug 10, 2007, at 6:54 AM, Christopher Blythe wrote: Jencks, et. al. Any idea if this was ever addressed? https://issues.apache.org/jira/browse/GERONIMO-3354 Sorry, that is not fixed in 2.0 david jencks Thanks... Chris On 8/10/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Forgot my +1 (perhaps implied) On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote: > I have put together the release and its been a long journey to get > here. > > If you have comments please put them on the corresponding [DISCUSS] > thread. > > [ ] +1 Release Geronimo 2.0 > [ ] 0 No opinion > [ ] -1 Do not release Geronimo 2.0 > > Vote will conclude on 0700 ET on Saturday August 11th. > > Binaries and source artifacts are at http://people.apache.org/ > ~hogstrom/geronimo-2.0-rc1 > > > Files are being uploaded as of the time of this writing. > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: building geronimo-2.0-rc1
I see this same problem on Windows while building branches/2.0.0 and
with a squeaky clean repo.
I do not have this problem on Linux.
Cheers
Prasad
On 8/10/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> I have not been so lucky. I have tried branches/2.0.0 also. I have
> tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without any
> success (The trunk builds fine).
>
> Thanks
> Anita
>
> --- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
>
> > I am not exactly building from geronimo-2.0-src.zip, but from
> > branches\2.0.0. If that still counts as if I built from src zip... I
> > have
> > not run into this problem. I have tried after removing
> > jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> > downloads a
> > fresh.
> >
> > --vamsi
> >
> >
> > On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> > >
> > >Is anyone else seeing this in geronimo-welcome.. I am building
> > from
> > >
> >
> http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> > >
> > > Thanks
> > > Anita
> > >
> > > Downloading:
> > > http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> > > -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> > > 4K downloaded
> > > [INFO] [jspc:compile {execution: default}]
> > > [INFO]
> > >
> >
>
> > > [ERROR] FATAL ERROR
> > > [INFO]
> > >
> >
>
> > > [INFO] null
> > > Illegal character in path at index 18: file:/C:/Documents and
> > > Settings/Anita/.m2
> > > /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> > > [INFO]
> > >
> >
>
> > > [INFO] Trace
> > > java.lang.IllegalArgumentException
> > > at java.net.URI.create(URI.java:842)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > > at
> > >
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > > java:39)
> > > at
> > >
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > > sorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > at
> > > org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> > > at
> > >
> > org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> > > 9)
> > > at
> > > org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> > > at org.apache.tools.ant.Project.setAntLib(Project.java:313)
> > > at
> > > org.apache.tools.ant.Project.initProperties(Project.java:309)
> > > at org.apache.tools.ant.Project.init(Project.java:295)
> > > at
> > >
> > org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> > > a:65)
> > > at
> > > org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> > > at
> > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > Method)
> > >
> > > at
> > >
> > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> > > orAccessorImpl.java:39)
> > > at
> > >
> > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> > > onstructorAccessorImpl.java:27)
> > > at
> > > java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> > > at
> > >
> > org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
> > > lassHelper.java:563)
> > > at
> > >
> > groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
> > > )
> > > at
> > > groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
> > > at
> > > groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
> > > at
> > >
> > org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
> > > 143)
> > > at
> > >
> > org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
> > > Helper.java:114)
>
Re: [VOTE] Geronimo 2.0 (RC1) and txmanager 2.0.1
Jencks, et. al. Any idea if this was ever addressed? https://issues.apache.org/jira/browse/GERONIMO-3354 Thanks... Chris On 8/10/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > Forgot my +1 (perhaps implied) > > On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote: > > > I have put together the release and its been a long journey to get > > here. > > > > If you have comments please put them on the corresponding [DISCUSS] > > thread. > > > > [ ] +1 Release Geronimo 2.0 > > [ ] 0 No opinion > > [ ] -1 Do not release Geronimo 2.0 > > > > Vote will conclude on 0700 ET on Saturday August 11th. > > > > Binaries and source artifacts are at http://people.apache.org/ > > ~hogstrom/geronimo-2.0-rc1 > > > > > > Files are being uploaded as of the time of this writing. > > > > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: building geronimo-2.0-rc1
I have not been so lucky. I have tried branches/2.0.0 also. I have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote:
> I am not exactly building from geronimo-2.0-src.zip, but from
> branches\2.0.0. If that still counts as if I built from src zip... I
> have
> not run into this problem. I have tried after removing
> jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
> downloads a
> fresh.
>
> --vamsi
>
>
> On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
> >
> >Is anyone else seeing this in geronimo-welcome.. I am building
> from
> >
>
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
> >
> > Thanks
> > Anita
> >
> > Downloading:
> > http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> > -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> > 4K downloaded
> > [INFO] [jspc:compile {execution: default}]
> > [INFO]
> >
>
> > [ERROR] FATAL ERROR
> > [INFO]
> >
>
> > [INFO] null
> > Illegal character in path at index 18: file:/C:/Documents and
> > Settings/Anita/.m2
> > /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> > [INFO]
> >
>
> > [INFO] Trace
> > java.lang.IllegalArgumentException
> > at java.net.URI.create(URI.java:842)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> > at
> >
> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> > 9)
> > at
> > org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> > at org.apache.tools.ant.Project.setAntLib(Project.java:313)
> > at
> > org.apache.tools.ant.Project.initProperties(Project.java:309)
> > at org.apache.tools.ant.Project.init(Project.java:295)
> > at
> >
> org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> > a:65)
> > at
> > org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> > at
> > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> >
> > at
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> > orAccessorImpl.java:39)
> > at
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> > onstructorAccessorImpl.java:27)
> > at
> > java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> > at
> >
> org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
> > lassHelper.java:563)
> > at
> >
> groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
> > )
> > at
> > groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
> > at
> > groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
> > at
> >
> org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
> > 143)
> > at
> >
> org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
> > Helper.java:114)
> > at
> >
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
> > tecodeAdapter.java:214)
> > at
> >
> org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
> > roovy:42)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> > sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> >
> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Ref
&
Re: building geronimo-2.0-rc1
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src zip... I have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
>
>Is anyone else seeing this in geronimo-welcome.. I am building from
> http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-src.zip
>
> Thanks
> Anita
>
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> 4K downloaded
> [INFO] [jspc:compile {execution: default}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
> Settings/Anita/.m2
> /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> at
> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> 9)
> at
> org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> at org.apache.tools.ant.Project.setAntLib(Project.java:313)
> at
> org.apache.tools.ant.Project.initProperties(Project.java:309)
> at org.apache.tools.ant.Project.init(Project.java:295)
> at
> org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> a:65)
> at
> org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> orAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> onstructorAccessorImpl.java:27)
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at
> org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
> lassHelper.java:563)
> at
> groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
> )
> at
> groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
> at
> groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
> at
> org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
> 143)
> at
> org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
> Helper.java:114)
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
> tecodeAdapter.java:214)
> at
> org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
> roovy:42)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Ref
> lectionMetaMethod.java:52)
> at
> org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassH
> elper.java:714)
> at
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:936)
> at
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:2183)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Ref
> lectionMetaMethod.java:52)
> at
> org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassH
> elp
Re: building geronimo-2.0-rc1
On Aug 9, 2007, at 7:22 AM, Anita Kulshreshtha wrote: Is anyone else seeing this in geronimo-welcome.. I am building from http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0- src.zip I haven't as I haven't built on a Windows system. Perhaps someone else can chime in?
