February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13469) Add property to disable JBoss Central opening when JBT are starting

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13469?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13469: ---------------------------------------- Fix Version/s: 4.1.0.Alpha2 Assignee: Snjezana Peco (was: Max Rydahl Andersen) > Add property to disable JBoss Central opening when JBT are starting > ------------------------------------------------------------------- > > Key: JBIDE-13469 > URL: https://issues.jboss.org/browse/JBIDE-13469 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > Would be nice to have property allowing to disable JBoss Central opening when JBT are started from command line. > It will stabilize and speed up swt bot tests and also users which are creating a lot of workspaces are annoyed by JBoss Central displaying each time they open new workspace -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13469) Add property to disable JBoss Central opening when JBT are starting

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13469?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13469: --------------------------------------------- Yes it makes sense to create such property, ie. org.jboss.tools.central.donotshow=true or similar (we have a few of these elsehwere (usage and wtp itself, need to check those - lets try follow the same name convention And no I do not see it as contradictory to JBIDE-9656; this property will simply just overrule these updates/checks. If the property is true > Add property to disable JBoss Central opening when JBT are starting > ------------------------------------------------------------------- > > Key: JBIDE-13469 > URL: https://issues.jboss.org/browse/JBIDE-13469 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > Would be nice to have property allowing to disable JBoss Central opening when JBT are started from command line. > It will stabilize and speed up swt bot tests and also users which are creating a lot of workspaces are annoyed by JBoss Central displaying each time they open new workspace -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13297) Prevent from associating xml files to Android xml editor

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13297?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13297: --------------------------------------------- this is android tooling "grabbing" the content type bindings. Needs fixing on android side. > Prevent from associating xml files to Android xml editor > -------------------------------------------------------- > > Key: JBIDE-13297 > URL: https://issues.jboss.org/browse/JBIDE-13297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Reporter: Stefan Bunciak > Assignee: Max Rydahl Andersen > > After installing the Android Development Tools into JBDS/JBT all xml files gets associated to Android Common Xml Editor, even pom.xml files which we used to open with the Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be fixed. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13426) Fresh JBoss Central installation shows stale blog entries

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13426?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-13426. ----------------------------------------- Fix Version/s: 4.1.0.Alpha1 Resolution: Done > Fresh JBoss Central installation shows stale blog entries > --------------------------------------------------------- > > Key: JBIDE-13426 > URL: https://issues.jboss.org/browse/JBIDE-13426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha1 > > Attachments: stale-blogs.png > > > I installed the JBT Central Community feature from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ on a fresh Kepler M4 installation. Once opened, JBoss Central displays very old blog entries : > !stale-blogs.png! > EDIT : > I also see the same problem on existing a JBDS installation, where a recent list of blog entries is replaced by that old list soon after Central is displayed. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13426) Fresh JBoss Central installation shows stale blog entries

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13426?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13426: --------------------------------------------- the planet.jboss.org feed timed out causing feeds to loose them. > Fresh JBoss Central installation shows stale blog entries > --------------------------------------------------------- > > Key: JBIDE-13426 > URL: https://issues.jboss.org/browse/JBIDE-13426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha1 > > Attachments: stale-blogs.png > > > I installed the JBT Central Community feature from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ on a fresh Kepler M4 installation. Once opened, JBoss Central displays very old blog entries : > !stale-blogs.png! > EDIT : > I also see the same problem on existing a JBDS installation, where a recent list of blog entries is replaced by that old list soon after Central is displayed. -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13672: ------------------------------- Description: Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). Sample files to check: http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... was: Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13673: ---------------------------------- Summary: jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version Key: JBIDE-13673 URL: https://issues.jboss.org/browse/JBIDE-13673 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.Alpha2 jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13672: ---------------------------------- Summary: could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? Key: JBIDE-13672 URL: https://issues.jboss.org/browse/JBIDE-13672 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.Alpha2 Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13232: ------------------------------------ New convention: * x.yz.i.((Alpha|Beta|CR)j|Final) Where x.yz maps to Eclipse version x.y.z i only increases after a Final is released j increases for every respin within that milestone (Alpha1, Alpha2, Alpha3...) Therefore *4.30.5.Alpha-SNAPSHOT* will be replaced on the next respin with: * 4.30.5.Alpha2-SNAPSHOT * 4.30.5.Alpha3-SNAPSHOT ... * 4.30.5.Beta1-SNAPSHOT * 4.30.5.Beta2-SNAPSHOT ... * 4.30.5.CR1-SNAPSHOT * 4.30.5.CR1 (released!) * 4.30.5.CR2-SNAPSHOT * 4.30.5.CR2 (released!) ... * 4.30.5.Final (released!) * 4.30.6.CR1-SNAPSHOT * 4.30.6.CR1 * 4.30.6.CR2-SNAPSHOT * 4.30.6.CR2 ... > refactor target platforms' GAVs, names, labels (was target platforms has the same name) > --------------------------------------------------------------------------------------- > > Key: JBIDE-13232 > URL: https://issues.jboss.org/browse/JBIDE-13232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Environment: > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > Attachments: JBIDE13232.parent.pom.tweaks.txt > > > .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either. > Makes it hard to actually see which target platform to choose -- 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13663?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13663: ------------------------------------- Fix Version/s: 4.1.x > Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13663 > URL: https://issues.jboss.org/browse/JBIDE-13663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > usecase: > EXECUTE: Create openshift project > EXECUTE: Make sure all is committed and Pushed. > EXECUTE: Edit an existing committed file - commit it. > EXECUTE: Add a "xyz.log" file that is not to be committed. > EXECUTE: Publish to server. > ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. > EXECUTE: Wait for publish to finish. > ASSERT: "xyz.log" should *not* be pushed nor committed. -- 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 month

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