[jira] Commented: (GERONIMO-3705) Maven 2.0.8 causes build problems
[ https://issues.apache.org/jira/browse/GERONIMO-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589434#action_12589434 ] David Jencks commented on GERONIMO-3705: Here's the servicemix trace, the one from geronimo looked similar: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Unable to create configuration for deployment Unable to resolve dependency org.apache.xbean/xbean-naming//jar [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to create configuration for deployment at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to create configuration for deployment at org.apache.geronimo.genesis.MojoSupport.execute(MojoSupport.java:137) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:121) at org.apache.geronimo.deployment.DeploymentContext.(DeploymentContext.java:101) at org.apache.geronimo.deployment.DeploymentContext.(DeploymentContext.java:81) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:205) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:177) at org.apache.geronimo.deployment.service.ServiceConfigBuilder$$FastClassByCGLIB$$9f173be6.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:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$21e3cf17.buildConfiguration() at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302) 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:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:665)
[jira] Commented: (GERONIMO-3705) Maven 2.0.8 causes build problems
[ https://issues.apache.org/jira/browse/GERONIMO-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589433#action_12589433 ] David Jencks commented on GERONIMO-3705: Problem seems to be the car-maven-plugin use of DependencyHelper leaves out a whole lotta dependencies. I think this can also occur even with maven 2.0.7, servicemix seems to be encountering a similar problem. It's pretty easy to have our plugins use the ArtifactCollector more directly which allows building with maven 2.0.9 about to check about servicemix. > Maven 2.0.8 causes build problems > - > > Key: GERONIMO-3705 > URL: https://issues.apache.org/jira/browse/GERONIMO-3705 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.1 >Reporter: Jason Dillon >Assignee: David Jencks >Priority: Critical > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3705) Maven 2.0.8 causes build problems
[ https://issues.apache.org/jira/browse/GERONIMO-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-3705: -- Assignee: David Jencks (was: Jason Dillon) > Maven 2.0.8 causes build problems > - > > Key: GERONIMO-3705 > URL: https://issues.apache.org/jira/browse/GERONIMO-3705 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.1 >Reporter: Jason Dillon >Assignee: David Jencks >Priority: Critical > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: branches/2.1.1 created
Updated the OpenEJB version! -David On Apr 15, 2008, at 3:10 PM, Joe Bohn wrote: I created a branch for 2.1.1 that will be used to prepare for the release. At the moment it is still versioned as 2.1.1-SNAPSHOT. Just prior to this branch I published new 2.1.1-SNAPSHOT artifacts. I also updated the branches/2.1 to 2.1.2-SNAPSHOT. After the change I published 2.1.2-SNAPSHOT artifacts. At the moment the only remaining changes that I am aware of that are necessary for 2.1.1 prior to creating a release candidate are: - Updating to utilize OpenEJB 3.0 - Updating the README and RELEASE_NOTES Joe
[jira] Resolved: (GERONIMODEVTOOLS-312) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell resolved GERONIMODEVTOOLS-312. Resolution: Fixed Created a new ConversionHelper class with static methods to assist in the conversion of various Geronimo deployment descriptors rather than implementing as a function of the Geronimo runtime instance. Resolved in revision 648451. > Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes > using JAXB > --- > > Key: GERONIMODEVTOOLS-312 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 2.1.0 >Reporter: Shiva Kumar H R >Assignee: Tim McConnell >Priority: Critical > Fix For: 2.1.0 > > > The fixGeronimo*Schema() function inside GeronimRuntime classes is curently > implemented using XMLBeans. As part of GERONIMODEVTOOLS-295, > xmlbeans-2.3.0.jar has been removed from GEP's dependencies. Hence > fixGeronimo*Schema() functionality needs to be reimplemented using JAXB. > Classes to be changed: > 1) org.apache.geronimo.st.core.IGeronimoRuntime > 2) org.apache.geronimo.st.core.operations.ImportDeploymentPlanOperation > 3) org.apache.geronimo.st.v11.core.GeronimoRuntime > 4) org.apache.geronimo.st.v20.core.GeronimoRuntime > 5) org.apache.geronimo.st.v21.core.GeronimoRuntime -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
branches/2.1.1 created
I created a branch for 2.1.1 that will be used to prepare for the release. At the moment it is still versioned as 2.1.1-SNAPSHOT. Just prior to this branch I published new 2.1.1-SNAPSHOT artifacts. I also updated the branches/2.1 to 2.1.2-SNAPSHOT. After the change I published 2.1.2-SNAPSHOT artifacts. At the moment the only remaining changes that I am aware of that are necessary for 2.1.1 prior to creating a release candidate are: - Updating to utilize OpenEJB 3.0 - Updating the README and RELEASE_NOTES Joe
[jira] Closed: (GERONIMODEVTOOLS-329) Need to add groupId and version for some maven plugins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMODEVTOOLS-329. - Resolution: Fixed committed revision 648358 in trunk (2.1.0) > Need to add groupId and version for some maven plugins > -- > > Key: GERONIMODEVTOOLS-329 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-329 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.0 >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.1.0 > > > Some of the maven plugins used in the build are being used without a groupId > or version, which could break future builds when new versions of the plugins > are released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-329) Need to add groupId and version for some maven plugins
Need to add groupId and version for some maven plugins -- Key: GERONIMODEVTOOLS-329 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-329 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Donald Woods Assignee: Donald Woods Fix For: 2.1.0 Some of the maven plugins used in the build are being used without a groupId or version, which could break future builds when new versions of the plugins are released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-328) Problems with latest maven-assembly-plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMODEVTOOLS-328. - Resolution: Fixed Fixed in branches/2.0.1. Version was already set to 2.2-beta-1 in trunk for 2.1.0. > Problems with latest maven-assembly-plugin > -- > > Key: GERONIMODEVTOOLS-328 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0, 2.0.x >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.0.x > > > The dependencySet - outputFileMapping changed in 2.2-beta-2, so use the prior > 2.2-beta-1 version that was working for us -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-328) Problems with latest maven-assembly-plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMODEVTOOLS-328: -- Affects Version/s: (was: 2.1.0) Fix Version/s: (was: 2.1.0) > Problems with latest maven-assembly-plugin > -- > > Key: GERONIMODEVTOOLS-328 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0, 2.0.x >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.0.x > > > The dependencySet - outputFileMapping changed in 2.2-beta-2, so use the prior > 2.2-beta-1 version that was working for us -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GEP 2.1.0 Branch Notification
Can we update the depends to match the same levels used by the 2.1.1 server? Like - xstream-1.2.1 --> 1.2.2 xpp3-1.1.3.3 --> 1.1.3.4.O I'd update these myself, but I know they are also specified in some other non-maven Eclipse specific files... Also, we should replace the javax.activation depend with geronimo-activation_1.1_spec-1.0.2 and add the proper maven excludes. There are several maven plugins which don't have a groupId or version set, which I'll update in the next few minutes. -Donald Tim McConnell wrote: Hi, As soon as the following JIRA is resolved sometime today, I intend to branch (i.e., devtools/eclipse-plugin/branches/2.1.0) in preparation for the release 2.1.0 of the Geronimo Eclipse Plugin. Does anyone have any objections or know of any other reason we shouldn't do so ?? -> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254 smime.p7s Description: S/MIME Cryptographic Signature
[jira] Commented: (GERONIMODEVTOOLS-328) Problems with latest maven-assembly-plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589161#action_12589161 ] Donald Woods commented on GERONIMODEVTOOLS-328: --- Fixed in branches/2.0.1 by revision 648353 > Problems with latest maven-assembly-plugin > -- > > Key: GERONIMODEVTOOLS-328 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0, 2.0.x, 2.1.0 >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.0.x, 2.1.0 > > > The dependencySet - outputFileMapping changed in 2.2-beta-2, so use the prior > 2.2-beta-1 version that was working for us -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-328) Problems with latest mavn-assembly-plugin
Problems with latest mavn-assembly-plugin - Key: GERONIMODEVTOOLS-328 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0, 2.0.x, 2.1.0 Reporter: Donald Woods Assignee: Donald Woods Fix For: 2.0.x, 2.1.0 The dependencySet - outputFileMapping changed in 2.2-beta-2, so use the prior 2.2-beta-1 version that was working for us -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-328) Problems with latest maven-assembly-plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMODEVTOOLS-328: -- Summary: Problems with latest maven-assembly-plugin (was: Problems with latest mavn-assembly-plugin) > Problems with latest maven-assembly-plugin > -- > > Key: GERONIMODEVTOOLS-328 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-328 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0, 2.0.x, 2.1.0 >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.0.x, 2.1.0 > > > The dependencySet - outputFileMapping changed in 2.2-beta-2, so use the prior > 2.2-beta-1 version that was working for us -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3957) Updating svn:ignore lists
[ https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589159#action_12589159 ] Vasily Zakharov commented on GERONIMO-3957: --- Jacek, Sorry for those dumb attachments, it looks like svn properties can't be handled by patches in any way. I'll provide a script of some kind to make those changes. > Updating svn:ignore lists > - > > Key: GERONIMO-3957 > URL: https://issues.apache.org/jira/browse/GERONIMO-3957 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: general >Affects Versions: 2.0.2, 2.1 >Reporter: Vasily Zakharov > Attachments: Geronimo-3957-20.patch, Geronimo-3957-21.patch, > Geronimo-3957-210.patch , Geronimo-3957-Trunk.patch, Geronimo-3957-Trunk.patch > > > When trying to create a patch in an already-built environment, a lot of > build-generated directories get in the way. > Probably they just need to be added to the corresponding SVN ignore list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3955) Typo
[ https://issues.apache.org/jira/browse/GERONIMO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3955: --- Fix Version/s: (was: 2.1.x) 2.1.1 updated fix versions > Typo > > > Key: GERONIMO-3955 > URL: https://issues.apache.org/jira/browse/GERONIMO-3955 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1, 2.1.x, 2.2 >Reporter: Afranio Moraes >Assignee: Joseph Leong >Priority: Trivial > Fix For: 2.1.1, 2.2 > > Attachments: GERONIMO-3955.patch > > > Typo in console after editing keystores: > Keysore 'keystore.jks' is now edit locked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
GEP 2.1.0 Branch Notification
Hi, As soon as the following JIRA is resolved sometime today, I intend to branch (i.e., devtools/eclipse-plugin/branches/2.1.0) in preparation for the release 2.1.0 of the Geronimo Eclipse Plugin. Does anyone have any objections or know of any other reason we shouldn't do so ?? -> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254 -- Thanks, Tim McConnell
Re: Subversion Client Configuration questions
Thanks for the answers. I went ahead and changed the wiki page to reflect the correct result. On Tue, Apr 15, 2008 at 3:39 AM, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On Mon, Apr 14, 2008 at 10:22 PM, Jason Warner <[EMAIL PROTECTED]> > wrote: > > I had a question about a disparity between the subversion client > > configuration file that is provided here [1] and the verification test > noted > > on the same page. For many of the file extensions listed in the > > configuration, the svn:keywords property is set to just "Date Revision". > > The verification steps say the output from svn propget svn:keywords > > test-auto-props.xml should be "Date Author Id Revision HeadURL." Which > is > > correct? > > Date Revision > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > -- ~Jason Warner
Re: [jira] Commented: (GERONIMODEVTOOLS-206) Error while deploying EAR to running server Geronimo 2.0.1
Welcome back Tomasz! We need any & all help in closing some 18 pending JIRAs for GEP 2.1.0. https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310111&fixfor=12312703 It would just be great if you & others can help to solve some of them. On Tue, Apr 15, 2008 at 1:57 PM, Tomasz Mazan (JIRA) <[EMAIL PROTECTED]> wrote: > >[ > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588972#action_12588972] > > Tomasz Mazan commented on GERONIMODEVTOOLS-206: > --- > > Tim, I've just go back from short holidays. I'm able to retest it in a few > days. Please, write if it's satisfying - if not, I'll close this issue with > hope that's not present. > > > Error while deploying EAR to running server Geronimo 2.0.1 > > -- > > > > Key: GERONIMODEVTOOLS-206 > > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206 > > Project: Geronimo-Devtools > > Issue Type: Bug > > Components: eclipse-plugin > >Affects Versions: 2.0.0 > > Environment: Geronimo 2.0.1 > > WTP 2.0 + GEP 2.0 > >Reporter: Tomasz Mazan > >Assignee: Tim McConnell > >Priority: Critical > > Fix For: 2.1.x > > > > > > Exception on deploy > > Distribution of configuration failed. See log for details. > > java.io.FileNotFoundException: > C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip > (File not found) > > org.apache.geronimo.common.DeploymentException: > java.io.FileNotFoundException: > C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip > (File not found) > > at > org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:121) > > 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:124) > > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) > > 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:124) > > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) > > 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:213) > > at > com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) > > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) > > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) > > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) > > at > javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) > > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) > > at java.security.AccessController.doPrivileged(Native Method) > > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) > > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) > > at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > > at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) > > at sun.rmi.transport.Transport$1.run(Transport.java:153) > > at java.security.AccessController.doPrivileged(Native Method) > > at sun.rmi.transport.Transport.serviceCall(Transport.java:149) > > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) > > at > sun.rmi.transport.tcp.TCPTransport$ConnectionH
[jira] Commented: (GERONIMODEVTOOLS-206) Error while deploying EAR to running server Geronimo 2.0.1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588972#action_12588972 ] Tomasz Mazan commented on GERONIMODEVTOOLS-206: --- Tim, I've just go back from short holidays. I'm able to retest it in a few days. Please, write if it's satisfying - if not, I'll close this issue with hope that's not present. > Error while deploying EAR to running server Geronimo 2.0.1 > -- > > Key: GERONIMODEVTOOLS-206 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-206 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0 > Environment: Geronimo 2.0.1 > WTP 2.0 + GEP 2.0 >Reporter: Tomasz Mazan >Assignee: Tim McConnell >Priority: Critical > Fix For: 2.1.x > > > Exception on deploy > Distribution of configuration failed. See log for details. > java.io.FileNotFoundException: > C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip > (File not found) > org.apache.geronimo.common.DeploymentException: > java.io.FileNotFoundException: > C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip > (File not found) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:121) > 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:124) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) > 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:124) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) > 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:213) > at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) > at > javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) > at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) > at sun.rmi.transport.Transport$1.run(Transport.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:149) > at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) > at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.io.FileNotFoundException: > C:\DEV\IDE\eclipse-wtp-2.0\workspace\.metadata\.plugins\org.apache.geronimo.st.core\server_13.09.07_14_454\FonBsaCore.zip > (File not found) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.(FileInputStream.java:106) > at > org.apache.geronimo.deployment.util.DeploymentUtil.copyFile(DeploymentUtil.java:92) > at org.apach
Re: svn commit: r648166 - /geronimo/server/branches/2.1/pom.xml
I am of the same opinion. It will also help in avoiding similar errors in future. ++Vamsi On Tue, Apr 15, 2008 at 1:54 PM, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On Tue, Apr 15, 2008 at 10:16 AM, <[EMAIL PROTECTED]> wrote: > > Author: gdamour > > Date: Tue Apr 15 01:16:50 2008 > > New Revision: 648166 > > > > URL: http://svn.apache.org/viewvc?rev=648166&view=rev > > Log: > > as pointed out by Donald, all WADI versions should have been upgraded > to 2.0-M10 > > Wouldn't it be easier to introduce a variable so the change would've > boiled down to updating it only? Just like derbyVersion oraz > openejbVersion. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl >
Re: svn commit: r648166 - /geronimo/server/branches/2.1/pom.xml
On Tue, Apr 15, 2008 at 10:16 AM, <[EMAIL PROTECTED]> wrote: > Author: gdamour > Date: Tue Apr 15 01:16:50 2008 > New Revision: 648166 > > URL: http://svn.apache.org/viewvc?rev=648166&view=rev > Log: > as pointed out by Donald, all WADI versions should have been upgraded to > 2.0-M10 Wouldn't it be easier to introduce a variable so the change would've boiled down to updating it only? Just like derbyVersion oraz openejbVersion. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: svn commit: r647361 - /geronimo/server/branches/2.1/pom.xml
Sorry for this mistake. It is now fixed. Thanks for having reported it. Gianny On 15/04/2008, at 5:04 AM, Donald Woods wrote: Is there a reason you only updated wadi-aop to 2.0-M10 and not the rest of the WADI artifacts? -Donald
Re: Subversion Client Configuration questions
On Mon, Apr 14, 2008 at 10:22 PM, Jason Warner <[EMAIL PROTECTED]> wrote: > I had a question about a disparity between the subversion client > configuration file that is provided here [1] and the verification test noted > on the same page. For many of the file extensions listed in the > configuration, the svn:keywords property is set to just "Date Revision". > The verification steps say the output from svn propget svn:keywords > test-auto-props.xml should be "Date Author Id Revision HeadURL." Which is > correct? Date Revision Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Commented: (GERONIMODEVTOOLS-256) Publish operation after an Eclipse restart deletes a deployed Web Service's "server-config.wsdd" file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588954#action_12588954 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-256: -- Other related bugzilla report on Eclipse WTP: "Remove the workarond to write server-config.wsdd for Geronimo" https://bugs.eclipse.org/bugs/show_bug.cgi?id=109292 > Publish operation after an Eclipse restart deletes a deployed Web Service's > "server-config.wsdd" file > - > > Key: GERONIMODEVTOOLS-256 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0 > Environment: AG 2.0.2 + Geronimo Eclipse Plug-in v2.0 + WTP 2.0.1 >Reporter: Shiva Kumar H R >Assignee: Shiva Kumar H R > Fix For: 2.1.0 > > > Steps to recreate: > 1) Create a Web Service as per the instructions at > http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpWebService/BottomUpWebService.html > 2) Test the web service using (the auto launched) Web Service Explorer. > Everything works fine. > 3) Shut down server and restart the server. Again launch the web service. It > runs fine without any error. > 4) Shut down server, close eclipse, restart eclipse, start server. This time > try to access the web service and you will not be able to access it. > An initial analysis shows that in Step-4 (after a Eclipse & Server restart) > the "Publish" operation of Eclipse is deleting "server-config.wsdd" from > \repository\\\WEB-INF > directory. > You will get the following error in the console: > 17:01:56,218 ERROR [EngineConfigurationFactoryServlet] Unable to find config > file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd > Is this related to the issue reported in > http://mail-archive.ow2.org/jonas-team/2006-08/msg00046.html ? Needs to be > explored. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
