April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11065: ---------------------------------------- Since it's not a trivial change, I guess we'd rather make it target 4.1.0.Alpha3 and apply only on master. > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13830) document reasons for using Eclipse Juno SR2 instead of earlier version on www.jboss.org install page for JBT 4.0.1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13830?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13830: ------------------------------------- If anything, number 2 is a new bug in wtp behavior. WTP now ignores meta files like .project whereas it did not used to. So a custom virtual component which explicitly exposes a .project file will have this ignored against their wishes. However, the unit test was made after SR1, and SR1 included this change in behaviour. The difference in behaviour is only noticable when running tests against pre-SR1, which the test was never designed to run against. So... if anything, the new behavior in wtp is a bug, and this should not be documented as a reason to use sr2 for 2 reasons: first, the change was made in sr1, so there's no change between sr1 and sr2, and the second reason is that hte new behaviour is kinda crap ;) > document reasons for using Eclipse Juno SR2 instead of earlier version on www.jboss.org install page for JBT 4.0.1 > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13830 > URL: https://issues.jboss.org/browse/JBIDE-13830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite, website > Affects Versions: 4.0.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > When we release JBT 4.0.1, we should update https://www.jboss.org/tools/download/installation/update_4_0#installon420421 to include a blurb about why we encourage users to use Juno SR2 instead of R or SR1. > Reasons include: > a) performance patch, JBIDE-13326 / JBIDE-13335 > b) WTP bug / behaviour change between WTP 3.3.0 & 3.3.1: JBIDE-13821 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13932) Remove connections from OpenShift Explorer tab on IDE (re)start

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13932?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-13932: ----------------------------------------- Actually, on further investigation, I take this all back. I can see that listing previous connections is useful as the user can just double-click on the connection to open the prefilled connection wizard and re-establish the connection. > Remove connections from OpenShift Explorer tab on IDE (re)start > --------------------------------------------------------------- > > Key: JBIDE-13932 > URL: https://issues.jboss.org/browse/JBIDE-13932 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Michelle Murray > Assignee: Andre Dietisheim > > On (re)starting the IDE, previously active connections show in the OpenShift Explorer tab. I think this is probably intended behaviour and not a bug. But I do not think this behaviour is useful for users. > On (re)starting the IDE, the connections listed in the OpenShift Explorer tab are inactive. To get active connections, a user has to click the 'Connect to OpenShift' icon and still pick a previous or new connection. So I cannot see the benefit to the user of listing previously active connections in the OpenShift Explorer tab. > I think it would be simpler from a user perspective if the OpenShift Explorer tab was always empty when the IDE starts (since no connections are active). Then, as currently happens, when the user clicks the 'Connect to OpenShift' icon they will see the list of previous connections and can choose from these or pick a new one. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2506) Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2506?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2506 at 4/4/13 8:29 PM: ---------------------------------------------------------- TPs have been recovered, but for consistency w/ the new publishing location, I've moved them here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.7... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... As such you can access them as an internal file:/// path, internal http:// path, or public http:// path: {code} -P local.site -Dlocal.site=http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ {code} Also recreated the Helios SR2 target platform in a similar way: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.6... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... was (Author: nickboldt): TPs have been recovered, but for consistency w/ the new publishing location, I've moved them here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.7... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... As such you can access them as an internal file:/// path, internal http:// path, or public http:// path: {code} -P local.site -Dlocal.site=file:///qa/services/http/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ {code} Also recreated the Helios SR2 target platform in a similar way: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.6... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... > Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x > ---------------------------------------------------------- > > Key: JBDS-2506 > URL: https://issues.jboss.org/browse/JBDS-2506 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Reporter: Douglas Palmer > Assignee: Nick Boldt > Priority: Blocker > Fix For: 5.0.4.GA-SOA > > > The target platforms (target-platform_3.3.indigo.SR2 and jbds-target-platform_3.3.indigo.SR2), required to build maintenance releases, have been removed from /home/hudson/static_build_env/jbds. Can you please restore them ASAP? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13932) Remove connections from OpenShift Explorer tab on IDE (re)start

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-13932: --------------------------------------- Summary: Remove connections from OpenShift Explorer tab on IDE (re)start Key: JBIDE-13932 URL: https://issues.jboss.org/browse/JBIDE-13932 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.0.0.Final Reporter: Michelle Murray Assignee: Andre Dietisheim On (re)starting the IDE, previously active connections show in the OpenShift Explorer tab. I think this is probably intended behaviour and not a bug. But I do not think this behaviour is useful for users. On (re)starting the IDE, the connections listed in the OpenShift Explorer tab are inactive. To get active connections, a user has to click the 'Connect to OpenShift' icon and still pick a previous or new connection. So I cannot see the benefit to the user of listing previously active connections in the OpenShift Explorer tab. I think it would be simpler from a user perspective if the OpenShift Explorer tab was always empty when the IDE starts (since no connections are active). Then, as currently happens, when the user clicks the 'Connect to OpenShift' icon they will see the list of previous connections and can choose from these or pick a new one. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2506) Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2506?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2506. ------------------------------ Resolution: Done TPs have been recovered, but for consistency w/ the new publishing location, I've moved them here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.7... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... As such you can access them as an internal file:/// path, internal http:// path, or public http:// path: {code} -P local.site -Dlocal.site=file:///qa/services/http/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/ or -P local.site -Dlocal.site=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/ {code} Also recreated the Helios SR2 target platform in a similar way: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.6... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... > Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x > ---------------------------------------------------------- > > Key: JBDS-2506 > URL: https://issues.jboss.org/browse/JBDS-2506 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Reporter: Douglas Palmer > Assignee: Nick Boldt > Priority: Blocker > Fix For: 5.0.4.GA-SOA > > > The target platforms (target-platform_3.3.indigo.SR2 and jbds-target-platform_3.3.indigo.SR2), required to build maintenance releases, have been removed from /home/hudson/static_build_env/jbds. Can you please restore them ASAP? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2506) Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2506?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2506 at 4/4/13 8:25 PM: ---------------------------------------------------------- TPs have been recovered, but for consistency w/ the new publishing location, I've moved them here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.7... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... As such you can access them as an internal file:/// path, internal http:// path, or public http:// path: {code} -P local.site -Dlocal.site=file:///qa/services/http/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ {code} Also recreated the Helios SR2 target platform in a similar way: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.6... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... was (Author: nickboldt): TPs have been recovered, but for consistency w/ the new publishing location, I've moved them here: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.7... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... As such you can access them as an internal file:/// path, internal http:// path, or public http:// path: {code} -P local.site -Dlocal.site=file:///qa/services/http/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/REPO/ or -P local.site -Dlocal.site=http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/ or -P local.site -Dlocal.site=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.72.0.Final-SNAPSHOT/ {code} Also recreated the Helios SR2 target platform in a similar way: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/3.6... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbosstoolstarget/3.... http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/3... > Recreate the target platforms for JBT 3.3.x and JBDS 5.0.x > ---------------------------------------------------------- > > Key: JBDS-2506 > URL: https://issues.jboss.org/browse/JBDS-2506 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Reporter: Douglas Palmer > Assignee: Nick Boldt > Priority: Blocker > Fix For: 5.0.4.GA-SOA > > > The target platforms (target-platform_3.3.indigo.SR2 and jbds-target-platform_3.3.indigo.SR2), required to build maintenance releases, have been removed from /home/hudson/static_build_env/jbds. Can you please restore them ASAP? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11065: ------------------------------------ missed your comment here. will look @ this tomorrow. Unfortunately we'll have to apply it in Alpha2x and master branches :( > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13919) Integrate LiveReload in JBT site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13919?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13919 at 4/4/13 8:12 PM: ------------------------------------------------------------ Pulled. Now need to still add the new feature to the JBT aggregate site. Not sure where you want it categorized: assuming "Other Tools" for now. See also JBIDE-13930 re: marketplace categorization. https://github.com/jbosstools/jbosstools-build-sites/pull/59 (master) https://github.com/jbosstools/jbosstools-build-sites/pull/60 (Alpha2) was (Author: nickboldt): Pulled. Need to still add the new feature(s) to the JBT aggregate site. > Integrate LiveReload in JBT site > -------------------------------- > > Key: JBIDE-13919 > URL: https://issues.jboss.org/browse/JBIDE-13919 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Add the livereload feature to aggregation. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13931) Add LiveReload feature to Eclipse Marketplace?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13931?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13931: ---------------------------------- Assignee: Xavier Coulon (was: Nick Boldt) > Add LiveReload feature to Eclipse Marketplace? > ---------------------------------------------- > > Key: JBIDE-13931 > URL: https://issues.jboss.org/browse/JBIDE-13931 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload, Marketplace > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > Should this feature be included in the list of features on the Eclipse Marketplace, or is it an "extra" thing that can be installed later? -- 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, 2 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 April 2013