[jira] [Assigned] (GERONIMO-5886) Exceptions after creating a new db in db manager portlet
[ https://issues.apache.org/jira/browse/GERONIMO-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang reassigned GERONIMO-5886: --- Assignee: Shenghao Fang > Exceptions after creating a new db in db manager portlet > > > Key: GERONIMO-5886 > URL: https://issues.apache.org/jira/browse/GERONIMO-5886 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Reporter: Rex Wang >Assignee: Shenghao Fang > > 1. go to DB manager portlet > 2. input a new db name and click create > 3. the db can be created successfully but when you click "Application" in > "view tables", exception occured: > javax.portlet.PortletException: javax.servlet.jsp.JspTagException: Error > getting connection: "java.sql.SQLException: No suitable driver found for > jdbc:derby:Vacation;create=true" > at > org.apache.pluto.container.impl.PortletRequestDispatcherImpl.doDispatch(PortletRequestDispatcherImpl.java:185) > at > org.apache.pluto.container.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:227) > at > org.apache.geronimo.console.internaldb.DBViewerPortlet.doView(DBViewerPortlet.java:144) > at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) > at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) > at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) > at > org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) > at > org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91) > at > org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105) > at > org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340) > at > org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) > at > org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) > at > org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117) > at > org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157) > at > org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165) > at > jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:927) > at > jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspx_meth_c_005fforEach_005f0(portlets_002donly_jsp.java:135) > at > jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspService(portlets_002donly_jsp.java:69) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDis -- This message is automatically generated by JIRA. For more information on JIRA, see: http://ww
[jira] [Created] (GERONIMO-5886) Exceptions after creating a new db in db manager portlet
Exceptions after creating a new db in db manager portlet Key: GERONIMO-5886 URL: https://issues.apache.org/jira/browse/GERONIMO-5886 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Reporter: Rex Wang 1. go to DB manager portlet 2. input a new db name and click create 3. the db can be created successfully but when you click "Application" in "view tables", exception occured: javax.portlet.PortletException: javax.servlet.jsp.JspTagException: Error getting connection: "java.sql.SQLException: No suitable driver found for jdbc:derby:Vacation;create=true" at org.apache.pluto.container.impl.PortletRequestDispatcherImpl.doDispatch(PortletRequestDispatcherImpl.java:185) at org.apache.pluto.container.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:227) at org.apache.geronimo.console.internaldb.DBViewerPortlet.doView(DBViewerPortlet.java:144) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340) at org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117) at org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:927) at jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspx_meth_c_005fforEach_005f0(portlets_002donly_jsp.java:135) at jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspService(portlets_002donly_jsp.java:69) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDis -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-5884) Support wsdl-file override for web service client
[ https://issues.apache.org/jira/browse/GERONIMO-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reopened GERONIMO-5884: Might need to consider more about geronimo-naming.xsd file > Support wsdl-file override for web service client > - > > Key: GERONIMO-5884 > URL: https://issues.apache.org/jira/browse/GERONIMO-5884 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > Currently, in Geronimo's specific deployment plan, we could define port info, > service completion info in the service-ref element. I am thinking to add a > new sub element named wsdl-file, which is used to override the configurations > from service interface and service-ref entry in the spec deployment > descriptor. Thus, we might get more flexibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1087504
Geronimo Revision: 1087504 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110401/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110401/unit-test-reports [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@6b746b74 Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-cdc/1.0-alpha-13/plexus-cdc-1.0-alpha-13.pom 2K downloaded (plexus-cdc-1.0-alpha-13.pom) [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@74b874b8 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@6b746b74 Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-tools/1.0.10/plexus-tools-1.0.10.pom 1K downloaded (plexus-tools-1.0.10.pom) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-container-default/1.0-alpha-43/plexus-container-default-1.0-alpha-43.pom 3K downloaded (plexus-container-default-1.0-alpha-43.pom) [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.AlwaysOnProfileActivator@74b874b8 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@6b746b74 Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-containers/1.0-alpha-43/plexus-containers-1.0-alpha-43.pom 1K downloaded (plexus-containers-1.0-alpha-43.pom) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/slf4j/slf4j-api/1.4.3/slf4j-api-1.4.3.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//ant/ant/1.5.1/ant-1.5.1.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//doxia/doxia-core/1.0-alpha-4/doxia-core-1.0-alpha-4.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//junit/junit/3.8.1/junit-3.8.1.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//jdom/jdom/1.0/jdom-1.0.jar 14K downloaded (slf4j-api-1.4.3.jar) 700K downloaded (ant-1.5.1.jar) 149K downloaded (jdom-1.0.jar) 254K downloaded (doxia-core-1.0-alpha-4.jar) 118K downloaded (junit-3.8.1.jar) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//com/thoughtworks/qdox/qdox/1.6.3/qdox-1.6.3.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//oro/oro/2.0.7/oro-2.0.7.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//jmock/jmock/1.0.0/jmock-1.0.0.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-cdc-anno/1.0-alpha-1/plexus-cdc-anno-1.0-alpha-1.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//commons-validator/commons-validator/1.1.4/commons-validator-1.1.4.jar 101K downloaded (qdox-1.6.3.jar) 63K downloaded (oro-2.0.7.jar) 67K downloaded (jmock-1.0.0.jar) 5K downloaded (plexus-cdc-anno-1.0-alpha-1.jar) 82K downloaded (commons-validator-1.1.4.jar) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/reporting/maven-reporting-impl/2.0/maven-reporting-impl-2.0.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/slf4j/slf4j-simple/1.4.3/slf4j-simple-1.4.3.jar Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-component-annotations/1.0-alpha-9/plexus-component-annotations-1.0-alpha-9.jar 15K downloaded (maven-reporting-impl-2.0.jar) 7K downloaded (slf4j-simple-1.4.3.jar) 4K downloaded (plexus-component-annotations-1.0-alpha-9.jar) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-cdc/1.0-alpha-13/plexus-cdc-1.0-alpha-13.jar 60K downloaded (plexus-cdc-1.0-alpha-13.jar) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar 164K downloaded (plexus-utils-1.1.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.plexus:plexus-maven-plugin:1.3.8:descriptor': Error adding plugin dependency 'org.codehaus.plexus:plexus-cdc-anno:jar' into plugin manager: Cannot add jar resource: /home/geronimo/.m2/repository/org/codehaus/plexus/plexus-cdc-anno/1.0-alpha-1/plexus-cdc-anno-1.0-alpha-1.jar (error discovering new components) No such file or directory /home/geronimo/.m2/repository/org/codehaus/plexus/plexus-maven-plugin/1.3.8/plexus-maven-plugin-1.3.8.jar [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionExceptio
[BUILD] trunk: Failed for Revision: 1087291
Geronimo Revision: 1087291 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110331/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110331/unit-test-reports Path to dependency: 1) org.apache.geronimo.modules:geronimo-j2ee:bundle:3.0-SNAPSHOT 2) org.apache.openwebbeans:openwebbeans-spi:jar:1.1.0 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-j2ee:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/groups/jetty-with-staging), openqa-releases (http://nexus.openqa.org/content/repositories/releases), java.net2 (http://download.java.net/maven/2/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openwebbeans:openwebbeans-impl:jar:1.1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openwebbeans -DartifactId=openwebbeans-impl -Dversion=1.1.0 -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.openwebbeans -DartifactId=openwebbeans-impl -Dversion=1.1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-j2ee:bundle:3.0-SNAPSHOT 2) org.apache.openwebbeans:openwebbeans-impl:jar:1.1.0 2) org.apache.openwebbeans:openwebbeans-spi:jar:1.1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openwebbeans -DartifactId=openwebbeans-spi -Dversion=1.1.0 -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.openwebbeans -DartifactId=openwebbeans-spi -Dversion=1.1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-j2ee:bundle:3.0-SNAPSHOT 2) org.apache.openwebbeans:openwebbeans-spi:jar:1.1.0 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-j2ee:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/groups/jetty-with-staging), openqa-releases
Re: svn commit: r1087186 - in /geronimo/server/trunk: ./ plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/
On Mar 31, 2011, at 1:25 AM, xuhaih...@apache.org wrote: > Author: xuhaihong > Date: Thu Mar 31 05:25:11 2011 > New Revision: 1087186 > > URL: http://svn.apache.org/viewvc?rev=1087186&view=rev > Log: > Use OWB 1.1.0 and update integration codes Yay. Clean build... ;-) Thanks for making the updates! --kevan
Re: Apache Tuscany Logo in Geronimo Wiki
On Mar 31, 2011, at 4:52 AM, chi runhua wrote: > The problem comes again on 3.0 doc website. Ivan helped export the space > manually and the Tuscany logo is still there. So I reasied INFRA-3555 and > hopefully someone from infra. team could help take a look. > > And I am out of options now. Any other suggestions? I noticed that the other day. No suggestions from me. Would be great to get this fixed... Thanks for looking into it. --kevan
[BUILD] trunk: Failed for Revision: 1087202
Geronimo Revision: 1087202 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110331/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110331/unit-test-reports 3) org.apache.maven.doxia:doxia-module-xhtml:jar:1.0-alpha-10 -- 2 required artifacts are missing. for artifact: org.apache.maven.plugins:maven-plugin-plugin:maven-plugin:2.5 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/groups/jetty-with-staging), openqa-releases (http://nexus.openqa.org/content/repositories/releases), java.net2 (http://download.java.net/maven/2/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.maven.doxia:doxia-module-xdoc:jar:1.0-alpha-10 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.doxia -DartifactId=doxia-module-xdoc -Dversion=1.0-alpha-10 -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.maven.doxia -DartifactId=doxia-module-xdoc -Dversion=1.0-alpha-10 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.maven.plugins:maven-plugin-plugin:maven-plugin:2.5 2) org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-10 3) org.apache.maven.doxia:doxia-module-xdoc:jar:1.0-alpha-10 2) org.apache.maven.doxia:doxia-module-xhtml:jar:1.0-alpha-10 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.doxia -DartifactId=doxia-module-xhtml -Dversion=1.0-alpha-10 -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.maven.doxia -DartifactId=doxia-module-xhtml -Dversion=1.0-alpha-10 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.maven.plugins:maven-plugin-plugin:maven-plugin:2.5 2) org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-10 3) org.apache.maven.doxia:doxia-module-xhtml:jar:1.0-alpha-10 -- 2 required artifacts are missing. for artifact: org.apache.maven.plugins:maven-plugin-plugin:maven-plugin:2.5 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus
[BUILD] branches/2.2: Failed for Revision: 1087254
Geronimo Revision: 1087254 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110331/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110331/unit-test-reports Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) org.apache.maven.shared:maven-filtering:jar:1.0-beta-2 24) org.codehaus.plexus:plexus-interpolation:jar:1.6 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-interpolation -Dversion=1.6 -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.codehaus.plexus -DartifactId=plexus-interpolation -Dversion=1.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) org.apache.maven.shared:maven-filtering:jar:1.0-beta-2 3) org.codehaus.plexus:plexus-interpolation:jar:1.6 25) org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-stax-api_1.0_spec -Dversion=1.0.1 -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.geronimo.specs -DartifactId=geronimo-stax-api_1.0_spec -Dversion=1.0.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 26) org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-activation_1.1_spec -Dversion=1.0.2 -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.geronimo.specs -DartifactId=geronimo-activation_1.1_spec -Dversion=1.0.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.2 27) org.apache.geronimo.specs:geronimo-javaee-deployment_1.1MR3_spec:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-javaee-deployment_1.1MR3_spec -Dversion=1.0 -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.geronimo.specs -DartifactId=geronimo-javaee-deployment_1.1MR3_spec -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) org.apache.geronimo.framework:geronimo-service-builder:jar:2.2.2-SNAPSHOT 3) org.apache.geronimo.specs:geronimo-javaee-deployment_1.1MR3_spec:jar:1.0 28) com.envoisolutions.sxc:sxc-runtime:jar:0.7.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.envoisolutions.sxc -DartifactId=sxc-runtime -Dversion=0.7.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.envoisolutions.sxc -DartifactId=sxc-runtime -Dversion=0.7.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-SNAPSHOT 2) com.envoisolutions.sxc:sxc-jaxb:jar:0.7.2 3) com.envoisolutions.sxc:sxc-runtime:jar:0.7.2 -- 28 required artifacts are missing. for artifact: org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2.2-20101219.134627-5 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) at
[BUILD] branches/2.1: Failed for Revision: 1087186
Geronimo Revision: 1087186 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20110331/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20110331/unit-test-reports org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.2 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.BuildFailureException: A required plugin was not found: 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.maven.plugins -DartifactId=maven-war-plugin -Dversion=2.0.2 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-war-plugin -Dversion=2.0.2 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.2 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.2 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:544) 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:592) 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.PluginNotFoundException: 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.maven.plugins -DartifactId=maven-war-plugin -Dversion=2.0.2 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-war-plugin -Dversion=2.0.2 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.2 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.2 from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:253) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184) at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642
[jira] [Commented] (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013903#comment-13013903 ] Tina Li commented on GERONIMODEVTOOLS-670: -- when create a runtime, choose gep 2.2 and use application server which build version is 2010.12.03-17:56:38.228+0800 > Geronimo deployment plan doesn't be created when creating projects using the > Geronimo 2.2 as the target runtime > --- > > Key: GERONIMODEVTOOLS-670 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS: Windows XP SP3 > JDK: IBM JDK 6 > Eclipse: 3.6 >Reporter: Wang Guang Zhe >Assignee: Delos Dai > Fix For: 3.0 > > > I created an web, an ejb and an ear projects using the Geronimo 2.2 as the > target runtime, the geronimo deployment plans which should be in these > projects don't exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li reopened GERONIMODEVTOOLS-670: -- The same problem also exists. > Geronimo deployment plan doesn't be created when creating projects using the > Geronimo 2.2 as the target runtime > --- > > Key: GERONIMODEVTOOLS-670 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS: Windows XP SP3 > JDK: IBM JDK 6 > Eclipse: 3.6 >Reporter: Wang Guang Zhe >Assignee: Delos Dai > Fix For: 3.0 > > > I created an web, an ejb and an ear projects using the Geronimo 2.2 as the > target runtime, the geronimo deployment plans which should be in these > projects don't exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013902#comment-13013902 ] Tina Li commented on GERONIMODEVTOOLS-670: -- 1.windows 7,eclipse helios sr1,ibm jdk6 IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr8ifx-20100609_59383 (JIT enabled, AOT enabled) 2.Install GEP 3.0-SNAPSHOT 3.created an web, an ejb and an ear projects using the Geronimo 2.2.1 which build version is 2010.12.03-17:56:38.228+0800 as the target runtime 4.Found the same problem, the geronimo deployment plans which should be in these projects don't exist either. > Geronimo deployment plan doesn't be created when creating projects using the > Geronimo 2.2 as the target runtime > --- > > Key: GERONIMODEVTOOLS-670 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS: Windows XP SP3 > JDK: IBM JDK 6 > Eclipse: 3.6 >Reporter: Wang Guang Zhe >Assignee: Delos Dai > Fix For: 3.0 > > > I created an web, an ejb and an ear projects using the Geronimo 2.2 as the > target runtime, the geronimo deployment plans which should be in these > projects don't exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Apache Tuscany Logo in Geronimo Wiki
The problem comes again on 3.0 doc website. Ivan helped export the space manually and the Tuscany logo is still there. So I reasied INFRA-3555 and hopefully someone from infra. team could help take a look. And I am out of options now. Any other suggestions? Jeff C On Sat, Aug 7, 2010 at 2:55 AM, Donald Woods wrote: > Just noticed the following autoexport logging when trying to run an > autoexport of the OpenJPA space - > > [Fri Aug 06 14:51:10 EDT 2010] Exporting: - null > [key=OPENEJBGMOxSITEOPENEJBx30=GMOxDEV] > > where when exporting a single space you would expect to see - > > [Fri Aug 06 14:51:54 EDT 2010] Exporting: - OpenJPA [key=openjpa] > > Wonder if that explains some of our earlier problems, where there are > multiple auto exports trying to run simultaneously due to space updates > > > -Donald > > > On 7/7/10 3:08 PM, Joe Bohn wrote: > > OK, it looks like doing a manual export fixed all of the links again for > > now. > > > > But since we still don't really understand what is causing this or how > > to fix it (as I mentioned earlier manual export didn't fix it a few > > weeks ago) ... then I don't know when it will happen again or for > > certain how we can resolve it. > > > > This is just strange. > > > > Joe > > > > > > On 7/7/10 2:54 PM, Joe Bohn wrote: > >> > >> > >> Actually, I think all of the GMOxDOC30 and GMOxDOC21 doc has/had the > >> Tuscany logo (not just the clustering page). It seems that most of the > >> GMOxDOC22 doc is clean with the exception of the clustering-and-farming > >> link that you mention and perhaps some others (I didn't look at all the > >> pages ;-) ). > >> > >> I did spend some time looking into this a few weeks back for 3.0 but > >> didn't find a cause or solution at the time. Here's what I tried: > >> - Validating the the export template for the space hadn't been > >> corrupted. It looked OK to me and matched what we have in svn. > >> - Forced an update of the template with what we saved in svn (even > >> though they looked the same) - didn't help. > >> - Forced a minor change to the template in confluence - also didn't > help. > >> - Moved the license header below the macros - Donald mentioned that this > >> may have fixed it when he looked into it earlier - but it didn't fix > >> anything when I tried it. > >> - I also posted a question on infra@ about it but didn't get any > >> responses. > >> > >> I ran out of ideas and gave up. > >> > >> However, after seeing this I thought I'd try to force an export again > >> and see if anything changed. I tried it for 3.0 and to my surprise it > >> seems to have fixed that one. I'll try on the others as well. > >> > >> This leads me to think that it is somehow timing related based upon > >> Tuscany exports ... but I really don't have a clue. Does anybody else > >> have any ideas? > >> > >> Joe > >> > >> On 7/7/10 12:59 PM, Kevan Miller wrote: > >>> > >>> On Jun 2, 2010, at 5:44 AM, chi runhua wrote: > >>> > G2.2 don't have the problem and I think we could just apply the > changes we made to G2.2 for G2.1 doc space . > >>> > >>> There are still parts of our Wiki documentation that still have the > >>> Tuscany logo. See: > >>> > >>> https://cwiki.apache.org/GMOxDOC30/clustering-and-farming.html > >>> https://cwiki.apache.org/GMOxDOC22/clustering-and-farming.html > >>> https://cwiki.apache.org/GMOxDOC21/clustering.html > >>> > >>> If somebody can help get these cleaned up, that would be great. > >>> > >>> --kevan > >>> > >>> > >> > >> > > > > >
