[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III edited comment on JBDS-2734 at 9/5/13 8:40 PM:
------------------------------------------------------------------
Hey Michelle,
That sounds good. Here is what we are planning to provide from a functionality point-of-view:
* Edit Addons
-- Install Addons
-- Remove Addons
-- Build and Install an Addon
* Create a new project with Forge 2 wizard.
-- Maven Java
-- Maven Resources
-- Maven Forge Addon
* Java EE
-- Setup Bean Validation
-- Setup CDI
-- Setup REST
-- Setup EJB
-- Setup JSF
-- Setup Servlet
-- Setup JPA
* New Entity
* New Field
* Reverse Engineer Database
-- Creates JPA entities in existing Project or Folder
* Scaffold
-- Setup
-- From JPA Entities
*** Our BHAG is a Multi-step Wizard that will Step the User through creating a new project, reverse engineering a database, setting up necessary EE specs, and generating scaffolding.
However, this does not address how users will/should interact with Forge1 and Forge2. Here is what I would like, and what I believe you suggested in your comments:
CTRL+4 should default to Forge 2 out-of-box. The user may then utilize the Eclipse standard "Keys preferences" page to change that setting to Forge1. Via this same mechanism, they may also configure the key to allow them to select Forge1 or Forge2 each time it is pressed. Max can confirm, but I believe this is standard Eclipse config and should not require much implementation on our part.
We should not need to change the Forge preferences pane in this release AFAIK.
was (Author: lincolnthree):
Hey Michelle,
That sounds good. Here is what we are planning to provide from a functionality point-of-view:
* Edit Addons
-- Install Addons
-- Remove Addons
-- Build and Install an Addon
* Create a new project with Forge 2 wizard.
-- Maven Java
-- Maven Resources
-- Maven Forge Addon
* Java EE
-- Setup CDI
-- Setup REST
-- Setup EJB
-- Setup JSF
-- Setup Servlet
-- Setup JPA
* New Entity
* New Field
* Reverse Engineer Database
-- Creates JPA entities in existing Project or Folder
* Scaffold
-- Setup
-- From JPA Entities
*** Our BHAG is a Multi-step Wizard that will Step the User through creating a new project, reverse engineering a database, setting up necessary EE specs, and generating scaffolding.
However, this does not address how users will/should interact with Forge1 and Forge2. Here is what I would like, and what I believe you suggested in your comments:
CTRL+4 should default to Forge 2 out-of-box. The user may then utilize the Eclipse standard "Keys preferences" page to change that setting to Forge1. Via this same mechanism, they may also configure the key to allow them to select Forge1 or Forge2 each time it is pressed. Max can confirm, but I believe this is standard Eclipse config and should not require much implementation on our part.
We should not need to change the Forge preferences pane in this release AFAIK.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in 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
12 years, 7 months
[JBoss JIRA] (JBDS-2047) gpd.xml is written in platform encoding
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2047?page=com.atlassian.jira.plugin.... ]
Kris Verlaenen resolved JBDS-2047.
----------------------------------
Resolution: Out of Date
> gpd.xml is written in platform encoding
> ---------------------------------------
>
> Key: JBDS-2047
> URL: https://issues.jboss.org/browse/JBDS-2047
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbpm
> Affects Versions: 4.1.1.GA
> Reporter: Toshiya Kobayashi
> Assignee: Kris Verlaenen
> Fix For: 6.0.0.Alpha1-SOA
>
>
> Platform JIRA for GPD-184 and GPD-98
> Here are the reproduce steps but basically the same as those GPD Jiras.
> 1. Window->Preference, General->Workspace, change the 'Text file encoding' to "Other: UTF-8". (Default is MS932 in Japanese Windows)
> 2. Create a jBPM3 project. (with a sample process)
> 3. Set 'スタート' the name of a start-state with GPD editor.
> 4. Look at .simple.gpd.xml (you may need to edit Package Explorer Filter for .* resources to find the file in JBDS)
> The file is written in Shift_JIS(MS932) even though it declares encoding="UTF-8".
> It will cause a problem when you use jbpm-console to see the process image.
> - In jbpm-console : An exception of type "org.jbpm.util.XmlException" was thrown. The message is: failed to parse xml
> - In server.log : [Fatal Error] :4:15: Invalid byte 1 of 1-byte UTF-8 sequence.
> GPD editor doesn't lookup the workspace settings when it generates gpd.xml.
> Hard-coded "UTF-8" may be fine (the proposed patch in GPD-184)
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-8247) Error message after opening file after opening jbpm editor in Package Explorer
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8247?page=com.atlassian.jira.plugin... ]
Kris Verlaenen closed JBIDE-8247.
---------------------------------
Resolution: Out of Date
> Error message after opening file after opening jbpm editor in Package Explorer
> ------------------------------------------------------------------------------
>
> Key: JBIDE-8247
> URL: https://issues.jboss.org/browse/JBIDE-8247
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jbpm
> Affects Versions: 3.2.0.CR1
> Environment: JBDS 4.0.0.CR1 H100, Linux 64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 3.3.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> There is error message / warning after these steps:
> 1. Create sample jBPM Project, be in Package Explorer
> 2. Open simple.jpdl.xml in package explorer
> 3. (You can wait as long as you want)
> 4. Open hibernate.cfg.xml or any other file type (except jbpm process)
> java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part org.eclipse.ui.views.PropertySheet while still in the middle of activating part org.jbpm.gd.jpdl.editor
> at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3487)
> at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:3077)
> at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:279)
> at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:237)
> 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.Widget.sendEvent(Widget.java:1282)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1533)
> at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:3403)
> at org.eclipse.swt.widgets.Control.gtk_event_after(Control.java:2760)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1738)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4796)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4360)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_grab_focus(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_grab_focus(OS.java:12672)
> at org.eclipse.swt.widgets.Control.forceFocus(Control.java:2170)
> at org.eclipse.swt.widgets.Composite.forceFocus(Composite.java:526)
> at org.eclipse.swt.widgets.Control.forceFocus(Control.java:2163)
> at org.eclipse.swt.widgets.Control.setFocus(Control.java:3760)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1372)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1370)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1370)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1370)
> at org.eclipse.swt.widgets.Control.fixFocus(Control.java:160)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:4156)
> at org.eclipse.ui.part.PageBook.showPage(PageBook.java:118)
> at org.eclipse.ui.part.PageBookView.showPageRec(PageBookView.java:977)
> at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:756)
> at org.eclipse.ui.views.properties.PropertySheet.partActivated(PropertySheet.java:325)
> at org.eclipse.ui.part.PageBookView$4.partActivated(PageBookView.java:1010)
> at org.eclipse.ui.internal.PartListenerList2$1.run(PartListenerList2.java:70)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.runtime.Platform.run(Platform.java:888)
> at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:55)
> at org.eclipse.ui.internal.PartListenerList2.firePartActivated(PartListenerList2.java:68)
> at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:192)
> at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:306)
> at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:57)
> at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136)
> at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3537)
> at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:3077)
> at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:279)
> at org.eclipse.ui.internal.EditorPane.requestActivation(EditorPane.java:98)
> at org.eclipse.ui.internal.PartPane.handleEvent(PartPane.java:237)
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-5234) jPDL 4 Graphical Designer problem when naming Nodes under Windows XP and maybe other Windows Products
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5234?page=com.atlassian.jira.plugin... ]
Kris Verlaenen closed JBIDE-5234.
---------------------------------
Resolution: Out of Date
> jPDL 4 Graphical Designer problem when naming Nodes under Windows XP and maybe other Windows Products
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-5234
> URL: https://issues.jboss.org/browse/JBIDE-5234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jbpm
> Affects Versions: 3.1.0.M4
> Environment: Affect as far as I seen, ONLY MIcrosoft WIndows XP Machines. LINUX doesn't seem to be affected.
> Reporter: Burjan Romulus Sorin
> Assignee: Koen Aers
> Priority: Minor
> Labels: usability
> Attachments: wrong-beanid1.png, wrong-beanid2.png
>
>
> This bug affects the Graphical Designer of JBoss Tools.
> Version tested on :
> jBPM 4 Graphical Editor and Tools 4.0.0.v200910281724M-H247-M4 org.jboss.tools.flow.jpdl4.feature.feature.group
> Issue : When creating a process definition inside a project, I open the Graphical Editor in order to design the process.
> I add tasks, transitions, etc. On the bottom of the page, on the tabs list, I have a "Proprieties" tab. In there, I can change/add specifications to the selected node.
> If I try to change the name from there, after Every character written the cursor goes at the first position of the box. So when I write a task with the name : "test", it will appear "tset".
> Note that editing from the XML directly works perfectly.
> Note that clicking on the task name and changing it from there, works perfectly too.
> Only issue is when modifying the task name from the Proprieties on the bottom area of the IDE.
> This is my first bug report, so please have mercy. I tried to be as technical as I could.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-15205.
--------------------------------------
Resolution: Done
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
> Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png
>
>
> The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project).
> The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly.
> Also, its icon (marker.png) is too large for a context menu action.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15261:
------------------------------------------
pushed PR for 4.2.0.Alpha1 to master.
> Cannot create wordpress example
> -------------------------------
>
> Key: JBIDE-15261
> URL: https://issues.jboss.org/browse/JBIDE-15261
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: nan wei
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: create-wordpress-example.png, initial-build-failed.png
>
>
> Version:
> JBoss Deverloper Studio 7 Beta
> OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65
> OpenShift Enterprise 1.2/2013-07-18.4
> How reproducible:
> always
> Steps to Reproduce:
> 1. Create an app in the JBoss Deverloper Studio.
> Name: mysqltest
> Type: PHP 5.3(php-5.3)
> Embeddable Cartridges: MySQL Database 5.1(mysql-5.1)
> 2. Click Advanced
> Add Source Code:https://github.com/openshift/wordpress-example
> !create-wordpress-example.png!
> Actual results:
> When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error:
> !initial-build-failed.png!
> {code}
> Could not create application "a3"
> Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output:
> httpd (no pid file) not running
> Could not find mysql database. Please run:
> rhc cartridge add -a a3 -c mysql-5.1
> then make a sample commit (add whitespace somewhere) and re-push
> An error occurred executing 'gear postreceive'
> For more details about the problem, try running the command again with the '--trace' option.
> {code}
> But if use rhc client, there is no such problem, it is created successfully.
> # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example
--
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
12 years, 7 months