[JBoss JIRA] (JBIDE-13476) Get rid of bootstrap prifiles
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13476:
----------------------------------------
I'll have a look at this specific BoweserSim case.
I submitted pull request for all components except VPE.
> Get rid of bootstrap prifiles
> -----------------------------
>
> Key: JBIDE-13476
> URL: https://issues.jboss.org/browse/JBIDE-13476
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng, Visual Page Editor core
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> It seens like the bootstrap profiles are not used by developers.
> The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone.
> We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms.
> Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general
--
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, 2 months
[JBoss JIRA] (JBIDE-13056) NPE when invoking Mapping diagram when model doesn't correspond with DB
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13056?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-13056.
--------------------------------
Fix Version/s: 4.0.0.Final
(was: 4.0.x)
(was: 4.1.x)
Resolution: Done
This was fixed along with some other jira, I cannot see this issue anymore.
> NPE when invoking Mapping diagram when model doesn't correspond with DB
> -----------------------------------------------------------------------
>
> Key: JBIDE-13056
> URL: https://issues.jboss.org/browse/JBIDE-13056
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.0.0.Beta2
> Environment: JBDS 6.0.0.Beta2,Linux 64
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Fix For: 4.0.0.Final
>
>
> There is NPE when starting Mapping Diagram with different schemas
> {code}
> !ENTRY org.eclipse.ui 4 0 2012-11-13 12:13:06.965
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.ui.diagram.editors.model.ElementsFactory.createForeingKeyConnections(ElementsFactory.java:81)
> at org.jboss.tools.hibernate.ui.diagram.editors.model.OrmDiagram.recreateChildren(OrmDiagram.java:231)
> at org.jboss.tools.hibernate.ui.diagram.editors.model.OrmDiagram.<init>(OrmDiagram.java:156)
> at org.jboss.tools.hibernate.ui.view.DiagramEditorInput.createOrmDiagram(DiagramEditorInput.java:68)
> at org.jboss.tools.hibernate.ui.view.DiagramEditorInput.<init>(DiagramEditorInput.java:64)
> at org.jboss.tools.hibernate.ui.view.OpenDiagramActionDelegate.openEditor(OpenDiagramActionDelegate.java:127)
> at org.jboss.tools.hibernate.ui.view.OpenDiagramActionDelegate.run(OpenDiagramActionDelegate.java:105)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> 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.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> {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, 2 months
[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11881:
-------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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, 2 months
[JBoss JIRA] (JBIDE-12015) OpenShift Wizard - Use Default Location is confusing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12015?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12015:
-------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
> OpenShift Wizard - Use Default Location is confusing
> ----------------------------------------------------
>
> Key: JBIDE-12015
> URL: https://issues.jboss.org/browse/JBIDE-12015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> The Cloning Settings: Use default location - suggests that the end-user needs to put in his Git location - users have been trying to use "C:\Program Files (x86)\Git" and that causes some other errors. This is also not the end-user's project directory. We should find a way to better explain what is being asked for here.
--
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, 2 months
[JBoss JIRA] (JBIDE-12015) OpenShift Wizard - Use Default Location is confusing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12015?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12015:
------------------------------------------
moving to Alpha2 since we ran out of time for Alpha1
> OpenShift Wizard - Use Default Location is confusing
> ----------------------------------------------------
>
> Key: JBIDE-12015
> URL: https://issues.jboss.org/browse/JBIDE-12015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png
>
>
> The Cloning Settings: Use default location - suggests that the end-user needs to put in his Git location - users have been trying to use "C:\Program Files (x86)\Git" and that causes some other errors. This is also not the end-user's project directory. We should find a way to better explain what is being asked for here.
--
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, 2 months
[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11881:
------------------------------------------
moving to Alpha2 since we ran out of time for Alpha1
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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, 2 months
[JBoss JIRA] (JBIDE-13075) Openshift Wizard should ask "would you like to push your project"?
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13075:
-------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.0.Alpha1)
> Openshift Wizard should ask "would you like to push your project"?
> ------------------------------------------------------------------
>
> Key: JBIDE-13075
> URL: https://issues.jboss.org/browse/JBIDE-13075
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Fix For: 4.1.0.Alpha2
>
> Attachments: 1-local-change.png, no_changes_yes.png
>
>
> I believe the end-user will rarely remember to perform a git push once he has completed the OpenShift New Application Wizard - it is totally "not obvious" that is what is the next step - especially when the end-user is warned away from a push (see screenshot).
> In JBIDE-12122 Fred suggested the following:
> {quote}
> When creating an new openshift application from an existing workspace project, I expect my project to be deployed automatically once the Openshift app is created.
> Since not all projects are openshift-ready, we should have a checkbox on the openshift wizard (enabled when using an existing project) that basically says "deploy my app once created".
> The state of that checkbox should be stored in the workspace preferences.
> And obviously, when the box is checked, the local git repo would be pushed after the openshift app is created.
> Workflow should be :
> * create a project 'myapp' from JBoss Central (say HTML5)
> * create a new OpenShift application 'myapp', based on the jbossas7 cartridge, using the existing 'myapp' project
> * check the deploy checkbox
> * once the myapp.<mydomain>.rhcloud.com server is ready, Opening http://myapp.<mydomain>.rhcloud.com should display the HTML5 app
> {quote}
--
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, 2 months