[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13602:
----------------------------------
Release Notes Docs Status: Not Required
> Backport to 4.0.x - Null Java EE Web Project Archetype
> ------------------------------------------------------
>
> Key: JBIDE-13602
> URL: https://issues.jboss.org/browse/JBIDE-13602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Priority: Minor
> Labels: maven
> Fix For: 4.0.1.Final
>
>
> When trying to create a new Java EE Web Project, the following description is presented:
> {quote}
> This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1.
> This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.
> Project based on the *null:null:null* Maven archetype
> {quote}
> If I go forward with the creation of the project, I get the following error message:
> {quote}
> Failed to create project.
> Root cause: For artifact null:null:null:pom : The group id cannot be empty.
> {quote}
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13601) Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13601?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13601:
----------------------------------
Release Notes Docs Status: Not Yet Documented
Affects: Release Notes
> Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13601
> URL: https://issues.jboss.org/browse/JBIDE-13601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7, Google Plugin for Eclipse 2.5.2, JBoss Tools 3.3.0.Beta1, m2e 1.0.100, m2e-wtp 0.15.2
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: 0001-JBIDE-13487-fix-errai-deployment-issues.patch
>
>
> We're trying to achieve the following workflow for the user inside Eclipse/ GPE / JBoss Tools:
> * create project
> * execute Google > GWT Compile
> * Run As > Run On Server
> * browse the application
> When a gwt maven project is detected, GPE sets the GWT compilation output directory to target/<artifactId>-<version>/. So ultimately we could automatically mark that folder as deployable for WTP and pretty much achieve that ideal workflow.
> Until this is done automatically, we can do it manually. Here's a slightly more complex workflow :
> * Create a new GWT Project from JBoss Central
> * Right-click on project > Google > GWT compile
> * Add the Kitchensink module
> * Click on Compile. Upon completion, a target/<artifactId>-<version> folder is created
> * Right-click on project > Properties > Deployment Assembly
> * Click Add > folder > select target/<artifactId>-<version> click ok to complete
> * Right-click on project > Run As > Run on server
> * select JBoss AS7 / EAP, OK
> * Project deploys without errors
> * KitchenSink.html is displayed in browser, with the full form.
> Problem is, when the page is displayed, the following exceptions appear in the AS console :
> {noformat}
> 23:24:33,487 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment jesuisoula.war
> 23:24:33,784 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) configuring Errai CDI
> 23:24:33,789 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Created Errai-CDI context: cbc75356-e760-43e2-9faf-e32025719b58
> 23:24:33,964 INFO [ErraiJNDI] (MSC service thread 1-2) searching to see if ErraiService is already bound...
> 23:24:34,167 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,168 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,169 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,170 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,172 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,206 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,368 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,389 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,692 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,783 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,821 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,833 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,898 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 690 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:34,899 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:35,332 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:35,344 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:35,505 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:35,597 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:35,627 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:35,637 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:35,703 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 804 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:35,815 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Bootstrap Errai
> 23:24:35,816 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Working directory: D:\Dev\servers\jboss-eap-6.0-ER3\bin
> 23:24:35,818 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher
> 23:24:35,825 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider
> 23:24:35,837 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) searching for Errai extensions ...
> 23:24:35,847 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) found extension org.jboss.errai.tools.monitoring.MonitorExtension
> 23:24:35,899 INFO [org.jboss.errai.bus.server.service.bootstrap.DiscoverServices] (MSC service thread 1-2) auto-discovery of services disabled.
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.BootstrapContext] (MSC service thread 1-2) Running deferred bootstrap tasks ...
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Initialization complete
> 23:24:35,930 INFO [ErraiJNDI] (MSC service thread 1-2) found ErraiService bound at: java:global/ErraiService
> 23:24:35,947 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Register RPC Endpoint: public@ApplicationScoped @Service class org.jboss.tools.gwt.kitchensink.controller.MemberServiceImpl(interface org.jboss.tools.gwt.kitchensink.client.shared.MemberService)
> 23:24:36,328 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /jesuisoula
> 23:24:36,335 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 20026ms - Started 195 of 268 services (72 services are passive or on-demand)
> 23:24:36,398 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jesuisoula.war"
> 23:24:40,547 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) searching for marshaller class: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl
> 23:24:40,548 WARN [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) could not locate marshaller class. will attempt dynamic generation.
> 23:24:40,562 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generating marshalling class...
> 23:24:40,622 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) Checking ErraiApp.properties for configured types ...
> 23:24:40,662 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) comprehended 59 classes
> 23:24:41,049 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generated marshalling class in 486ms.
> 23:24:42,057 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** FAILED TO COMPILE MARSHALLER CLASS ***
> 23:24:42,058 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** Classpath Used: D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-bus-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-cdi-client-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-ioc-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-marshalling-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-tools-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-weld-integration-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\com\sun\jsf-impl\main\jsf-impl-2.1.5-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\org\jboss\as\weld\main\jboss-as-weld-7.1.0.Final-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar
> 23:24:42,066 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'uniqueConstraints()' in type 'javax.persistence.Table': class file for javax.persistence.Table not found
> 23:24:42,071 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'columnNames()' in type 'javax.persistence.UniqueConstraint': class file for javax.persistence.UniqueConstraint not found
> 23:24:42,076 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size': class file for javax.validation.constraints.Size not found
> 23:24:42,081 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,086 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'regexp()' in type 'javax.validation.constraints.Pattern': class file for javax.validation.constraints.Pattern not found
> 23:24:42,092 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'message()' in type 'javax.validation.constraints.Pattern'
> 23:24:42,097 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size'
> 23:24:42,103 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,110 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'fraction()' in type 'javax.validation.constraints.Digits': class file for javax.validation.constraints.Digits not found
> 23:24:42,117 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'integer()' in type 'javax.validation.constraints.Digits'
> 23:24:42,124 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'name()' in type 'javax.persistence.Column': class file for javax.persistence.Column not found
> 23:24:42,128 INFO [stdout] (http-localhost-127.0.0.1-8080-1) error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider org.jboss.errai.common.rebind.ModuleAnnotationProcessor not found
> 23:24:42,129 ERROR [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failed to load static marshallers: java.lang.NullPointerException
> at org.jboss.errai.marshalling.server.MappingContextSingleton.loadPrecompiledMarshallers(MappingContextSingleton.java:98) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.marshalling.server.MappingContextSingleton.<clinit>(MappingContextSingleton.java:78) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.getParts(MessageFactory.java:109) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.createCommandMessage(MessageFactory.java:93) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:117) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final-redhat-1.jar:2012-02-22 16:46]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
> 23:24:42,147 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failing over to dynamic marshallers ... performance may be affected.
> {noformat}
> It turns out some files are missing from the deployment folder :
> * WEB-INF/classes/classlist.mf
> * WEB-INF/classes/org/jboss/errai/**
> These files should be created under the project /target/classes folder in the first place, during GWT Compile, as would mvn package do.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13642) link to target platform used when building from build description field in Jenkins jobs
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13642?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13642:
----------------------------------
Release Notes Docs Status: Not Required
> link to target platform used when building from build description field in Jenkins jobs
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13642
> URL: https://issues.jboss.org/browse/JBIDE-13642
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> Using this, we can link to Nexus & easily see which TP version was used:
> {code}
> regex: (http.+/org/jboss/tools/targetplatforms/jbosstools-unified/(.+))/maven-metadata.xml
> desc: <li><a href="\1">TP</a> <a href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/\2">Site</a> (\2) <li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">Coverage report</a> & <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> (EclEmma)</li>
> {code}
> or...
> {code}
> <hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
> - <regexp/>
> + <regexp>(http.+/org/jboss/tools/targetplatforms/jbosstools-unified/(.+))/maven-metadata.xml</regexp>
> <regexpForFailed/>
> - <description><li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">coverage report</a>. Load <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> into EclEmma</li></description>
> + <description><li><a href="\1">TP</a> <a href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/\2&... (\2) <li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">Coverage report</a> &amp; <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> (EclEmma)</li></description>
> <setForMatrix>false</setForMatrix>
> </hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
> {code}
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13642) link to target platform used when building from build description field in Jenkins jobs
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13642?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-13642.
---------------------------------
Resolution: Done
> link to target platform used when building from build description field in Jenkins jobs
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13642
> URL: https://issues.jboss.org/browse/JBIDE-13642
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> Using this, we can link to Nexus & easily see which TP version was used:
> {code}
> regex: (http.+/org/jboss/tools/targetplatforms/jbosstools-unified/(.+))/maven-metadata.xml
> desc: <li><a href="\1">TP</a> <a href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/\2">Site</a> (\2) <li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">Coverage report</a> & <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> (EclEmma)</li>
> {code}
> or...
> {code}
> <hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
> - <regexp/>
> + <regexp>(http.+/org/jboss/tools/targetplatforms/jbosstools-unified/(.+))/maven-metadata.xml</regexp>
> <regexpForFailed/>
> - <description><li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">coverage report</a>. Load <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> into EclEmma</li></description>
> + <description><li><a href="\1">TP</a> <a href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/\2&... (\2) <li><a href="http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/">Update Site</a> <li><a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/target/coverage-report/html/JBoss_Tools_Chunk/index.html">Coverage report</a> &amp; <a href="/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/artifact/sources/*/target/jacoco.exec" style="color: purple; font-weight:bold">jacoco.exec</a> (EclEmma)</li></description>
> <setForMatrix>false</setForMatrix>
> </hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
> {code}
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13671 at 3/1/13 12:55 PM:
-------------------------------------------------------------
A related change I did recently (in master branch only so far) is this: JBIDE-13672
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/\{jobname\}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
was (Author: nickboldt):
A related change I did recently (in master branch only so far) is this: JBIDE-13672
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/{jobname}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13672 at 3/1/13 12:55 PM:
-------------------------------------------------------------
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/\{jobname\}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
was (Author: nickboldt):
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/{jobname}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
> could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13672
> URL: https://issues.jboss.org/browse/JBIDE-13672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published.
> May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate).
> Sample files to check:
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo...
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13672:
------------------------------------
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/{jobname}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
> could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13672
> URL: https://issues.jboss.org/browse/JBIDE-13672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published.
> May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate).
> Sample files to check:
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo...
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13671:
------------------------------------
A related change I did recently (in master branch only so far) is this: JBIDE-13672
Now, if the previous build's git revision (SHA) is the same as the current one, it won't bother to push the new bits to the staging/{jobname}/all/repo site, which means the composite site will not change, and therefore the downstream aggregation will not happen. This minimizes builds for the sake of building, but still allows us to rebuild/retest as a result of upstream changes (like a new target platform or a possible API change).
So, should Base change, you can manually kick off Server to ensure everything still builds. But if the CODE in Server is unchanged, Server will not be *published*, only built & tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with 'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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
12 years, 8 months