[JBoss JIRA] (JBIDE-13865) Class ProgressPart disposes system cursors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13865?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13865:
------------------------------------
Assuming that since Max +1'd this DURING the 4.0.1.CR1a respin cycle, it's for respin-b, targeting 4.0.1.Final, not 4.0.2.Final.
> Class ProgressPart disposes system cursors
> ------------------------------------------
>
> Key: JBIDE-13865
> URL: https://issues.jboss.org/browse/JBIDE-13865
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: respin-b
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> This causes https://issues.jboss.org/browse/JBDS-2503
> Only Add Custom Capabilities wizard creates progress monitor based on this class, so that the issue can be reproduced only by adding custom capabilities as described in JBDS-2503.
> After wizard completes, it is impossible to work in Eclipse, because system wait cursor is disposed, and almost all jobs in Eclipse invoke that cursor.
--
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
13 years
[JBoss JIRA] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2504:
-------------------------------------
OK, fair enough. But users running on SR2 will probably not be able to install it, since they will already have that fix, right?
> JBDS 6.0.1 central software updates contain Juno SR1 fix
> --------------------------------------------------------
>
> Key: JBDS-2504
> URL: https://issues.jboss.org/browse/JBDS-2504
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, central
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA
>
>
> Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix.
> Since JBDS 6.0.1 is based on SR2, this has nothing to do there.
> Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that.
> Anyway, it should be removed from central for 6.0.1.
--
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
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2505:
----------------------------------
Once downloaded/installed you can diff the target platform's plugin contents w/ the install folder's plugin contents.
Of course one quick check that verifies that 4.22.2 was used is this:
{code:title=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable_branch.updatesite/all/ (build #360)}
org.eclipse.m2e.feature 1.3.1.20130219-1424
org.eclipse.m2e.wtp.feature 0.17.0.20130212-1819{code}
And this:
{code:title=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable_branch.updatesite/all/plugins/ (build #360)}
org.eclipse.platform_4.2.2.v201302041200.jar{code}
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
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
13 years
[JBoss JIRA] (JBIDE-13601) Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13601?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-13601:
-------------------------------------
Assignee: Nick Boldt (was: Denis Golovin)
Nick, can you check why the Central update site doesn't contain the updated version of the maven gwt feature?
The PR seems to have been applied a while back https://github.com/jbosstools/jbosstools-central/pull/61/files
> 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: Nick Boldt
> 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
13 years
[JBoss JIRA] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2504.
----------------------------
Resolution: Won't Fix
In JBIDE-13335 it was decided that since this doesn't hurt anything and since we may have users installing JBDS onto Juno R or SR1, we should leave this in so that they can benefit.
> JBDS 6.0.1 central software updates contain Juno SR1 fix
> --------------------------------------------------------
>
> Key: JBDS-2504
> URL: https://issues.jboss.org/browse/JBDS-2504
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build, central
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA
>
>
> Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix.
> Since JBDS 6.0.1 is based on SR2, this has nothing to do there.
> Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that.
> Anyway, it should be removed from central for 6.0.1.
--
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
13 years
[JBoss JIRA] (JBIDE-5333) Renaming opened jBPM process definition does not work
by Dominik Pospisil (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5333?page=com.atlassian.jira.plugin... ]
Dominik Pospisil closed JBIDE-5333.
-----------------------------------
Resolution: Out of Date
> Renaming opened jBPM process definition does not work
> -----------------------------------------------------
>
> Key: JBIDE-5333
> URL: https://issues.jboss.org/browse/JBIDE-5333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jbpm
> Affects Versions: 3.1.0.M4
> Reporter: Dominik Pospisil
> Assignee: Koen Aers
> Priority: Minor
> Fix For: LATER
>
>
> 1. Open jPMB process definition
> 2. On jBPM process definition package choose Refactor -> Rename
> 3. Choose another name
> 4. Confirm saving changes
> 5. Modify definiton in opened editor
> 6. Try to save file
> Two problems:
> 1) During refactoring, file is not saved no matter what users choose in refactoring dialog. Unsaved changes are lost.
> 2) After refactoring saving the file is no longer possible - fails with No such file exception.
--
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
13 years
[JBoss JIRA] (JBIDE-8289) Generated Seam portled does not work on EPP 4.3
by Dominik Pospisil (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8289?page=com.atlassian.jira.plugin... ]
Dominik Pospisil closed JBIDE-8289.
-----------------------------------
Resolution: Out of Date
> Generated Seam portled does not work on EPP 4.3
> -----------------------------------------------
>
> Key: JBIDE-8289
> URL: https://issues.jboss.org/browse/JBIDE-8289
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Portal/GateIn, UpStream
> Affects Versions: 3.2.0.CR1
> Reporter: Dominik Pospisil
> Assignee: Snjezana Peco
> Fix For: 3.3.x
>
> Attachments: eppcp06deployseamportlet.log
>
>
> Generated Seam portled does not work on EPP 4.3. This is due to incompatibility of Potletbridge 2.0.Final and Seam 2.0.2.FP in EPP 4.3. See PBR-186.
> Steps to reproduce:
> 1) Create Seam Project on EPP 4.3 with included Seam 2.0 and Seam portlet facet
> 2) Add Seam portlet to the project
> 3) Deploy on EPP 4.3
> Snjezana, where are portledbridge libraries generated by the wizard comming from?
--
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
13 years