May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2458) JBDS uninstaller doesn't actually remove JBDS

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2458?page=com.atlassian.jira.plugin.... ] Vlado Pakan closed JBDS-2458. ----------------------------- Verified with JBDS 7.0.0.Beta1-v20130529-0631-B257. > JBDS uninstaller doesn't actually remove JBDS > --------------------------------------------- > > Key: JBDS-2458 > URL: https://issues.jboss.org/browse/JBDS-2458 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, Upstream > Affects Versions: 6.0.0.GA > Environment: Fedora 17 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.0.0.Beta1 > > > The uninstaller has two options: > 1. force deletion of installation folder (select check box) > 2 don't force the deletion of the installation folder (don't select check box) > I would expect option 1 to delete the whole installation folder including any files I might have added in there. It does. :) > I would expect option 2 to delete anything to do with JBDS but leave the folder and any files I have created in it. It doesn't. It leaves a studio folder full of JBDS files and a shortcut by which I can still launch what appears to be a working JBDS. As a user I would assume that the uninstaller would remove JBDS at the very least and I shouldn't still be able to launch it. :( -- 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-14694) Cheatsheet is not opened when importing project as existing one

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14694: --------------------------------------- The issue has been caused by https://github.com/jbosstools/jbosstools-central/pull/112 The PR supposes Eclipse always notifies resource change listeners with one notification which isn't correct. When importing an existing project, Eclipse works as follows: - creates a project (adds the .project file) and notifies resource change listeners In that moment, createdProject[0] = true, but a cheatsheet isn't added and shown - adds other project's resources and notifies resource change listeners A cheatcheet is added, but createdProject[0] = false so the cheatsheet isn't shown again. I think there is no way to distinguish how a resource (cheatsheet) is added to a project because we can't suppose that Eclipse will notify an event for all changes. What we can do is the following: - keep https://github.com/jbosstools/jbosstools-central/pull/112 In this case, a cheatsheet will be opened when importing a maven project, but won't be opened in some other cases what depends on how Eclipse notifies resource changes listeners. In the case of the change of the importing maven project procedure, it could happen that a cheatsheet isn't opened even if a maven project is imported. When adding a cheatsheet to an existing project, it won't be opened. The PR fixes this case correctly. - remove https://github.com/jbosstools/jbosstools-central/pull/112 A cheatsheet will be opened no matter how it has been added to the workspace: importing a project, opening a project, adding the cheatcheet to an existing project ... When closing/opening a project, a cheatsheet will be opened with and without this PR. > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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-14694) Cheatsheet is not opened when importing project as existing one

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14694?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14694: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > Cheatsheet is not opened when importing project as existing one > --------------------------------------------------------------- > > Key: JBIDE-14694 > URL: https://issues.jboss.org/browse/JBIDE-14694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > Attachments: jboss-as-kitchensink.zip > > > When I try to import project via Existing projects into workspace no cheatsheet is opened. -- 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-14638) Freezing Behavior in ECFTransport locks Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14638?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14638. ------------------------------- Verified with JBDS 7.0.0.Beta1-v20130529-0631-B257. > Freezing Behavior in ECFTransport locks Central > ----------------------------------------------- > > Key: JBIDE-14638 > URL: https://issues.jboss.org/browse/JBIDE-14638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > > Regression in behavior causes lockup of eclipse and inability to shut down. -- 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-14695) no version set for org.codehaus.mojo:exec-maven-plugin in parent pom on line 733

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14695?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14695. ------------------------------ Fix Version/s: 4.1.0.Beta2 Resolution: Done Fixed, d'oh. > no version set for org.codehaus.mojo:exec-maven-plugin in parent pom on line 733 > -------------------------------------------------------------------------------- > > Key: JBIDE-14695 > URL: https://issues.jboss.org/browse/JBIDE-14695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > {code} > [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ org.jboss.tools:parent:4.1.0.Beta2-SNAPSHOT, /mnt/hudson_workspace/workspace/devstudio.signed.product_trunk/.repository/org/jboss/tools/parent/4.1.0.Beta2-SNAPSHOT/parent-4.1.0.Beta2-SNAPSHOT.pom, line 733, column 19{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-14555) Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14555?page=com.atlassian.jira.plugi... ] Juergen Zimmermann commented on JBIDE-14555: -------------------------------------------- 1) I'm getting errors like these: !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.817 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.833 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.864 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.880 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.895 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.911 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder !ENTRY org.jboss.tools.arquillian.core 4 0 2013-05-30 17:33:09.942 !MESSAGE Could not initialize class de.shop.util.ArchiveBuilder 2) It's hard to reproduce now because I'm also getting with the latest release (not related to this issue, but afterwards the workspace is broken and not usable anymore): !ENTRY org.eclipse.core.jobs 4 2 2013-05-30 17:33:24.997 !MESSAGE An internal error occurred during: "Updating Maven Project". !STACK 0 javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found > Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian > ------------------------------------------------------------------------------ > > Key: JBIDE-14555 > URL: https://issues.jboss.org/browse/JBIDE-14555 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.0.Beta1 > Reporter: Juergen Zimmermann > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.0.Beta1, 4.1.0.Beta2 > > > I'm using JBoss Tools 41-Update-2013-05-19_01-13-51-B207 having the new Arquillian component. > I'm getting a warning "Could not initialize class my.pkg.ArchiveBuilder" in all Arquillian-based test classes. > In fact my ArchiveBuilder isn't a regular class, but it's an enum: > public enum ArchiveBuilder { > INSTANCE; > private final WebArchive archive = ShrinkWrap.create(WebArchive.class, "shop.war"); > private ArchiveBuilder() {...} > public static ArchiveBuilder getInstance() { return INSTANCE; } > public Archive<? extends Archive<?>> getArchive() { return archive; } -- 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-14419) use Beta1 parent pom

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14419?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-14419. ------------------------------- > use Beta1 parent pom > --------------------- > > Key: JBIDE-14419 > URL: https://issues.jboss.org/browse/JBIDE-14419 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > -- 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-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-13349. ------------------------------- > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Fix For: 4.1.0.Beta1 > > Attachments: Screenshot-2.png > > > See attached screenshot -- 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-14457) add new stacks features (and test features) to JBT (and JBDS?) aggregate sites

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14457?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-14457. -------------------------------- In JBDS 7.0.beta1b: org.jboss.tools.stacks.core.feature_1.0.0.Beta1-v20130525-0108-B68 > add new stacks features (and test features) to JBT (and JBDS?) aggregate sites > ------------------------------------------------------------------------------ > > Key: JBIDE-14457 > URL: https://issues.jboss.org/browse/JBIDE-14457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.1.0.Beta1 > > > When installing "Abridged JBoss Tools" from nightly core trunk site [1], I get this: > {code} > !MESSAGE Missing requirement: org.jboss.tools.as.runtimes.integration 2.4.100.Alpha2-v20130514-1022-B278 requires > 'bundle org.jboss.tools.stacks.core 1.0.0' but it could not be found > {code} > [1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ > [~rob.stryker] The solution here is to add your new stacks features to > * https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... and > * https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Send me a PR and I'll apply it. Thanks! -- 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] (JBDS-2646) Cannot deploy created Seam2.2 project to EAP 5.2

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2646?page=com.atlassian.jira.plugin.... ] Vlado Pakan closed JBDS-2646. ----------------------------- > Cannot deploy created Seam2.2 project to EAP 5.2 > ------------------------------------------------ > > Key: JBDS-2646 > URL: https://issues.jboss.org/browse/JBDS-2646 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: seam > Affects Versions: 7.0.0.Beta1 > Reporter: Tomas Remes > Fix For: 7.0.0.Beta1 > > > Cannot deploy created Seam2.2 project to EAP 5.2, because of following exception, which is caused by wrong web.xml webapps tag values: > {noformat} > org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tremes/EAP/ER6/jboss-eap-5.2/jboss-as/server/default/deploy/testproject.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:471) > at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > 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) > ... 27 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) > ... 36 more > {noformat} -- 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 May 2013