March 2013 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------ PR 40 replaced by 41 and 42: {code}* 7f7634c - (HEAD, origin/master, nickboldt/JBIDE-11065-clean_2, master, JBIDE-11065-clean_2) fix update.site.name and support passing in update.site.descriptio * 7d3a7a9 - refactoring, cleanup, typos, removal of dead code, simpler console out for external <exec> calls, move to Eclipse 4.2.2 (JBIDE-11065) nickboldt@gmai * addb00a - update list of component owners / source repos nickboldt(a)gmail.com (3 days ago) * 0ce71be - fix paths in local-site/pom.xml nickboldt(a)gmail.com (3 days ago) * fbac971 - merge multiple clones of the README.building.txt into a single one nickboldt(a)gmail.com (3 days ago) * 21a10bf - fix deprecation warnings on soa-site and soatests-site nickboldt(a)gmail.com (3 days ago) * b1fde36 - JBIDE-11065 PR 40, with some changes nickboldt(a)gmail.com (3 days ago){code} > 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.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

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 closed JBIDE-13672. ------------------------------ Nothing to document, nothing to QE. Closing. > 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 > > Attachments: jbide13672-proposed-markup.png, jbide13672-proposed-markup2.png, jbide13672-proposed-markup_v2.png, jbide13672-proposed-markup_v2_2.png > > > 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
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: ------------------------------- Release Notes Docs Status: Not Required Release Notes Text: N/A > 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 > > Attachments: jbide13672-proposed-markup.png, jbide13672-proposed-markup2.png, jbide13672-proposed-markup_v2.png, jbide13672-proposed-markup_v2_2.png > > > 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
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 resolved JBIDE-13672. -------------------------------- Resolution: Done Rolled out to all applicable _41 and _master jobs in the DevStudio_Trunk and DevStudio_7.0.kepler views. > 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 > > Attachments: jbide13672-proposed-markup.png, jbide13672-proposed-markup2.png, jbide13672-proposed-markup_v2.png, jbide13672-proposed-markup_v2_2.png > > > 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
0
0 / 0

[JBoss JIRA] (JBIDE-13801) Wrong Server Adapter name generated from Wizard

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-13801: ------------------------------------- Summary: Wrong Server Adapter name generated from Wizard Key: JBIDE-13801 URL: https://issues.jboss.org/browse/JBIDE-13801 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.1.0.Alpha1 Reporter: Xavier Coulon Assignee: Andre Dietisheim When you create a server adapter for an existing application, in case it's missing, the server name is made after the first app in the domain, not the selected app in the openshift explorer view. In my case, I had 2 applications: "html5" and "test", and I wanted to create a server adapter for the "test" one (using the "Create Server Adapter" command), but the name was "html5 on OpenShift" -- 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-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: ------------------------------- Attachment: jbide13672-proposed-markup_v2.png jbide13672-proposed-markup_v2_2.png New markup: !jbide13672-proposed-markup_v2.png! !jbide13672-proposed-markup_v2_2.png! > 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 > > Attachments: jbide13672-proposed-markup.png, jbide13672-proposed-markup2.png, jbide13672-proposed-markup_v2.png, jbide13672-proposed-markup_v2_2.png > > > 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
0
0 / 0

[JBoss JIRA] (JBIDE-11558) Repositories are missing source feature titles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11558?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11558: ---------------------------------------- Tested staging release candidate of Tycho 0.17, and it fixes this issue. > Repositories are missing source feature titles > ---------------------------------------------- > > Key: JBIDE-11558 > URL: https://issues.jboss.org/browse/JBIDE-11558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, UpStream > Affects Versions: 3.3.0.Beta3 > Environment: jbt33beta3-trunk,L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.1.x > > Attachments: empty-list.png, JBIDE-11558_empty_names.png, missing-names.png, missing-titles.png > > > While updating JBT 3.3. trunk there are missing titles in dialog (see screenshot) -- 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-13796) rename jbosstools-integration-tests to jbosstools-itests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13796: ------------------------------------ This avoids having jbosstools-integration-stack-integration-tests, which uses the term "integration" in two different contexts. And it adopts the maven convention of "itest". > rename jbosstools-integration-tests to jbosstools-itests > -------------------------------------------------------- > > Key: JBIDE-13796 > URL: https://issues.jboss.org/browse/JBIDE-13796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests. > Once renamed, will need to refactor: > * job name > * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/ -- 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-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13800?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13800: ---------------------------------- Bugzilla Update: (was: Perform) > Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13800 > URL: https://issues.jboss.org/browse/JBIDE-13800 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. > Could not embed cartridges for application test2 > Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. > Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" > I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. > Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- 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-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13800?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-13800: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=922711 > Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13800 > URL: https://issues.jboss.org/browse/JBIDE-13800 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. > Could not embed cartridges for application test2 > Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. > Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" > I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. > Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- 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