June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13938) Add support for reddeer server requirements to integration-tests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13938?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-13938: ------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > Add support for reddeer server requirements to integration-tests > ----------------------------------------------------------------- > > Key: JBIDE-13938 > URL: https://issues.jboss.org/browse/JBIDE-13938 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: QA > Affects Versions: 4.1.0.Alpha1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.1.0.CR1 > > > * new annotations for test classes will be introduced > * server will be defined in reddeer requirement xml > * server adapter will be configured according to the xml configuration -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14761) Forge Wizards: NPE when project name is empty

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14761?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-14761. ------------------------------- Resolution: Done > Forge Wizards: NPE when project name is empty > --------------------------------------------- > > Key: JBIDE-14761 > URL: https://issues.jboss.org/browse/JBIDE-14761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.0.Beta2 > > > It would be very nice to have a check for empty text field in new project wizard. > {code} > java.lang.NullPointerException > at java.io.File.<init>(File.java:291) > at org.jboss.tools.forge.importer.ProjectImporter.createMavenProjectInfo(ProjectImporter.java:50) > at org.jboss.tools.forge.importer.ProjectImporter.getProjectToImport(ProjectImporter.java:63) > at org.jboss.tools.forge.importer.ProjectImporter.access$0(ProjectImporter.java:61) > at org.jboss.tools.forge.importer.ProjectImporter$1.runInWorkspace(ProjectImporter.java:34) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13914) Have a test run that runs test plugins for each component in a fully installed JBT

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13914?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13914. ------------------------------------ Resolution: Duplicate Issue > Have a test run that runs test plugins for each component in a fully installed JBT > ---------------------------------------------------------------------------------- > > Key: JBIDE-13914 > URL: https://issues.jboss.org/browse/JBIDE-13914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Affects Versions: 4.1.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > You said you had a way to run tests against existing install. > Thus lets get this rolling by having a way to run a components test plugins and its included Test classes in a fully loaded JBoss Tools installation. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14840) LiveReload proxy should forward request to server host, not proxy host

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14840: ------------------------------------- Summary: LiveReload proxy should forward request to server host, not proxy host Key: JBIDE-14840 URL: https://issues.jboss.org/browse/JBIDE-14840 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.1.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.0.Beta2 This should allow for remote connections via the LiveReload proxy to a JBoss AS (for exemple) running on the same host, even if the AS only accepts requests from 127.0.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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13869: ---------------------------------------- [~maxandersen]: The difficulty in that task is not to run the test. Eclipse already provides what's necessary to run tests automatically, and we do publish the tests on an update-site for "external" installation and execution. The difficulty is more to find a simple way to define the target platform. I don't think we can/want to use directly a target definition. What I can propose you for good efficiency/low price is the following: A CI job that takes the latest build of JBDS, install tests in it, and run some of the tests on demand (that would be a job parameter). WDYT? > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.0.2.Final, 4.1.0.Beta2 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13948) Error when fixing location of fileset

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13948?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13948: -------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > Error when fixing location of fileset > ------------------------------------- > > Key: JBIDE-13948 > URL: https://issues.jboss.org/browse/JBIDE-13948 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha2 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.CR1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13661: ------------------------------------- Jaroslav: I've tried many times on clean workspaces with no project archives view open, and am unable to replicate it. I'm going to push this for cr1, but, if I can't replicate it, we may need to set up some screen-sharing or screencasting. > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Beta2 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13661: -------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.CR1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14026) new web projects always use web.xml from EE7 causing failure to deploy

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14026?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14026. --------------------------------- Resolution: Done Upstream indicates this has been solved in RC3, as have other similar code-path issues. > new web projects always use web.xml from EE7 causing failure to deploy > ---------------------------------------------------------------------- > > Key: JBIDE-14026 > URL: https://issues.jboss.org/browse/JBIDE-14026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.1.0.Alpha2 > Environment: JBDS 7.0.0.Alpha2 B135 > EAP 5.1.2 / 5.2.0 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.0.Beta2 > > > When I try to deploy a simple dynamic web project to EAP 5.1.2 I get this: > {code} > 14:43:28,703 INFO [TomcatDeployment] undeploy, ctxPath=/dynproj > 14:43:28,771 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2-noauth/jboss-as/server/default/deploy/dynproj.war/ state=PreParse mode=Manual requiredState=Parse > org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2-noauth/jboss-as/server/default/deploy/dynproj.war/ > at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) > at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:680) > Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) > at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) > at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) > at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) > ... 28 more > Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. > at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) > at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) > ... 37 more > 14:43:28,772 WARN [HDScanner] Failed to process changes > org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): > *** DEPLOYMENTS IN ERROR: Name -> Error > vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2-noauth/jboss-as/server/default/deploy/dynproj.war/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2-noauth/jboss-as/server/default/deploy/dynproj.war/ > DEPLOYMENTS IN ERROR: > Deployment "vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2-noauth/jboss-as/server/default/deploy/dynproj.war/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. > at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008) > at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954) > at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870) > at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:680) > {code} > https://bugs.eclipse.org/bugs/show_bug.cgi?id=405873 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-94) Creating BPMN2 process throws NPE

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-94?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-94: --------------------------------- Hey Bob - Assigning to you first to look at the NullPointerException. --paull > Creating BPMN2 process throws NPE > --------------------------------- > > Key: JBTIS-94 > URL: https://issues.jboss.org/browse/JBTIS-94 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPMN2 > Affects Versions: 4.0.1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Blocker > Attachments: bpmnBug.png, command_line.log, ide.log > > > Creating BPMN2 process throws NullPointerException, see the attachments. -- 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, 10 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 June 2013