[JBoss JIRA] (JBIDE-15246) JQuery Checkboxes have broken CSS layout on desktop browsers
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15246?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15246:
--------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> JQuery Checkboxes have broken CSS layout on desktop browsers
> ------------------------------------------------------------
>
> Key: JBIDE-15246
> URL: https://issues.jboss.org/browse/JBIDE-15246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.1.0.CR1
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.x
>
> Attachments: browserSim.png, chrome.png, firefox.png, int.png, jquery-mobile-checkboxes-desktop.png
>
>
> JQuery Mobile palette does render properly on desktop browser (internal browser, chrome).
> How to reproduce:
> 1/ Create mobile example from JBoss Central
> 2/ Add "Checkboxes" from JQuery Mobile palette
> 3/ Deploy and open on desktop
--
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-15246) JQuery Checkboxes have broken CSS layout on desktop browsers
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15246?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15246:
-------------------------------------
Damn it, I moved the wrong clone :-/
I'll keep it that way (aerogear team can use the orginal comments in AEROGEAR-1370 after all).
If it bothers someone, I'll switch issues from one project to another.
> JQuery Checkboxes have broken CSS layout on desktop browsers
> ------------------------------------------------------------
>
> Key: JBIDE-15246
> URL: https://issues.jboss.org/browse/JBIDE-15246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.1.0.CR1
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha1
>
> Attachments: browserSim.png, chrome.png, firefox.png, int.png, jquery-mobile-checkboxes-desktop.png
>
>
> JQuery Mobile palette does render properly on desktop browser (internal browser, chrome).
> How to reproduce:
> 1/ Create mobile example from JBoss Central
> 2/ Add "Checkboxes" from JQuery Mobile palette
> 3/ Deploy and open on desktop
--
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-15201) JQuery Mobile "Checkboxes" does not render properly on desktop browsers
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15201?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15201:
--------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> JQuery Mobile "Checkboxes" does not render properly on desktop browsers
> -----------------------------------------------------------------------
>
> Key: JBIDE-15201
> URL: https://issues.jboss.org/browse/JBIDE-15201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.1.0.CR1
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha2
>
> Attachments: browserSim.png, chrome.png, firefox.png, int.png, jquery-mobile-checkboxes-desktop.png
>
>
> JQuery Mobile palette does render properly on desktop browser (internal browser, chrome).
> How to reproduce:
> 1/ Create mobile example from JBoss Central
> 2/ Add "Checkboxes" from JQuery Mobile palette
> 3/ Deploy and open on desktop
--
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-16233) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16233?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-16233.
----------------------------------
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]
> ---------------------------------------------------
>
> Key: JBIDE-16233
> URL: https://issues.jboss.org/browse/JBIDE-16233
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Base]: 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 Base 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-16228) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16228?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-16228.
------------------------------------
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
> --------------------------------------------------
>
> Key: JBIDE-16228
> URL: https://issues.jboss.org/browse/JBIDE-16228
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [JST]: 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 JST 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-16228) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16228?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-16228.
----------------------------------
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
> --------------------------------------------------
>
> Key: JBIDE-16228
> URL: https://issues.jboss.org/browse/JBIDE-16228
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [JST]: 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 JST 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-16233) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16233?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-16233.
------------------------------------
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]
> ---------------------------------------------------
>
> Key: JBIDE-16233
> URL: https://issues.jboss.org/browse/JBIDE-16233
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Base]: 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 Base 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-16173) org.jboss.tools.stacks.core.test.StacksCoreTest failure on Luna
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16173?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16173:
--------------------------------------
Assignee: Denis Golovin (was: Rob Stryker)
> org.jboss.tools.stacks.core.test.StacksCoreTest failure on Luna
> ---------------------------------------------------------------
>
> Key: JBIDE-16173
> URL: https://issues.jboss.org/browse/JBIDE-16173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.stacks.core.test.StacksAllTests
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.353 sec <<< FAILURE!
> testManagerUseDefaultStacks(org.jboss.tools.stacks.core.test.StacksCoreTest) Time elapsed: 0.308 sec <<< FAILURE!
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks(StacksCoreTest.java:48)
> {code}
--
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-16173) org.jboss.tools.stacks.core.test.StacksCoreTest failure on Luna
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16173?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16173:
-----------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.2.0.Alpha1)
> org.jboss.tools.stacks.core.test.StacksCoreTest failure on Luna
> ---------------------------------------------------------------
>
> Key: JBIDE-16173
> URL: https://issues.jboss.org/browse/JBIDE-16173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Fix For: 4.2.0.Alpha2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.stacks.core.test.StacksAllTests
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 0.353 sec <<< FAILURE!
> testManagerUseDefaultStacks(org.jboss.tools.stacks.core.test.StacksCoreTest) Time elapsed: 0.308 sec <<< FAILURE!
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.stacks.core.test.StacksCoreTest.testManagerUseDefaultStacks(StacksCoreTest.java:48)
> {code}
--
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