[JBoss JIRA] (JBIDE-10650) EGitUtils is too large, needs to be split into smaller parts
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10650?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-10650:
------------------------------------------
postponed to 4.2.x since there's no urgency, only a matter of code maintenance.
> EGitUtils is too large, needs to be split into smaller parts
> ------------------------------------------------------------
>
> Key: JBIDE-10650
> URL: https://issues.jboss.org/browse/JBIDE-10650
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
>
> EGitUtils is a collection of handy utilities to simplify tasks when dealing with EGit/JGit in OpenShift. It holds all its functionality in static methods. The class grew up to > 800 lines in its current incarnation. This is by far too large to be maintained effectively. We need to split it up into smaller parts (into commands? into several util classes?)
--
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-16271) Support jquery mobile 1.4
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-16271:
-------------------------------------------
Summary: Support jquery mobile 1.4
Key: JBIDE-16271
URL: https://issues.jboss.org/browse/JBIDE-16271
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.1.1.Final
Reporter: Max Rydahl Andersen
Fix For: 4.1.2.Final, 4.2.0.Alpha2
jquery mobile 1.4 is coming out and apparently have performance fixes making it better suited for cordova development.
Noets from Vineet:
"I wouldn't say 1.4 is more compatible. It's a case of jQM 1.4 being more suitable
for Cordova apps. jQM 1.4 is more performant and thus Cordova apps are less sluggish.
The release notes allude to this: http://jquerymobile.com/blog/2013/09/24/announcing-jquery-mobile-1-4-beta/
I've got no hard numbers here, but this slides in this talk - http://www.slideshare.net/AlexanderSchmitz/austin-26252266
gives a better overview of what's in 1.4. Slide 22 is most relevant -
jQM 1.4 ships with a better default theme that improves performance,
among various other changes discussed in other slides."
Need to find out what issues jquery mobile palette and others might have with supporting jquery mobile for both 1.3 and 1.4...will be relevant with future new versions too.
--
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-2859) Include information on EAP version in installer
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-2859:
--------------------------------
Description:
I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
!step-6.png!
was:I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> Include information on EAP version in installer
> -----------------------------------------------
>
> Key: JBDS-2859
> URL: https://issues.jboss.org/browse/JBDS-2859
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Attachments: step-6.png
>
>
> I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> !step-6.png!
--
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-2859) Include information on EAP version in installer
by Martin Malina (JIRA)
Martin Malina created JBDS-2859:
-----------------------------------
Summary: Include information on EAP version in installer
Key: JBDS-2859
URL: https://issues.jboss.org/browse/JBDS-2859
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 7.1.0.CR1
Reporter: Martin Malina
I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
--
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-16239) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16239?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-16239:
---------------------------------------
Done:
{code}
$> git checkout -b jbosstools-4.2.0.Alpha1x
Switched to a new branch 'jbosstools-4.2.0.Alpha1x'
$> git push origin jbosstools-4.2.0.Alpha1x
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:jbosstools/jbosstools-webservices.git
* [new branch] jbosstools-4.2.0.Alpha1x -> jbosstools-4.2.0.Alpha1x
{code}
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]
> ----------------------------------------------------------
>
> Key: JBIDE-16239
> URL: https://issues.jboss.org/browse/JBIDE-16239
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Webservices]: 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 Webservices 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-16239) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16239?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-16239.
---------------------------------
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]
> ----------------------------------------------------------
>
> Key: JBIDE-16239
> URL: https://issues.jboss.org/browse/JBIDE-16239
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Webservices]: 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 Webservices 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