[JBoss JIRA] (JBIDE-14434) insert new jquery mobile page - add back button
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-14434:
-----------------------------------
Summary: insert new jquery mobile page - add back button
Key: JBIDE-14434
URL: https://issues.jboss.org/browse/JBIDE-14434
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
When using the Page jquery Mobile palette option, it would be great if the "property sheet" could ask if the user wishes to have a back button automatically. This is useful for pages 2+ in a multi-page application.
--
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, 11 months
[JBoss JIRA] (JBIDE-14003) Automatically discover library sources for non-maven projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14003:
-------------------------------------
{quote}Windows>Preferences>JBoss Tools>Source Lookup>Automatically configure the Java Source Attachment
{quote}
My bad, I was looking at the wrong Eclipse instance Prefs page :-)
What Max proposed also contained "Warning: this will add a machine specific path to your classpath settings."
As for the m2e container, ideally I'd have the m2e source lookup mechanism have precedence over yours, but since it's not doable apparently and I can't see a compelling reason now to prevent the SL plugin from fixing m2e's missing links, I can live with that.
I'll do a more detailed code review tomorrow, but feature-wise, and provided you fix the warning, that looks ok to me overall.
> Automatically discover library sources for non-maven projects
> -------------------------------------------------------------
>
> Key: JBIDE-14003
> URL: https://issues.jboss.org/browse/JBIDE-14003
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta1
>
> Attachments: test13848a.zip
>
>
> As a follow up of JBIDE-13848, enable automatic discovery of library sources for non-maven projects.
> * This feature should be turned on/off in the preferences
> * If the source file referenced in .classpath doesn't exist, it should attempt to discover a new, valid one.
--
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, 11 months
[JBoss JIRA] (JBIDE-14432) data-icon="bars"
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-14432:
-----------------------------------
Summary: data-icon="bars"
Key: JBIDE-14432
URL: https://issues.jboss.org/browse/JBIDE-14432
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Reporter: Burr Sutter
Attachments: jquery_mobile_bars.png
The jQuery Mobile Palette should have a data-icon="bars" option for a button.
--
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, 11 months
[JBoss JIRA] (JBIDE-14421) Conficting Birt for Kepler M7 and JEE bundle
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14421?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-14421:
----------------------------------------
Seems like the issue is the org.eclipse.birt.chart.integration.wtp feature which depends on older stuff from WTP. Here is the error I see while validation TP with some installable units removed:
{quote}
[INFO] --- target-platform-validation-plugin:0.17.0:validate-target-platform (default) @ jbosstools-multiple ---
[INFO] Validating /home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/jbosstools-multiple.target...
[INFO] {osgi.ws=gtk, osgi.os=linux, osgi.arch=x86_64, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612
[ERROR] Software being installed: org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357
[ERROR] Software being installed: org.eclipse.wst.server_ui.feature.feature.group 3.3.203.v20130413_1400-7B7AFO9AtNdu_xdGY1JfPeC8EAB
[ERROR] Missing requirement: org.eclipse.wst.ws_ui.feature.feature.group 3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL requires 'org.eclipse.wst.xml_ui.feature.feature.group [3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKpRz-T4SU]' but it could not be found
[ERROR] Only one of the following can be installed at once: [org.eclipse.wst.internet.monitor.ui 1.0.606.v20120306_1603, org.eclipse.wst.internet.monitor.ui 1.0.608.v20130501_1206]
[ERROR] Only one of the following can be installed at once: [org.eclipse.wst.sse.ui 1.3.200.v201303281757, org.eclipse.wst.sse.ui 1.3.200.v201302262134]
[ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612 depends on: org.eclipse.jst.web_ui.feature.feature.group 3.1.0
[ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgi_3_iP75rjOs9WPy-5VkAg depends on: org.eclipse.wst.ws_ui.feature.feature.group [3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2B4kKz-2RpqYy5Sl_RjU]
[ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgjb-_fhALqUqcxTpwxR8dsR depends on: org.eclipse.wst.ws_ui.feature.feature.group [3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL]
[ERROR] Cannot satisfy dependency: org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357 depends on: org.eclipse.wst.web_ui.feature.feature.group 3.2.0
[ERROR] Cannot satisfy dependency: org.eclipse.wst.server_ui.feature.feature.group 3.3.203.v20130413_1400-7B7AFM_AtNduZxaId1JfOVC87BG depends on: org.eclipse.wst.internet.monitor.ui [1.0.606.v20120306_1603]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.server_ui.feature.feature.group 3.3.203.v20130413_1400-7B7AFO9AtNdu_xdGY1JfPeC8EAB depends on: org.eclipse.wst.internet.monitor.ui [1.0.608.v20130501_1206]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.web_ui.feature.feature.group 3.5.0.v201209252144-7O7QG-6EMkBQ38QbjcZ0w2Iyj1kPm5hMQiOwS5ip depends on: org.eclipse.wst.server_ui.feature.feature.group [3.3.203.v20130413_1400-7B7AFM_AtNduZxaId1JfOVC87BG]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.web_ui.feature.feature.group 3.5.0.v201209252144-7O7QG-6EMkBQ3A-bjcZ0x5QBPrhj48Zz-Bojv422 depends on: org.eclipse.wst.xml_ui.feature.feature.group [3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKrQxT5SU]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.ws_ui.feature.feature.group 3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2B4kKz-2RpqYy5Sl_RjU depends on: org.eclipse.wst.xml_ui.feature.feature.group [3.5.0.v201301022000-7H7IFisDxumVsz0U7pjYVjTsxJcZQiTZKpRz-T4S]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.xml_ui.feature.feature.group 3.5.0.v201301022000-7H7IFisDxumVsz0U7pjYVjTsxJcZQiTZKpRz-T4S depends on: org.eclipse.wst.sse.ui [1.3.200.v201302262134]
[ERROR] Cannot satisfy dependency: org.eclipse.wst.xml_ui.feature.feature.group 3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKrQxT5SU depends on: org.eclipse.wst.sse.ui [1.3.200.v201303281757]
{quote}
> Conficting Birt for Kepler M7 and JEE bundle
> --------------------------------------------
>
> Key: JBIDE-14421
> URL: https://issues.jboss.org/browse/JBIDE-14421
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta1
>
>
> Dependency resolution in target platform fails because of a conflict between Birt and JST:
> {quote}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612
> [ERROR] Software being installed: org.eclipse.jst.jee 1.0.600.v201305070100
> [ERROR] Missing requirement: org.eclipse.wst.ws_ui.feature.feature.group 3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL requires 'org.eclipse.wst.xml_ui.feature.feature.group [3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKpRz-T4SU]' but it could not be found
> [ERROR] Only one of the following can be installed at once: [org.eclipse.jst.jee 1.0.600.v201305070100, org.eclipse.jst.jee 1.0.600.v201303142300]
> [ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612 depends on: org.eclipse.jst.web_ui.feature.feature.group 3.1.0
> [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_core.feature.feature.group 3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877 depends on: org.eclipse.jst.jee [1.0.600.v201303142300]
> [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgi_3_iP75rjOs9WPy-5VkAg depends on: org.eclipse.jst.web_core.feature.feature.group [3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877]
> [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgjb-_fhALqUqcxTpwxR8dsR depends on: org.eclipse.wst.ws_ui.feature.feature.group [3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL]
> {quote}
> To highlight the specificity of this issue:
> {quote}
> [ERROR] Software being installed: org.eclipse.jst.jee 1.0.600.v201305070100
> ...
> [ERROR] Only one of the following can be installed at once: [org.eclipse.jst.jee 1.0.600.v201305070100, org.eclipse.jst.jee 1.0.600.v201303142300]
> ...
> [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_core.feature.feature.group 3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877 depends on: org.eclipse.jst.jee [1.0.600.v201303142300]
> {quote}
--
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, 11 months
[JBoss JIRA] (JBIDE-14003) Automatically discover library sources for non-maven projects
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14003:
---------------------------------------
{quote}
'jarname' should show the original jar name
{quote}
Fixed.
{quote}
I think the message should somehow emphasize a non-portable path will be used to store the source attachment link.
{quote}
Max has proposed that message.
{quote}
there are no workspace prefs that'd allow a user to turn that feature on/off
{quote}
Windows>Preferences>JBoss Tools>Source Lookup>Automatically configure the Java Source Attachment
"Prompt" is the default.
{quote}
I haven't tried / checked if the code works on classpath containers. If it does, then the Maven container should be ignored to prevent collisions (use hard coded links when m2e can do better)
{quote}
The code works for classpath containers.
Re the Maven container, m2e also uses hardcoded paths. However, source attachments for the Maven container aren't saved in the workspace (.classpath), but in the m2e.jdt plugin instance area. The Source Lookup plugin works the same way.
The Source Lookup plugin will additionally check whether a source attachment file exists and, if it doesn't exist, will try to download it again. M2e ignores invalid source attachments. If m2e has added a valid source attachment, the Source Lookup plugin won't do anything.
> Automatically discover library sources for non-maven projects
> -------------------------------------------------------------
>
> Key: JBIDE-14003
> URL: https://issues.jboss.org/browse/JBIDE-14003
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta1
>
> Attachments: test13848a.zip
>
>
> As a follow up of JBIDE-13848, enable automatic discovery of library sources for non-maven projects.
> * This feature should be turned on/off in the preferences
> * If the source file referenced in .classpath doesn't exist, it should attempt to discover a new, valid one.
--
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, 11 months
[JBoss JIRA] (JBIDE-14426) Add arquillian support dialog is too bare-bones
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14426?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-14426:
-------------------------------------
Assignee: Snjezana Peco
> Add arquillian support dialog is too bare-bones
> -----------------------------------------------
>
> Key: JBIDE-14426
> URL: https://issues.jboss.org/browse/JBIDE-14426
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta1
>
>
> Using Configure Arquillian Support just asks if I want to add Arquillian support + link to global arquillian settings.
> Following thing should be done IMO,
> A) When saying yes, it should preview what changes are going to happen (changing pom.xml by default)
> B) I should be able to say no, don't change pom, and just have arquillian nature added (i.e. assume the classpath contain what is needed, warn if possible problems) - optimally not require Maven to be on the project.
> C) On the "next" page let user configure the settings he wish applied (now I have to go to global preferences first and change those which might not be what one wants)
--
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, 11 months