July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12100) AS7 poller is set to as7 management by default while EAP6 is set to web port

by Martin Malina (JIRA)

Martin Malina created JBIDE-12100: ------------------------------------- Summary: AS7 poller is set to as7 management by default while EAP6 is set to web port Key: JBIDE-12100 URL: https://issues.jboss.org/browse/JBIDE-12100 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: JBDS 5.0.0.CR1a Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.0.CR1 Feel free to push this to a future version. But I just found out about this and it seems odd. When I add a local AS7 server, it is, by default, set to AS7 management startup poller. But when I create a local EAP6 server, it is set to web poller. Why is that? This applies to both adding manually or using jboss runtime detection plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

[JBoss JIRA] (JBIDE-12271) Automatic creation of xpath model fails during some tests; metadata folder DNE

by Rob Stryker (JIRA)

12 years

2
5
0 / 0

[JBoss JIRA] (JBDS-2246) Provide automated notification to users of available updates

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2246: ---------------------------------- Summary: Provide automated notification to users of available updates Key: JBDS-2246 URL: https://issues.jboss.org/browse/JBDS-2246 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: central Affects Versions: 5.0.0.GA Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 6.0.0.M1 Attachments: Screenshot-1.png, Screenshot.png Release 5.0.1 is now available - how (other than actively executing Help->Software Upgrade) will a 5.0.0.GA user know that a new update is available? Can we add a notification (push) feature? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
8
0 / 0

[JBoss JIRA] (JBIDE-12360) Wrapper bug for mistake commit

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12360: ----------------------------------- Summary: Wrapper bug for mistake commit Key: JBIDE-12360 URL: https://issues.jboss.org/browse/JBIDE-12360 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 The following commit was mistakenly sent in at once due to a faulty commit command. Committed revision 42683. https://source.jboss.org/changelog/JBossTools?cs=42683 The changes include: 1) Organizing imports 2) A significant error in WorkspaceFIlesetVirtualComponent 3) An error in WTPZippedPublisher which sent the zipped archive to the remote machine TWICE unnecessarily. 4) Slightly enhanced API (added api, none changed or removed) to allow easier access to the deployment per-module preferences 5) An *INCORRECT* change to ServerCreationUtils turning off auto-deployment for newly created servers. This should properly be placed in teh TEST SUITE, and not in the main code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (JBIDE-12362) ZIpped publish over the wire sends zip file twice instead of once

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12362: ----------------------------------- Summary: ZIpped publish over the wire sends zip file twice instead of once Key: JBIDE-12362 URL: https://issues.jboss.org/browse/JBIDE-12362 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 3) An error in WTPZippedPublisher which sent the zipped archive to the remote machine TWICE unnecessarily. 4) Slightly enhanced API (added api, none changed or removed) to allow easier access to the deployment per-module preferences To reproduce, well, you'd have to use breakpoints really. Inspecting the progress monitor won't do much, because it will still look like it's sending the same file. It will be hard to tell when the first transfer has finished and the second began. The original commit to trunk was made over at JBIDE-12360 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] (JBIDE-11990) When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out

by Martin Malina (JIRA)

Martin Malina created JBIDE-11990: ------------------------------------- Summary: When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out Key: JBIDE-11990 URL: https://issues.jboss.org/browse/JBIDE-11990 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: JBT 3.3 nightly 2012-05-24 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this is what happens: 1. The process keeps running on the remote host 2. The server is in Starting state until it reaches time out 3. This is where remote and local servers differ, but both behave wrongly 3.a - remote server: When time out is reached, server stops, but the process keeps running - you have to kill it manually 3.b - local server: When time out is reached, server tries to stop, but fails doing so. So you have to force stop and then it stops and the process is killed. The the bigger problem is with remote servers - you have no way of stopping the server other than sshing to the server and killing the process. In the case of local server, it is not so bad, but still after the time out the tools should be able to stop the server on first attempt. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
5
0 / 0

[JBoss JIRA] (JBIDE-12174) Portlet wizards should not be restricted to portlet enabled projects (regression)

by Lucia Jelinkova (JIRA)

12 years

4
15
0 / 0

[JBoss JIRA] (JBIDE-12361) PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12361: ----------------------------------- Summary: PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component Key: JBIDE-12361 URL: https://issues.jboss.org/browse/JBIDE-12361 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.2, 3.4.0.M1 Steps to reproduce: 1) Create a dynamic web project 2) Create a POJP 3) Inside POJP, make some file structure (foldera, foldera/file1.txt, foldera/file2.txt, folderb, folderb/b1.txt, etc) 4) Right-click web project, go to deployment assembly page 5) click add 6) click 'fileset' 7) set root to /pojp 8) set includes pattern to **/file1* 9) finish 10) publish this to some server You will note that matching files inside a subdirectory that is not explicitly included in the includes pattern does not get included. In this case, foldera/file1.txt will not be included, and folder 'foldera' will also not be created in the deployment. This is a bug. Part of this commit has been made over at JBIDE-12360 by accident -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
6
0 / 0

[JBoss JIRA] (JBIDE-12239) Migrate Central module to eclipse Juno

by Denis Golovin (JIRA)

12 years

4
5
0 / 0

[JBoss JIRA] (JBIDE-12033) New Seam Project Wizard - when AS7 runtime is set, seam config is not set properly after changing to EAP5.1.2 runtime

by Martin Malina (JIRA)

Martin Malina created JBIDE-12033: ------------------------------------- Summary: New Seam Project Wizard - when AS7 runtime is set, seam config is not set properly after changing to EAP5.1.2 runtime Key: JBIDE-12033 URL: https://issues.jboss.org/browse/JBIDE-12033 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.CR1 Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar Reporter: Martin Malina Assignee: Alexey Kazakov Fix For: 3.3.1 I guess this is not really so urgent, so targeting for 3.3.1. While verifying JBIDE-11815, I noticed the following: When you open the New Seam Project Wizard and select AS7/EAP6 runtime, both Dynamic web module and Configuration are set properly, to 3.0 and Dynamic Web Project with Seam 2.3, respectively. But when you then change the runtime to EAP 5.1.2 the web module version is not changed (it stays empty) and the Configuration is set to <custom>. Even if set the web module to 2.5, Configuration is not set to Seam 2.2. I would expect that after changing runtime to EAP 5.1, both web module version and configuration would be changed accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012