April 2013 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13265) Install dialog warning should be properly wrapped

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13265?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-13265: ------------------------------------ Verified in JBDS 7.0.0.Alpha2c. > Install dialog warning should be properly wrapped > ------------------------------------------------- > > Key: JBIDE-13265 > URL: https://issues.jboss.org/browse/JBIDE-13265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final > Reporter: Denis Golovin > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > Attachments: screenshot-20121206144846.png, WarningDialog.png, WarningDialog1.png > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14293) JBoss Central should be available under Window>Show View

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14293?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-14293. ------------------------------ > JBoss Central should be available under Window>Show View > -------------------------------------------------------- > > Key: JBIDE-14293 > URL: https://issues.jboss.org/browse/JBIDE-14293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Fix For: 4.1.0.Alpha2 > > > Click Window>Show View> Other. JBoss Central should be listed here under JBoss Tools along with all of the other views. > I realise you can also show JBoss Central by clicking the icon in the toolbar. But if someone chooses to customize the toolbar and remove the icon then they have no way of showing JBoss Central. -- 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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBDS-2469) Cannot install all extras from central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2469?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-2469. ---------------------------- I could successfully install all extras from central in JBDS 7.0.0.Alpha2c. Closing. > Cannot install all extras from central > -------------------------------------- > > Key: JBDS-2469 > URL: https://issues.jboss.org/browse/JBDS-2469 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > Attachments: central-install.png, central-install2.png > > > devstudio-directory.xml is: > <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> > <entry url="plugins/com.jboss.jbds.central.discovery_7.0.0.Alpha1-v20130211-0546-B6.jar" permitCategories="true"/> > </directory> > I selected all components in the list and could not complete the install. Please see screenshots. -- 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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14285) JBoss Central New and Noteworthy for 4.1.0.Alpha2

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14285?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-14285. ------------------------------ Looks good. Closing. > JBoss Central New and Noteworthy for 4.1.0.Alpha2 > ------------------------------------------------- > > Key: JBIDE-14285 > URL: https://issues.jboss.org/browse/JBIDE-14285 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.2 in JBoss Central 7

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-2395. ---------------------------- SpringIDE 3.2 can be installed into JBDS without errors. Closing. > Investigate use of SpringIDE 3.2 in JBoss Central 7 > --------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.0.0.Alpha2 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ - 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ - 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2013