July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3959) DevSuite Uninstaller for Windows

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3959?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3959: ----------------------------- > DevSuite Uninstaller for Windows > -------------------------------- > > Key: JBDS-3959 > URL: https://issues.jboss.org/browse/JBDS-3959 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.1.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > > DevSuite should provide uninstaller that would remove what was installed by installer and skip what was detected during installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3959) DevSuite Uninstaller for Windows

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3959: ----------------------------------- Summary: DevSuite Uninstaller for Windows Key: JBDS-3959 URL: https://issues.jboss.org/browse/JBDS-3959 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Affects Versions: 10.0.1.AM3 Reporter: Denis Golovin Assignee: Denis Golovin DevSuite should provide uninstaller that would remove what was installed by installer and skip what was detected during installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-671) Teiid smoke tests are failing on fenix

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-671?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-671: ----------------------------------------- is there any pull request? > Teiid smoke tests are failing on fenix > -------------------------------------- > > Key: JBTIS-671 > URL: https://issues.jboss.org/browse/JBTIS-671 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Matus Makovy > > Stacktrace > {code} > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.teiid.ui.bot.test.ModelWizardTest.xsdDatatypeModel(ModelWizardTest.java:99) > {code} > and > Error Message > The following shells remained open [New Model Wizard] > Stacktrace > {code} > java.lang.AssertionError: The following shells remained open [New Model Wizard] > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:68) > at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTest(CloseAllShellsExt.java:60) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:64) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69) > at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35) > at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60) > at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58) > at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44) > at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-682) Fix bugs in the Guides Test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-682?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-682. ----------------------------------- pushed to master > Fix bugs in the Guides Test > --------------------------- > > Key: JBTIS-682 > URL: https://issues.jboss.org/browse/JBTIS-682 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Beta1 > Reporter: Matej Kralik > Assignee: Matej Kralik > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22683) OpenShift Explorer: Manage project context menu item is missing in context menu of a connection

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22683?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22683: ----------------------------------------------- [~adietish], please take a look at the pul request. > OpenShift Explorer: Manage project context menu item is missing in context menu of a connection > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22683 > URL: https://issues.jboss.org/browse/JBIDE-22683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3 > > I have not spotted any JIRA related to this so I guess it's a bug. We had a context menu item for managing projects in context menu of an OpenShift 3 connection. Now in nightly build of devstudio 10.0.1.AM1 I don't have this context menu item anymore in the context menu of a connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Daniel Atallah (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Daniel Atallah updated JBIDE-22578: ----------------------------------- Attachment: jboss_tools.20160630.stdout.log Unfortunately(?) we have been able to recreate it with Eclipse Neon and the nightly JBoss Tools build. The following appears in the standard log (now featuring a stacktrace): {noformat} !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-30 15:40:12.013 !MESSAGE Incremental publish failed for module TMSWeb !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-30 15:40:12.013 !MESSAGE Could not delete C:/lean2/development/tms/pippin. May be locked by another process. !STACK 0 java.lang.Exception: Could not delete C:\lean2\development\tms\pippin. May be locked by another process. at org.jboss.ide.eclipse.as.wtp.core.server.behavior.LocalFilesystemController.deleteDirectory(LocalFilesystemController.java:322) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.LocalFilesystemController.deleteResource(LocalFilesystemController.java:254) at org.jboss.ide.eclipse.as.wtp.core.server.publish.PublishModuleIncrementalRunner.publishDelta(PublishModuleIncrementalRunner.java:193) at org.jboss.ide.eclipse.as.wtp.core.server.publish.PublishModuleIncrementalRunner.publishDelta(PublishModuleIncrementalRunner.java:187) at org.jboss.ide.eclipse.as.wtp.core.server.publish.PublishModuleIncrementalRunner.publish(PublishModuleIncrementalRunner.java:118) at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:381) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} I've also attached the stdout log from running in {{-debug}} mode (jboss_tools.20160630.stdout.log). > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.AM1 > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22683) OpenShift Explorer: Manage project context menu item is missing in context menu of a connection

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22683?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-22683: --------------------------------------------- Assignee: Viacheslav Kabanovich > OpenShift Explorer: Manage project context menu item is missing in context menu of a connection > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22683 > URL: https://issues.jboss.org/browse/JBIDE-22683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3 > > I have not spotted any JIRA related to this so I guess it's a bug. We had a context menu item for managing projects in context menu of an OpenShift 3 connection. Now in nightly build of devstudio 10.0.1.AM1 I don't have this context menu item anymore in the context menu of a connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21854) Use the dedicated "link" field for report link

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21854?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21854: -------------------------------------- Assignee: Marcel Bruch > Use the dedicated "link" field for report link > ---------------------------------------------- > > Key: JBIDE-21854 > URL: https://issues.jboss.org/browse/JBIDE-21854 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Assignee: Marcel Bruch > Priority: Minor > > In the description when creating a JIRA from AERI, there are 2 links available in "Other resources" > I think that it makes sens having the first one "Report:" available in the specific Link JIRA field. > Manually, you can do "More->Link -> Web Link" > see https://issues.jboss.org/browse/FUSETOOLS-1702 in "Issue links" section for a sample -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3879: ----------------------------- Target Release: (was: ) > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 10.0.1.AM1 > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3879: --------------------------------- Component/s: target-platform > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 10.0.1.AM1 > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016