March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2505: --------------------------------- I made the change on job config to no override TARGET_PLATFORM_VERSION. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is running, [~mmalina]: when finished, can you please check its output and verify it's using SR2? > JBDS 6.0.1 is based on Juno SR0 instead of SR2 > ---------------------------------------------- > > Key: JBDS-2505 > URL: https://issues.jboss.org/browse/JBDS-2505 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA > > > JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. > I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. > My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. > Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2505: --------------------------------- On job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... , we can read on maven execution "-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT". This used to make the build use 4.20.6.Final-SNAPSHOT, ignoring the maximum profile and settings in the parent pom. A fix was made as part of JBIDE-13821 , but it did not apply to the parent 4.0.1.Final-SNAPSHOT, so the issue occurs for devstudio job. For this job, the fix is simply to remove "-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION_MAXIMUM=4.22.2.Final-SNAPSHOT", which cause the error, and is useless since those are default values from parent pom. > JBDS 6.0.1 is based on Juno SR0 instead of SR2 > ---------------------------------------------- > > Key: JBDS-2505 > URL: https://issues.jboss.org/browse/JBDS-2505 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA > > > JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. > I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. > My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. > Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13875. --------------------------------- Resolution: Done pushed to master. Ready for QE ;) > Incorrect Module status when starting server/module > --------------------------------------------------- > > Key: JBIDE-13875 > URL: https://issues.jboss.org/browse/JBIDE-13875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Create and deploy a webapp on an *stopped* AS or EAP server. > * When the app server is started, the webapp module appears as "stopped", even though it's started. > * When the server is restarted, The module just says "synchronized" > * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2501) App code and config migration to EAP 6 (QuckFixes, refactoring)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2501?page=com.atlassian.jira.plugin.... ] Ondrej Zizka updated JBDS-2501: ------------------------------- Attachment: NetBeans-analyzers-FS.png > App code and config migration to EAP 6 (QuckFixes, refactoring) > --------------------------------------------------------------- > > Key: JBDS-2501 > URL: https://issues.jboss.org/browse/JBDS-2501 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ondrej Zizka > Labels: eap6, migration > Attachments: NetBeans-analyzers-FS.png, NetBeans-analyzers.png > > > This feature would identify > 1) configuration bits > 2) source code constructs > 3) old API usage > and help migrating these to EAP 6 or later, in the form of QuickFixes and refactoring dialogs. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-2504: -------------------------------- Description: Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. Since JBDS 6.0.1 is based on SR2, this has nothing to do there. Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. Anyway, it should be removed from central for 6.0.1. was: Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. Since JBDS 6.0.1 is based on SR2, this has nothing to do there. Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0. Anyway, it should be removed from central for 6.0.1. > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-2505: -------------------------------- Steps to Reproduce: 1. Install JBDS 2. Go to Help -> About. 3. Click the eclipse icon close to the right 4. Check the version of Eclipse Platform > JBDS 6.0.1 is based on Juno SR0 instead of SR2 > ---------------------------------------------- > > Key: JBDS-2505 > URL: https://issues.jboss.org/browse/JBDS-2505 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA > > > JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. > I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. > My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. > Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2

by Martin Malina (JIRA)

Martin Malina created JBDS-2505: ----------------------------------- Summary: JBDS 6.0.1 is based on Juno SR0 instead of SR2 Key: JBDS-2505 URL: https://issues.jboss.org/browse/JBDS-2505 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 6.0.1.GA Environment: JBDS 6.0.1.CR1a B354 Reporter: Martin Malina Assignee: Nick Boldt Priority: Blocker Fix For: 6.0.1.GA JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2. I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0. My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here. Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Martin Malina (JIRA)

Martin Malina created JBDS-2504: ----------------------------------- Summary: JBDS 6.0.1 central software updates contain Juno SR1 fix Key: JBDS-2504 URL: https://issues.jboss.org/browse/JBDS-2504 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, central Affects Versions: 6.0.1.GA Environment: JBDS 6.0.1.CR1a B354 -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml Reporter: Martin Malina Assignee: Nick Boldt Fix For: 6.0.1.GA Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. Since JBDS 6.0.1 is based on SR2, this has nothing to do there. Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0. Anyway, it should be removed from central for 6.0.1. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2501) App code and config migration to EAP 6 (QuckFixes, refactoring)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2501?page=com.atlassian.jira.plugin.... ] Ondrej Zizka commented on JBDS-2501: ------------------------------------ Somebody started writing a Cake plugin: https://github.com/jboss-cake/cake-jbds-plugin > App code and config migration to EAP 6 (QuckFixes, refactoring) > --------------------------------------------------------------- > > Key: JBDS-2501 > URL: https://issues.jboss.org/browse/JBDS-2501 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ondrej Zizka > Labels: eap6, migration > Attachments: NetBeans-analyzers.png > > > This feature would identify > 1) configuration bits > 2) source code constructs > 3) old API usage > and help migrating these to EAP 6 or later, in the form of QuickFixes and refactoring dialogs. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2501) App code and config migration to EAP 6 (QuckFixes, refactoring)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2501?page=com.atlassian.jira.plugin.... ] Ondrej Zizka updated JBDS-2501: ------------------------------- Attachment: NetBeans-analyzers.png Attaching a screenshot for inspiration how it could look like. > App code and config migration to EAP 6 (QuckFixes, refactoring) > --------------------------------------------------------------- > > Key: JBDS-2501 > URL: https://issues.jboss.org/browse/JBDS-2501 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ondrej Zizka > Labels: eap6, migration > Attachments: NetBeans-analyzers.png > > > This feature would identify > 1) configuration bits > 2) source code constructs > 3) old API usage > and help migrating these to EAP 6 or later, in the form of QuickFixes and refactoring dialogs. -- 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

13 years

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 March 2013