October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18700: --------------------------------------- I thought something around this was reported elsewhere, but now I couldn't find the JIRA. The problem here is that your EAP 6.x could be configured to use Java 6 (that's the default, if you have such JRE when creating the server) and in that case the Java facet should be set to java 6. Ideally it should be set to the same version that the runtime will run on, but I'm not sure if that's achievable. > EAP 6.x Configuration doesn't select Java 7 by default > ------------------------------------------------------ > > Key: JBIDE-18700 > URL: https://issues.jboss.org/browse/JBIDE-18700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > > - Create a new EAP 6.3 server > - Create a new Dynamic Web Project > - Select the EAP runtime > => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer." > !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png! > The EAP 6 Default Configuration should have the Java 1.7 Facet set by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBTIS-348?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBTIS-348: --------------------------------- Assignee: Michelle Murray > User can not download the release note from Red Hat Customer Portal > ------------------------------------------------------------------- > > Key: JBTIS-348 > URL: https://issues.jboss.org/browse/JBTIS-348 > Project: JBoss Tools Integration Stack > Issue Type: Documentation > Environment: JBDSIS 7.0.3.GA > Reporter: hisao furuichi > Assignee: Michelle Murray > > From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. > [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... > [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... > [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16885: ------------------------------------- Fix Version/s: 4.3.x > Embed wizard: Can provide "Code Anything" without url, should not be able to > ---------------------------------------------------------------------------- > > Key: JBIDE-16885 > URL: https://issues.jboss.org/browse/JBIDE-16885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Labels: embed_wizard > Fix For: 4.3.x > > Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). > Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18696 at 10/24/14 5:49 AM: -------------------------------------------------------------------- I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain? was (Author: adietish): I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18696: ------------------------------------------ I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18696: ------------------------------------- Workaround Description: restart eclipse Workaround: Workaround Exists > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-348) User can not download the release note from Red Hat Customer Portal

by hisao furuichi (JIRA)

hisao furuichi created JBTIS-348: ------------------------------------ Summary: User can not download the release note from Red Hat Customer Portal Key: JBTIS-348 URL: https://issues.jboss.org/browse/JBTIS-348 Project: JBoss Tools Integration Stack Issue Type: Documentation Environment: JBDSIS 7.0.3.GA Reporter: hisao furuichi >From Red Hat Customer Portal[1][2], user can not download the release note for JBDSIS 7.0.3[3]. [1] https://access.redhat.com/documentation/ja-JP/Red_Hat_JBoss_Developer_Stu... [2] https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl... [3] https://devstudio.jboss.com/updates/7.0/integration-stack/release-notes/R... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18595: ---------------------------------------- Assigning to QE. I believe we are most likely affected by this issue, but no tested/supported use-case of JBDS shows it up. [~ldimaggio] Can you please look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 and see whether you can reproduce this issue inside JBDS (for example when installing STS or other stuff known to be failing)? > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18595: ----------------------------------- Assignee: Len DiMaggio (was: Mickael Istria) > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file

by Andrei Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ] Andrei Ivanov edited comment on JBIDE-18572 at 10/24/14 5:29 AM: ----------------------------------------------------------------- This bug is so annoying, I have a lot of outgoing files to verify and for each of them I get this error notification popup (using 4.2.0 final). was (Author: andrei.ivanov): This bug is so annoying, I have a lot of outgoing files to verify and for each of them I get this error notification popup. > NPE while calling a diff between 2 versions of a JS file > -------------------------------------------------------- > > Key: JBIDE-18572 > URL: https://issues.jboss.org/browse/JBIDE-18572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Priority: Critical > > Not sure if the error is related {{summarry}}, but here's the stacktrace: > I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem) > {code} > java.lang.NullPointerException > at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572) > at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551) > at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674) > at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369) > at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132) > at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313) > at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254) > at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546) > at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413) > at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567) > at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537) > at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199) > at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139) > at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102) > at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414) > at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) > at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850) > at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142) > at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249) > at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278) > at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:484) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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 October 2014