July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18001) Consider using a more pale shade of yellow to identify Early Access content in JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18001?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18001: ---------------------------------------- [~nickboldt] Is this something you're interested in implementing? > Consider using a more pale shade of yellow to identify Early Access content in JBoss Central > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18001 > URL: https://issues.jboss.org/browse/JBIDE-18001 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.CR1 > > > From [~maxandersen] (sic): > {quote} > (2014-07-30 09:43:42) maxandersen: nickboldt1: yes but having a paler yellow actually sounds like better than what is there now > (2014-07-30 09:47:42) maxandersen: nickboldt1: suggestions to make the bigy ellow we got now very welcome. thus yes if we dont have a jira for better suggestion for this alrady > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18007) Server adapter: Enhancement of deletion of an application via server adapter

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18007: ---------------------------------- Summary: Server adapter: Enhancement of deletion of an application via server adapter (was: Server adapter: Delete non-existing application via server adapter provides inaccurate error message) > Server adapter: Enhancement of deletion of an application via server adapter > ---------------------------------------------------------------------------- > > Key: JBIDE-18007 > URL: https://issues.jboss.org/browse/JBIDE-18007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Attachments: delete_app_via_adapter.png > > > After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about application in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the application in the workspace. It only delete an application on OpenShift server. > However, trying to delete an OpenShift application via adapter with non-existing application in workspace (but existing on OpenShift) this error message is correct. > !delete_app_via_adapter.png! > We should either: > 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift. > 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18007) Server adapter: Deletion of an application via server adapter

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18007: ---------------------------------- Summary: Server adapter: Deletion of an application via server adapter (was: Server adapter: Enhancement of deletion of an application via server adapter) > Server adapter: Deletion of an application via server adapter > ------------------------------------------------------------- > > Key: JBIDE-18007 > URL: https://issues.jboss.org/browse/JBIDE-18007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Attachments: delete_app_via_adapter.png > > > After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about application in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the application in the workspace. It only delete an application on OpenShift server. > However, trying to delete an OpenShift application via adapter with non-existing application in workspace (but existing on OpenShift) this error message is correct. > !delete_app_via_adapter.png! > We should either: > 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift. > 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18007) Server adapter: Delete non-existing application via server adapter provides inaccurate error message

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-18007: ------------------------------------- Summary: Server adapter: Delete non-existing application via server adapter provides inaccurate error message Key: JBIDE-18007 URL: https://issues.jboss.org/browse/JBIDE-18007 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Beta3 Reporter: Marián Labuda Priority: Minor Attachments: delete_app_via_adapter.png After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about application in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the application in the workspace. It only delete an application on OpenShift server. However, trying to delete an OpenShift application via adapter with non-existing application in workspace (but existing on OpenShift) this error message is correct. !delete_app_via_adapter.png! We should either: 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift. 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18007) Server adapter: Delete non-existing application via server adapter provides inaccurate error message

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18007: ---------------------------------- Attachment: delete_app_via_adapter.png > Server adapter: Delete non-existing application via server adapter provides inaccurate error message > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-18007 > URL: https://issues.jboss.org/browse/JBIDE-18007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Attachments: delete_app_via_adapter.png > > > After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about application in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the application in the workspace. It only delete an application on OpenShift server. > However, trying to delete an OpenShift application via adapter with non-existing application in workspace (but existing on OpenShift) this error message is correct. > !delete_app_via_adapter.png! > We should either: > 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift. > 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17960. --------------------------------- Assignee: Rob Stryker Thanks, [~the_alchemist], for confirming. I am closing this issue. Feel free to reopen if you see this problem again. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Beta3 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17724. --------------------------------- > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta3 > > Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17960: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.0.CR1) > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.Beta3 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17616) Move 'externally managed' from launch config to server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17616?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-17616: ----------------------------------- Assignee: Rob Stryker > Move 'externally managed' from launch config to server editor > ------------------------------------------------------------- > > Key: JBIDE-17616 > URL: https://issues.jboss.org/browse/JBIDE-17616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR1 > > > in JBIDE-17076 externally managed was *moved* into launch UI even though that externally managed defaults to false and when users enable it launch configurations becomes irrelevant. > Why can't we have it both so we do not have to get users to work with launch configuraiton UI for the simple case of not wanting to start a server but just connect to what is there ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies

by Harald Wellmann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ] Harald Wellmann commented on JBIDE-17990: ----------------------------------------- I tried all sorts of things... I can't reproduce the issue with a clean install (Virgin Eclipse Luna + 4.2.0.Beta3 Abridged JBoss Tools). I suspect something went wrong during the update from the update site, and things went from bad to worse, as there was no way to cleanly rollback this update. Before the update, I had * Luna Enterprise Edition * A subset of Beta2 Abridged Tools * Some additional m2e extensions. After the broken update, I noticed that all library folders previously named {{Maven Dependencies}} were now called something like {{Persistent container \[some technical identifer\]}} which looked rather suspicious. I don't remember the exact wording - maybe this is a clue to which plugin was broken during the update. I tried to revert to the previous configuration from Installation History, which gave me an error message about 4.2.0.Beta2 no longer available from any update site. Seeing that Eclipse never really deletes any updated plugins, I don't see why Eclipse is unable to revert to a known configuration when all required plugins are still on my local disk. To get out of this mess, I had to revert to the configuration I had before the original Beta2 install (thus reverting both Beta2 and Beta3 and some other stuff I had installed in the meantime). > Organize imports does not work for Maven dependencies > ----------------------------------------------------- > > Key: JBIDE-17990 > URL: https://issues.jboss.org/browse/JBIDE-17990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta3 > Environment: Oracle JDK 1.8.0_05, Eclipse Luna > Reporter: Harald Wellmann > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN. > The corresponding Quick Fix is also broken. > It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository. > This is even worse than JBIDE-17724, I'll have to revert to Beta2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014