May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-14549: ------------------------------------------- I added steps for both use cases. Hope it's sufficient > Deploying archive via drag&drop triggers server start > ----------------------------------------------------- > > Key: JBIDE-14549 > URL: https://issues.jboss.org/browse/JBIDE-14549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > > If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. > STEP: create a simple java project > STEP: create an archive in it (via explorer/view) > STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view > ASSERT: archive is deployed on the server > FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start > There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. > STEP: create a simple java project > STEP: open Project Explorer view and drag & drop the project into a server > ASSERT: project is deployed > ASSERT: server is not started > STEP: undeploy the project from a server > STEP: create an archive in the project > STEP: drag & drop the project into a server > ASSERT: project is deployed > FAIL: server's start is triggered -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič updated JBIDE-14549: -------------------------------------- Description: If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. STEP: create a simple java project STEP: create an archive in it (via explorer/view) STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view ASSERT: archive is deployed on the server FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. STEP: create a simple java project STEP: open Project Explorer view and drag & drop the project into a server ASSERT: project is deployed ASSERT: server is not started STEP: undeploy the project from a server STEP: create an archive in the project STEP: drag & drop the project into a server ASSERT: project is deployed FAIL: server's start is triggered was: If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. > Deploying archive via drag&drop triggers server start > ----------------------------------------------------- > > Key: JBIDE-14549 > URL: https://issues.jboss.org/browse/JBIDE-14549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > > If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. > STEP: create a simple java project > STEP: create an archive in it (via explorer/view) > STEP: in Project Explorer view, expand Project Archives explorer, select the created archive and drag & drop into server in server's view > ASSERT: archive is deployed on the server > FAIL: server start is initiated but I think it should be not, because archive deploy via Publish Archive dialog doesn't trigger server's start > There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. > STEP: create a simple java project > STEP: open Project Explorer view and drag & drop the project into a server > ASSERT: project is deployed > ASSERT: server is not started > STEP: undeploy the project from a server > STEP: create an archive in the project > STEP: drag & drop the project into a server > ASSERT: project is deployed > FAIL: server's start is triggered -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14549) Deploying archive via drag&drop triggers server start

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14549?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14549: -------------------------------- Fix Version/s: 4.1.1.Final (was: 4.1.0.Beta2) Drag and drop will try either a simple publish if possible (ie, if the node is adaptable to both an IProject and has modules registered for it), and if not, it will attempt a run-on-server action, which involves a publish but also involves starting the server and trying to load a web browser or other relevant client to show to the user. So for example if you drag and drop a servlet file, it will attempt to run it on the server. In the case of a plain old java project containing project archives, the root itself is converible to a project and does have a module in it, so only a publish should be initiated. My tests demonstrate this to be correct. Can you be more specific what exactly you are dragging and dropping, what node, from what view? Please list the use-cases separately as I'm a little confused. Either way, I'm marking this for 4.1.x. > Deploying archive via drag&drop triggers server start > ----------------------------------------------------- > > Key: JBIDE-14549 > URL: https://issues.jboss.org/browse/JBIDE-14549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.1.Final > > > If archive is deployed with Publish dialog, server is (correctly) not started. However, drag&drop archive under server in servers view cause server starting. > There is another bug. When user wants to drag&drop whole project into the server, server's starting process is also initiated, but should be not. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-14619: ----------------------------------- Assignee: Snjezana Peco (was: Rob Stryker) Snjezana: you're usually good at finding out the root cause to problems like this ;) > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Snjezana Peco > Fix For: LATER > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13843) Investigate use of SWTBot 2.1 (and org.junit_4.11) in target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13843: ---------------------------------------- Newer snapshot of SWTBot fixes compatibility with Junit 4.11 and Hamcrest 1.3. Release of SWTBot should happen by the end of June (ideally same day as Kepler). If we have issues in JBT tests because of SWTBot bug #404346, we could mirror a newer snapshot and use it in TP until the release gets out. > Investigate use of SWTBot 2.1 (and org.junit_4.11) in target platform > --------------------------------------------------------------------- > > 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 > Priority: Blocker > Fix For: 4.1.0.Beta2 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14574) JBoss WS runtime version not recognized

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14574?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-14574: ------------------------------------------- It works for 6.0.0 GA, but doesn't work for 6.0.1 GA. Maybe 6.0.1 GA is the borderline. WDYT? > JBoss WS runtime version not recognized > --------------------------------------- > > Key: JBIDE-14574 > URL: https://issues.jboss.org/browse/JBIDE-14574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Beta2 > > > JBoss WS runtime from EAP which comes with JBDS 7.0.0 Beta1 is not recognized. Both "Implementation" and "Version" values are empty. > Note that EAP version is 6.1.0.Beta1. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14330) Create an OpenShift connector in the JBoss Tools discovery catalog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14330?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14330: ------------------------------------- Indeed. Once a feature has been installed, it's hidden from the software page > Create an OpenShift connector in the JBoss Tools discovery catalog > ------------------------------------------------------------------ > > Key: JBIDE-14330 > URL: https://issues.jboss.org/browse/JBIDE-14330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: openshift-discovery.png > > > JBoss Central will now always display the OpenShift wizard, even if not installed already (see JBIDE-13987). > If the OpenShift feature is missing, we should install it via the discovery mechanism. > Hence, OpenShift must be added to the JBT discovery catalog (JBDS has it installed by default) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-341?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-341: ------------------------------------------ Revised doc with QE corrections has brewed and changes will be visible here when server refreshes: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > Review: QE to review Beta1 Release Notes > ---------------------------------------- > > Key: TOOLSDOC-341 > URL: https://issues.jboss.org/browse/TOOLSDOC-341 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf, Screenshot.png > > > *Please review* the Beta1 Release Notes document: > 1) Are new features correctly documented? > 2) Are there any new features that are missing? > 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 > *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14677) jobs that depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT are broken as that version no longer exists

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14677?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14677. ------------------------------ Assignee: Nick Boldt (was: Mickael Istria) Fix Version/s: 4.1.0.Beta1 Resolution: Done Fixed in SVN (trunk). > jobs that depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT are broken as that version no longer exists > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14677 > URL: https://issues.jboss.org/browse/JBIDE-14677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > 21 jenkins jobs such as ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests.matrix/config.xml and ./DevStudio/view/DevStudio_Trunk/job/jbosstools-composite-install_master/config.xml, which depend on com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0-SNAPSHOT, are currently failing. I suspect this is because the 1.1.0 release has happened. > Complete list of config.xml files containing the string "maven-download-plugin:1" are: > {code} > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.director-install-tests.egit.matrix/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.director-install-tests.m2e.matrix/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e3.7.0-jbt_3.3.x/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e3.7.2-jbt_3.3.0-jbt_3.3.x/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-e4.2-jbt_3.3.x/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-tests.egit.matrix/config.xml > ./DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.install-tests.m2e.matrix/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbdevstudio-6.0_stable_branch.install-tests-e4.2-jbds_BYOE_stable_branch/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbdevstudio-6.0_stable_branch.install-tests-eclipseLatest-jbds_BYOE_stable_branch/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests-e4.2-jbt_4.0.juno/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests-eclipseLatest-jbt_4.0.juno/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.upgrade-tests.matrix/config.xml > ./DevStudio/view/DevStudio_6.0.juno/job/jbosstools-composite-install_40/config.xml > ./DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-composite-install_41/config.xml > ./DevStudio/view/DevStudio_Disabled/job/zz_disabled_jbdevstudio-7.0_trunk.install-tests-eclipseLatest-jbds_BYOE_trunk/config.xml > ./DevStudio/view/DevStudio_Disabled/job/zz_disabled_jbosstools-4.1_trunk.install-tests-eclipseLatest-jbt_trunk/config.xml > ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests-e4.3-jbt_trunk/config.xml > ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests-eclipseLatest-jbt_trunk/config.xml > ./DevStudio/view/DevStudio_Trunk/job/jbosstools-4.1_trunk.install-tests.matrix/config.xml > ./DevStudio/view/DevStudio_Trunk/job/jbosstools-composite-install_master/config.xml > {code} > Can you update the above jobs to use the correct new version, either 1.2.0-SNAPSHOT or 1.1.0 ? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14674) Livereload is not in Central for 4.1.0.beta1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14674?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-14674 at 5/29/13 11:36 PM: -------------------------------------------------------------- LiveReload added to JBoss Tools Central and JBDS Central (installed by default though, so sorta redundant). was (Author: nickboldt): LiveReload added to JBoss Tools Central and JBDS. > Livereload is not in Central for 4.1.0.beta1 > -------------------------------------------- > > Key: JBIDE-14674 > URL: https://issues.jboss.org/browse/JBIDE-14674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Labels: respin-b > Fix For: 4.1.0.Beta1 > > Attachments: JBIDE14656_JBIDE14673_JBIDE14674.png > > -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2013