January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13355: ------------------------------------------- Xavier, I finally had a chance to run this locally on the master branch in github. And the test failures I'm seeing are in the JAXRS Core tests... Tests in error: shouldDoNothingWhenPackageInfoAdded(org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilderTestCase): Problems encountered while deleting resources. shouldDoNothingWhenPackageInfoChanged(org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuilderTestCase): Resource '/org.jboss.tools.ws.jaxrs.tests.sampleproject/src/main/java/org/jboss/tools/ws/jaxrs/sample/services/package-info.java' already exists. This is different than the erros that Jaroslav and Nick were seeing last week, but I am executing on Windows, not Linux, so I'm not sure what the diffs are. I'm sure I'm on the master branch and have all the latest bells and whistled. And I'm running maven as follows: mvn clean verify -Punified.target -Djbosstools.test.jre.5=c:/jdk5/jre -Djbosstools.test.jre.6=c:/jdk6/jre Long story short, locally it's getting through the parts it's failing on during the build on jenkins, but failing later on. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: launch a server.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: New Server Workflow.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: New Server Workflow.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Anonymous updated JBIDE-13263: ------------------------------ Attachment: runtime workflow.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png, runtime workflow.gliffy, runtime workflow.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13401) Cannot binary deploy to EWS OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13401?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13401: ------------------------------------------ apparently working around this is possible by either settings the deployments folder in the server adapter editor or in the settings file: {quote} (01:11:21 PM) sbunciak: i changed the deployments dir in server adapter and it works (01:11:51 PM) sbunciak: will try to change the settings file (it was not changed by overriding settings in server adapter) (01:13:01 PM) sbunciak: works also {quote} > Cannot binary deploy to EWS OpenShift application > ------------------------------------------------- > > Key: JBIDE-13401 > URL: https://issues.jboss.org/browse/JBIDE-13401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, openshift > Affects Versions: 3.3.2 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.x > > > EWS application type uses for deployments folder 'webapps' instead of 'deployments' as JBoss AS7/EAP6. The Server Adapter sets directory for deployments to <app>/deployments but in this case it is <app>/webapps. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13211) Update JBoss Central tests to work with JBDS 6.0.0

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13211?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-13211: ------------------------------- Summary: Update JBoss Central tests to work with JBDS 6.0.0 (was: Update JBoss Central tests to work with latest JBDS) > Update JBoss Central tests to work with JBDS 6.0.0 > -------------------------------------------------- > > Key: JBIDE-13211 > URL: https://issues.jboss.org/browse/JBIDE-13211 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Affects Versions: 4.0.0.CR1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: LATER > > > Change JBoss Central tests to reflect cahnges in JBoss Central component. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13332) Update list of quickstarts to be consistent with current goals

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13332?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13332. ------------------------------ Verified in JBT 4.0.0.Final > Update list of quickstarts to be consistent with current goals > -------------------------------------------------------------- > > Key: JBIDE-13332 > URL: https://issues.jboss.org/browse/JBIDE-13332 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0 > Reporter: Pete Muir > Assignee: Snjezana Peco > Fix For: 4.0.0.Final > > > We should update the list of quickstarts to be consistent with the things we want to promote right now. > Here is the current list, in this order: > * kitchensink-html5-mobile > * kitchensink > * greeter > * helloworld > * kitchensink-rf > * jax-rs-client -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13331) Names of quickstarts are wrong

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13331?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13331. ------------------------------ Verified in JBT 4.0.0.Final > Names of quickstarts are wrong > ------------------------------ > > Key: JBIDE-13331 > URL: https://issues.jboss.org/browse/JBIDE-13331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0 > Reporter: Pete Muir > Assignee: Snjezana Peco > Fix For: 4.0.0.Final > > > We should use consistent names for quickstarts in all locations, which are governed by the quickstarts themselves: > * Hello World -> helloworld > * Hello World JMS -> helloworld-jms > * Hello World Errai -> helloworld-errai > * Hello World OSGi -> *remove it entirely* > * Kitchensink -> kitchensink > * Number Guess -> numberguess > * Aerogear HTML5/Mobile -> kitchensink-html5-mobile > * Greeter -> greeter -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13263: -------------------------------- Attachment: astools api.png > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > Attachments: astools api.gliffy, astools api.png > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- 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, 3 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 January 2013