[JBoss JIRA] (JBIDE-16199) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16199?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16199.
------------------------------
Resolution: Done
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [Central Discovery]
> -----------------------------------------------------------------------
>
> Key: JBIDE-16199
> URL: https://issues.jboss.org/browse/JBIDE-16199
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. 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 Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 4 months
[JBoss JIRA] (JBIDE-16197) For JBIDE 4.1.1.Final: Prepare for Final/GA release [JBT Update Sites]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16197?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16197.
------------------------------
Resolution: Done
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [JBT Update Sites]
> ----------------------------------------------------------------------
>
> Key: JBIDE-16197
> URL: https://issues.jboss.org/browse/JBIDE-16197
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: updatesite
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [JBT Update Sites]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. 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 JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 4 months
[JBoss JIRA] (JBDS-2846) For JBDS 7.1.0.GA: Prepare for Final/GA release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2846?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2846.
----------------------------
Resolution: Done
> For JBDS 7.1.0.GA: Prepare for Final/GA release
> -----------------------------------------------
>
> Key: JBDS-2846
> URL: https://issues.jboss.org/browse/JBDS-2846
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: installer
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. 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...]
--
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, 4 months
[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16161:
----------------------------------------
I feel it's better to put this in the parent pom to make sure it will get cleaned later. If we put those extra-dependencies in all component, I'm afraid some will always keep them so that in the end, we'll never fully get rid of them.
Putting it in parent pom will allow easier removal of those dependencies across all projects.
> Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
> Priority: Critical
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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, 4 months
[JBoss JIRA] (JBIDE-14758) Help Button is not working for jQuery Palette Element's Wizard
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14758?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-14758 at 12/3/13 1:49 PM:
----------------------------------------------------------------
This can be done just with one line of code like this:
{code}
PlatformUI.getWorkbench().getHelpSystem().setHelp(parent, IJSFHelpContextIds.NEW_JSF_PROJECT);
{code}
in method createPageControls()
All what we need is document topic id.
[~mmurray], do we have topic in our documentation for jQuery Mobile Palette?
was (Author: dazarov):
This can be done just with one line of code like this:
{code}
PlatformUI.getWorkbench().getHelpSystem().setHelp(parent, IJSFHelpContextIds.NEW_JSF_PROJECT);
{code}
in method createPageControls()
All what we need is document topic id.
[~mmurray], do we have such topic in our documentation?
> Help Button is not working for jQuery Palette Element's Wizard
> --------------------------------------------------------------
>
> Key: JBIDE-14758
> URL: https://issues.jboss.org/browse/JBIDE-14758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Nothing happens if Help button in dialog footer is pressed
--
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, 4 months
[JBoss JIRA] (JBIDE-14758) Help Button is not working for jQuery Palette Element's Wizard
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14758?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-14758:
---------------------------------------
This can be done just with one line of code like this:
{code}
PlatformUI.getWorkbench().getHelpSystem().setHelp(parent, IJSFHelpContextIds.NEW_JSF_PROJECT);
{code}
in method createPageControls()
All what we need is document topic id.
[~mmurray], do we have such topic in our documentation?
> Help Button is not working for jQuery Palette Element's Wizard
> --------------------------------------------------------------
>
> Key: JBIDE-14758
> URL: https://issues.jboss.org/browse/JBIDE-14758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Nothing happens if Help button in dialog footer is pressed
--
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, 4 months
[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16161:
---------------------------------------
This missing osgi.event is a must for eclipse workbench to start normally.
Actually I was thinking about adding only osqi.event into parent/pom.xml and whatever is needed compatibility would be added it into local test's pom.xml.
> Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
> Priority: Critical
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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, 4 months
[JBoss JIRA] (JBIDE-16175) Support browser reload after changes in JSP on both AS7+ and EAP6+
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16175?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16175:
---------------------------------------------
Afaik AS7 and EAP7 *disables* by default auto compilation of JSP.
A real annoyance IMO.
> Support browser reload after changes in JSP on both AS7+ and EAP6+
> ------------------------------------------------------------------
>
> Key: JBIDE-16175
> URL: https://issues.jboss.org/browse/JBIDE-16175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> See if there anything that can be done on the tooling side to trigger a browser refresh after a JSP was modified.
> [~nsaad] reported that he needed to modify his EAP configuration by adding a <configuration> tag for JSP development re-deployment to subsystem "default-host” to get it working.
--
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, 4 months
[JBoss JIRA] (JBDS-2848) Anonymous Usage Stats
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2848:
---------------------------------
Summary: Anonymous Usage Stats
Key: JBDS-2848
URL: https://issues.jboss.org/browse/JBDS-2848
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
Areas worth tracking include (in priority order):
- Use of the OpenShift Wizard to successful completion vs error
- Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
- Successful installation of the features found on Software/Update tab of JBoss Central
- Use of the JSF/RichFaces Visual Page Editor
- Use of the Hibernate Tooling
- Use of the jQuery Mobile Palette
- Use of BrowserSim
- Use of CordovaSim
We will also need to update http://www.jboss.org/tools/usage
Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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, 4 months