[JBoss JIRA] (JBIDE-13195) Deployment tab of server editor is enabled when server is stopped but not synchronized
by Martin Malina (JIRA)
Martin Malina created JBIDE-13195:
-------------------------------------
Summary: Deployment tab of server editor is enabled when server is stopped but not synchronized
Key: JBIDE-13195
URL: https://issues.jboss.org/browse/JBIDE-13195
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.CR1
Environment: JBDS 6.0.0.CR1b B147
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha1
When verifying JBIDE-13136 I found one edge scenario that still doesn't work correctly.
See these steps:
1. Server is started and module is deployed - editing disabled - fine
2. Stop server - editing disabled - fine
3. Remove module - editing enabled! - FAIL - it should still be disabled unless you click Publish on the server
Please see the other JIRA if you need more information.
--
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, 4 months
[JBoss JIRA] (JBDS-2412) Compare JBDS 5.0.0 vs 6.0.0 memory consumption
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2412?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2412:
--------------------------------------
Labels: f2f2012 (was: )
> Compare JBDS 5.0.0 vs 6.0.0 memory consumption
> ----------------------------------------------
>
> Key: JBDS-2412
> URL: https://issues.jboss.org/browse/JBDS-2412
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Environment: JBDS 6.0.0.CR1a vs JBDS 5.0.1.GA
> Reporter: Jiri Peterka
> Assignee: Martin Malina
> Labels: f2f2012
> Fix For: 6.0.0.CR1
>
>
> Perform manual testing done by hooking up jvisualvm or another profiler to JBDS 5 and 6
> and compare the memory usage in the following cases:
> 1) Default install, nothing extra, no projects loaded.
> 2) Default install, nothing extra, create the HTML5 and Richfaces App.
> 3) After a restart with same workspace used in #2
> 4) Install all plugins from Central, no projects loaded, restarted.
> 5) Install all plugins from Central, projects loaded from step #2
--
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, 4 months
[JBoss JIRA] (JBIDE-13193) Allow git operations over https instead of https
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13193:
-------------------------------------
Summary: Allow git operations over https instead of https
Key: JBIDE-13193
URL: https://issues.jboss.org/browse/JBIDE-13193
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.1.0.Alpha1
If the user has some required proxy settings, he may need to tweek his git global config to be able run clone/push/pull git operations.
Furthermore, in some corporate environments, proxies may not allow for ssh usage .
The OpenShift tooling could offer an alternative by switching to https instead of ssh protocol, provided that openshift.com itself supports the former one.
--
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, 4 months
[JBoss JIRA] (JBDS-2361) Consider moving com.jboss.jbds.* features content out of Extras (keep only in Central)
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2361:
--------------------------------
Summary: Consider moving com.jboss.jbds.* features content out of Extras (keep only in Central)
Key: JBDS-2361
URL: https://issues.jboss.org/browse/JBDS-2361
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build, central, updatesite
Affects Versions: 6.0.0.Beta1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 6.0.0.CR1
As per https://issues.jboss.org/browse/JBDS-2284?focusedCommentId=12726296&page=... ...
we can now look at eliminating the remaining JBDS Extras features, and keeping the contents therein only in Central:
{quote}
* TestNG
* SpringIDE
* Mylyn
* Git.Mylyn
* Eclipse-CS
* GWT
* GWT.Designer
* Subclipse
* Subclipse.Mylyn
* com.jboss.jbds.m2e.extras (JBoss Tools Maven Integration plugins for GWT and JBoss Packaging + org.eclipse.m2e.wtp.feature + org.sonatype.m2e.mavenarchiver.feature)
{quote}
Assigned to Max for comment then back to me to do the 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, 4 months
[JBoss JIRA] (JBDS-2353) Missing jpt.jaxb feature
by Mustafa Musaji (JIRA)
Mustafa Musaji created JBDS-2353:
------------------------------------
Summary: Missing jpt.jaxb feature
Key: JBDS-2353
URL: https://issues.jboss.org/browse/JBDS-2353
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build
Affects Versions: 5.0.0.GA
Reporter: Mustafa Musaji
Assignee: Nick Boldt
The ability to right click on .XSD file, Generate->JAXB Classes which was in JBDS4 is no longer available and was removed from JBDS 5.0
[~nickboldt] wrote:
JBT3.2/JBDS4 used a target platform with this feature in it from WTP 3.2:
<unit id="org.eclipse.jpt.feature.feature.group" version="2.3.4.v201104192310-7N7UF77FD3wTgcVbmmf0cT"/>
And that massive feature contains (among other things):
./features/org.eclipse.jpt.feature_2.3.4.v201104192310-7N7UF77FD3wTgcVbmmf0cT.jar
./plugins/org.eclipse.jpt.jaxb.ui_1.0.1.v201006300000.jar
./plugins/org.eclipse.jpt.jaxb.core.schemagen_1.0.1.v201006300000.jar
---
In WTP 3.3, they refactored their uber-features into smaller features.
So, in JBT3.3/JBDS5, we used a target platform with these features:
<unit id="org.eclipse.jpt.common.feature.feature.group" version="1.0.2.v201111103010-6-3AkF7BC9EBID797"/>
<unit id="org.eclipse.jpt.common.eclipselink.feature.feature.group" version="1.0.1.v201108080010-3-08s73553F3G3343"/>
<unit id="org.eclipse.jpt.jpa.feature.feature.group" version="3.0.2.v201110193010-7S7B7HFC7sRdlV6fmbQaRBF5"/>
<unit id="org.eclipse.persistence.jpa.feature.group" version="2.3.2.v20111125-r10461"/>
But since we did not include the new jpt.jaxb feature, we did not include these:
./features/org.eclipse.jpt.jaxb.feature_1.0.2.v201111103010-508cAkF7BC8GBGA78A.jar
./plugins/org.eclipse.jpt.jaxb.ui_1.1.2.v201201260000.jar
./plugins/org.eclipse.jpt.jaxb.core.schemagen_1.0.100.v201104110000.jar
---
Similarly, in JBT4/JBDS6 (WTP 3.4), we have this:
<unit id="org.eclipse.jpt.common.feature.feature.group" version="1.2.1.v201208222210-663AkF7BF7cFFFFB7"/>
<unit id="org.eclipse.jpt.common.eclipselink.feature.feature.group" version="1.2.1.v201208222210-3318s73573J777753"/>
<unit id="org.eclipse.jpt.jpa.eclipselink.feature.feature.group" version="3.2.1.v201208222210-7M7J78F7RZHQYJAQsS4SVFD7"/>
<unit id="org.eclipse.jpt.jpa.feature.feature.group" version="3.2.1.v201208222210-7S7K8gFBBoPapQieUcW_TFD7"/>
<unit id="org.eclipse.persistence.jpa.feature.group" version="2.4.0.v20120608-r11652"/>
And we're therefore (still) missing these:
./features/org.eclipse.jpt.jaxb.feature_1.2.1.v201208222210-56ABAkF7BF7cFFFFB7.jar
./plugins/org.eclipse.jpt.jaxb.ui_1.3.1.v201208222210.jar
./plugins/org.eclipse.jpt.jaxb.core.schemagen_1.0.201.v201208222210.jar
This JIRA is to track the addition of these plugins back in to JBDS.
--
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, 4 months
[JBoss JIRA] (JBIDE-10808) Illegal State exception when deleting project
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-10808:
----------------------------------------
Summary: Illegal State exception when deleting project
Key: JBIDE-10808
URL: https://issues.jboss.org/browse/JBIDE-10808
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.Beta1
Reporter: Rastislav Wagner
Message: An exception occurred invoking extension: org.eclipse.jst.jee.ui.web for object P/DynWebP
Stack Trace: java.lang.IllegalStateException: The project <P/DynWebP> is not accessible.
at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:148)
at org.eclipse.jst.jee.model.internal.Web25ModelProvider.getModelObject(Web25ModelProvider.java:44)
at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelObject(JEE5ModelProvider.java:217)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.loadProviders(AbstractMergedModelProvider.java:261)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.access$2(AbstractMergedModelProvider.java:255)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider$LoadModelsWorkspaceRunnable.run(AbstractMergedModelProvider.java:278)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.loadModel(AbstractMergedModelProvider.java:249)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getMergedModel(AbstractMergedModelProvider.java:219)
at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getModelObject(AbstractMergedModelProvider.java:139)
at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getNewContentProviderInstance(Web25ContentProvider.java:69)
at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedContentProvider(JEE5ContentProvider.java:92)
at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getChildren(Web25ContentProvider.java:35)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1352)
at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:605)
at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2620)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908)
at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1915)
at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840)
at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561)
at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548)
at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:353)
at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465)
at org.jboss.tools.seam.ui.views.AbstractSeamContentProvider$3.run(AbstractSeamContentProvider.java:233)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331)
at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:605)
at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:153)
at org.eclipse.ltk.ui.refactoring.resource.DeleteResourcesWizard$DeleteResourcesRefactoringConfigurationPage.performFinish(DeleteResourcesWizard.java:151)
at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:678)
at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:455)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:181)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:193)
at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:116)
at org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommandInContext(HandlerService.java:270)
at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95)
at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47)
at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:474)
at org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:165)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
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.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2168) Review and improve mechanism to provide 3rd-party features
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2168:
------------------------------------
Summary: Review and improve mechanism to provide 3rd-party features
Key: JBDS-2168
URL: https://issues.jboss.org/browse/JBDS-2168
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: 3rdPartyDependencies, Build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 6.x
Currently, we wrap (in a 1-1 mapping) most 3rd-party features as "requirements" into features of ours. It allows to show our license and lable when installing.
We should think about other approaches, and choose the best one:
* Get rid of our features and directly include 3rd-party features in site. Keep our features only when we want an assembly of several 3rd-party features (we do it for springide)
* Prefer inclusion over requirement so that we can restrict the version we allow for 3rd-party features. If someone wants a different one, he'll have to uninstall the JBDS "supported" feature first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months