[JBoss JIRA] (JBIDE-13656) New project dialog from central does not reflect runtimes defined in stacks.yaml
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13656?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-13656.
------------------------------
EAP 6.1 is now accepted as valid server for archetypes.
Closing this issue, even though it's hardcoded in XMLs.
Followup: [JBIDE-13686]
> New project dialog from central does not reflect runtimes defined in stacks.yaml
> --------------------------------------------------------------------------------
>
> Key: JBIDE-13656
> URL: https://issues.jboss.org/browse/JBIDE-13656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Environment: JBDS 7.0.0.Alpha1b
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.0.0.Final, 4.1.0.Alpha2
>
>
> This is a follow-up of JDF-216.
> They created a new branch of jdf-stacks to test EAP 6.1. But even if I used that branch using
> -Dorg.jboss.examples.stacks.url=https://raw.github.com/jboss-jdf/jdf-stack/eap6.1/stacks.yaml
> I am still told that the required runtime is not defined and that I need to have EAP 6 or AS 7.
> The dialog should take advantage of the information provided by stacks.yaml and notice that the correct server is defined.
> See JDF-216 for more details.
--
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, 11 months
[JBoss JIRA] (JBIDE-14329) ESB Bot tests should fail if there are no examples
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14329?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-14329:
--------------------------------------
Description:
ESB Bot tests should fail if there are no examples. Now, the tests pass even if the examples are unavailable.
Edit: this was already done but comitted in master branch instead of jbosstools-4.0.x
was:ESB Bot tests should fail if there are no examples. Now, the tests pass even if the examples are unavailable.
> ESB Bot tests should fail if there are no examples
> --------------------------------------------------
>
> Key: JBIDE-14329
> URL: https://issues.jboss.org/browse/JBIDE-14329
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: QA
> Affects Versions: 4.0.0.Alpha1-SOA
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0.Alpha1-SOA
>
>
> ESB Bot tests should fail if there are no examples. Now, the tests pass even if the examples are unavailable.
> Edit: this was already done but comitted in master branch instead of jbosstools-4.0.x
--
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, 11 months
[JBoss JIRA] (JBIDE-14329) ESB Bot tests should fail if there are no examples
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-14329:
-----------------------------------------
Summary: ESB Bot tests should fail if there are no examples
Key: JBIDE-14329
URL: https://issues.jboss.org/browse/JBIDE-14329
Project: Tools (JBoss Tools)
Issue Type: Task
Components: QA
Affects Versions: 4.0.0.Alpha1-SOA
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.0.0.Alpha1-SOA
ESB Bot tests should fail if there are no examples. Now, the tests pass even if the examples are unavailable.
--
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, 11 months
[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13159:
---------------------------------------
This is still an issue in JBDS 7.0.0.Alpha2 - when I use just mvn package and then deploy, I get the ClassNotFound error. If I use mvn clean package, the deployment works.
> gwt-kitchensink fails to deploy - class not found
> -------------------------------------------------
>
> Key: JBIDE-13159
> URL: https://issues.jboss.org/browse/JBIDE-13159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: GWT, maven
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 6.0.0.CR1a B133
> JBT 4.0.0.CR1a B97
> OS X 10.8.2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta1
>
>
> When you try to deploy the gwt project from Central, it fails to deploy with the following error:
> {code}
> 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy
> 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war"
> 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
> 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war
> 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war
> 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary'
> 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
> 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
> 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
> 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}
> 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms
> 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}}
> {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, 11 months
[JBoss JIRA] (JBIDE-13868) Project Archives incorrectly loading saved .packages
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič closed JBIDE-13868.
-------------------------------------
Verified with JBDS 7.0.0 Alpha2c
> Project Archives incorrectly loading saved .packages
> ----------------------------------------------------
>
> Key: JBIDE-13868
> URL: https://issues.jboss.org/browse/JBIDE-13868
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives
> Affects Versions: 4.0.0.Final
> Environment: Eclipse juno 32 bit
> Reporter: Rafael Sisto
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
> Attachments: .packages, loaded packages.png
>
>
> After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully.
> After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset.
> Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars.
--
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, 11 months