[JBoss JIRA] (JBDS-2497) Building JBDS product w/ -Ppack200 results in NPE and build failure
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2497?page=com.atlassian.jira.plugin.... ]
Mickael Istria resolved JBDS-2497.
----------------------------------
Resolution: Done
JBDS repo contains .pack.gz artifacts as well as .jar artifacts.
> Building JBDS product w/ -Ppack200 results in NPE and build failure
> -------------------------------------------------------------------
>
> Key: JBDS-2497
> URL: https://issues.jboss.org/browse/JBDS-2497
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 7.0.0.Alpha2
>
> Attachments: log.txt, log2.zip
>
>
> Building JBDS product w/ -Ppack200 results in NPE and build failure:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate,pack200 -X | tee log.txt
> {code}
> whereas:
> {code}
> cd ~/trunk/product
> mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
> {code}
> works fine.
--
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
13 years
[JBoss JIRA] (JBIDE-13778) Descriptions for jQuery Widget Palette elements
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13778?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13778:
----------------------------------
Description:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
2. Page
*Page:*
<div data-role="page">
...
</div>
3. Dialog
*Dialog:*
<div data-role="dialog">
...
</div>
4. Popup
*Popup:*
<a href="#popupBasic" data-rel="popup">...</a>
<div data-role="popup" id="popupBasic">
...
</div>
5. Grid
*Grid:*
<div class="ui-grid-b">
...
</div>
6. Field Container
*Field Container:*
<div data-role="fieldcontain">
...
</div>
7. Panel
*Panel:*
<div data-role="panel">
...
</div>
8. Table
*Table:*
<table data-role="table"></code><br>
...
</table>
9. Collapsible
*Collapsible:*
<div data-role="collapsible">
...
</div>
10. Collapsible Set
*Collapsible Set:*
<div data-role="collapsible-set">
...
</div>
11. Header Bar
*Header Bar:*
<div data-role="header">
...
</div>
12. Footer Bar
*Footer Bar:*
<div data-role="footer">
...
</div>
13. Navbar
*Navbar:*
<div data-role="navbar">
...
</div>
14. Select
*Select menu:*
<label for="select-choice-0" class="select">...</label>
<select name="select-choice-0">
...
</select>
15. Listview
*Listview:*
<ul data-role="listview">
...
</ul>
16. Button
*Button:*
<a href="..." data-role="button">...</a>
17. Buttons
*Grouped buttons:*
<div data-role="controlgroup">
...
</div>
18. Link
*Link:*
<a href="...">...</a>
19. Toggle
*Flip toggle switch:*
<div data-role="fieldcontain">
<label for="flip-1">...</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
20. Radio
*Radio button:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="radio-choice-1" id="radio-choice-1a" value="A" type="radio"/>
<label for="radio-choice-1a">...</label>
</fieldset>
21. Checkbox
*Checkbox:*
<label>
<input type="checkbox" name="checkbox-1"/>
...
</label>
22. Checkboxes
*Grouped checkboxes:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="checkbox-1a" id="checkbox-1a" type="checkbox"/>
<label for="checkbox-1a">...</label>
</fieldset>
23. Slider
*Slider/Range slider:*
<label for="range-1">...</label>
<input name="range-1" data-highlight="true" type="range"/>
24. Text Input
*Text Input:*
<div data-role="fieldcontain">
<label for="text-1">...</label>
<input name="text-1" id="text-1" type="text"/>
</div>
Test case:
EXECUTE:
1. Create Java Project "test"
2. Create folder "test" in test project
3. Create file "test.html" in test folder
{code}
<!DOCTYPE html>
<html>
</html>
{code}
4. Open file test.html in Visual Page Editor
ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side
5. Point mouse to palette element then hold
ASSERT: Palette element description is shown in tooltip popup window
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
2. Page
*Page:*
<div data-role="page">
...
</div>
3. Dialog
*Dialog:*
<div data-role="dialog">
...
</div>
4. Popup
*Popup:*
<a href="#popupBasic" data-rel="popup">...</a>
<div data-role="popup" id="popupBasic">
...
</div>
5. Grid
*Grid:*
<div class="ui-grid-b">
...
</div>
6. Field Container
*Field Container:*
<div data-role="fieldcontain">
...
</div>
7. Panel
*Panel:*
<div data-role="panel">
...
</div>
8. Table
*Table:*
<table data-role="table"></code><br>
...
</table>
9. Collapsible
*Collapsible:*
<div data-role="collapsible">
...
</div>
10. Collapsible Set
*Collapsible Set:*
<div data-role="collapsible-set">
...
</div>
11. Header Bar
*Header Bar:*
<div data-role="header">
...
</div>
12. Footer Bar
*Footer Bar:*
<div data-role="footer">
...
</div>
13. Navbar
*Navbar:*
<div data-role="navbar">
...
</div>
14. Select
*Select menu:*
<label for="select-choice-0" class="select">...</label>
<select name="select-choice-0">
...
</select>
15. Listview
*Listview:*
<ul data-role="listview">
...
</ul>
16. Button
*Button:*
<a href="..." data-role="button">...</a>
17. Buttons
*Grouped buttons:*
<div data-role="controlgroup">
...
</div>
18. Link
*Link:*
<a href="...">...</a>
19. Toggle
*Flip toggle switch:*
<div data-role="fieldcontain">
<label for="flip-1">...</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
20. Radio
*Radio button:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="radio-choice-1" id="radio-choice-1a" value="A" type="radio"/>
<label for="radio-choice-1a">...</label>
</fieldset>
21. Checkbox
*Checkbox:*
<label>
<input type="checkbox" name="checkbox-1"/>
...
</label>
22. Checkboxes
*Grouped checkboxes:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="checkbox-1a" id="checkbox-1a" type="checkbox"/>
<label for="checkbox-1a">...</label>
</fieldset>
23. Slider
*Slider/Range slider:*
<label for="range-1">...</label>
<input name="range-1" data-highlight="true" type="range"/>
24. Text Input
*Text Input:*
<div data-role="fieldcontain">
<label for="text-1">...</label>
<input name="text-1" id="text-1" type="text"/>
</div>
> Descriptions for jQuery Widget Palette elements
> -----------------------------------------------
>
> Key: JBIDE-13778
> URL: https://issues.jboss.org/browse/JBIDE-13778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
>
> We need to have palette elements descriptions and we need to show them in tooltips.
> 1. JS/CSS
> Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
> 2. Page
> *Page:*
> <div data-role="page">
> ...
> </div>
> 3. Dialog
> *Dialog:*
> <div data-role="dialog">
> ...
> </div>
> 4. Popup
> *Popup:*
> <a href="#popupBasic" data-rel="popup">...</a>
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> 5. Grid
> *Grid:*
> <div class="ui-grid-b">
> ...
> </div>
> 6. Field Container
> *Field Container:*
> <div data-role="fieldcontain">
> ...
> </div>
> 7. Panel
> *Panel:*
> <div data-role="panel">
> ...
> </div>
> 8. Table
> *Table:*
> <table data-role="table"></code><br>
> ...
> </table>
> 9. Collapsible
> *Collapsible:*
> <div data-role="collapsible">
> ...
> </div>
> 10. Collapsible Set
> *Collapsible Set:*
> <div data-role="collapsible-set">
> ...
> </div>
> 11. Header Bar
> *Header Bar:*
> <div data-role="header">
> ...
> </div>
> 12. Footer Bar
> *Footer Bar:*
> <div data-role="footer">
> ...
> </div>
> 13. Navbar
> *Navbar:*
> <div data-role="navbar">
> ...
> </div>
> 14. Select
> *Select menu:*
> <label for="select-choice-0" class="select">...</label>
> <select name="select-choice-0">
> ...
> </select>
> 15. Listview
> *Listview:*
> <ul data-role="listview">
> ...
> </ul>
> 16. Button
> *Button:*
> <a href="..." data-role="button">...</a>
> 17. Buttons
> *Grouped buttons:*
> <div data-role="controlgroup">
> ...
> </div>
> 18. Link
> *Link:*
> <a href="...">...</a>
> 19. Toggle
> *Flip toggle switch:*
> <div data-role="fieldcontain">
> <label for="flip-1">...</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> 20. Radio
> *Radio button:*
> <fieldset data-role="controlgroup">
> <legend></legend>
> <input name="radio-choice-1" id="radio-choice-1a" value="A" type="radio"/>
> <label for="radio-choice-1a">...</label>
> </fieldset>
> 21. Checkbox
> *Checkbox:*
> <label>
> <input type="checkbox" name="checkbox-1"/>
> ...
> </label>
> 22. Checkboxes
> *Grouped checkboxes:*
> <fieldset data-role="controlgroup">
> <legend></legend>
> <input name="checkbox-1a" id="checkbox-1a" type="checkbox"/>
> <label for="checkbox-1a">...</label>
> </fieldset>
> 23. Slider
> *Slider/Range slider:*
> <label for="range-1">...</label>
> <input name="range-1" data-highlight="true" type="range"/>
> 24. Text Input
> *Text Input:*
> <div data-role="fieldcontain">
> <label for="text-1">...</label>
> <input name="text-1" id="text-1" type="text"/>
> </div>
> Test case:
> EXECUTE:
> 1. Create Java Project "test"
> 2. Create folder "test" in test project
> 3. Create file "test.html" in test folder
> {code}
> <!DOCTYPE html>
> <html>
> </html>
> {code}
> 4. Open file test.html in Visual Page Editor
> ASSERT: Visual Page Editor appears with test.html and jQuery Mobile Widget Palette on the right side
> 5. Point mouse to palette element then hold
> ASSERT: Palette element description is shown in tooltip popup window
--
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
13 years
[JBoss JIRA] (JBIDE-11558) Repositories are missing source feature titles
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11558?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-11558:
-----------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.x)
This should be fixed now (since we moved to Tycho 0.17)
> Repositories are missing source feature titles
> ----------------------------------------------
>
> Key: JBIDE-11558
> URL: https://issues.jboss.org/browse/JBIDE-11558
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite, UpStream
> Affects Versions: 3.3.0.Beta3
> Environment: jbt33beta3-trunk,L64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha2
>
> Attachments: empty-list.png, JBIDE-11558_empty_names.png, missing-names.png, missing-titles.png
>
>
> While updating JBT 3.3. trunk there are missing titles in dialog (see screenshot)
--
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
13 years
[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13843:
------------------------------------
Assign to Len so it's on his radar as something that QE needs to worry about. Kepler M6 target platform will include this (but we can revert to 2.0.5 if necessary).
> SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13843
> URL: https://issues.jboss.org/browse/JBIDE-13843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.0.Alpha2
>
>
> Eclipse 4.3M5a contains:
> {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code}
> But in Eclipse 4.3M6, the only JUnit available is:
> {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code}
> So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4.
--
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
13 years
[JBoss JIRA] (JBDS-2455) automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2455?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2455:
-----------------------------
Fix Version/s: 6.0.1.GA
7.0.0.Alpha2
> automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2455
> URL: https://issues.jboss.org/browse/JBDS-2455
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA, 7.0.0.Alpha2
>
>
> Install-grinder tests [1] attempt to install from JBDS Central, via this URL [2]
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
> [2] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... -> plugins/com.jboss.jbds.central.discovery_6.0.1.GA-v20130130-1759-B206.jar
> When you look in the discovery jar [3], you see that the URLs referenced within the plugin.xml are on devstudio.jboss.com [4], rather than www.qa.jboss.com [5].
> [3] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> [4] https://devstudio.jboss.com/updates/6.0/central/core/
> [5] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> So, we need to implement Central somehow so that the plugin.xml (with a plugin.properties) can have those URLs overridden by a commandline flag.
> This is somewhat already done for the SOA Tooling discovery plugin, using %jboss.soa.update.url:
> https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-so...
> However, IIRC it's only implemented at BUILD time, not RUN time, which means we would have to manually adjust the plugin within the Jenkins job workspace (with unzip, sed, zip) to make the change stick at RUN time, or wed have to rebuild it as part of the test run.
> Is there a better way?
--
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
13 years
[JBoss JIRA] (JBDS-2455) automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2455?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2455.
----------------------------
Release Notes Docs Status: Not Required
Resolution: Done
> automated install-grinder install tests for JBDS will always fail because Jenkins can't see https://devstudio.jboss.com
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2455
> URL: https://issues.jboss.org/browse/JBDS-2455
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 6.0.1.GA, 7.0.0.Alpha2
>
>
> Install-grinder tests [1] attempt to install from JBDS Central, via this URL [2]
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
> [2] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... -> plugins/com.jboss.jbds.central.discovery_6.0.1.GA-v20130130-1759-B206.jar
> When you look in the discovery jar [3], you see that the URLs referenced within the plugin.xml are on devstudio.jboss.com [4], rather than www.qa.jboss.com [5].
> [3] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> [4] https://devstudio.jboss.com/updates/6.0/central/core/
> [5] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable...
> So, we need to implement Central somehow so that the plugin.xml (with a plugin.properties) can have those URLs overridden by a commandline flag.
> This is somewhat already done for the SOA Tooling discovery plugin, using %jboss.soa.update.url:
> https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-so...
> However, IIRC it's only implemented at BUILD time, not RUN time, which means we would have to manually adjust the plugin within the Jenkins job workspace (with unzip, sed, zip) to make the change stick at RUN time, or wed have to rebuild it as part of the test run.
> Is there a better way?
--
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
13 years