[JBoss JIRA] (JBIDE-19135) Unify feature labels in Mobile category
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19135?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-19135.
-----------------------------------------
Resolution: Done
closing this for alpha1, cloning JBIDE-19253 for branch since not yet merged.
> Unify feature labels in Mobile category
> ---------------------------------------
>
> Key: JBIDE-19135
> URL: https://issues.jboss.org/browse/JBIDE-19135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Alpha1
>
> Attachments: category.png
>
>
> JBoss Tools FeedHenry integration contains dash in feature label - other features don't. We should unify feature labels across other features in the same category.
> Screenshot attached.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19253) Unify feature labels in Mobile category
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19253:
-------------------------------------------
Summary: Unify feature labels in Mobile category
Key: JBIDE-19253
URL: https://issues.jboss.org/browse/JBIDE-19253
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Reporter: Pavol Srna
Assignee: Gorkem Ercan
Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
JBoss Tools FeedHenry integration contains dash in feature label - other features don't. We should unify feature labels across other features in the same category.
Screenshot attached.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19244) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Freemarker]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19244?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19244:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Freemarker]
> ---------------------------------------------------------
>
> Key: JBIDE-19244
> URL: https://issues.jboss.org/browse/JBIDE-19244
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Freemarker]: 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 Freemarker 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-355:
----------------------------------
Once the update site for JBTIS4.2/JBDSIS 8 is live, adding the marketplace entry is like 10 mins of work, assuming the copy is written and the tags you want are known. So... whatever you want, whenever you want.
> 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] (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:
----------------------------------
I didn't want to stress out the first Luna tooling release since it was minimal (just the DataVirt tools) - the rest as EA. I agree it would be better to get some live testing before Fuse comes along. I'll split the difference and plan on an Eclipse Marketplace presence for JBDSIS 8.0.1 (B*MS). Then we can test all of the JDV and BPM stuff. WDYT?
> 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] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBTIS-355 at 2/12/15 2:32 PM:
--------------------------------------------------------------------
Why do we want to wait with the marketplace entry ? is it not better to get it live and tested/seen live ?
was (Author: maxandersen):
Why do we want with the marketplace entry ? is it not better to get it live and tested/seen live ?
> 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-19237) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19237?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19237:
------------------------------------
Belay last comment, I meant this site:
http://download.jboss.org/jbosstools/updates/stable/luna/core/birt/1.7.0....
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19237?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19237.
------------------------------
Now building JBT 4.3 from http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/1.6...
> 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-19243) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19243?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19243.
------------------------------
Now building JBT 4.3 from http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/1.6...
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
> ------------------------------------------------------
>
> Key: JBIDE-19243
> URL: https://issues.jboss.org/browse/JBIDE-19243
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: portal-gatein
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Portlet]: 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 Portlet 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