[JBoss JIRA] (JBIDE-16234) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16234?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-16234.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
pushed new branch jbosstools-4.2.0.Alpha1x to upstream
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
> --------------------------------------------------------
>
> Key: JBIDE-16234
> URL: https://issues.jboss.org/browse/JBIDE-16234
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (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.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.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 OpenShift 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-16234) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16234?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-16234.
------------------------------------
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
> --------------------------------------------------------
>
> Key: JBIDE-16234
> URL: https://issues.jboss.org/browse/JBIDE-16234
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (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.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.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 OpenShift 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-16234) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16234?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16234:
------------------------------------------
bump to 2.6.0. was done 3 months ago in JBIDE-15462
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
> --------------------------------------------------------
>
> Key: JBIDE-16234
> URL: https://issues.jboss.org/browse/JBIDE-16234
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (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.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.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 OpenShift 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-16234) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16234?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16234:
------------------------------------------
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT -Dtycho.localArtifacts=ignore
{code}
{code}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openshift.all ..................................... SUCCESS [0.625s]
[INFO] openshift.plugins ................................. SUCCESS [0.009s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.676s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.626s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.078s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.311s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [3.913s]
[INFO] openshift.tests ................................... SUCCESS [0.010s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [20.403s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [14.336s]
[INFO] openshift.features ................................ SUCCESS [0.009s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.196s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.177s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.103s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.158s]
[INFO] openshift.site .................................... SUCCESS [7.139s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{code}
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
> --------------------------------------------------------
>
> Key: JBIDE-16234
> URL: https://issues.jboss.org/browse/JBIDE-16234
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (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.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.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 OpenShift 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-16246) Conversion wizard : Better handle multiple dependencies
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16246?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16246:
--------------------------------
Labels: maven_conversion new_and_noteworthy (was: conver new_and_noteworthy)
> Conversion wizard : Better handle multiple dependencies
> -------------------------------------------------------
>
> Key: JBIDE-16246
> URL: https://issues.jboss.org/browse/JBIDE-16246
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: maven_conversion, new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependency.
> A better approach would be to select several dependencies at once and edit the scope in one action
> Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
--
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-16246) Conversion wizard : Better handle multiple dependencies
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16246?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16246:
--------------------------------
Description:
When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependency.
A better approach would be to select several dependencies at once and edit the scope in one action
Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
was:
When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependencies.
A better approach would be to select several dependencies at once and edit the scope in one action
Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
> Conversion wizard : Better handle multiple dependencies
> -------------------------------------------------------
>
> Key: JBIDE-16246
> URL: https://issues.jboss.org/browse/JBIDE-16246
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependency.
> A better approach would be to select several dependencies at once and edit the scope in one action
> Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
--
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-16246) Conversion wizard : Better handle multiple dependencies
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16246?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16246:
--------------------------------
Labels: conver new_and_noteworthy (was: new_and_noteworthy)
> Conversion wizard : Better handle multiple dependencies
> -------------------------------------------------------
>
> Key: JBIDE-16246
> URL: https://issues.jboss.org/browse/JBIDE-16246
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: conver, new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependency.
> A better approach would be to select several dependencies at once and edit the scope in one action
> Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
--
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-16246) Conversion wizard : Better handle multiple dependencies
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-16246:
-----------------------------------
Summary: Conversion wizard : Better handle multiple dependencies
Key: JBIDE-16246
URL: https://issues.jboss.org/browse/JBIDE-16246
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Affects Versions: 4.1.0.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.2.0.Alpha1
When a project has a large number of dependencies to convert, and if you need to change the scope of several of them for instance, you currently need to select, double click and modify each dependencies.
A better approach would be to select several dependencies at once and edit the scope in one action
Another pain point : checking/unchecking a subset of all the dependencies requires as many clicks as the number of dependencies. Showing a context menu on right click with select/deselect options would help
--
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-15890) Regarding JSON input data is not working in smooks-config.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15890?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-15890.
---------------------------------------
Resolution: Rejected
Please use forum or support portal for how to use features.
This jira is for bug reports and feature requests.
Thank you.
> Regarding JSON input data is not working in smooks-config.xml
> -------------------------------------------------------------
>
> Key: JBIDE-15890
> URL: https://issues.jboss.org/browse/JBIDE-15890
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: smooks
> Reporter: siva maturi
>
> Hi All,
> Can any one tell me how to Add Json file to Input Data Under Selected Task Details , when i am trying to add JSON file this Add button is not working in smooks-confif.xml file .All Input Types are working except this JSON .
> So if any one know Please tell me how to Add JSON file to Smooks Editor .
--
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