October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-493) Add info for GTK3 issues and workaround

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-493?page=com.atlassian.jira.plug... ] Len DiMaggio updated TOOLSDOC-493: ---------------------------------- Assignee: Michelle Murray (was: Len DiMaggio) > Add info for GTK3 issues and workaround > ---------------------------------------- > > Key: TOOLSDOC-493 > URL: https://issues.jboss.org/browse/TOOLSDOC-493 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.0.Beta1, 4.2.0.Final > Reporter: Jiri Peterka > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > There are many serious issues related to GTK3 systems (Ubuntu, Fedora and other GNU/Linux distros). For example https://issues.jboss.org/browse/JBIDE-16315 . It would be good to mention that for OS containing GTK3 this tweak is needed to avoid these issues: > {code} > export SWT_GTK3=0 > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) Some platform bundles comes from pre-SR1 build in CR2 builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18571. ------------------------------ I did a quick verification test of jboss-devstudio-8.0.0.GA-v20141017-1111-B314-installer-standalone.jar [0] and it contains org.eclipse.platform_4.4.0.v20140925-0400.jar from SR1a [1], not the older org.eclipse.platform_4.4.0.v20140910-2310.jar from SR1 [2]. [0] http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.CR2b-build... [1] http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... [2] http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... So, I think we're good here. Closing on behalf of QE (cc: [~mmalina] [~ldimaggio] ) > Some platform bundles comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-b > Fix For: 4.2.0.CR2 > > Attachments: missing-bonus-jdt.core-hacked-by-otdt.png, p2diff_SR1_SR1a, SR1vSR1a.p2diff.txt > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18591) "Error while JSDT ClassPath changed" exception occurs when creating thym project

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18591?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-18591: ----------------------------------------- PR with fix is created for tern.java project: https://github.com/angelozerr/tern.java/pull/156 > "Error while JSDT ClassPath changed" exception occurs when creating thym project > -------------------------------------------------------------------------------- > > Key: JBIDE-18591 > URL: https://issues.jboss.org/browse/JBIDE-18591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > Error message is "Error while JSDT ClassPath changed." and stacktrace is: > {code}org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications. > at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116) > at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251) > at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1322) > at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1376) > at tern.eclipse.ide.core.TernNature.configure(TernNature.java:59) > at tern.eclipse.ide.internal.core.IDETernProject.ensureNatureIsConfigured(IDETernProject.java:817) > at tern.eclipse.ide.internal.core.IDETernProject.<init>(IDETernProject.java:111) > at tern.eclipse.ide.internal.core.IDETernProject.getTernProject(IDETernProject.java:134) > at tern.eclipse.ide.core.TernCorePlugin.getTernProject(TernCorePlugin.java:99) > at tern.eclipse.ide.jsdt.internal.JSDTClassPathManager.elementChanged(JSDTClassPathManager.java:67) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1591) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1581) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1416) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1392) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1945) > at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378) > at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) > at org.eclipse.wst.jsdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:807) > at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:2992) > at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:3023) > at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.setUpJavaScriptProject(HybridProjectCreator.java:135) > at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createProject(HybridProjectCreator.java:104) > at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createBasicTemplatedProject(HybridProjectCreator.java:78) > at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard$1.run(NewHybridProjectWizard.java:91) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059) > at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.performFinish(NewHybridProjectWizard.java:103) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:697) > at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:682) > at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:636) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3188: ------------------------------------------- I feel this is a duplicate. But in short - the client library side is probably easy to implement but the whole management of kerboros keys portably is afaik a complete mess. This requires you to add it to the keystore of the javavm I reckon ? would be great if someone knows how rhc client does is and how we can avoid having to configure it in mutiple difference ways pr. Operating system etc. > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBDS-3188 > URL: https://issues.jboss.org/browse/JBDS-3188 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.x > Reporter: Christos Triantafyllidis > Assignee: Max Rydahl Andersen > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-3188: --------------------------------- Affects Version/s: 8.0.x > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBDS-3188 > URL: https://issues.jboss.org/browse/JBDS-3188 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.x > Reporter: Christos Triantafyllidis > Assignee: Max Rydahl Andersen > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBDS-3188: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1153533 > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBDS-3188 > URL: https://issues.jboss.org/browse/JBDS-3188 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Reporter: Christos Triantafyllidis > Assignee: Max Rydahl Andersen > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by Christos Triantafyllidis (JIRA)

Christos Triantafyllidis created JBDS-3188: ---------------------------------------------- Summary: Support of krb5-principal keys in openshift-java-client (eclipse) Key: JBDS-3188 URL: https://issues.jboss.org/browse/JBDS-3188 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: openshift Reporter: Christos Triantafyllidis Assignee: Max Rydahl Andersen The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-537) IDE How To: Update JBDS

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-537?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-537: -------------------------------------------- Hey [~mmurray], completed the review for the doc. Thanks, Supriya > IDE How To: Update JBDS > ----------------------- > > Key: TOOLSDOC-537 > URL: https://issues.jboss.org/browse/TOOLSDOC-537 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Installation Guide > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > Instructions to cover: > * Update JBDS 7.x or earlier > * Update JBDS 8.0 early access > * Update version of eclipse in use -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3187) enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3187: -------------------------------- Summary: enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier Key: JBDS-3187 URL: https://issues.jboss.org/browse/JBDS-3187 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: build Affects Versions: 8.0.0.CR2 Reporter: Nick Boldt Assignee: Nick Boldt Add a custom enforcer rule (using org.apache.maven.enforcer.rule) that will check if the parent pom contains .Final, and if so, will fail the build unless BUILD_ALIAS is set to "GA". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-543) MobileDev How To: Customize Your App using the jQM and HTML5 palettes

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-543?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-543: -------------------------------------------- Hi [~aakanksha_writer], I have completed reviewing this article. Thanks, Supriya > MobileDev How To: Customize Your App using the jQM and HTML5 palettes > --------------------------------------------------------------------- > > Key: TOOLSDOC-543 > URL: https://issues.jboss.org/browse/TOOLSDOC-543 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - Hybrid Mobile Tools and CordovaSim, User Guide - Mobile Web Tools > Reporter: Michelle Murray > Assignee: Aakanksha Singh > Fix For: 4.2.0.Final > > Time Spent: 3 days > Remaining Estimate: 0 minutes > > Include instructions on the following: > * Drag-and-drop widget wizards > * Content assist? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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