[JBoss JIRA] (JBDS-2964) Mylyn Jenkis/Hudson Connector - User can create a build server - but may not find how/where to delete it
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2964?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2964:
--------------------------------------
Workaround Description: Click on Builds View menu and choose "Show Team Repositories" View and from here you can delete the build server.
There is a workaround for this now, but bug still exists at https://bugs.eclipse.org/bugs/show_bug.cgi?id=340986
The PR [~snjeza] made did not seem to work for the mylyn committer ;/
> Mylyn Jenkis/Hudson Connector - User can create a build server - but may not find how/where to delete it
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2964
> URL: https://issues.jboss.org/browse/JBDS-2964
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.1.1.CR1
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 8.0.x
>
>
> The user is able to create a new build server in the Builds view - but they cannot delete a server from that view. The user must move to the Team Repositories view to delete a build. This is confusing - at first it may appear to the user as if he cannot delete a build server.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-2964) Mylyn Jenkis/Hudson Connector - User can create a build server - but may not find how/where to delete it
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2964?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2964:
--------------------------------------
Fix Version/s: 8.0.x
(was: 7.1.x)
> Mylyn Jenkis/Hudson Connector - User can create a build server - but may not find how/where to delete it
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2964
> URL: https://issues.jboss.org/browse/JBDS-2964
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.1.1.CR1
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 8.0.x
>
>
> The user is able to create a new build server in the Builds view - but they cannot delete a server from that view. The user must move to the Team Repositories view to delete a build. This is confusing - at first it may appear to the user as if he cannot delete a build server.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Fix Version/s: 4.2.0.CR2
(was: 4.2.0.CR1)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.2.0.CR2
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-4523) Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4523?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-4523:
---------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Visual Page Editor doesn't work with Eclipse with OSX Cocoa 64-bit (32-bit already fixed)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-4523
> URL: https://issues.jboss.org/browse/JBIDE-4523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M1
> Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1
> Reporter: César Pérez
> Assignee: Konstantin Marmalyukov
> Labels: cocoa, new_and_noteworthy, osx, vpe
> Fix For: 4.3.x
>
>
> The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace:
> org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found.
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3009) use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3009?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3009:
--------------------------------------
Labels: new_and_noteworthy (was: )
> use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3009
> URL: https://issues.jboss.org/browse/JBDS-3009
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build, installer, updatesite
> Affects Versions: 8.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 8.0.0.CR1
>
> Attachments: ssl-enabled-for-filemgmt-but-at-what-cost.png
>
>
> use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)
> Affected files: *.xml, *.inf, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15148) CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15148?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15148:
----------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> CLONE - VPE-Remove Visual/Source Tab and Preview Tab on 64-bit OSs
> ------------------------------------------------------------------
>
> Key: JBIDE-15148
> URL: https://issues.jboss.org/browse/JBIDE-15148
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Environment: 64-bit
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: jbide10711-v2.patch, jbide10711.patch, Screen Shot 2012-01-25 at 11.25.49 AM.png, Screen Shot 2012-01-25 at 11.25.59 AM.png
>
>
> *Cloned description:*
> Currently the end-user is presented with
> Could not open the Visual Page Editor:
> Current platform 'cocoa.macosx.x86_64' is not supported.
> There is no need to tease the user if the features are not available, hide the tabs.
> *Update:*
> * Now there is only one tab on 64-bit Mac.
> * On 64-bit Windows there are three tabs, visual parts show the following message:
> bq. Visual Page Editor has experimental support for Windows 64-bit. Follow the link below to get details on how to install. Until then you can click on the Source tab to hide this error/info message. [Also see VPE FAQ|https://community.jboss.org/docs/DOC-10862]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months