[JBoss JIRA] (JBIDE-22416) Plugins dependency conflict when importing JavaEE7 Sample
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22416?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22416:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Plugins dependency conflict when importing JavaEE7 Sample
> ---------------------------------------------------------
>
> Key: JBIDE-22416
> URL: https://issues.jboss.org/browse/JBIDE-22416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160520-0424-B5396
> Build date: 20160520-0424
> Reporter: Josef Kopriva
> Assignee: Fred Bricon
> Fix For: 4.5.x
>
> Attachments: import_issue.png
>
>
> When I import JavaEE7 sample sample extra/spock-tests, I cannot install plugin due to plugin conflict issue.
> {code:java}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> Software currently installed: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> Software currently installed: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> Only one of the following can be installed at once:
> Java Development Tools Core 3.12.0.v20160426-1326 (org.eclipse.jdt.core 3.12.0.v20160426-1326)
> Java Development Tools Core 3.11.0.xx-201604081629-e45 (org.eclipse.jdt.core 3.11.0.xx-201604081629-e45)
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Core Features) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.feature.feature.group 10.0.0.Alpha1-v20160520-0424-B5396)
> To: org.eclipse.jdt.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> To: com.jboss.devstudio.core.feature.feature.group [10.0.0.Alpha1-v20160520-0424-B5396]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.compilerless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Headless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.headless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.jdt.patch.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Java Development Tools JUnit support 3.9.0.v20160421-1701 (org.eclipse.jdt.junit 3.9.0.v20160421-1701)
> To: bundle org.eclipse.jdt.core [3.12.0,4.0.0)
> Cannot satisfy dependency:
> From: TestNG Eclipse Support 6.9.11.201604020423 (org.testng.eclipse 6.9.11.201604020423)
> To: bundle org.eclipse.jdt.junit 0.0.0
> Cannot satisfy dependency:
> From: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> To: org.testng.eclipse [6.9.11.201604020423]
> Cannot satisfy dependency:
> From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.9.2.xx-201604081629-e45 Eclipse Java Development Tools 3.12.0.v20160428-0800 (org.eclipse.jdt.feature.group 3.12.0.v20160428-0800)
> To: org.eclipse.jdt.core [3.11.0.xx-201604081629-e45]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-15246) JQuery Checkboxes have broken CSS layout on desktop browsers
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15246?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-15246:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> 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: Jeff MAURY
> Fix For: 4.5.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 was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22138:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21674:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, upstream
> Reporter: Xavier Coulon
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23602:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Server adapter: Hot code replace failed dialog has poor usability
> -----------------------------------------------------------------
>
> Key: JBIDE-23602
> URL: https://issues.jboss.org/browse/JBIDE-23602
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
> Attachments: hot-code-replace-failed-2.png
>
>
> steps to reproduce:
> # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it
> # EXEC: open HelloService and change it to the following:
> {code:title=HelloService}
> public class HelloService {
> private static final String MAGIC_STRING = "42";
>
> String createHelloMessage(String name) {
> return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!";
> }
> }
> {code}
> and save the editor
> Result:
> "Hot code replace failed" dialog pops up, which is expected.
> !hot-code-replace-failed-2.png!
> But it's usability is poor:
> * the affected module is not fully shown (half of it cut off)
> * there's no margin on the right border of the dialog
> * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months