[jira] [Commented] (XBEAN-239) toURL() is deprecated and causes a build error
[
https://issues.apache.org/jira/browse/XBEAN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573437#comment-13573437
]
Mark Struberg commented on XBEAN-239:
-
Additional patch from Romain applied. Waiting for JIRA privileges to set it to
'resolved' ;)
> toURL() is deprecated and causes a build error
> --
>
> Key: XBEAN-239
> URL: https://issues.apache.org/jira/browse/XBEAN-239
> Project: XBean
> Issue Type: Bug
>Affects Versions: 3.12
>Reporter: Mark Struberg
> Attachments: xbean-java7.patch
>
>
> When compiling XBean I get the following error
> [ERROR]
> /Users/struberg/develop/java/apache/geronimo/xbean/xbean-spring/src/main/java/org/apache/xbean/spring/generator/QdoxMappingLoader.java:545:
> warning: [deprecation] toURL() in File has been deprecated
> [ERROR] builder.addSource(new URL("jar:" + base.toURL().toString() + "!/" +
> name));
> The solution is to replace toURL() with .toURI().toURL().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (XBEAN-239) toURL() is deprecated and causes a build error
Mark Struberg created XBEAN-239:
---
Summary: toURL() is deprecated and causes a build error
Key: XBEAN-239
URL: https://issues.apache.org/jira/browse/XBEAN-239
Project: XBean
Issue Type: Bug
Affects Versions: 3.12
Reporter: Mark Struberg
When compiling XBean I get the following error
[ERROR]
/Users/struberg/develop/java/apache/geronimo/xbean/xbean-spring/src/main/java/org/apache/xbean/spring/generator/QdoxMappingLoader.java:545:
warning: [deprecation] toURL() in File has been deprecated
[ERROR] builder.addSource(new URL("jar:" + base.toURL().toString() + "!/" +
name));
The solution is to replace toURL() with .toURI().toURL().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-89) Daytrader plugin build error: can't package plugin
[ https://issues.apache.org/jira/browse/DAYTRADER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed DAYTRADER-89. - Resolution: Fixed plugins folder doesn't exist in daytrader 3.0 currently. So close it. > Daytrader plugin build error: can't package plugin > -- > > Key: DAYTRADER-89 > URL: https://issues.apache.org/jira/browse/DAYTRADER-89 > Project: DayTrader > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0-M2, 3.0 > Environment: OS:win2003 > JDK 1.6 >Reporter: viola.lu >Assignee: viola.lu > Fix For: 3.0-M2, 3.0 > > > 1. Build daytrader plugins folder, but got build error: can't package plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: New server trunk build error.
Resolved. Thx. 2011/1/19 Shawn Jiang > you need to rebuild tomcat7 plugins to pull following fix. > > Author: rwonly > Date: Wed Jan 19 03:08:10 2011 > New Revision: 1060665 > > URL: http://svn.apache.org/viewvc?rev=1060665&view=rev > Log: > revert the changes in 1060171, and will try a new approach. > > On Wed, Jan 19, 2011 at 5:26 PM, Shenghao Fang > wrote: > >> Hi, >> >> I got the same error on revision 1060723. Could anyone help with this? >> Thanks. >> >> Michael Fang >> >> 2011/1/19 Kevan Miller >> >> >>> On Jan 18, 2011, at 12:44 PM, Rick McGuire wrote: >>> >>> > I'm getting the following error building the latest trunk. Where >>> should the wsdl generator be coming from? >>> >>> I built trunk, earlier today without a problem. My revision number is >>> 1060171. >>> >>> --kevan >> >> >> > > > -- > Shawn >
Re: New server trunk build error.
you need to rebuild tomcat7 plugins to pull following fix. Author: rwonly Date: Wed Jan 19 03:08:10 2011 New Revision: 1060665 URL: http://svn.apache.org/viewvc?rev=1060665&view=rev Log: revert the changes in 1060171, and will try a new approach. On Wed, Jan 19, 2011 at 5:26 PM, Shenghao Fang wrote: > Hi, > > I got the same error on revision 1060723. Could anyone help with this? > Thanks. > > Michael Fang > > 2011/1/19 Kevan Miller > > >> On Jan 18, 2011, at 12:44 PM, Rick McGuire wrote: >> >> > I'm getting the following error building the latest trunk. Where should >> the wsdl generator be coming from? >> >> I built trunk, earlier today without a problem. My revision number is >> 1060171. >> >> --kevan > > > -- Shawn
Re: New server trunk build error.
Hi, I got the same error on revision 1060723. Could anyone help with this? Thanks. Michael Fang 2011/1/19 Kevan Miller > > On Jan 18, 2011, at 12:44 PM, Rick McGuire wrote: > > > I'm getting the following error building the latest trunk. Where should > the wsdl generator be coming from? > > I built trunk, earlier today without a problem. My revision number is > 1060171. > > --kevan
Re: New server trunk build error.
On Jan 18, 2011, at 12:44 PM, Rick McGuire wrote: > I'm getting the following error building the latest trunk. Where should the > wsdl generator be coming from? I built trunk, earlier today without a problem. My revision number is 1060171. --kevan
New server trunk build error.
I'm getting the following error building the latest trunk. Where should the wsdl generator be coming from? Rick [org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState for: org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car State changed from running to stopping [org.apache.geronimo.kernel.config.Configuration] : Stopping configuration org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car [org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState for: org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/uddi-tomcat/3.0-SNAPSHOT/car State changed from stopping to stopped [INFO] [ERROR] BUILD ERROR [INFO] [INFO] could not package plugin Embedded error: Wsdl generator not found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: could not package plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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: could not package plugin at org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:238) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.geronimo.common.DeploymentException: Wsdl generator not found at org.apache.geronimo.axis2.builder.Axis2Builder.getWsdlGenerator(Axis2Builder.java:193) at org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:218) at org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:183) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:617) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:716) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) 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:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:524) at org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:340) at org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.jav
[jira] Closed: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang closed GERONIMODEVTOOLS-676. -- Released in GEP 2.1.7, so I close this JIRA. > branch 2.1.7 build error > > > Key: GERONIMODEVTOOLS-676 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.7 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Fix For: 2.1.7 > > Attachments: GERONIMODEVTOOLS-676.patch > > > Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAYTRADER-89) Daytrader plugin build error: can't package plugin
Daytrader plugin build error: can't package plugin -- Key: DAYTRADER-89 URL: https://issues.apache.org/jira/browse/DAYTRADER-89 Project: DayTrader Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0-M2, 3.0 Environment: OS:win2003 JDK 1.6 Reporter: viola.lu Assignee: viola.lu Fix For: 3.0-M2, 3.0 1. Build daytrader plugins folder, but got build error: can't package plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMODEVTOOLS-676: --- Fix Version/s: 2.1.7 Edit Fix Version as 2.1.7 > branch 2.1.7 build error > > > Key: GERONIMODEVTOOLS-676 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.7 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Fix For: 2.1.7 > > Attachments: GERONIMODEVTOOLS-676.patch > > > Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-676. Resolution: Fixed Build successfully with your patch. commit it in revision 1022868. Thanks Hong Fang Han for the patch! > branch 2.1.7 build error > > > Key: GERONIMODEVTOOLS-676 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.7 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Attachments: GERONIMODEVTOOLS-676.patch > > > Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
branch 2.1.7 build error Key: GERONIMODEVTOOLS-676 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Attachments: GERONIMODEVTOOLS-676.patch Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMODEVTOOLS-676: --- Attachment: GERONIMODEVTOOLS-676.patch Patch is available. Please help to review. Thanks! > branch 2.1.7 build error > > > Key: GERONIMODEVTOOLS-676 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.7 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Attachments: GERONIMODEVTOOLS-676.patch > > > Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: HELP: trunk build error with plugins/debugviews/debugviews-portlet
Thanks for the info. I was trying to re-order navigation items according to Geronimo-4950. I'll skip these modules and try other modules. Jeff On Wed, Aug 18, 2010 at 12:32 AM, David Jencks wrote: > What did you try to build? AFAIK these modules haven't been updated to > build in g. 3. > > david jencks > > On Aug 17, 2010, at 9:00 AM, chi runhua wrote: > > > Hi, I ran into the following errors when trying to build trunk for > experiments. Could anyone lend me a hand on this? Thanks in advance. > > > > > > [INFO] Compiling 10 source files to > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/target/classes > > [INFO] > > > [ERROR] BUILD FAILURE > > [INFO] > > > [INFO] Compilation failure > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[29,40] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: package org.apache.geronimo.kernel.config > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[30,38] > cannot find symbol > > symbol : class ClassLoaderRegistry > > location: package org.apache.geronimo.kernel.util > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[45,26] > [deprecation] uk.ltd.getahead.dwr.WebContextFactory in uk.ltd.getahead.dwr > has been deprecated > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[47,20] > cannot find symbol > > symbol : variable ClassLoaderRegistry > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[67,35] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,12] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,52] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[94,35] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,12] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,52] > cannot find symbol > > symbol : class MultiParentClassLoader > > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[63,37] > cannot find symbol > > symbol : method getDependencies() > > location: class org.apache.geronimo.kernel.config.Configuration > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[66,37] > cannot find symbol > > symbol : method getServiceParents() > > location: class org.apache.geronimo.kernel.config.Configuration > > > > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/jmxmanager/JMXManagerHelper.java:[142,44] > [deprecation] lis
Re: HELP: trunk build error with plugins/debugviews/debugviews-portlet
What did you try to build? AFAIK these modules haven't been updated to build in g. 3. david jencks On Aug 17, 2010, at 9:00 AM, chi runhua wrote: > Hi, I ran into the following errors when trying to build trunk for > experiments. Could anyone lend me a hand on this? Thanks in advance. > > > [INFO] Compiling 10 source files to > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/target/classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[29,40] > cannot find symbol > symbol : class MultiParentClassLoader > location: package org.apache.geronimo.kernel.config > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[30,38] > cannot find symbol > symbol : class ClassLoaderRegistry > location: package org.apache.geronimo.kernel.util > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[45,26] > [deprecation] uk.ltd.getahead.dwr.WebContextFactory in uk.ltd.getahead.dwr > has been deprecated > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[47,20] > cannot find symbol > symbol : variable ClassLoaderRegistry > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[67,35] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,12] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,52] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[94,35] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,12] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,52] > cannot find symbol > symbol : class MultiParentClassLoader > location: class > org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[63,37] > cannot find symbol > symbol : method getDependencies() > location: class org.apache.geronimo.kernel.config.Configuration > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[66,37] > cannot find symbol > symbol : method getServiceParents() > location: class org.apache.geronimo.kernel.config.Configuration > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/jmxmanager/JMXManagerHelper.java:[142,44] > [deprecation] listGBeans(javax.management.ObjectName) in > org.apache.geronimo.kernel.Kernel has been deprecated > > /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[414,25] > [deprecation] uk.ltd.getahead.dwr.
HELP: trunk build error with plugins/debugviews/debugviews-portlet
Hi, I ran into the following errors when trying to build trunk for experiments. Could anyone lend me a hand on this? Thanks in advance. [INFO] Compiling 10 source files to /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[29,40] cannot find symbol symbol : class MultiParentClassLoader location: package org.apache.geronimo.kernel.config /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[30,38] cannot find symbol symbol : class ClassLoaderRegistry location: package org.apache.geronimo.kernel.util /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[45,26] [deprecation] uk.ltd.getahead.dwr.WebContextFactory in uk.ltd.getahead.dwr has been deprecated /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[47,20] cannot find symbol symbol : variable ClassLoaderRegistry location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[67,35] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,12] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[68,52] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[94,35] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,12] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/classloaderview/ClassLoaderViewHelper.java:[95,52] cannot find symbol symbol : class MultiParentClassLoader location: class org.apache.geronimo.console.classloaderview.ClassLoaderViewHelper /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[63,37] cannot find symbol symbol : method getDependencies() location: class org.apache.geronimo.kernel.config.Configuration /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/dependencyview/DependencyViewHelper.java:[66,37] cannot find symbol symbol : method getServiceParents() location: class org.apache.geronimo.kernel.config.Configuration /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/jmxmanager/JMXManagerHelper.java:[142,44] [deprecation] listGBeans(javax.management.ObjectName) in org.apache.geronimo.kernel.Kernel has been deprecated /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[414,25] [deprecation] uk.ltd.getahead.dwr.WebContextFactory in uk.ltd.getahead.dwr has been deprecated /home/jeffchi/Geronimo/SourceCode/server/trunk/plugins/debugviews/debugviews-portlets/src/main/java/org/apache/geronimo/console/ldapmanager/LDAPManagerHelper.java:[414,42] [deprecation] get() in uk.ltd.getahead.dwr.WebContextFactory has been deprecated /home/jeffchi/Geronimo/SourceCod
Build Error
Hi Devs, I am trying to build Geronimo trunk and encountering the following error while building: Can you please see why this error occurs? Many Thanks, rahul [ERROR] Could not load deployer configuration: org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car: ADD org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car: READING FINISHED org.apache.geronimo.kernel.config.LifecycleException: load of org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:306) at org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:356) at org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:243) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.geronimo.framework.geronimo-gbean-deployer [1]: package; (package=org.apache.ger onimo.deployment) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3357) at org.apache.felix.framework.Felix.startBundle(Felix.java:1698) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:301) ... 21 more [INFO] [ERROR] BUILD ERROR [INFO] [INFO] could not package plugin Embedded error: org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car (configId: org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: could not package plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[jira] Closed: (GERONIMO-5138) G 2.1 branch activemq build error saying that 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor
[ https://issues.apache.org/jira/browse/GERONIMO-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5138. -- Resolution: Fixed Fix Version/s: 2.1.5 This has been fixed when upgrade the server root pom to leverage genesis 2.0. So closing it. Thanks all the same. > G 2.1 branch activemq build error saying that > 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor > --- > > Key: GERONIMO-5138 > URL: https://issues.apache.org/jira/browse/GERONIMO-5138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.1.5 > > Attachments: GERONIMO-5138.patch > > > [INFO] > > [INFO] Building Geronimo Plugins, ActiveMQ :: Portlets > [INFO]task-segment: [install] > [INFO] > > [INFO] > -------- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Internal error in the plugin manager getting plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the > plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': > Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:330) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:224) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540) > ... 18 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5138) G 2.1 branch activemq build error saying that 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor
[ https://issues.apache.org/jira/browse/GERONIMO-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5138: -- Attachment: GERONIMO-5138.patch Upgrading the jspc-maven-plugin version from 2.0-alpha-1-20070806 to 2.0-alpha-2 can resolve the problem. > G 2.1 branch activemq build error saying that > 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor > --- > > Key: GERONIMO-5138 > URL: https://issues.apache.org/jira/browse/GERONIMO-5138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.5 >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5138.patch > > > [INFO] > > [INFO] Building Geronimo Plugins, ActiveMQ :: Portlets > [INFO]task-segment: [install] > [INFO] > > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Internal error in the plugin manager getting plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the > plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': > Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Plugin > 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an > invalid descriptor: > 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:330) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:224) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540) > ... 18 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5138) G 2.1 branch activemq build error saying that 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor
G 2.1 branch activemq build error saying that 'org.codehaus.mojo.jspc:jspc-maven-plugin' has invalid descriptor --- Key: GERONIMO-5138 URL: https://issues.apache.org/jira/browse/GERONIMO-5138 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.5 Reporter: Forrest Xia Assignee: Forrest Xia [INFO] [INFO] Building Geronimo Plugins, ActiveMQ :: Portlets [INFO]task-segment: [install] [INFO] [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:330) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:224) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540) ... 18 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Puzzling 3.0 build error
David Jencks wrote:
Can you run it with -e or -X? However, these schemas are all ones
that xmlbeans should not need to compile for this plugin, it should be
using the already compiled classes from the bundles that already have
them. So I think there's a classloading problem involved. The
xmlbeans plugin is not osgi based, so I don't think its caused by bad
Export-Package specification. The two things to check are that:
1. the bundles from the modules that do have these schemas do contain
the xmlbeans classes and .xsb files.
2. the bundles are actually on the xmlbeans plugin's classpath.
I would have guessed missing .xsb files but checking my copy of
geronimo-naming-builder it looks like they are present.
Looks like this was just a stupid error on my part. I hadn't built the
new version of the j2ee plugin yet, so of course it wasn't finding these.
Rick
thanks
david jencks
On Oct 20, 2009, at 8:36 AM, Rick McGuire wrote:
I'm trying to get the Tomcat plugin building, and I'm getting a
puzzling error trying to build geronimo-tomcat-builder:
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Builder
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6-builder\targe
t (included: [**], excluded: [])
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-naming-1.2.xsd (The system cannot find
the file s
pecified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-application-2.0.xsd (The system cannot
find the f
ile specified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-module-1.2.xsd (The system cannot find
the file s
pecified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-jaspi.xsd (The system cannot find the
file specif
ied)
Time to build schema type system: 5.875 seconds
BUILD FAILED
[INFO]
--------
[ERROR] BUILD ERROR
[INFO]
[INFO] XmlBeans compile failed:
It appears like it is looking in the wrong location for the
references xsd files. I haven't been able to spot any obvious
changes from the other plugins that have already been converted that
might also be required here.
Rick
Re: Puzzling 3.0 build error
Can you run it with -e or -X? However, these schemas are all ones
that xmlbeans should not need to compile for this plugin, it should be
using the already compiled classes from the bundles that already have
them. So I think there's a classloading problem involved. The
xmlbeans plugin is not osgi based, so I don't think its caused by bad
Export-Package specification. The two things to check are that:
1. the bundles from the modules that do have these schemas do contain
the xmlbeans classes and .xsb files.
2. the bundles are actually on the xmlbeans plugin's classpath.
I would have guessed missing .xsb files but checking my copy of
geronimo-naming-builder it looks like they are present.
thanks
david jencks
On Oct 20, 2009, at 8:36 AM, Rick McGuire wrote:
I'm trying to get the Tomcat plugin building, and I'm getting a
puzzling error trying to build geronimo-tomcat-builder:
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Builder
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set: C:\g-3.0\plugins\tomcat\geronimo-tomcat6-
builder\targe
t (included: [**], excluded: [])
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
IO Error java.io.FileNotFoundException: C:\g-3.0\plugins\tomcat
\geronimo-tomcat6
-builder\src\main\xsd\geronimo-naming-1.2.xsd (The system cannot
find the file s
pecified)
IO Error java.io.FileNotFoundException: C:\g-3.0\plugins\tomcat
\geronimo-tomcat6
-builder\src\main\xsd\geronimo-application-2.0.xsd (The system
cannot find the f
ile specified)
IO Error java.io.FileNotFoundException: C:\g-3.0\plugins\tomcat
\geronimo-tomcat6
-builder\src\main\xsd\geronimo-module-1.2.xsd (The system cannot
find the file s
pecified)
IO Error java.io.FileNotFoundException: C:\g-3.0\plugins\tomcat
\geronimo-tomcat6
-builder\src\main\xsd\geronimo-jaspi.xsd (The system cannot find the
file specif
ied)
Time to build schema type system: 5.875 seconds
BUILD FAILED
[INFO]
----
[ERROR] BUILD ERROR
[INFO]
[INFO] XmlBeans compile failed:
It appears like it is looking in the wrong location for the
references xsd files. I haven't been able to spot any obvious
changes from the other plugins that have already been converted that
might also be required here.
Rick
Puzzling 3.0 build error
I'm trying to get the Tomcat plugin building, and I'm getting a puzzling
error trying to build geronimo-tomcat-builder:
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, Tomcat :: Builder
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6-builder\targe
t (included: [**], excluded: [])
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-naming-1.2.xsd (The system cannot find
the file s
pecified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-application-2.0.xsd (The system cannot
find the f
ile specified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-module-1.2.xsd (The system cannot find
the file s
pecified)
IO Error java.io.FileNotFoundException:
C:\g-3.0\plugins\tomcat\geronimo-tomcat6
-builder\src\main\xsd\geronimo-jaspi.xsd (The system cannot find the
file specif
ied)
Time to build schema type system: 5.875 seconds
BUILD FAILED
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] XmlBeans compile failed:
It appears like it is looking in the wrong location for the references
xsd files. I haven't been able to spot any obvious changes from the
other plugins that have already been converted that might also be
required here.
Rick
[jira] Closed: (GERONIMO-4889) sysdb-portlets BUILD ERROR
[ https://issues.apache.org/jira/browse/GERONIMO-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Higuchi closed GERONIMO-4889. --- Resolution: Invalid Fix Version/s: 2.2 > sysdb-portlets BUILD ERROR > -- > > Key: GERONIMO-4889 > URL: https://issues.apache.org/jira/browse/GERONIMO-4889 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.2 >Reporter: Akira Higuchi > Fix For: 2.2 > > > I got error while building System-databse portelts. Error message was same as > "2.2/2009022/build-2000.log". > I found jar files from this URL, and installed jar files manually. > > https://repository.apache.org/content/repositories/public/org/apache/geronimo/ext/tomcat/ > Jar files > :jasper-6.0.20.0.jar,shared-6.0.20.0.jar,jasper-el-6.0.20.0.jar,tribes-6.0.20.0.jar,catalina-6.0.20.0.jar,util-6.0.20.0-javadoc.jar > > After "mvn clean", I built sysdb-portlets again. But,I got different error > message. > > [INFO] > > > > [ERROR] FATAL ERROR > > [INFO] > > > > [INFO] can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > > Stacktrace: > > [INFO] -- > > [INFO] Trace > > org.apache.jasper.JasperException: can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > It was jspc erorr, then I removed jspc-maven-plugin and maven-war-plugin from > pom.xml. Build was successful, > but test result of sysdb-portlets is not good. > Thank you. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4889) sysdb-portlets BUILD ERROR
[ https://issues.apache.org/jira/browse/GERONIMO-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759101#action_12759101 ] Akira Higuchi commented on GERONIMO-4889: - REX, On my env,I can build successfully, and I could test portlet . Had you finished tomcat staging? I would like to confirm if I can close this issue. Thank you. > sysdb-portlets BUILD ERROR > -- > > Key: GERONIMO-4889 > URL: https://issues.apache.org/jira/browse/GERONIMO-4889 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.2 >Reporter: Akira Higuchi > > I got error while building System-databse portelts. Error message was same as > "2.2/2009022/build-2000.log". > I found jar files from this URL, and installed jar files manually. > > https://repository.apache.org/content/repositories/public/org/apache/geronimo/ext/tomcat/ > Jar files > :jasper-6.0.20.0.jar,shared-6.0.20.0.jar,jasper-el-6.0.20.0.jar,tribes-6.0.20.0.jar,catalina-6.0.20.0.jar,util-6.0.20.0-javadoc.jar > > After "mvn clean", I built sysdb-portlets again. But,I got different error > message. > > [INFO] > > > > [ERROR] FATAL ERROR > > [INFO] > > > > [INFO] can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > > Stacktrace: > > [INFO] -- > > [INFO] Trace > > org.apache.jasper.JasperException: can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > It was jspc erorr, then I removed jspc-maven-plugin and maven-war-plugin from > pom.xml. Build was successful, > but test result of sysdb-portlets is not good. > Thank you. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4889) sysdb-portlets BUILD ERROR
[ https://issues.apache.org/jira/browse/GERONIMO-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758560#action_12758560 ] Rex Wang commented on GERONIMO-4889: Just try on my env, can build successful, please just wait our tomcat staging resume... -Rex > sysdb-portlets BUILD ERROR > -- > > Key: GERONIMO-4889 > URL: https://issues.apache.org/jira/browse/GERONIMO-4889 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.2 >Reporter: Akira Higuchi > > I got error while building System-databse portelts. Error message was same as > "2.2/2009022/build-2000.log". > I found jar files from this URL, and installed jar files manually. > > https://repository.apache.org/content/repositories/public/org/apache/geronimo/ext/tomcat/ > Jar files > :jasper-6.0.20.0.jar,shared-6.0.20.0.jar,jasper-el-6.0.20.0.jar,tribes-6.0.20.0.jar,catalina-6.0.20.0.jar,util-6.0.20.0-javadoc.jar > > After "mvn clean", I built sysdb-portlets again. But,I got different error > message. > > [INFO] > > > > [ERROR] FATAL ERROR > > [INFO] > > > > [INFO] can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > > Stacktrace: > > [INFO] -- > > [INFO] Trace > > org.apache.jasper.JasperException: can't compile JSP class: > > > > An error occurred at line: 1 in the generated java file > > The type org.apache.InstanceManager cannot be resolved. It is indirectly > > referenced from required .class files > > > > An error occurred at line: 18 in the generated java file > > org.apache.InstanceManager cannot be resolved to a type > > > > An error occurred at line: 28 in the generated java file > > _jsp_instancemanager cannot be resolved > > > It was jspc erorr, then I removed jspc-maven-plugin and maven-war-plugin from > pom.xml. Build was successful, > but test result of sysdb-portlets is not good. > Thank you. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4889) sysdb-portlets BUILD ERROR
sysdb-portlets BUILD ERROR -- Key: GERONIMO-4889 URL: https://issues.apache.org/jira/browse/GERONIMO-4889 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: databases Affects Versions: 2.2 Reporter: Akira Higuchi I got error while building System-databse portelts. Error message was same as "2.2/2009022/build-2000.log". I found jar files from this URL, and installed jar files manually. https://repository.apache.org/content/repositories/public/org/apache/geronimo/ext/tomcat/ Jar files :jasper-6.0.20.0.jar,shared-6.0.20.0.jar,jasper-el-6.0.20.0.jar,tribes-6.0.20.0.jar,catalina-6.0.20.0.jar,util-6.0.20.0-javadoc.jar After "mvn clean", I built sysdb-portlets again. But,I got different error message. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] can't compile JSP class: > > An error occurred at line: 1 in the generated java file > The type org.apache.InstanceManager cannot be resolved. It is indirectly > referenced from required .class files > > An error occurred at line: 18 in the generated java file > org.apache.InstanceManager cannot be resolved to a type > > An error occurred at line: 28 in the generated java file > _jsp_instancemanager cannot be resolved > > Stacktrace: > [INFO] -- > [INFO] Trace > org.apache.jasper.JasperException: can't compile JSP class: > > An error occurred at line: 1 in the generated java file > The type org.apache.InstanceManager cannot be resolved. It is indirectly > referenced from required .class files > > An error occurred at line: 18 in the generated java file > org.apache.InstanceManager cannot be resolved to a type > > An error occurred at line: 28 in the generated java file > _jsp_instancemanager cannot be resolved > It was jspc erorr, then I removed jspc-maven-plugin and maven-war-plugin from pom.xml. Build was successful, but test result of sysdb-portlets is not good. Thank you. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Trunk Build Error - geronimo-jetty7-jee5 assembly?
I've never seen this problem. I'm assuming you are trying to build the entire server with the same jdk? I have run into problems switching from java 6 to java 5, even when using java 5 class file format, because some added operations in java 6 classes get added to serialized GBeanInfos; however this looks like a very different kind of problem. I guess if you can't figure out what is going on you might comment out the affected code since it doesn't look like it would be involved in the wadi problem you are looking into. thanks david jencks On Sep 5, 2009, at 6:25 PM, Gianny Damour wrote: Hi, I am not able to build the geronimo-jetty7-jee5 assembly due to the following error: [java] Exception in thread "main" java.lang.NoSuchMethodError: org .apache .xalan.transformer.SerializerSwitcher.switchSerializerIfHTML(Ljava/ lang/String;Ljava/lang/String;Ljava/util/Properties;Lorg/apache/xml/ serializer/Serializer;)Lorg/apache/xml/serializer/Serializer; [java] at org .apache .xalan .transformer .TransformerIdentityImpl.startElement(TransformerIdentityImpl.java: 1044) [java] at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359) [java] at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145) [java] at org .apache .xalan .transformer .TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390) [java] at org.apache.geronimo.jaxws.builder.GShellCommandRegistration $Layout.save(GShellCommandRegistration.java:276) [java] at org .apache .geronimo .jaxws .builder .GShellCommandRegistration.main(GShellCommandRegistration.java:158) I am using maven 2.0.10 (tried with maven 2.2.1) with JDK 1.6 (tried with JDK 1.5) with a clean repo. Any clues so that I can try to reproduce a problem with form authentication + WADI clustering? Thanks, Gianny
Trunk Build Error - geronimo-jetty7-jee5 assembly?
Hi, I am not able to build the geronimo-jetty7-jee5 assembly due to the following error: [java] Exception in thread "main" java.lang.NoSuchMethodError: org.apache.xalan.transformer.SerializerSwitcher.switchSerializerIfHTML (Ljava/lang/String;Ljava/lang/String;Ljava/util/Properties;Lorg/ apache/xml/serializer/Serializer;)Lorg/apache/xml/serializer/Serializer; [java] at org.apache.xalan.transformer.TransformerIdentityImpl.startElement (TransformerIdentityImpl.java:1044) [java] at org.apache.xml.serializer.TreeWalker.startNode (TreeWalker.java:359) [java] at org.apache.xml.serializer.TreeWalker.traverse (TreeWalker.java:145) [java] at org.apache.xalan.transformer.TransformerIdentityImpl.transform (TransformerIdentityImpl.java:390) [java] at org.apache.geronimo.jaxws.builder.GShellCommandRegistration $Layout.save(GShellCommandRegistration.java:276) [java] at org.apache.geronimo.jaxws.builder.GShellCommandRegistration.main (GShellCommandRegistration.java:158) I am using maven 2.0.10 (tried with maven 2.2.1) with JDK 1.6 (tried with JDK 1.5) with a clean repo. Any clues so that I can try to reproduce a problem with form authentication + WADI clustering? Thanks, Gianny
Re: [Build Error] Missing Artifact
Fixed in Rev802023 by moving up to 7.0.0.RC4-SNAPSHOT. -Donald rahul.soa wrote: Hello Devs, I tried building a brand new Geronimo server and got the missing artifact error. I see this URL is not available (404 error) http://repository.apache.org/snapshots/org/eclipse/jetty/jetty-servlet/7.0.0.RC3-SNAPSHOT/jetty-servlet-7.0.0.RC3-SNAPSHOT.jar Full traces are given below: Can you please help me in this? Thanks. Best Regards, Rahul - [INFO] Unable to find resource 'org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT' in repository codehaus.snapshots (http://snapshots.repository.codehaus.org) Downloading: http://repository.apache.org/snapshots/org/eclipse/jetty/jetty-servlet/7.0.0.RC3-SNAPSHOT/jetty-servlet-7.0.0.RC3-SNAPSHOT.jar [INFO] Unable to find resource 'org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT' in repository apache.snapshots (http://repository.apache.org/snapshots) [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.eclipse.jetty:jetty-ajp:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:7.0.0.RC3-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:7.0.0.RC3-SNAPSHOT 3) org.eclipse.jetty:jetty-webapp:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:7.0.0.RC3-SNAPSHOT 4) org.eclipse.jetty:jetty-security:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:7.0.0.RC3-SNAPSHOT 5) org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT -- 5 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT from
[Build Error] Missing Artifact
Hello Devs, I tried building a brand new Geronimo server and got the missing artifact error. I see this URL is not available (404 error) http://repository.apache.org/snapshots/org/eclipse/jetty/jetty-servlet/7.0.0.RC3-SNAPSHOT/jetty-servlet-7.0.0.RC3-SNAPSHOT.jar Full traces are given below: Can you please help me in this? Thanks. Best Regards, Rahul - [INFO] Unable to find resource 'org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT' in repository codehaus.snapshots (http://snapshots.repository.codehaus.org) Downloading: http://repository.apache.org/snapshots/org/eclipse/jetty/jetty-servlet/7.0.0.RC3-SNAPSHOT/jetty-servlet-7.0.0.RC3-SNAPSHOT.jar [INFO] Unable to find resource 'org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT' in repository apache.snapshots (http://repository.apache.org/snapshots) [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.eclipse.jetty:jetty-ajp:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:7.0.0.RC3-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:7.0.0.RC3-SNAPSHOT 3) org.eclipse.jetty:jetty-webapp:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:7.0.0.RC3-SNAPSHOT 4) org.eclipse.jetty:jetty-security:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:7.0.0.RC3-SNAPSHOT 5) org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=7.0.0.RC3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:7.0.0.RC3-SNAPSHOT -- 5 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty7:jar:2.2-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.rep
Re: Build Error
I can't recreate your problem locally. Anyway, things you could give it a
try:
1, Change setting.xml to use a clean local repo.
2, Switch to JDK 1.5.
On Thu, Jul 2, 2009 at 2:55 PM, rahul.soa wrote:
> Thanks for your reply Shawn.
>
> I am using version 6. I have not changed my JDK recently.
>
> [ra...@localhost modules]$ java -version
> java version "1.6.0_12"
> Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
> Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode)
>
>
> I also tried the mvn clean build after removing the
> /.m2/repository/org/apache/geronimo/modules/geronimo-jaxws-ejb-builder. but
> received the similar error.
>
> Thanks again.
>
> Best Regards,
> Rahul
>
>
> Full traces are below:
>
>
> [INFO]
>
> [INFO] Building Geronimo Plugins, AXIS2 :: EJB Deployer
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO] [genesis:validate-configuration {execution: default}]
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] [remote-resources:process {execution: default}]
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [INFO] [resources:resources]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/src/main/resources
> [INFO] skip non existing resourceDirectory
> /home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/src/main/filtered-resources
> [INFO] Copying 3 resources
> [INFO] [car:validate-configuration]
> [INFO] [car:prepare-plan]
> [INFO] Generated:
> /home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/target/resources/META-INF/plan.xml
> [INFO] [car:verify-no-dependency-change]
> [INFO] [car:package]
> [INFO] Packaging module configuration:
> /home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/target/resources/META-INF/plan.xml
> [INFO] Started deployer:
> org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
> [ERROR] Deployment failed due to
> java.lang.VerifyError: (class:
> org/apache/geronimo/jaxws/builder/JAXWSEJBModuleBuilderExtension, method:
> addGBeans signature:
> (Lorg/apache/geronimo/j2ee/deployment/EARContext;Lorg/apache/geronimo/j2ee/deployment/Module;Ljava/lang/ClassLoader;Ljava/util/Collection;)V)
> Incompatible argument to function
> java.lang.Class.getDeclaredMethods0(Native Method)
> java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
> java.lang.Class.getDeclaredMethod(Class.java:1935)
>
> org.apache.geronimo.gbean.BasicGBeanInfoFactory.getGBeanInfo(BasicGBeanInfoFactory.java:47)
>
> org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:60)
>
> org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
>
> org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
>
> org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
>
> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
>
> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
> org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
> sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
>
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
>
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
>
> org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:483)
>
> org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:309)
>
> org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:209)
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>
> org.apache.maven.lifecycle.DefaultLifecycleExecu
Re: Build Error
Thanks for your reply Shawn.
I am using version 6. I have not changed my JDK recently.
[ra...@localhost modules]$ java -version
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode)
I also tried the mvn clean build after removing the
/.m2/repository/org/apache/geronimo/modules/geronimo-jaxws-ejb-builder. but
received the similar error.
Thanks again.
Best Regards,
Rahul
Full traces are below:
[INFO]
[INFO] Building Geronimo Plugins, AXIS2 :: EJB Deployer
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/src/main/resources
[INFO] skip non existing resourceDirectory
/home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/target/resources/META-INF/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/rahul/GeronimoServer/plugins/axis2/axis2-ejb-deployer/target/resources/META-INF/plan.xml
[INFO] Started deployer:
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[ERROR] Deployment failed due to
java.lang.VerifyError: (class:
org/apache/geronimo/jaxws/builder/JAXWSEJBModuleBuilderExtension, method:
addGBeans signature:
(Lorg/apache/geronimo/j2ee/deployment/EARContext;Lorg/apache/geronimo/j2ee/deployment/Module;Ljava/lang/ClassLoader;Ljava/util/Collection;)V)
Incompatible argument to function
java.lang.Class.getDeclaredMethods0(Native Method)
java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
java.lang.Class.getDeclaredMethod(Class.java:1935)
org.apache.geronimo.gbean.BasicGBeanInfoFactory.getGBeanInfo(BasicGBeanInfoFactory.java:47)
org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:60)
org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:483)
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:309)
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:209)
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
org.apache.maven.DefaultMaven.execute(DefaultMaven.
Re: Build Error
What's JDK version are you using ? Did you change your JDK recently ? Seems like a imcompatiblity classes problem in geronimo-jaxws-ejb-builder. You can delete your localrepo/org/apache/modules/geronimo-jaxws-ejb-builder and try the build again. On Thu, Jul 2, 2009 at 7:30 AM, rahul.soa wrote: > JAXWSEJBModuleBuilderExtension -- Shawn
Build Error
Hello Devs,
I have got an abrupt error (as I was not getting it before) while building
(clean build) the CXF plugin in Geronimo. Can someone please point me to the
root of the problem? The full traces are given below:
Thanks.
Best Regards,
Rahul
[INFO]
[INFO] Building Geronimo Plugins, CXF :: EJB Deployer
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting file set:
/home/rahul/GeronimoServer/plugins/cxf/cxf-ejb-deployer/target (included:
[**], excluded: [])
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[WARNING] Invalid project model for artifact [stax-ex:org.jvnet.staxex:1.0].
It will be ignored by the remote resources Mojo.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/rahul/GeronimoServer/plugins/cxf/cxf-ejb-deployer/src/main/resources
[INFO] skip non existing resourceDirectory
/home/rahul/GeronimoServer/plugins/cxf/cxf-ejb-deployer/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] Generated:
/home/rahul/GeronimoServer/plugins/cxf/cxf-ejb-deployer/target/resources/META-INF/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] [car:package]
[WARNING] POM for 'org.jvnet.staxex:stax-ex:pom:1.0:compile' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[INFO] Packaging module configuration:
/home/rahul/GeronimoServer/plugins/cxf/cxf-ejb-deployer/target/resources/META-INF/plan.xml
[INFO] Started deployer:
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[ERROR] Deployment failed due to
java.lang.VerifyError: (class:
org/apache/geronimo/jaxws/builder/JAXWSEJBModuleBuilderExtension, method:
addGBeans signature:
(Lorg/apache/geronimo/j2ee/deployment/EARContext;Lorg/apache/geronimo/j2ee/deployment/Module;Ljava/lang/ClassLoader;Ljava/util/Collection;)V)
Incompatible argument to function
java.lang.Class.getDeclaredMethods0(Native Method)
java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
java.lang.Class.getDeclaredMethod(Class.java:1935)
org.apache.geronimo.gbean.BasicGBeanInfoFactory.getGBeanInfo(BasicGBeanInfoFactory.java:47)
org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:60)
org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:483)
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:309)
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:209)
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
org.apac
Re: [Geronimo] - Build Error
Got it. thanks for your prompt reply.
Jeff
On Tue, Jun 30, 2009 at 4:00 PM, rahul.soa wrote:
> Hello Jeff,
>
> I did *build new trunk* as I had an old one and was getting a few different
> errors too. Thus, did nothing to bypass that particular error.
>
> Thanks.
> Rahul
>
> On Tue, Jun 30, 2009 at 9:48 AM, chi runhua wrote:
>
>> Hi Rahul.soa,
>>
>> Could you let me know how you bypass the error, your tips might be
>> contributed to our doc.
>>
>> Thanks in advance.
>>
>> Jeff C
>>
>>
>> On Sat, Jun 27, 2009 at 1:15 AM, rahul.soa wrote:
>>
>>> Hello all,
>>>
>>> You can ignore this email as I built a new server.
>>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Rahul
>>>
>>>
>>>
>>> On Fri, Jun 26, 2009 at 1:05 AM, rahul.soa wrote:
>>>
>>>> Hello Devs,
>>>>
>>>> While building the Geronimo from the scratch, I have got the build error
>>>> due to the following error
>>>>
>>>> Embedded error: org.apache.geronimo.gbean.GBeanInfoFactoryException: *
>>>> Cannot create a GBeanInfo for*
>>>> [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>>>> *
>>>> Full trace:*
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Building Geronimo Plugins, OpenEJB :: Deployer
>>>> [INFO]task-segment: [install]
>>>> [INFO]
>>>>
>>>> [INFO] [enforcer:enforce {execution: default}]
>>>> [INFO] [remote-resources:process {execution: process}]
>>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>>> license.name is not a valid reference.
>>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>>> license.name is not a valid reference.
>>>> [INFO] [remote-resources:process {execution: default}]
>>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>>> license.name is not a valid reference.
>>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>>> license.name is not a valid reference.
>>>> [INFO] [dependency:unpack {execution: default}]
>>>> [INFO] snapshot
>>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>>> for updates from apache.org
>>>> [INFO] snapshot
>>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>>> for updates from apache.snapshots
>>>> [INFO] snapshot
>>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>>> for updates from apache.nexus.snapshots
>>>> [INFO] snapshot
>>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>>> for updates from apache-snapshots
>>>> [INFO] snapshot
>>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>>> for updates from codehaus-snapshots
>>>> [INFO] [resources:resources]
>>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>>> [INFO] skip non existing resourceDirectory
>>>> /home/rahul/server/plugins/openejb/openejb-deployer/src/main/resources
>>>> [INFO] Copying 3 resources
>>>> [INFO] Copying 3 resources
>>>> [INFO] [car:validate-configuration]
>>>> [INFO] [car:prepare-plan]
>>>> [INFO] Generated:
>>>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>>>> [INFO] [car:verify-no-dependency-change]
>>>> [INFO] [car:package]
>>>> [INFO] Packaging module configuration:
>>>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>>>> [INFO] Started deployer:
>>>> org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
>>>> [ERROR] Deployment failed due to
>>>> org.apache.geronimo.gbean.GBeanInfoFactoryException: Cannot create a
>>
Re: [Geronimo] - Build Error
Hello Jeff,
I did *build new trunk* as I had an old one and was getting a few different
errors too. Thus, did nothing to bypass that particular error.
Thanks.
Rahul
On Tue, Jun 30, 2009 at 9:48 AM, chi runhua wrote:
> Hi Rahul.soa,
>
> Could you let me know how you bypass the error, your tips might be
> contributed to our doc.
>
> Thanks in advance.
>
> Jeff C
>
>
> On Sat, Jun 27, 2009 at 1:15 AM, rahul.soa wrote:
>
>> Hello all,
>>
>> You can ignore this email as I built a new server.
>>
>> Thanks.
>>
>> Best Regards,
>> Rahul
>>
>>
>>
>> On Fri, Jun 26, 2009 at 1:05 AM, rahul.soa wrote:
>>
>>> Hello Devs,
>>>
>>> While building the Geronimo from the scratch, I have got the build error
>>> due to the following error
>>>
>>> Embedded error: org.apache.geronimo.gbean.GBeanInfoFactoryException: *
>>> Cannot create a GBeanInfo for*
>>> [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>>> *
>>> Full trace:*
>>>
>>> [INFO]
>>>
>>> [INFO] Building Geronimo Plugins, OpenEJB :: Deployer
>>> [INFO]task-segment: [install]
>>> [INFO]
>>>
>>> [INFO] [enforcer:enforce {execution: default}]
>>> [INFO] [remote-resources:process {execution: process}]
>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>> license.name is not a valid reference.
>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>> license.name is not a valid reference.
>>> [INFO] [remote-resources:process {execution: default}]
>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>> license.name is not a valid reference.
>>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>>> license.name is not a valid reference.
>>> [INFO] [dependency:unpack {execution: default}]
>>> [INFO] snapshot
>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>> for updates from apache.org
>>> [INFO] snapshot
>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>> for updates from apache.snapshots
>>> [INFO] snapshot
>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>> for updates from apache.nexus.snapshots
>>> [INFO] snapshot
>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>> for updates from apache-snapshots
>>> [INFO] snapshot
>>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>>> for updates from codehaus-snapshots
>>> [INFO] [resources:resources]
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] skip non existing resourceDirectory
>>> /home/rahul/server/plugins/openejb/openejb-deployer/src/main/resources
>>> [INFO] Copying 3 resources
>>> [INFO] Copying 3 resources
>>> [INFO] [car:validate-configuration]
>>> [INFO] [car:prepare-plan]
>>> [INFO] Generated:
>>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>>> [INFO] [car:verify-no-dependency-change]
>>> [INFO] [car:package]
>>> [INFO] Packaging module configuration:
>>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>>> [INFO] Started deployer:
>>> org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
>>> [ERROR] Deployment failed due to
>>> org.apache.geronimo.gbean.GBeanInfoFactoryException: Cannot create a
>>> GBeanInfo for [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>>>
>>> org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:64)
>>>
>>> org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
>>>
>>> org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
>>>
>>> org.apache.geronimo.deployment.Namesp
Re: [Geronimo] - Build Error
Hi Rahul.soa,
Could you let me know how you bypass the error, your tips might be
contributed to our doc.
Thanks in advance.
Jeff C
On Sat, Jun 27, 2009 at 1:15 AM, rahul.soa wrote:
> Hello all,
>
> You can ignore this email as I built a new server.
>
> Thanks.
>
> Best Regards,
> Rahul
>
>
>
> On Fri, Jun 26, 2009 at 1:05 AM, rahul.soa wrote:
>
>> Hello Devs,
>>
>> While building the Geronimo from the scratch, I have got the build error
>> due to the following error
>>
>> Embedded error: org.apache.geronimo.gbean.GBeanInfoFactoryException: *
>> Cannot create a GBeanInfo for*
>> [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>> *
>> Full trace:*
>>
>> [INFO]
>>
>> [INFO] Building Geronimo Plugins, OpenEJB :: Deployer
>> [INFO]task-segment: [install]
>> [INFO]
>>
>> [INFO] [enforcer:enforce {execution: default}]
>> [INFO] [remote-resources:process {execution: process}]
>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>> license.name is not a valid reference.
>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>> license.name is not a valid reference.
>> [INFO] [remote-resources:process {execution: default}]
>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>> license.name is not a valid reference.
>> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
>> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
>> license.name is not a valid reference.
>> [INFO] [dependency:unpack {execution: default}]
>> [INFO] snapshot
>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>> for updates from apache.org
>> [INFO] snapshot
>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>> for updates from apache.snapshots
>> [INFO] snapshot
>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>> for updates from apache.nexus.snapshots
>> [INFO] snapshot
>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>> for updates from apache-snapshots
>> [INFO] snapshot
>> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
>> for updates from codehaus-snapshots
>> [INFO] [resources:resources]
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] skip non existing resourceDirectory
>> /home/rahul/server/plugins/openejb/openejb-deployer/src/main/resources
>> [INFO] Copying 3 resources
>> [INFO] Copying 3 resources
>> [INFO] [car:validate-configuration]
>> [INFO] [car:prepare-plan]
>> [INFO] Generated:
>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>> [INFO] [car:verify-no-dependency-change]
>> [INFO] [car:package]
>> [INFO] Packaging module configuration:
>> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
>> [INFO] Started deployer:
>> org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
>> [ERROR] Deployment failed due to
>> org.apache.geronimo.gbean.GBeanInfoFactoryException: Cannot create a
>> GBeanInfo for [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>>
>> org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:64)
>>
>> org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
>>
>> org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
>>
>> org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
>>
>> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
>>
>> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
>> org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
>> sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> java.lang.reflect.Method.invoke(
Re: [Geronimo] - Build Error
Hello all,
You can ignore this email as I built a new server.
Thanks.
Best Regards,
Rahul
On Fri, Jun 26, 2009 at 1:05 AM, rahul.soa wrote:
> Hello Devs,
>
> While building the Geronimo from the scratch, I have got the build error
> due to the following error
>
> Embedded error: org.apache.geronimo.gbean.GBeanInfoFactoryException: *
> Cannot create a GBeanInfo for*
> [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
> *
> Full trace:*
>
> [INFO]
>
> [INFO] Building Geronimo Plugins, OpenEJB :: Deployer
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] [remote-resources:process {execution: process}]
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [INFO] [remote-resources:process {execution: default}]
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException:
> reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
> license.name is not a valid reference.
> [INFO] [dependency:unpack {execution: default}]
> [INFO] snapshot
> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
> for updates from apache.org
> [INFO] snapshot
> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
> for updates from apache.snapshots
> [INFO] snapshot
> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
> for updates from apache.nexus.snapshots
> [INFO] snapshot
> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
> for updates from apache-snapshots
> [INFO] snapshot
> org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
> for updates from codehaus-snapshots
> [INFO] [resources:resources]
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/rahul/server/plugins/openejb/openejb-deployer/src/main/resources
> [INFO] Copying 3 resources
> [INFO] Copying 3 resources
> [INFO] [car:validate-configuration]
> [INFO] [car:prepare-plan]
> [INFO] Generated:
> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
> [INFO] [car:verify-no-dependency-change]
> [INFO] [car:package]
> [INFO] Packaging module configuration:
> /home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
> [INFO] Started deployer:
> org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
> [ERROR] Deployment failed due to
> org.apache.geronimo.gbean.GBeanInfoFactoryException: Cannot create a
> GBeanInfo for [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
>
> org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:64)
>
> org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
>
> org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
>
> org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
>
> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
>
> org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
> org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
> sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
>
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
>
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
>
> org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:483)
>
> org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(P
[Geronimo] - Build Error
Hello Devs,
While building the Geronimo from the scratch, I have got the build error due
to the following error
Embedded error: org.apache.geronimo.gbean.GBeanInfoFactoryException: *
Cannot create a GBeanInfo for*
[org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
*
Full trace:*
[INFO]
[INFO] Building Geronimo Plugins, OpenEJB :: Deployer
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: process}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $
license.name is not a valid reference.
[INFO] [dependency:unpack {execution: default}]
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
for updates from apache.org
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
for updates from apache.nexus.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/rahul/server/plugins/openejb/openejb-deployer/src/main/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/rahul/server/plugins/openejb/openejb-deployer/target/resources/META-INF/plan.xml
[INFO] Started deployer:
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[ERROR] Deployment failed due to
org.apache.geronimo.gbean.GBeanInfoFactoryException: Cannot create a
GBeanInfo for [org.apache.geronimo.openejb.deployment.EjbModuleBuilder]
org.apache.geronimo.gbean.MultiGBeanInfoFactory.getGBeanInfo(MultiGBeanInfoFactory.java:64)
org.apache.geronimo.deployment.service.GBeanBuilder.addGBeanData(GBeanBuilder.java:112)
org.apache.geronimo.deployment.service.GBeanBuilder.build(GBeanBuilder.java:107)
org.apache.geronimo.deployment.NamespaceDrivenBuilderCollection.build(NamespaceDrivenBuilderCollection.java:46)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:240)
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199)
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:483)
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:309)
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:209)
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecuto
Re: G 2.2 snapshot build error (activemq-parent not found)
I looks to me that the maven metadata from the merged snapshot repo is
wrong, pointing to the very old people.apache.org repo version.
I pinged the repository list for advice. I suspect that we should get
activemq or infra to delete the old snapshots and probably move to
unique timestamped snapshots.
thanks
david jencks
On Jun 16, 2009, at 7:55 PM, Ivan wrote:
Hi, Geronimo daily build has been stopped for a long time.
Currently, it is blocked by ActiveMQ.
While accessing the new proxy site "http://repository.apache.org/snapshots
", it first forwards the request to the old site "http://people.apache.org/repo/m2-snapshot-repository
", not the new nexus site "https://repository.apache.org/content/repositories/snapshots
". And some files of Active MQ in the people's site are not cleared,
so the build is always failed due to "parent not found". Not sure
what we can do for it.
I have a workaround way, we needs to add two snapshot site : people
site and nexus site explicitly in the Geronimo's pom file, we use
the same repository id to overide the proxy site in the Apache 6 pom
file. So in the build process, Maven could found the new files in
the nexus site.
This is just a temporary solution and we could recover it once the
all those repositories work fine.
I wish that we could see the Geronimo daily build as soon as possible.
Any comment !
Thanks !
2009/6/15 Jarek Gawor
Is there some documentation describing nexus setup at apache? I'm
really confused by the different repositories. For example, the
apache-6.pom points to http://repository.apache.org/snapshots url. But
https://repository.apache.org/index.html#view-repositories does not
list that exact repository url. From browsing the repos it looks to me
like http://repository.apache.org/snapshots is really just an alias
for https://repository.apache.org/content/groups/snapshots-group/. And
that repo looks like a grouping of old snapshots from people and the
new nexus snapshots location. So it seems like
http://repository.apache.org/snapshots already contains the old and
new snapshots.
And if I have this right, adding the old snapshot repo to activemq
module won't work (since it's redundant) and there are some activemq
artifacts already published to
https://repository.apache.org/content/repositories/snapshots. So I
think there is something else going here.
Jarek
On Sat, Jun 13, 2009 at 1:58 PM, David
Jencks wrote:
> Usually we yell at people posting user list questions on the dev
list
> this is actually more appropriate for the dev list.
>
> I suspect the problem is that activemq is not publishing snapshots
to the
> apache nexus instance.
>
> I think the possible solutions are either
> - add the old file based repo into the amq module
> - get amq onto the nexus repo.
>
> The second would IMO be a lot better but more work. I have a
bunch of stuff
> to finish up before I can look into this.
>
> thanks
> david jencks
>
> On Jun 13, 2009, at 8:33 AM, Peter Petersson wrote:
>
>> For some days now I have hit this build error (starting from a
clean local
>> repo).
>> Is this to be expected due to the current flux of the project or
is there
>> a simple fix for this ?
>> regards
>> peter petersson
>>
>> [INFO]
>>
>> [INFO] Building Geronimo Plugins, ActiveMQ v5 :: Core
>> [INFO]task-segment: [clean, install]
>> [INFO]
>>
>> [INFO] [clean:clean]
>> [INFO] [genesis:validate-configuration {execution: default}]
>> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT:
checking
>> for updates from apache.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT:
checking
>> for updates from codehaus.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT:
checking
>> for updates from apache.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT:
checking
>> for updates from codehaus.snapshots
>> Downloading:
>>
http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/activemq-parent/5.3-SNAPSHOT/activemq-parent-5.3-20090417.072917-276.pom
>> [INFO]
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>>
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: null:activemq-core:bundle:null
>>
>> Reason: Cannot find parent: org.apache.activemq:activemq-parent for
>> project: null:activemq-core:bundle:null for project
>> null:activemq-core:bundle:null
>>
>
--
Ivan
Re: G 2.2 snapshot build error (activemq-parent not found)
Hi, Geronimo daily build has been stopped for a long time. Currently, it is
blocked by ActiveMQ.
While accessing the new proxy site "http://repository.apache.org/snapshots";,
it first forwards the request to the old site "
http://people.apache.org/repo/m2-snapshot-repository";, not the new nexus
site "https://repository.apache.org/content/repositories/snapshots";. And
some files of Active MQ in the people's site are not cleared, so the build
is always failed due to "parent not found". Not sure what we can do for it.
I have a workaround way, we needs to add two snapshot site : people site and
nexus site explicitly in the Geronimo's pom file, we use the same repository
id to overide the proxy site in the Apache 6 pom file. So in the build
process, Maven could found the new files in the nexus site.
This is just a temporary solution and we could recover it once the all those
repositories work fine.
I wish that we could see the Geronimo daily build as soon as possible.
Any comment !
Thanks !
2009/6/15 Jarek Gawor
> Is there some documentation describing nexus setup at apache? I'm
> really confused by the different repositories. For example, the
> apache-6.pom points to http://repository.apache.org/snapshots url. But
> https://repository.apache.org/index.html#view-repositories does not
> list that exact repository url. From browsing the repos it looks to me
> like http://repository.apache.org/snapshots is really just an alias
> for https://repository.apache.org/content/groups/snapshots-group/. And
> that repo looks like a grouping of old snapshots from people and the
> new nexus snapshots location. So it seems like
> http://repository.apache.org/snapshots already contains the old and
> new snapshots.
>
> And if I have this right, adding the old snapshot repo to activemq
> module won't work (since it's redundant) and there are some activemq
> artifacts already published to
> https://repository.apache.org/content/repositories/snapshots. So I
> think there is something else going here.
>
> Jarek
>
> On Sat, Jun 13, 2009 at 1:58 PM, David Jencks
> wrote:
> > Usually we yell at people posting user list questions on the dev list
> > this is actually more appropriate for the dev list.
> >
> > I suspect the problem is that activemq is not publishing snapshots to the
> > apache nexus instance.
> >
> > I think the possible solutions are either
> > - add the old file based repo into the amq module
> > - get amq onto the nexus repo.
> >
> > The second would IMO be a lot better but more work. I have a bunch of
> stuff
> > to finish up before I can look into this.
> >
> > thanks
> > david jencks
> >
> > On Jun 13, 2009, at 8:33 AM, Peter Petersson wrote:
> >
> >> For some days now I have hit this build error (starting from a clean
> local
> >> repo).
> >> Is this to be expected due to the current flux of the project or is
> there
> >> a simple fix for this ?
> >> regards
> >> peter petersson
> >>
> >> [INFO]
> >>
> >> [INFO] Building Geronimo Plugins, ActiveMQ v5 :: Core
> >> [INFO]task-segment: [clean, install]
> >> [INFO]
> >>
> >> [INFO] [clean:clean]
> >> [INFO] [genesis:validate-configuration {execution: default}]
> >> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking
> >> for updates from apache.snapshots
> >> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking
> >> for updates from codehaus.snapshots
> >> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT:
> checking
> >> for updates from apache.snapshots
> >> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT:
> checking
> >> for updates from codehaus.snapshots
> >> Downloading:
> >>
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/activemq-parent/5.3-SNAPSHOT/activemq-parent-5.3-20090417.072917-276.pom
> >> [INFO]
> >>
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >>
> >> [INFO] Error building POM (may not be this project's POM).
> >>
> >>
> >> Project ID: null:activemq-core:bundle:null
> >>
> >> Reason: Cannot find parent: org.apache.activemq:activemq-parent for
> >> project: null:activemq-core:bundle:null for project
> >> null:activemq-core:bundle:null
> >>
> >
>
--
Ivan
Re: G 2.2 snapshot build error (activemq-parent not found)
Is there some documentation describing nexus setup at apache? I'm
really confused by the different repositories. For example, the
apache-6.pom points to http://repository.apache.org/snapshots url. But
https://repository.apache.org/index.html#view-repositories does not
list that exact repository url. From browsing the repos it looks to me
like http://repository.apache.org/snapshots is really just an alias
for https://repository.apache.org/content/groups/snapshots-group/. And
that repo looks like a grouping of old snapshots from people and the
new nexus snapshots location. So it seems like
http://repository.apache.org/snapshots already contains the old and
new snapshots.
And if I have this right, adding the old snapshot repo to activemq
module won't work (since it's redundant) and there are some activemq
artifacts already published to
https://repository.apache.org/content/repositories/snapshots. So I
think there is something else going here.
Jarek
On Sat, Jun 13, 2009 at 1:58 PM, David Jencks wrote:
> Usually we yell at people posting user list questions on the dev list
> this is actually more appropriate for the dev list.
>
> I suspect the problem is that activemq is not publishing snapshots to the
> apache nexus instance.
>
> I think the possible solutions are either
> - add the old file based repo into the amq module
> - get amq onto the nexus repo.
>
> The second would IMO be a lot better but more work. Â I have a bunch of stuff
> to finish up before I can look into this.
>
> thanks
> david jencks
>
> On Jun 13, 2009, at 8:33 AM, Peter Petersson wrote:
>
>> For some days now I have hit this build error (starting from a clean local
>> repo).
>> Is this to be expected due to the current flux of the project or is there
>> a simple fix for this ?
>> regards
>> Â peter petersson
>>
>> [INFO]
>>
>> [INFO] Building Geronimo Plugins, ActiveMQ v5 :: Core
>> [INFO] Â Â task-segment: [clean, install]
>> [INFO]
>>
>> [INFO] [clean:clean]
>> [INFO] [genesis:validate-configuration {execution: default}]
>> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking
>> for updates from apache.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking
>> for updates from codehaus.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT: checking
>> for updates from apache.snapshots
>> [INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT: checking
>> for updates from codehaus.snapshots
>> Downloading:
>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/activemq-parent/5.3-SNAPSHOT/activemq-parent-5.3-20090417.072917-276.pom
>> [INFO]
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>>
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: null:activemq-core:bundle:null
>>
>> Reason: Cannot find parent: org.apache.activemq:activemq-parent for
>> project: null:activemq-core:bundle:null for project
>> null:activemq-core:bundle:null
>>
>
[jira] Resolved: (GERONIMODEVTOOLS-134) BUILD ERROR - Reason: Unable to download the artifact from any repository org.apache.geronimo.specs:specs:pom:1.1.1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed resolved GERONIMODEVTOOLS-134. Resolution: Fixed I haven't seen this kind of error in a while and it seems that this JIRA has been open for quite some time. I believe this has been fixed. If this is still an error, please re-open. > BUILD ERROR - Reason: Unable to download the artifact from any repository > org.apache.geronimo.specs:specs:pom:1.1.1 > --- > > Key: GERONIMODEVTOOLS-134 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-134 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0 >Reporter: Jacek Laskowski >Assignee: Jacek Laskowski >Priority: Critical > > Got the following error: > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.geronimo.specs > ArtifactId: specs > Version: 1.1.1 > Reason: Unable to download the artifact from any repository > org.apache.geronimo.specs:specs:pom:1.1.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > apache.incubator (http://people.apache.org/repo/m2-incubating-repository/), > sppatel (http://people.apache.org/~sppatel/maven/repository/), > apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), > codehaus-snapshots (http://snapshots.repository.codehaus.org) > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 140 minutes 58 seconds > [INFO] Finished at: Tue Feb 27 00:50:07 CET 2007 > [INFO] Final Memory: 40M/254M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GEP Build Error for revision 683248
Hi Ashish, I updated GEP Trunk to use the new 2.1.2 server earlier today with
rev. 683355 (instead of the 2.1.2-SNAPSHOT). If you update your local copy of
trunk then do another build, you should be good to go. Thanks
Ashish Jain wrote:
Joe, thanks for your response. However I hit another error
*[INFO] Executing tasks
[unzip] Expanding:
C:\m2repo\org\apache\geronimo\assemblies\geronimo-tomcat6
-javaee5\2.1.2-SNAPSHOT\geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-bin.zip
into C:\
gep_new\trunk\testsuite\launcher
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Error while expanding
C:\m2repo\org\apache\geronimo\assemblies\g
eronimo-tomcat6-javaee5\2.1.2-SNAPSHOT\geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-b
in.zip
C:\m2repo\org\apache\geronimo\assemblies\geronimo-tomcat6-javaee5\2.1.2-SNAPSHOT
\geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-bin.zip (The system cannot find
the pat
h specified)*
As G 2.1.2 is released so snapshot may no longer be available.Attaching
a patch for it. Please see if it can be applied to trunk.
Thanks
Ashish
On Wed, Aug 6, 2008 at 10:50 PM, Joe Bohn <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
That's the version of pluto that we have checked into out svn repo
in trunk. If you aren't planning to build trunk the easiest thing
to do is to just cd into the repository directory of server/trunk
and mvn install. This will add all of the checked in artifacts into
your local m2 repo.
Joe
Ashish Jain wrote:
Hi,
I am getting a missing dependency error while trying to build
GEP. Any suggestions on getting this artifacts rather than
manually downloading it my m2repo.
[INFO]
---
[ERROR] BUILD ERROR
[INFO]
---
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.pluto
-DartifactId=pluto-t
lib \
-Dversion=1.1.6-G643117 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy
the file there:
mvn deploy:deploy-file -DgroupId=org.apache.pluto
-DartifactId=pluto-tagli
\
-Dversion=1.1.6-G643117 -Dpackaging=jar
-Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2
2)
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1
3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2
4) org.apache.geronimo.plugins:pluto-support:car:2.1.2
5) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117
2) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.pluto
-DartifactId=pluto-d
criptor-impl \
-Dversion=1.1.6-G643117 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy
the file there:
mvn deploy:deploy-file -DgroupId=org.apache.pluto
-DartifactId=pluto-descr
tor-impl \
-Dversion=1.1.6-G643117 -Dpackaging=jar
-Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2
2)
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1
3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2
4) org.apache.geronimo.plugins:pluto-support:car:2.1.2
5) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117
3) org.apache.tomcat:jasper:jar:6.0.16-G652117
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tomcat
-DartifactId=jasper
-Dversion=6.0.16-G652117 -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy
the file there:
mvn deploy:deploy-file -DgroupId=org.apache.tomcat
Re: GEP Build Error for revision 683248
Joe, thanks for your response. However I hit another error *[INFO] Executing tasks [unzip] Expanding: C:\m2repo\org\apache\geronimo\assemblies\geronimo-tomcat6 -javaee5\2.1.2-SNAPSHOT\geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-bin.zip into C:\ gep_new\trunk\testsuite\launcher [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: Error while expanding C:\m2repo\org\apache\geronimo\assemblies\g eronimo-tomcat6-javaee5\2.1.2-SNAPSHOT\geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-b in.zip C:\m2repo\org\apache\geronimo\assemblies\geronimo-tomcat6-javaee5\2.1.2-SNAPSHOT \geronimo-tomcat6-javaee5-2.1.2-SNAPSHOT-bin.zip (The system cannot find the pat h specified)* As G 2.1.2 is released so snapshot may no longer be available.Attaching a patch for it. Please see if it can be applied to trunk. Thanks Ashish On Wed, Aug 6, 2008 at 10:50 PM, Joe Bohn <[EMAIL PROTECTED]> wrote: > That's the version of pluto that we have checked into out svn repo in > trunk. If you aren't planning to build trunk the easiest thing to do is to > just cd into the repository directory of server/trunk and mvn install. This > will add all of the checked in artifacts into your local m2 repo. > > Joe > > > > Ashish Jain wrote: > >> Hi, >> I am getting a missing dependency error while trying to build GEP. Any >> suggestions on getting this artifacts rather than manually downloading it my >> m2repo. >> >> [INFO] >> --- >> [ERROR] BUILD ERROR >> [INFO] >> --- >> [INFO] Failed to resolve artifact. >> >> Missing: >> -- >> 1) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file -DgroupId=org.apache.pluto >> -DartifactId=pluto-t >> lib \ >> -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file >> Alternatively, if you host your own repository you can deploy the file >> there: >>mvn deploy:deploy-file -DgroupId=org.apache.pluto >> -DartifactId=pluto-tagli >> \ >> -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ >> -Durl=[url] -DrepositoryId=[id] >> >> Path to dependency: >>1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 >>2) >> org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 >> >>3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 >>4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 >>5) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 >> >> 2) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file -DgroupId=org.apache.pluto >> -DartifactId=pluto-d >> criptor-impl \ >> -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file >> Alternatively, if you host your own repository you can deploy the file >> there: >>mvn deploy:deploy-file -DgroupId=org.apache.pluto >> -DartifactId=pluto-descr >> tor-impl \ >> -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ >> -Durl=[url] -DrepositoryId=[id] >> >> Path to dependency: >>1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 >>2) >> org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 >> >>3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 >>4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 >>5) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 >> >> 3) org.apache.tomcat:jasper:jar:6.0.16-G652117 >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file -DgroupId=org.apache.tomcat >> -DartifactId=jasper >> >> -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file >> Alternatively, if you host your own repository you can deploy the file >> there: >>mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=jasper >> \ >> -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file \ >> -Durl=[url] -Dreposit
Re: GEP Build Error for revision 683248
That's the version of pluto that we have checked into out svn repo in trunk. If you aren't planning to build trunk the easiest thing to do is to just cd into the repository directory of server/trunk and mvn install. This will add all of the checked in artifacts into your local m2 repo. Joe Ashish Jain wrote: Hi, I am getting a missing dependency error while trying to build GEP. Any suggestions on getting this artifacts rather than manually downloading it my m2repo. [INFO] --- [ERROR] BUILD ERROR [INFO] --- [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-t lib \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.pluto -DartifactId=pluto-tagli \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 5) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 2) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-d criptor-impl \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.pluto -DartifactId=pluto-descr tor-impl \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 5) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 3) org.apache.tomcat:jasper:jar:6.0.16-G652117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=jasper \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.configs:jasper:car:2.1.2 4) org.apache.tomcat:jasper:jar:6.0.16-G652117 4) org.apache.tomcat:catalina:jar:6.0.16-G652117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=catali \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=catalina \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.configs:tomcat6:car:2.1.2 4) org.apache.tomcat:catalina:jar:6.0.16-G652117 5) juddi:juddi:jar:0.9rc4 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=juddi -DartifactId=juddi \ -Dversion=0.9rc4 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=juddi -DartifactId=juddi \ -Dversion=0.9rc4 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse
GEP Build Error for revision 683248
Hi, I am getting a missing dependency error while trying to build GEP. Any suggestions on getting this artifacts rather than manually downloading it my m2repo. [INFO] --- [ERROR] BUILD ERROR [INFO] --- [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-t lib \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.pluto -DartifactId=pluto-tagli \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 5) org.apache.pluto:pluto-taglib:jar:1.1.6-G643117 2) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-d criptor-impl \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.pluto -DartifactId=pluto-descr tor-impl \ -Dversion=1.1.6-G643117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.2 4) org.apache.geronimo.plugins:pluto-support:car:2.1.2 5) org.apache.pluto:pluto-descriptor-impl:jar:1.1.6-G643117 3) org.apache.tomcat:jasper:jar:6.0.16-G652117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=jasper \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.configs:jasper:car:2.1.2 4) org.apache.tomcat:jasper:jar:6.0.16-G652117 4) org.apache.tomcat:catalina:jar:6.0.16-G652117 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=catali \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.tomcat -DartifactId=catalina \ -Dversion=6.0.16-G652117 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.configs:tomcat6:car:2.1.2 4) org.apache.tomcat:catalina:jar:6.0.16-G652117 5) juddi:juddi:jar:0.9rc4 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=juddi -DartifactId=juddi \ -Dversion=0.9rc4 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=juddi -DartifactId=juddi \ -Dversion=0.9rc4 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.1.2 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1 3) org.apache.geronimo.configs:uddi-tomcat:car:2.1.2 4) juddi:juddi:jar:0.9rc4 6) org.apache.pluto:pluto-descriptor-api:jar:1.1.6-G643117 Try downloading the file manually from the project website. Then, install it using the command: mvn
Re: DayTrader build error
Howdy,
I'm getting a somewhat similar error when building DT from trunk. Any advise?
[INFO]
[INFO] Building DayTrader :: Web Application
[INFO]task-segment: [install]
[INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.0-M1] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jsp_2.1_spec:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Wed Mar 26 09:40:35 EDT 2008
[INFO] Final Memory: 22M/508M
[INFO]
Cheers!
Hernan
seleshmaster wrote:
hello;
while trying to build DayTrader after getting the latest build, I am getting
the following error, anyone has any idea?
please help
thx
here is the error
seleshmaster-macbook:trunk seleshmaster$ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] DayTrader :: Performance Benchmark Sample
[INFO] DayTrader :: WS Application Client
[INFO] DayTrader :: EJBs
[INFO] DayTrader :: Web Application
[INFO] DayTrader :: Quote Streamer
[INFO] DayTrader :: Enterprise Application
[INFO] DayTrader :: JSON Proxy
[INFO] DayTrader :: Dojo User Interface
[INFO] DayTrader :: Dojo Interface and Proxy Ear
[INFO]
[INFO] Building DayTrader :: Performance Benchmark Sample
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/target/test-classes
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] [install:install]
[INFO] Installing /Users/seleshmaster/workspace/trunk/pom.xml to
/Users/seleshmaster/.m2/repository/org/apache/geronimo/daytrader/daytrader/2.0-SNAPSHOT/daytrader-2.0-SNAPSHOT.pom
[INFO]
[INFO] Building DayTrader :: WS Application Client
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/test-classes
[INFO]
----
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Couldn't find a version in [2.0.0] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Mar 10 22:04:36 EDT 2008
[INFO] Final Memory: 14M/26M
[INFO]
Re: DayTrader build error
Thank you guys for your help, I finally got it to work. I pretty much removed everything and re-installed everything again and that seems to fix the problem. Joe Bohn wrote: > > seleshmaster wrote: > >> 2) I put maven-ejb-plugin.jar under >> /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin >> Note: for some reason, there was no directory name "2.1", so I just >> created >> it manually and put the .jar file there too > I'm not sure why this isn't being pulled for you as part of the build > for you ... but if you must manually place the jar in your local repo > make sure that the name includes the version ... ie. > maven-ejb-plugin-2.1.jar and not just maven-ejb-plugin.jar. You would > also have to create the version directory path as you noted. > > One other thing to try before that is to rm -rf > /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin > prior attempting the build. Perhaps something has become corrupted in > the maven-ejb-plugin pom that is causing maven from not being able to > download this. > > Hope that helps, > Joe > > -- View this message in context: http://www.nabble.com/DayTrader-build-error-tp15973242s134p16020140.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: DayTrader build error
thx guys again; I removed the whole repo directory and run "mvn install" command again. This seem to fix the problem I was getting in the past but now I am getting a new type of error message but still related to maven-ejb-plugin. here is the error message. - [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-ejb-plugin:2.1:ejb': Unable to find the mojo 'org.apache.maven.plugins:maven-ejb-plugin:2.1:ejb' in the plugin 'org.apache.maven.plugins:maven-ejb-plugin' org/codehaus/plexus/archiver/jar/ManifestException [INFO] - Jason Warner wrote: > > selesh, > > You could try using maven to install the jar into the repo. This would > guarantee that the jar would be in the correct directory structure. > Instructions on what command to use and how to use it can be found here: > http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html > > Hope this helps, > > On Wed, Mar 12, 2008 at 7:31 AM, seleshmaster <[EMAIL PROTECTED]> > wrote: > >> >> >> >> Kevan Miller wrote: >> > >> > >> > On Mar 11, 2008, at 6:52 AM, seleshmaster wrote: >> > >> > >> >> thx again >> >> >> >> I dont know what I am missing but I installed the jar file under >> >> maven/lib >> >> directory where other jar file exist but I am still getting the same >> >> error. >> >> by the way, i reverted back to maven 2.0.6 >> > >> > >> > The maven-ejb-plugin needs to end up in your .m2 repository. For me, >> > it's: >> > >> > /Users/kevan/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin/ >> > 2.1/maven-ejb-plugin-2.1.jar >> > >> > --kevan >> > >> > >> > >> > >> > >> >> thx kevan; >> >> obviously I am still missing something else cause I am still getting the >> same error. >> >> here is what i did >> >> 0) I installed maven.2.0.7 >> >> Maven version: 2.0.7 >> Java version: 1.5.0_13 >> OS name: "mac os x" version: "10.5.2" arch: "i386" >> >> >> 1) I checked out the source. svn co >> 2) I put maven-ejb-plugin.jar under >> >> /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin >> Note: for some reason, there was no directory name "2.1", so I just >> created >> it manually and put the .jar file there too >> 3) and from /Users/seleshmaster/workspace/trunk directory i run "mvn >> install" >> >> 4) and I am getting this error >> >> ERROR] BUILD ERROR >> [INFO] >> >> [INFO] The plugin 'org.apache.maven.plugins:maven-ejb-plugin' does not >> exist >> or no valid version could be found >> >> >> thx for the help. >> >> -- >> View this message in context: >> http://www.nabble.com/DayTrader-build-error-tp15973242s134p16001762.html >> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com. >> >> > > > -- > ~Jason Warner > > -- View this message in context: http://www.nabble.com/DayTrader-build-error-tp15973242s134p16015060.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: DayTrader build error
seleshmaster wrote: 2) I put maven-ejb-plugin.jar under /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin Note: for some reason, there was no directory name "2.1", so I just created it manually and put the .jar file there too I'm not sure why this isn't being pulled for you as part of the build for you ... but if you must manually place the jar in your local repo make sure that the name includes the version ... ie. maven-ejb-plugin-2.1.jar and not just maven-ejb-plugin.jar. You would also have to create the version directory path as you noted. One other thing to try before that is to rm -rf /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin prior attempting the build. Perhaps something has become corrupted in the maven-ejb-plugin pom that is causing maven from not being able to download this. Hope that helps, Joe
Re: DayTrader build error
selesh, You could try using maven to install the jar into the repo. This would guarantee that the jar would be in the correct directory structure. Instructions on what command to use and how to use it can be found here: http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html Hope this helps, On Wed, Mar 12, 2008 at 7:31 AM, seleshmaster <[EMAIL PROTECTED]> wrote: > > > > Kevan Miller wrote: > > > > > > On Mar 11, 2008, at 6:52 AM, seleshmaster wrote: > > > > > >> thx again > >> > >> I dont know what I am missing but I installed the jar file under > >> maven/lib > >> directory where other jar file exist but I am still getting the same > >> error. > >> by the way, i reverted back to maven 2.0.6 > > > > > > The maven-ejb-plugin needs to end up in your .m2 repository. For me, > > it's: > > > > /Users/kevan/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin/ > > 2.1/maven-ejb-plugin-2.1.jar > > > > --kevan > > > > > > > > > > > > thx kevan; > > obviously I am still missing something else cause I am still getting the > same error. > > here is what i did > > 0) I installed maven.2.0.7 > > Maven version: 2.0.7 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" > > > 1) I checked out the source. svn co > 2) I put maven-ejb-plugin.jar under > > /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin > Note: for some reason, there was no directory name "2.1", so I just > created > it manually and put the .jar file there too > 3) and from /Users/seleshmaster/workspace/trunk directory i run "mvn > install" > > 4) and I am getting this error > > ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-ejb-plugin' does not > exist > or no valid version could be found > > > thx for the help. > > -- > View this message in context: > http://www.nabble.com/DayTrader-build-error-tp15973242s134p16001762.html > Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com. > > -- ~Jason Warner
Re: DayTrader build error
Kevan Miller wrote: > > > On Mar 11, 2008, at 6:52 AM, seleshmaster wrote: > > >> thx again >> >> I dont know what I am missing but I installed the jar file under >> maven/lib >> directory where other jar file exist but I am still getting the same >> error. >> by the way, i reverted back to maven 2.0.6 > > > The maven-ejb-plugin needs to end up in your .m2 repository. For me, > it's: > > /Users/kevan/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin/ > 2.1/maven-ejb-plugin-2.1.jar > > --kevan > > > > > thx kevan; obviously I am still missing something else cause I am still getting the same error. here is what i did 0) I installed maven.2.0.7 Maven version: 2.0.7 Java version: 1.5.0_13 OS name: "mac os x" version: "10.5.2" arch: "i386" 1) I checked out the source. svn co 2) I put maven-ejb-plugin.jar under /Users/seleshmaster/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin Note: for some reason, there was no directory name "2.1", so I just created it manually and put the .jar file there too 3) and from /Users/seleshmaster/workspace/trunk directory i run "mvn install" 4) and I am getting this error ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-ejb-plugin' does not exist or no valid version could be found thx for the help. -- View this message in context: http://www.nabble.com/DayTrader-build-error-tp15973242s134p16001762.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: DayTrader build error
On Mar 11, 2008, at 6:52 AM, seleshmaster wrote: thx again I dont know what I am missing but I installed the jar file under maven/lib directory where other jar file exist but I am still getting the same error. by the way, i reverted back to maven 2.0.6 The maven-ejb-plugin needs to end up in your .m2 repository. For me, it's: /Users/kevan/.m2/repository/org/apache/maven/plugins/maven-ejb-plugin/ 2.1/maven-ejb-plugin-2.1.jar --kevan
Re: DayTrader build error
Kevan Miller wrote: > > > On Mar 10, 2008, at 11:05 PM, seleshmaster wrote: > >> >> >> >> Kevan Miller wrote: >>> >>> >>> On Mar 10, 2008, at 10:20 PM, Jason Warner wrote: >>> >>>> Hello, >>>> >>>> This is a known bug that has been addressed in the following jira: >>>> https://issues.apache.org/jira/browse/DAYTRADER-58 >>>> There is a patch attached to the issue that can be applied and >>>> should allow you to build daytrader. >>>> >>>> Hope this helps! >>> >>> Should be fixed in svn, now. >>> >>> --kevan >>> >> >> thx guys, >> >> that part of the problem is fixed but I am still getting build >> error, here >> is what I am getting.. I am using maven 2.0.8, the README file >> states maven >> 2.0.5 or later would be fine. > > There have been some issues with 2.0.8. That readme was written prior > to the 2.0.8 release. We're all using 2.0.7. It's building fine for me > w/ 2.0.7. I get maven-ejb-plugin from: > > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ejb-plugin/2.1/maven-ejb-plugin-2.1.jar > > --kevan > thx again I dont know what I am missing but I installed the jar file under maven/lib directory where other jar file exist but I am still getting the same error. by the way, i reverted back to maven 2.0.6 -- View this message in context: http://www.nabble.com/DayTrader-build-error-tp15973242s134p15975865.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: DayTrader build error
On Mar 10, 2008, at 11:05 PM, seleshmaster wrote: Kevan Miller wrote: On Mar 10, 2008, at 10:20 PM, Jason Warner wrote: Hello, This is a known bug that has been addressed in the following jira: https://issues.apache.org/jira/browse/DAYTRADER-58 There is a patch attached to the issue that can be applied and should allow you to build daytrader. Hope this helps! Should be fixed in svn, now. --kevan thx guys, that part of the problem is fixed but I am still getting build error, here is what I am getting.. I am using maven 2.0.8, the README file states maven 2.0.5 or later would be fine. There have been some issues with 2.0.8. That readme was written prior to the 2.0.8 release. We're all using 2.0.7. It's building fine for me w/ 2.0.7. I get maven-ejb-plugin from: Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ejb-plugin/2.1/maven-ejb-plugin-2.1.jar --kevan
Re: DayTrader build error
Kevan Miller wrote: > > > On Mar 10, 2008, at 10:20 PM, Jason Warner wrote: > >> Hello, >> >> This is a known bug that has been addressed in the following jira: >> https://issues.apache.org/jira/browse/DAYTRADER-58 >> There is a patch attached to the issue that can be applied and >> should allow you to build daytrader. >> >> Hope this helps! > > Should be fixed in svn, now. > > --kevan > thx guys, that part of the problem is fixed but I am still getting build error, here is what I am getting.. I am using maven 2.0.8, the README file states maven 2.0.5 or later would be fine. INFO] -------- [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-ejb-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Mon Mar 10 23:01:12 EDT 2008 [INFO] Final Memory: 16M/29M -- View this message in context: http://www.nabble.com/DayTrader-build-error-tp15973242s134p15973752.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: DayTrader build error
On Mar 10, 2008, at 10:20 PM, Jason Warner wrote: Hello, This is a known bug that has been addressed in the following jira: https://issues.apache.org/jira/browse/DAYTRADER-58 There is a patch attached to the issue that can be applied and should allow you to build daytrader. Hope this helps! Should be fixed in svn, now. --kevan
Re: DayTrader build error
Hello,
This is a known bug that has been addressed in the following jira:
https://issues.apache.org/jira/browse/DAYTRADER-58
There is a patch attached to the issue that can be applied and should allow
you to build daytrader.
Hope this helps!
On Mon, Mar 10, 2008 at 10:14 PM, seleshmaster <[EMAIL PROTECTED]>
wrote:
>
> hello;
>
> while trying to build DayTrader after getting the latest build, I am
> getting
> the following error, anyone has any idea?
>
> please help
>
> thx
>
> here is the error
>
> seleshmaster-macbook:trunk seleshmaster$ mvn clean install
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] DayTrader :: Performance Benchmark Sample
> [INFO] DayTrader :: WS Application Client
> [INFO] DayTrader :: EJBs
> [INFO] DayTrader :: Web Application
> [INFO] DayTrader :: Quote Streamer
> [INFO] DayTrader :: Enterprise Application
> [INFO] DayTrader :: JSON Proxy
> [INFO] DayTrader :: Dojo User Interface
> [INFO] DayTrader :: Dojo Interface and Proxy Ear
> [INFO]
>
>
> [INFO] Building DayTrader :: Performance Benchmark Sample
> [INFO]task-segment: [clean, install]
> [INFO]
>
>
> [INFO] [clean:clean]
> [INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target
> [INFO] Deleting directory
> /Users/seleshmaster/workspace/trunk/target/classes
> [INFO] Deleting directory
> /Users/seleshmaster/workspace/trunk/target/test-classes
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] [tools:copy-legal-files {execution: install-legal-files}]
> [INFO] [site:attach-descriptor]
> [INFO] [tools:verify-legal-files {execution: verify-legal-files}]
> [INFO] [install:install]
> [INFO] Installing /Users/seleshmaster/workspace/trunk/pom.xml to
>
> /Users/seleshmaster/.m2/repository/org/apache/geronimo/daytrader/daytrader/2.0-SNAPSHOT/daytrader-
> 2.0-SNAPSHOT.pom
> [INFO]
>
>
> [INFO] Building DayTrader :: WS Application Client
> [INFO]task-segment: [clean, install]
> [INFO]
>
>
> [INFO] [clean:clean]
> [INFO] Deleting directory
> /Users/seleshmaster/workspace/trunk/modules/wsappclient/target
> [INFO] Deleting directory
> /Users/seleshmaster/workspace/trunk/modules/wsappclient/target/classes
> [INFO] Deleting directory
>
> /Users/seleshmaster/workspace/trunk/modules/wsappclient/target/test-classes
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
>
> Couldn't find a version in [2.0.0] to match range [1.0,2.0)
> org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> codehaus-snapshots (http://snapshots.repository.codehaus.org),
> apache-incubator (http://people.apache.org/repo/m2-incubating-repository/
> )
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Mon Mar 10 22:04:36 EDT 2008
> [INFO] Final Memory: 14M/26M
> [INFO]
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/DayTrader-build-error-tp15973242s134p15973242.html
> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
>
>
--
~Jason Warner
DayTrader build error
hello;
while trying to build DayTrader after getting the latest build, I am getting
the following error, anyone has any idea?
please help
thx
here is the error
seleshmaster-macbook:trunk seleshmaster$ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] DayTrader :: Performance Benchmark Sample
[INFO] DayTrader :: WS Application Client
[INFO] DayTrader :: EJBs
[INFO] DayTrader :: Web Application
[INFO] DayTrader :: Quote Streamer
[INFO] DayTrader :: Enterprise Application
[INFO] DayTrader :: JSON Proxy
[INFO] DayTrader :: Dojo User Interface
[INFO] DayTrader :: Dojo Interface and Proxy Ear
[INFO]
[INFO] Building DayTrader :: Performance Benchmark Sample
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/target/test-classes
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] [install:install]
[INFO] Installing /Users/seleshmaster/workspace/trunk/pom.xml to
/Users/seleshmaster/.m2/repository/org/apache/geronimo/daytrader/daytrader/2.0-SNAPSHOT/daytrader-2.0-SNAPSHOT.pom
[INFO]
[INFO] Building DayTrader :: WS Application Client
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/test-classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Couldn't find a version in [2.0.0] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Mar 10 22:04:36 EDT 2008
[INFO] Final Memory: 14M/26M
[INFO]
--
View this message in context:
http://www.nabble.com/DayTrader-build-error-tp15973242s134p15973242.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Build error on branches\2.0 building Persistence Deployer config
argh... My bad... I should have read the message more carefully :(. I thought it is failing to build the car. While building G 2.0 branch, my system crashed 3 times in a span of 2 hours and the metadata file must have got corrupted. Thanks Kevan. On Jan 23, 2008 8:02 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Jan 23, 2008, at 8:32 AM, Vamsavardhana Reddy wrote: > > > Has anyone come across this build error "Error installing artifact's > > metadata: Error installing metadata: Error updating group repository > > metadata. only whitespace content allowed before start tag and not > > \u0 (position: START_DOCUMENT seen \u0... @1:1)"? Output from build > > window given below. > > I don't recall ever seeing this. I'd cleanup your local repo -- looks > like one of the xml files has some bad characters. I'd start by > deleting the following directory: > > C:\M2REPO\org\apache\geronimo\configs\persistence-jpa10-deployer\ > > And see if that fixes your problem. > > --kevan >
Re: Build error on branches\2.0 building Persistence Deployer config
On Jan 23, 2008, at 8:32 AM, Vamsavardhana Reddy wrote: Has anyone come across this build error "Error installing artifact's metadata: Error installing metadata: Error updating group repository metadata. only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1)"? Output from build window given below. I don't recall ever seeing this. I'd cleanup your local repo -- looks like one of the xml files has some bad characters. I'd start by deleting the following directory: C:\M2REPO\org\apache\geronimo\configs\persistence-jpa10-deployer\ And see if that fixes your problem. --kevan
Build error on branches\2.0 building Persistence Deployer config
Has anyone come across this build error "Error installing artifact's
metadata: Error installing metadata: Error updating group repository
metadata. only whitespace content allowed before start tag and not \u0
(position: START_DOCUMENT seen \u0... @1:1)"? Output from build window
given below.
C:\G\server\branches\2.0\configs\persistence-jpa10-deployer>mvn -o -e
+ Error stacktraces are turned on.
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
loca
l
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
-
---
[INFO] Building Geronimo Configs :: Persistence Deployer
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:prepare-plan]
[INFO] Generated:
C:\G\server\branches\2.0\configs\persistence-jpa10-deployer\ta
rget\plan\plan.xml
log4j:WARN No appenders could be found for logger (
org.codehaus.mojo.pluginsuppo
rt.logging.Logging).
log4j:WARN Please initialize the log4j system properly.
[INFO] [car:package]
[INFO] Packaging module configuration:
C:\G\server\branches\2.0\configs\persiste
nce-jpa10-deployer\target\plan\plan.xml
[INFO] Building jar:
C:\G\server\branches\2.0\configs\persistence-jpa10-deployer
\target\persistence-jpa10-deployer-2.0.3-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in:
persistence-jpa10-deployer-2.0.3-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
C:\G\server\branches\2.0\configs\persistence-jpa10-deployer\ta
rget\persistence-jpa10-deployer-2.0.3-SNAPSHOT.car to
C:\M2REPO\org\apache\geron
imo\configs\persistence-jpa10-deployer\2.0.3-SNAPSHOT\persistence-jpa10-deployer
-2.0.3-SNAPSHOT.car
[INFO]
--------
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error installing metadata:
Error up
dating group repository metadata
only whitespace content allowed before start tag and not \u0 (position:
START_DO
CUMENT seen \u0... @1:1)
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error installing
artifac
t's metadata: Error installing metadata: Error updating group repository
metadat
a
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(Defa
ultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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.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: Error installing
arti
fact's metadata: Error installing metadata: Error updating group repository
meta
data
at org.apache.maven.plugin.install.InstallMojo.execute(
InstallMojo.java:
143)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPlugi
nManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(Defa
ultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException:
Er
ror installing artifact's metadata: Error installing metadata: Error
updating gr
oup repository metadata
at
org.apache.maven.artifact.installer.DefaultArtifactInstaller.ins
[jira] Closed: (GERONIMO-2495) Build error: server/config/j2ee-corba-* plans refer to corba-tss-config-2.0 instead of corba-tss-config-2.1
[ https://issues.apache.org/jira/browse/GERONIMO-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-2495. -- Resolution: Invalid User reports can not reproduce. > Build error: server/config/j2ee-corba-* plans refer to corba-tss-config-2.0 > instead of corba-tss-config-2.1 > --- > > Key: GERONIMO-2495 > URL: https://issues.apache.org/jira/browse/GERONIMO-2495 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.2 > Environment: windows xp >Reporter: Mark DeLaFranier >Assignee: Rick McGuire > Attachments: corba-plan-patch.txt > > > While building the latest codeline, the build failed due to bad references in > the xml namespace. The following plans: > j2ee-corba-sun/src/plan/plan.xml > j2ee-corba-yoko/src/plan/plan.xml > refer to the namespace: > http://www.openejb.org/xml/ns/corba-tss-config-2.0 > but looking at the openejb2 codeline, I only find: > http://www.openejb.org/xml/ns/corba-tss-config-2.1 > From: > openejb/openejb2/modules/openejb-builder/src/main/xsd/corba-tss-config-2.1.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-3209. Resolution: Fixed Committed revision 544893 in trunk. Removed previous updates as it seems the jspc-maven-plugin-2.0-20070603.144720-1.jar creates invalid web.xml files on Windows, but works correctly on Linux when the and fragment comments are used. Verified changes on WinXP and SLED10 by accessing the Admin Console and deploying the servlet-examples. > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501971 ] Paul McMahan commented on GERONIMO-3209: Donald, I can't recreate but it seems the plugin is behaving differently in different environments. I think your refinement should work in all environments and is safe to commit. Or attach a patch here if you prefer. > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reopened GERONIMO-3209: These changes are actually breaking my builds on WinXP w/ Sun 1.5.0_11 and Maven 2.0.6 now for the Tomcat config of geronimo-welcome app. If I remove the added attributes from jspc-maven-plugin, remove the Fragment comment from the web.xml source and use the 20070603 snapshot of jspc-maven-plugin, then it builds fine again > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-3209. -- Resolution: Fixed > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: BUILD ERROR while Building Geronimo Configs JSP Examples Jetty
Doing an "mvn clean install" on trunk solved this build problem. Thanks, Shiva On 6/5/07, Shiva Kumar H R <[EMAIL PROTECTED]> wrote: [INFO] Building Geronimo Configs :: JSP Examples Jetty [INFO]task-segment: [clean, install] ... ... [INFO] Packaging module configuration: E:\_src\ag_trunk\configs\jsp-examples-jet ty\target\plan\plan.xml [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Error parsing web.xml for . Unexpected element: XML_DOC_OR_TEXT_DECL [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing web.xml fo r . at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main (MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) ... ...
BUILD ERROR while Building Geronimo Configs JSP Examples Jetty
[INFO] Building Geronimo Configs :: JSP Examples Jetty [INFO]task-segment: [clean, install] ... ... [INFO] Packaging module configuration: E:\_src\ag_trunk\configs\jsp-examples-jet ty\target\plan\plan.xml [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error parsing web.xml for . Unexpected element: XML_DOC_OR_TEXT_DECL [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing web.xml fo r . at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) ... ...
[jira] Commented: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501360 ] Paul McMahan commented on GERONIMO-3209: not everyone is seeing this error, but I can recreate. I think that explicitly declaring the injectString for the jspc maven plugin will resolve the error > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
[ https://issues.apache.org/jira/browse/GERONIMO-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan reassigned GERONIMO-3209: -- Assignee: Paul McMahan > Build error on trunk in config/jsp-examples-jetty (parsing web.xml) > --- > > Key: GERONIMO-3209 > URL: https://issues.apache.org/jira/browse/GERONIMO-3209 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jay D. McHugh >Assignee: Paul McMahan > Fix For: 2.0-M7 > > > [WARNING] > Artifact junit:junit:jar:3.8.1:test retains local scope 'test' > overriding broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] [car:package] > [INFO] Packaging module configuration: > /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml > [INFO] > ---- > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing web.xml for . > Unexpected element: XML_DOC_OR_TEXT_DECL > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 > [INFO] Final Memory: 45M/81M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3209) Build error on trunk in config/jsp-examples-jetty (parsing web.xml)
Build error on trunk in config/jsp-examples-jetty (parsing web.xml) --- Key: GERONIMO-3209 URL: https://issues.apache.org/jira/browse/GERONIMO-3209 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Reporter: Jay D. McHugh Fix For: 2.0-M7 [WARNING] Artifact junit:junit:jar:3.8.1:test retains local scope 'test' overriding broader scope 'compile' given by a dependency. If this is not intended, modify or remove the local scope. [INFO] [car:package] [INFO] Packaging module configuration: /usr/src/geronimo/configs/jsp-examples-jetty/target/plan/plan.xml [INFO] ---- [ERROR] BUILD ERROR [INFO] [INFO] Error parsing web.xml for . Unexpected element: XML_DOC_OR_TEXT_DECL [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 41 seconds [INFO] Finished at: Mon Jun 04 15:28:42 CDT 2007 [INFO] Final Memory: 45M/81M [INFO] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error
[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-2915. - Resolution: Fixed Close the jira... was fixed quite some time ago. > Disable the call to processHTTPGetRequest to fix the build error > > > Key: GERONIMO-2915 > URL: https://issues.apache.org/jira/browse/GERONIMO-2915 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: winzp + sun 1.5 >Reporter: Lin Sun >Assignee: Lin Sun > Fix For: 2.0-M5 > > > Axis2 team commented out this processHTTPGetRequest method this AM and it > caused a build error! > The quick workaround is to disable the call. I was able to run a full build > with the workaround below and a clean Axis2 repo. > // deal with GET request > /*boolean processed = HTTPTransportUtils.processHTTPGetRequest( > msgContext, > response.getOutputStream(), > soapAction, > path, > configurationContext, > HTTPTransportReceiver.getGetRequestParameters(path));*/ > > boolean processed = false; > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error
[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reopened GERONIMO-2915: --- I think there is a bug with the jira system. I don't see an action to close this jira. trying to reopen it to see if i can close it afterwards. > Disable the call to processHTTPGetRequest to fix the build error > > > Key: GERONIMO-2915 > URL: https://issues.apache.org/jira/browse/GERONIMO-2915 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: winzp + sun 1.5 >Reporter: Lin Sun >Assignee: Lin Sun > Fix For: 2.0-M5 > > > Axis2 team commented out this processHTTPGetRequest method this AM and it > caused a build error! > The quick workaround is to disable the call. I was able to run a full build > with the workaround below and a clean Axis2 repo. > // deal with GET request > /*boolean processed = HTTPTransportUtils.processHTTPGetRequest( > msgContext, > response.getOutputStream(), > soapAction, > path, > configurationContext, > HTTPTransportReceiver.getGetRequestParameters(path));*/ > > boolean processed = false; > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error
[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reassigned GERONIMO-2915: - Assignee: Lin Sun (was: Joe Bohn) > Disable the call to processHTTPGetRequest to fix the build error > > > Key: GERONIMO-2915 > URL: https://issues.apache.org/jira/browse/GERONIMO-2915 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: winzp + sun 1.5 >Reporter: Lin Sun >Assignee: Lin Sun > Fix For: 2.0-M5 > > > Axis2 team commented out this processHTTPGetRequest method this AM and it > caused a build error! > The quick workaround is to disable the call. I was able to run a full build > with the workaround below and a clean Axis2 repo. > // deal with GET request > /*boolean processed = HTTPTransportUtils.processHTTPGetRequest( > msgContext, > response.getOutputStream(), > soapAction, > path, > configurationContext, > HTTPTransportReceiver.getGetRequestParameters(path));*/ > > boolean processed = false; > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: strange build error
SuSE 10.2 has problems with the IBM JDK. Don helped me out with a fix to glibc. You'll get a message indicating Failed to start VM. Just a heads up. On May 29, 2007, at 12:39 PM, Anita Kulshreshtha wrote: Don, I wiped out 9.2 and installed 10.2. I do not have any details other than the trace in this thread :(. Thanks Anita --- Don Hill <[EMAIL PROTECTED]> wrote: Anita, Do we have all the details for the suse 9.2 / 1.5_011 issue, I can look into this, maybe put some feelers out to some of those suse developers. Don. On 5/28/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote: --- Kevan Miller <[EMAIL PROTECTED]> wrote: On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: Kevan, Thanks for the hint. I was using jdk1.5.0_11. I have gone back to JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly like to get a better understanding of the problem. I thought that others were building successfully on _11. So, I'll assume we're ok, until someone else (or you) can document the problem... 1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 did not mix well. Do we care about 9.2? Thanks Anita --kevan __ __Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469 __ __ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/
Re: strange build error
Don, I wiped out 9.2 and installed 10.2. I do not have any details other than the trace in this thread :(. Thanks Anita --- Don Hill <[EMAIL PROTECTED]> wrote: > Anita, > > Do we have all the details for the suse 9.2 / 1.5_011 issue, I can > look into > this, maybe put some feelers out to some of those suse developers. > > Don. > > On 5/28/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote: > > > > > > --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > > > > > > > On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: > > > > > > > Kevan, > > > >Thanks for the hint. I was using jdk1.5.0_11. I have gone > back > > > to > > > > JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. > > > > > > Hmm. Well, if there's an issue with 1.5.0_11, I think we'd > certainly > > > > > > like to get a better understanding of the problem. I thought that > > > others were building successfully on _11. So, I'll assume we're > ok, > > > until someone else (or you) can document the problem... > > > >1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 > did > > not mix well. Do we care about 9.2? > > > > Thanks > > Anita > > > > > > > > --kevan > > > > > > > > > > > > > > Be > > a better Globetrotter. Get better travel answers from someone who > knows. > > Yahoo! Answers - Check it out. > > http://answers.yahoo.com/dir/?link=list&sid=396545469 > > > Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/
Re: strange build error
Anita, Do we have all the details for the suse 9.2 / 1.5_011 issue, I can look into this, maybe put some feelers out to some of those suse developers. Don. On 5/28/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote: --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: > > > Kevan, > >Thanks for the hint. I was using jdk1.5.0_11. I have gone back > to > > JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. > > Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly > > like to get a better understanding of the problem. I thought that > others were building successfully on _11. So, I'll assume we're ok, > until someone else (or you) can document the problem... 1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 did not mix well. Do we care about 9.2? Thanks Anita > > --kevan > Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469
Re: strange build error
SLES10, SLED10 and RHEL4u5 w/ Sun 1.5.0_11 are all working fine for me... -Donald Anita Kulshreshtha wrote: --- Kevan Miller <[EMAIL PROTECTED]> wrote: On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: Kevan, Thanks for the hint. I was using jdk1.5.0_11. I have gone back to JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly like to get a better understanding of the problem. I thought that others were building successfully on _11. So, I'll assume we're ok, until someone else (or you) can document the problem... 1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 did not mix well. Do we care about 9.2? Thanks Anita --kevan Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469 smime.p7s Description: S/MIME Cryptographic Signature
Re: strange build error
On May 28, 2007, at 11:06 PM, Anita Kulshreshtha wrote: --- Kevan Miller <[EMAIL PROTECTED]> wrote: On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: Kevan, Thanks for the hint. I was using jdk1.5.0_11. I have gone back to JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly like to get a better understanding of the problem. I thought that others were building successfully on _11. So, I'll assume we're ok, until someone else (or you) can document the problem... 1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 did not mix well. Do we care about 9.2? I see. I thought your combination was 10.2 and _8. I'm not going to lose any sleep over a build problem on 9.2... --kevan
Re: strange build error
--- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: > > > Kevan, > >Thanks for the hint. I was using jdk1.5.0_11. I have gone back > to > > JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. > > Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly > > like to get a better understanding of the problem. I thought that > others were building successfully on _11. So, I'll assume we're ok, > until someone else (or you) can document the problem... 1.5.0_11 and SUSE 10.2 are working fine. SUSE 9.2 and 1.5.0_11 did not mix well. Do we care about 9.2? Thanks Anita > > --kevan > Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469
Re: strange build error
On May 28, 2007, at 9:53 AM, Anita Kulshreshtha wrote: Kevan, Thanks for the hint. I was using jdk1.5.0_11. I have gone back to JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. Hmm. Well, if there's an issue with 1.5.0_11, I think we'd certainly like to get a better understanding of the problem. I thought that others were building successfully on _11. So, I'll assume we're ok, until someone else (or you) can document the problem... --kevan
Re: strange build error
Kevan, Thanks for the hint. I was using jdk1.5.0_11. I have gone back to JDK_1.5.0_8 and upgraded to SUSE 10.2. The build is happy now.. Thanks Anita --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On May 27, 2007, at 8:20 AM, Anita Kulshreshtha wrote: > > > I am seeing this error on SUSE 9.2... The build on Win XP works > fine. > > Has any one used SUSE 9.2? > > > > Thanks > > Anita > > > > --- > > T E S T S > > --- > > Running org.apache.geronimo.mavenplugins.car.PlanProcessorMojoTest > > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: > 0.521 > > sec <<< FAILURE! > > I'm not using 9.2. What level of the JDK are you running? You'll need > > to get the test output for PlanProcessorMojoTest to start > diagnosing... > > --kevan Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php
Re: strange build error
On May 27, 2007, at 8:20 AM, Anita Kulshreshtha wrote: I am seeing this error on SUSE 9.2... The build on Win XP works fine. Has any one used SUSE 9.2? Thanks Anita --- T E S T S --- Running org.apache.geronimo.mavenplugins.car.PlanProcessorMojoTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.521 sec <<< FAILURE! I'm not using 9.2. What level of the JDK are you running? You'll need to get the test output for PlanProcessorMojoTest to start diagnosing... --kevan
strange build error
I am seeing this error on SUSE 9.2... The build on Win XP works fine. Has any one used SUSE 9.2? Thanks Anita --- T E S T S --- Running org.apache.geronimo.mavenplugins.car.PlanProcessorMojoTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.521 sec <<< FAILURE! Results : Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) 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:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Sun May 27 08:16:55 PDT 2007 [INFO] Final Memory: 16M/29M [INFO] Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
Re: M5 Build Error
Much better--thanks Sachin Patel wrote: You'll need to -Dstage=bootstrap first. -sachin On Apr 26, 2007, at 1:40 PM, Tim McConnell wrote: Hi, I'm not able to build M5 using an empty M2 repo. Does anyone know where I can pickup this Plugin ?? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0-M5 -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0-M5 --Thanks, Tim McConnell
Re: M5 Build Error
You'll need to -Dstage=bootstrap first. -sachin On Apr 26, 2007, at 1:40 PM, Tim McConnell wrote: Hi, I'm not able to build M5 using an empty M2 repo. Does anyone know where I can pickup this Plugin ?? [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.plugins - DartifactId=car-maven-plugin \ -Dversion=2.0-M5 -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0-M5 -- Thanks, Tim McConnell
M5 Build Error
Hi, I'm not able to build M5 using an empty M2 repo. Does anyone know where I can pickup this Plugin ?? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.plugins -DartifactId=car-maven-plugin \ -Dversion=2.0-M5 -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.geronimo.plugins:car-maven-plugin:maven-plugin:2.0-M5 -- Thanks, Tim McConnell
Re: Seeing trunk build error after recent changes to remove backport-util-concurrent
I didn't hit this. (I refreshed my trunk at around 3pm EST). I didn't cleaned my entire .m2 repo either (just cleaned aixs2 and openejb). Lin Donald Woods wrote: Trying to build trunk Rev522511 on WinXP with a clean .m2 repo and getting the following error - [INFO] [INFO] Building Geronimo Configs :: RMI Naming [INFO]task-segment: [install] [INFO] . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] org.apache.geronimo.gbean.InvalidConfigurationException: Could not find getGBeanInfo method on org.apache.geronimo.gjndi.GlobalContextGBean edu/emory/mathcs/backport/java/util/concurrent/locks/Lock Adding backport-util-concurrent back into configs/rmi-naming/pom.xml fixes this build failure, but then the J2EE Client config fails for the same reason Is anyone else seeing this build failure??? -Donald
Re: Seeing trunk build error after recent changes to remove backport-util-concurrent
Never mind, it's working now... For some reason, it was still using the 3/23 snapshot level of XBean instead of grabbing the latest 3/24 version. -Donald Donald Woods wrote: Trying to build trunk Rev522511 on WinXP with a clean .m2 repo and getting the following error - [INFO] [INFO] Building Geronimo Configs :: RMI Naming [INFO]task-segment: [install] [INFO] . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] org.apache.geronimo.gbean.InvalidConfigurationException: Could not find getGBeanInfo method on org.apache.geronimo.gjndi.GlobalContextGBean edu/emory/mathcs/backport/java/util/concurrent/locks/Lock Adding backport-util-concurrent back into configs/rmi-naming/pom.xml fixes this build failure, but then the J2EE Client config fails for the same reason Is anyone else seeing this build failure??? -Donald smime.p7s Description: S/MIME Cryptographic Signature
Re: Seeing trunk build error after recent changes to remove backport-util-concurrent
Chances are you have an old xbean-naming 3.0-SNAPSHOT. This weekend xbean/trunk was moved to build with Java 5 and the backport jar was dropped as a dependency. I published new snaps right after the change was made. Though David Jencks did bring up a point about backport being needed on the client's config anyways if some jms muck was needed, so perhaps we need to add it back to the client car, but it shouldn't be needed for rmi-naming anymore for sure. --jason On Mar 26, 2007, at 1:12 PM, Donald Woods wrote: Trying to build trunk Rev522511 on WinXP with a clean .m2 repo and getting the following error - [INFO] [INFO] Building Geronimo Configs :: RMI Naming [INFO]task-segment: [install] [INFO] . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] org.apache.geronimo.gbean.InvalidConfigurationException: Could not find getGBeanInfo method on org.apache.geronimo.gjndi.GlobalContextGBean edu/emory/mathcs/backport/java/util/concurrent/locks/Lock Adding backport-util-concurrent back into configs/rmi-naming/ pom.xml fixes this build failure, but then the J2EE Client config fails for the same reason Is anyone else seeing this build failure??? -Donald
Seeing trunk build error after recent changes to remove backport-util-concurrent
Trying to build trunk Rev522511 on WinXP with a clean .m2 repo and getting the following error - [INFO] [INFO] Building Geronimo Configs :: RMI Naming [INFO]task-segment: [install] [INFO] . . . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] org.apache.geronimo.gbean.InvalidConfigurationException: Could not find getGBeanInfo method on org.apache.geronimo.gjndi.GlobalContextGBean edu/emory/mathcs/backport/java/util/concurrent/locks/Lock Adding backport-util-concurrent back into configs/rmi-naming/pom.xml fixes this build failure, but then the J2EE Client config fails for the same reason Is anyone else seeing this build failure??? -Donald smime.p7s Description: S/MIME Cryptographic Signature
Re: [test]-build error of webservices-testsuite
ave successfull run the other 4 module of testsuite and get the
> > report as below(skip webservices)
> >
> > Package Tests Errors FailuresSkipped Success RateTime
> > enterprise-testsuite# 39 30 0 0 23.077% 147.958
> > web-testsuite# 18 1 4 0 72.222% 126.882
> > console-testsuite# 40 0 0 0 100%275.764
> > deployment-testsuite# 7 0 0 0 100%68.137
> >
> > But unfortunately, the webservices-testsuite still failed.
> > ===
> > [INFO] [INFO] Distributing module artifact:
> >
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-client-2.0-SNAPSHOT.jar
> > with plan null
> > [WARNING] Deployer operation failed: No JAX-WS ServiceRefBuilders registered
> > [WARNING] org.apache.geronimo.common.DeploymentException: No JAX-WS
> > ServiceRefBuilders registered
> >
> > [WARNING] at
> >
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> > [WARNING] at java.lang.Thread.run(Thread.java:595)
> > [INFO] [WARNING] Ignoring failure !
> > [INFO] [INFO] [geronimo:run-client {execution: run-client}]
> > [INFO] [INFO] Geronimo Home:
> >
/home/sean/trunk/testsuite/webservices-testsuite/target/geronimo-jetty6-jee5-2.0-SNAPSHOT
> > [INFO] [INFO] Starting Geronimo client...
> > [INFO] [INFO] Redirecting output to:
> >
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/client.log
> > [INFO] [INFO]
> > [INFO] [ERROR] BUILD ERROR
> > [INFO] [INFO]
> > [INFO] [INFO] Java returned: 2
> > [INFO]
> > [INFO] [INFO]
> > [INFO] [INFO] Trace
> > [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Java
returned: 2
> > [INFO] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> > [INFO] at
> >
> > [INFO] [INFO]
--------
> > [INFO] [INFO] Total time: 27 seconds
> > [INFO] [INFO] Finished at: Fri Mar 09 14:50:36 CST 2007
> > [INFO] [INFO] Final Memory: 21M/508M
> > [INFO] [INFO]
> > [INFO]
> > [ERROR] BUILD ERROR
> > [INFO]
> > [INFO] exec returned: 1
> >
> > [INFO]
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: exec returned: 1
> > at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> >
> > ===
> > And in the log file
> > webservices-testsuite/jaxws-tests/jaxws-client/target/client.log, the
> > message is :
> > ===
> > 17:52:54,538 INFO [Log4jService]
--
> > org.apache.geronimo.kernel.config.LifecycleException: load of
> > JEE5/JAXWSClient/1.1/car failed
> > at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:274)
> > at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
> > at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
> > at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> > ===
> >
> > Is there any good solution to find out what happened? Then i can debug
> > myself, thanks.
> > --
> > Sean Qiu
> >
>
--
Sean Qiu
Re: [test]-build error of webservices-testsuite
> console-testsuite# 40 0 0 0 100%275.764
> deployment-testsuite# 7 0 0 0 100%68.137
>
> But unfortunately, the webservices-testsuite still failed.
> ===
> [INFO] [INFO] Distributing module artifact:
>
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-client-2.0-SNAPSHOT.jar
> with plan null
> [WARNING] Deployer operation failed: No JAX-WS ServiceRefBuilders registered
> [WARNING] org.apache.geronimo.common.DeploymentException: No JAX-WS
> ServiceRefBuilders registered
>
> [WARNING] at
>
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> [WARNING] at java.lang.Thread.run(Thread.java:595)
> [INFO] [WARNING] Ignoring failure !
> [INFO] [INFO] [geronimo:run-client {execution: run-client}]
> [INFO] [INFO] Geronimo Home:
>
/home/sean/trunk/testsuite/webservices-testsuite/target/geronimo-jetty6-jee5-2.0-SNAPSHOT
> [INFO] [INFO] Starting Geronimo client...
> [INFO] [INFO] Redirecting output to:
>
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/client.log
> [INFO] [INFO]
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> [INFO] [INFO] Java returned: 2
> [INFO]
> [INFO] [INFO]
> [INFO] [INFO] Trace
> [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Java returned:
2
> [INFO] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> [INFO] at
>
> [INFO] [INFO]
> [INFO] [INFO] Total time: 27 seconds
> [INFO] [INFO] Finished at: Fri Mar 09 14:50:36 CST 2007
> [INFO] [INFO] Final Memory: 21M/508M
> [INFO] [INFO]
> [INFO]
> [ERROR] BUILD ERROR
> [INFO]
> [INFO] exec returned: 1
>
> [INFO]
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: exec returned: 1
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>
> ===
> And in the log file
> webservices-testsuite/jaxws-tests/jaxws-client/target/client.log, the
> message is :
> ===
> 17:52:54,538 INFO [Log4jService]
--
> org.apache.geronimo.kernel.config.LifecycleException: load of
> JEE5/JAXWSClient/1.1/car failed
> at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:274)
> at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
> at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
> at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> ===
>
> Is there any good solution to find out what happened? Then i can debug
> myself, thanks.
> --
> Sean Qiu
>
--
Sean Qiu
Re: [test]-build error of webservices-testsuite
Hi there, is this CXF or Axis2? Thanks, Lin
Sean Qiu wrote:
Os: Redhat
Revision: 516311
After successfully build the geronimo, i want to run the testsuite of it.
I have successfull run the other 4 module of testsuite and get the
report as below(skip webservices)
PackageTestsErrors FailuresSkippedSuccess RateTime
enterprise-testsuite#39300023.077%147.958
web-testsuite#1814072.222%126.882
console-testsuite#40000100%275.764
deployment-testsuite#7000100%68.137
But unfortunately, the webservices-testsuite still failed.
===
[INFO] [INFO] Distributing module artifact:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-client-2.0-SNAPSHOT.jar
with plan null
[WARNING] Deployer operation failed: No JAX-WS ServiceRefBuilders
registered
[WARNING] org.apache.geronimo.common.DeploymentException: No JAX-WS
ServiceRefBuilders registered
[WARNING] at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[WARNING] at java.lang.Thread.run(Thread.java:595)
[INFO] [WARNING] Ignoring failure !
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/sean/trunk/testsuite/webservices-testsuite/target/geronimo-jetty6-jee5-2.0-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] Redirecting output to:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/client.log
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Java returned: 2
[INFO]
[INFO] [INFO]
[INFO] [INFO] Trace
[INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Java
returned: 2
[INFO] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
[INFO] at
[INFO] [INFO]
[INFO] [INFO] Total time: 27 seconds
[INFO] [INFO] Finished at: Fri Mar 09 14:50:36 CST 2007
[INFO] [INFO] Final Memory: 21M/508M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] exec returned: 1
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: exec returned: 1
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
===
And in the log file
webservices-testsuite/jaxws-tests/jaxws-client/target/client.log, the
message is :
===
17:52:54,538 INFO [Log4jService]
--
org.apache.geronimo.kernel.config.LifecycleException: load of
JEE5/JAXWSClient/1.1/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:274)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
===
Is there any good solution to find out what happened? Then i can debug
myself, thanks.
Re: [test]-build error of webservices-testsuite
Sean,
Check the *.txt files in the target/surefire-reports directory for a
more detailed error report and fuller stack trace.
I'm wondering if there is more to your LifecycleException than just
load failed. Is there a root cause which says, "Config already exists
exception" ?
Cheers
Prasad
On 3/9/07, Sean Qiu <[EMAIL PROTECTED]> wrote:
Os: Redhat
Revision: 516311
After successfully build the geronimo, i want to run the testsuite of it.
I have successfull run the other 4 module of testsuite and get the
report as below(skip webservices)
Package Tests Errors FailuresSkipped Success RateTime
enterprise-testsuite# 39 30 0 0 23.077% 147.958
web-testsuite# 18 1 4 0 72.222% 126.882
console-testsuite# 40 0 0 0 100%275.764
deployment-testsuite# 7 0 0 0 100%68.137
But unfortunately, the webservices-testsuite still failed.
===
[INFO] [INFO] Distributing module artifact:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-client-2.0-SNAPSHOT.jar
with plan null
[WARNING] Deployer operation failed: No JAX-WS ServiceRefBuilders registered
[WARNING] org.apache.geronimo.common.DeploymentException: No JAX-WS
ServiceRefBuilders registered
[WARNING] at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[WARNING] at java.lang.Thread.run(Thread.java:595)
[INFO] [WARNING] Ignoring failure !
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/sean/trunk/testsuite/webservices-testsuite/target/geronimo-jetty6-jee5-2.0-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] Redirecting output to:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/client.log
[INFO] [INFO]
----
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Java returned: 2
[INFO]
[INFO] [INFO]
[INFO] [INFO] Trace
[INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Java returned: 2
[INFO] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
[INFO] at
[INFO] [INFO]
[INFO] [INFO] Total time: 27 seconds
[INFO] [INFO] Finished at: Fri Mar 09 14:50:36 CST 2007
[INFO] [INFO] Final Memory: 21M/508M
[INFO] [INFO]
[INFO] ----
[ERROR] BUILD ERROR
[INFO]
[INFO] exec returned: 1
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: exec returned: 1
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
===
And in the log file
webservices-testsuite/jaxws-tests/jaxws-client/target/client.log, the
message is :
===
17:52:54,538 INFO [Log4jService] --
org.apache.geronimo.kernel.config.LifecycleException: load of
JEE5/JAXWSClient/1.1/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:274)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
===
Is there any good solution to find out what happened? Then i can debug
myself, thanks.
--
Sean Qiu
[test]-build error of webservices-testsuite
Os: Redhat
Revision: 516311
After successfully build the geronimo, i want to run the testsuite of it.
I have successfull run the other 4 module of testsuite and get the
report as below(skip webservices)
Package Tests Errors FailuresSkipped Success RateTime
enterprise-testsuite# 39 30 0 0 23.077% 147.958
web-testsuite# 18 1 4 0 72.222% 126.882
console-testsuite# 40 0 0 0 100%275.764
deployment-testsuite# 7 0 0 0 100%68.137
But unfortunately, the webservices-testsuite still failed.
===
[INFO] [INFO] Distributing module artifact:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-client-2.0-SNAPSHOT.jar
with plan null
[WARNING] Deployer operation failed: No JAX-WS ServiceRefBuilders registered
[WARNING] org.apache.geronimo.common.DeploymentException: No JAX-WS
ServiceRefBuilders registered
[WARNING] at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[WARNING] at java.lang.Thread.run(Thread.java:595)
[INFO] [WARNING] Ignoring failure !
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/sean/trunk/testsuite/webservices-testsuite/target/geronimo-jetty6-jee5-2.0-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] Redirecting output to:
/home/sean/trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/target/client.log
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Java returned: 2
[INFO]
[INFO] [INFO]
[INFO] [INFO] Trace
[INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Java returned: 2
[INFO] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
[INFO] at
[INFO] [INFO]
[INFO] [INFO] Total time: 27 seconds
[INFO] [INFO] Finished at: Fri Mar 09 14:50:36 CST 2007
[INFO] [INFO] Final Memory: 21M/508M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] exec returned: 1
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: exec returned: 1
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
===
And in the log file
webservices-testsuite/jaxws-tests/jaxws-client/target/client.log, the
message is :
===
17:52:54,538 INFO [Log4jService] --
org.apache.geronimo.kernel.config.LifecycleException: load of
JEE5/JAXWSClient/1.1/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:274)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:253)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
===
Is there any good solution to find out what happened? Then i can debug
myself, thanks.
--
Sean Qiu
