February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23964) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23964: ---------------------------------- Summary: externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) Key: JBIDE-23964 URL: https://issues.jboss.org/browse/JBIDE-23964 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.3.Final Reporter: Nick Boldt Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23965: ---------------------------------- Summary: externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) Key: JBIDE-23965 URL: https://issues.jboss.org/browse/JBIDE-23965 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.3.Final Reporter: Nick Boldt Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23965?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23965: ------------------------------- Fix Version/s: 4.4.4.AM1 4.5.0.AM1 > externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23965 > URL: https://issues.jboss.org/browse/JBIDE-23965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23965?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23965: ---------------------------------- Assignee: Nick Boldt > externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23965 > URL: https://issues.jboss.org/browse/JBIDE-23965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23868) Fix jbt-server otherOS test cases: take 2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23868?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23868: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.Final) > Fix jbt-server otherOS test cases: take 2 > ----------------------------------------- > > Key: JBIDE-23868 > URL: https://issues.jboss.org/browse/JBIDE-23868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23857) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [integration-tests]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23857?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23857. ------------------------------ Resolution: Done > For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [integration-tests] > ------------------------------------------------------------------------------ > > Key: JBIDE-23857 > URL: https://issues.jboss.org/browse/JBIDE-23857 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.Final > > > For JBIDE 4.4.3.Final [integration-tests]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.3.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23768: ------------------------------- Labels: releasework (was: ) > Publish tagged version of jboss tools parent pom to public repository > --------------------------------------------------------------------- > > Key: JBIDE-23768 > URL: https://issues.jboss.org/browse/JBIDE-23768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.Final, 4.4.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.Final > > > it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release. > i'm talking about org.jboss.tools:parent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Labels: releasework (was: ) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.3.Final > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23318) fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23318?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23318: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.4.AM1) > fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23318 > URL: https://issues.jboss.org/browse/JBIDE-23318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.x, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23318) fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23318?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23318. ------------------------------ Resolution: Done Done yesterday. > fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23318 > URL: https://issues.jboss.org/browse/JBIDE-23318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.x, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017