[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-13537.
-------------------------------------
Resolution: Done
Resetting resolution after reopening to edit release notes text
> Unable to create EAP6.1 server [4.0.1 maintenance]
> ---------------------------------------------------
>
> Key: JBIDE-13537
> URL: https://issues.jboss.org/browse/JBIDE-13537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, runtime-detection
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png
>
>
> EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13213:
------------------------------------
Writer: mmurray
Release Notes Text: Project Archives capabilities for a project could previously only be set through the Project Archives view. To make it easier to find and more intuitive to use, this functionality has also been added to the context menu for a project. Now Project Archives capabilities can be added and removed from a project by right-clicking on a project and selecting Configure->Add Project Archives Support or Configure->Remove Project Archives Support, respectively. This can be accessed in Navigator, Project Explorer and Java Package Explorer views. (was: Cause: There is no visible action to enable Project Archives capabilities through project pop-up menu [Configure]->[Add Project Archive Support]
Consequence: The way to do it through opening Project Archives view is not obvious for users
Fix: Project pop-up menu has [Configure]->[Add Project Archives Support...] item to make it easier to find
Result: Project Archives support can be enabled for a project through popup-menu in several Eclipse Views: Navigator, Project Explorer and Java Package Explorer)
> Simple adding/removing Project Archives capabilities into project
> -----------------------------------------------------------------
>
> Key: JBIDE-13213
> URL: https://issues.jboss.org/browse/JBIDE-13213
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives
> Reporter: Vlado Pakan
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
>
> It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-13213.
-------------------------------------
Resolution: Done
Resetting resolution after reopening to edit release notes text
> Simple adding/removing Project Archives capabilities into project
> -----------------------------------------------------------------
>
> Key: JBIDE-13213
> URL: https://issues.jboss.org/browse/JBIDE-13213
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives
> Reporter: Vlado Pakan
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
>
> It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-12901) Show in File Browser shows error for EAP 5.1.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12901?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12901:
------------------------------------
Writer: mmurray
Release Notes Text: Through the Remote Server Explorer (RSE), file systems on remote servers can be viewed and managed. Previously, when an archived file was expanded in RSE it caused an exception to occur. A patch was submitted to RSE and it was accepted and applied to RSE 3.4.2 (Eclipse Juno SR2). The RSE now checks that the element to be expanded is a directory before performing the expansion and, consequently, exceptions relating to expanding archived files no longer occur. (was: Cause: Upstream issue in Eclipse RSE https://bugs.eclipse.org/bugs/show_bug.cgi?id=393384
Consequence: Exception occurs when folder with archive extension is expanded in Remote File System Browser
Fix: Code checks if expanding element is a directory
Result: No exceptions in eclipse Error View)
> Show in File Browser shows error for EAP 5.1.2
> ----------------------------------------------
>
> Key: JBIDE-12901
> URL: https://issues.jboss.org/browse/JBIDE-12901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, UpStream
> Affects Versions: 4.0.0.Beta1
> Environment: JBDS 6.0.0.Beta1 B45
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: upstream
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: ifile-error.png, RemoteSystemExplorer-JBIDE-12901.png
>
>
> When you try to see what's in the deployment folder of a remote EAP 5.1.2 server, you will get an error (but the Remote System explorer will be opened correctly and will show the files).
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Folder cannot be cast to org.eclipse.core.resources.IFile
> at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getLocalResource(SystemViewRemoteFileAdapter.java:632)
> at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getImageDescriptor(SystemViewRemoteFileAdapter.java:574)
> at org.eclipse.rse.ui.view.SystemTableViewProvider.getImage(SystemTableViewProvider.java:236)
> at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:85)
> at org.eclipse.rse.internal.ui.view.SystemDecoratingLabelProvider.getColumnImage(SystemDecoratingLabelProvider.java:46)
> at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:71)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
> at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636)
> at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590)
> at org.eclipse.rse.ui.view.SystemTableView.inputChanged(SystemTableView.java:479)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
> at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1599)
> at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1578)
> at org.jboss.ide.eclipse.as.rse.ui.SystemShowInTableAction.run(SystemShowInTableAction.java:77)
> at org.jboss.ide.eclipse.as.rse.ui.RSEDeploymentPreferenceUI$2.openExplorer(RSEDeploymentPreferenceUI.java:115)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:89)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:83)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.access$0(ExploreActionProvider.java:82)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider$1.run(ExploreActionProvider.java:74)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-12901) Show in File Browser shows error for EAP 5.1.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12901?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-12901.
-------------------------------------
Resolution: Done
Resetting resolution after reopening to edit release notes text
> Show in File Browser shows error for EAP 5.1.2
> ----------------------------------------------
>
> Key: JBIDE-12901
> URL: https://issues.jboss.org/browse/JBIDE-12901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, UpStream
> Affects Versions: 4.0.0.Beta1
> Environment: JBDS 6.0.0.Beta1 B45
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: upstream
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: ifile-error.png, RemoteSystemExplorer-JBIDE-12901.png
>
>
> When you try to see what's in the deployment folder of a remote EAP 5.1.2 server, you will get an error (but the Remote System explorer will be opened correctly and will show the files).
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.ClassCastException: org.eclipse.core.internal.resources.Folder cannot be cast to org.eclipse.core.resources.IFile
> at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getLocalResource(SystemViewRemoteFileAdapter.java:632)
> at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getImageDescriptor(SystemViewRemoteFileAdapter.java:574)
> at org.eclipse.rse.ui.view.SystemTableViewProvider.getImage(SystemTableViewProvider.java:236)
> at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:85)
> at org.eclipse.rse.internal.ui.view.SystemDecoratingLabelProvider.getColumnImage(SystemDecoratingLabelProvider.java:46)
> at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:71)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
> at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636)
> at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590)
> at org.eclipse.rse.ui.view.SystemTableView.inputChanged(SystemTableView.java:479)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
> at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1599)
> at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1578)
> at org.jboss.ide.eclipse.as.rse.ui.SystemShowInTableAction.run(SystemShowInTableAction.java:77)
> at org.jboss.ide.eclipse.as.rse.ui.RSEDeploymentPreferenceUI$2.openExplorer(RSEDeploymentPreferenceUI.java:115)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:89)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:83)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.access$0(ExploreActionProvider.java:82)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider$1.run(ExploreActionProvider.java:74)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-10398) OpenShift Express : Can not delete git project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10398?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-10398:
------------------------------------
Writer: mmurray
Release Notes Text: EGit provides tooling for Git in Eclipse and it is used by applications deployed to OpenShift. Previously the EGit cache held references to the files in a project and these references prevented workspace projects from being deleted on Microsoft Windows operating systems. Consequently, the projects of OpenShift applications that were imported into the workspace could not be deleted. A patch was submitted to EGit and it was accepted and applied to EGit 2.3.1 (Eclipse Juno SR2). The Git cache now releases references to missing files so projects of OpenShift applications can be deleted from the workspace on Microsoft Windows operating systems. (was: Cause:
The EGit cache held references to files in the project. These references prevented the project from bein deleted on Windows.
Consequence:
A windows user could not delete projects in his workspace he had imported from OpenShift applications.
Fix:
A patch was submitted to EGit that was accepted and applied to EGit 2.3.1 (Eclipse Juno SR2). The patch tells the Git cache to release references to missing files.
Result:
A windows user can delete a project he had imported from OpenShift)
> OpenShift Express : Can not delete git project
> ----------------------------------------------
>
> Key: JBIDE-10398
> URL: https://issues.jboss.org/browse/JBIDE-10398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: UpStream
> Affects Versions: 3.3.0.M5
> Environment: windows 7 (most likely all windows flavors)
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.0.1.Final
>
> Attachments: openshift.ogv
>
>
> Whenever I try to physically delete my openshift project from the workspace, I get a popup with the following errors :
> {noformat}
> Problems encountered while deleting resources.
> Could not delete '/hello/.git'.
> Problems encountered while deleting resources.
> Problems encountered while deleting files.
> Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack\pack-10eb864ff7ab3a1edfc8b868c90a743fdee571db.pack.
> Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack.
> Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects.
> Could not delete: C:\Users\Fred Bricon\git\hello\.git.
> Could not delete 'C:\Users\Fred Bricon\git\hello'.
> {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
13 years, 1 month
[JBoss JIRA] (JBDS-2438) include EAP 6.0.1 in JBDS 6.0.1 installer
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2438?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2438:
----------------------------------
Release Notes Docs Status: Documented as Feature Request (was: Documented as Resolved Issue)
Writer: mmurray
Release Notes Text: A universal installer that includes JBoss Enterprise Application Platform is available for each release of JBoss Developer Studio. Previously, JBoss Enterprise Application Platform 6.0.0 was included. JBoss Enterprise Application Platform 6.0.1 has now been released, which fixes issues in JBoss Enterprise Application Platform 6.0.0. Consequently, JBoss Enterprise Application Platform 6.0.1 is now included in the combined universal installer. (was: Cause: EAP 6.0.0 is old
Consequence: EAP 6.0.0 should be replaced by EAP 6.0.1
Fix: replace EAP 6.0.0 with 6.0.1
Result: installer has been updated to include EAP 6.0.1 instead of 6.0.0
(Really? Do RN need to be this verbose?))
> include EAP 6.0.1 in JBDS 6.0.1 installer
> -----------------------------------------
>
> Key: JBDS-2438
> URL: https://issues.jboss.org/browse/JBDS-2438
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 6.0.1.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA
>
> Attachments: JBDS2438.patch.txt, JBDS2438.patch2.txt
>
>
> EAP 6.0.1 is out. Time to update the installer to include the latest n' greatest EAP 6.
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2365:
----------------------------------
Writer: mmurray
Release Notes Text: JBoss Enterprise Service Bus (ESB) 4.11 and 4.12 projects were not recognized as compatible for deploying on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server and, as a result, the associated applications could not be deployed to these servers. The list of compatible facets held by Server Tools has been extended to include JBoss ESB 4.11 and 4.12. Consequently, the applications of JBoss ESB 4.11 and 4.12 projects can now be deployed on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server without errors or warnings. (was: Cause: as.core (Server tools) did not list ESB 4.11 and 4.12 as a compatible runtime/facet to use together with AS and EAP servers.
Consequence: When using ESB tooling the wizards to create ESB 4.11 and 4.12 projects the projects were not possible to deploy to the server because the project was considered incompatible with the servers.
Fix: The list of compatible facets/runtimes now list ESB 4.11 and 4.12 for the AS and EAP server's. JBIDE-13328 includes additional fixing to make it possible for the esb project to manage this without updates to the server core.
Result: ESB 4.11 and 4.12 projects can be deployed using the server adapter without errors/warnings. )
> ESB projects cannot be deployed using Server Add/Remove
> -------------------------------------------------------
>
> Key: JBDS-2365
> URL: https://issues.jboss.org/browse/JBDS-2365
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Jeremy Davis
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 6.0.0.CR1, 6.0.1.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-2284) Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2284?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2284:
----------------------------------
Writer: mmurray
Release Notes Text: A limited number of third party extensions and tools could be installed from the JBoss Developer Studio Extras site. This was achieved through mirroring of other sites and the use of Tycho, a set of plug-ins for Eclipse used to build update sites. The site for FindBugs 2.0.1 was not compatible with Tycho and made maintaining the Extras site difficult. To resolve this issue, FindBugs is now only available through JBoss Central and as version 2.0.2. Similarly, PMD and Android Tooling are also no longer available through the Extras site but are now available through JBoss Central. (was: Cause: FindBugs 2.0.1 site was old, and hard to mirror
Consequence: we had to manually hack up an update site, which was hard to maintain
Fix: move up to FindBugs 2.0.2 and improve mirroring to suppress 3rd party references in the site metadata
Result: JBT4.0.1/JBDS6.0.1 now includes FindBugs 2.0.2 within Central.)
> Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central
> ---------------------------------------------------------------
>
> Key: JBDS-2284
> URL: https://issues.jboss.org/browse/JBDS-2284
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central
> Affects Versions: 6.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 6.0.1.GA
>
>
> Bits mirrored here:
> http://download.jboss.org/jbosstools/updates/requirements/findbugs/2.0.1....
--
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
13 years, 1 month