[JBoss JIRA] (JBTIS-382) BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-382?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-382.
-----------------------------------
Verified with JBDS-IS 8.0.0.CR2
> BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site
> ----------------------------------------------------
>
> Key: JBTIS-382
> URL: https://issues.jboss.org/browse/JBTIS-382
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.CR1
> Environment: 8.0.2.GA + JBDS-IS 8.0.0.CR1 (no early access)
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 4.2.0.CR2, 8.0.0.CR2, 4.2.1.CR1-TP
>
> Attachments: tp1.png, tp2.png
>
>
> BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site where should not be.
> By default this feature is not visible when you install integration stack from the update site. But when you uncheck "Group item by category" the feature is available and can be installed. Moreover, the old version of BPMN2 modeler is installed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden would not be more user friendly just disable it and add some label why it's disabled? The same way as selecting of GTK for BrowserSim/CordovaSim works?
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19241) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19241?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-19241.
---------------------------------
Resolution: Done
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
> ---------------------------------------------------------
>
> Key: JBIDE-19241
> URL: https://issues.jboss.org/browse/JBIDE-19241
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Arquillian]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19162:
---------------------------------------
Tried to reproduce the error I was seeing. Reran with and without tests. With tests failed which was a result of test failures and not the error i was seeing. Running without tests built successfully. I dont know what changed but I'll consider it resolved.
> add new plugins to openshift pom and create feature
> ---------------------------------------------------
>
> Key: JBIDE-19162
> URL: https://issues.jboss.org/browse/JBIDE-19162
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19232) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19232?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-19232.
-------------------------------
Assignee: Rob Stryker
Resolution: Done
branched
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-19232
> URL: https://issues.jboss.org/browse/JBIDE-19232
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-355:
----------------------------------
JDV is currently going GA. My current plan is to wait until B*MS and FSW goes GA and then enable all JBDSIS tooling in Eclipse Marketplace at the same time.
Does that sound okay to you? (esp [~maxandersen] [~nickboldt] )
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-18177:
-------------------------------------
Yet another one:
# Set HTML5 support
# Open .xhtml page and say "Stay with HTML5"
# Restart Eclipse
ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy, requirements
> Fix For: 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, engine_dialog.png, preferences.png, prefs_confirm_restart.png, restart.jpg, vpe.png
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19237) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19237?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-19237:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-19237
> URL: https://issues.jboss.org/browse/JBIDE-19237
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Birt]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19237) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19237?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-19237.
-----------------------------------
Resolution: Rejected
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-19237
> URL: https://issues.jboss.org/browse/JBIDE-19237
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Birt]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha1x
> git push origin jbosstools-4.3.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months