December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18914: ------------------------------- Fix Version/s: 4.3.0.Alpha1 > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18914: ------------------------------------ Looking for feedback/agreement from [~maxandersen] [~akazakov] [~fbricon] [~dgolovin] [~mickael_istria] etc. Any naysayers? Or should I assume you all are OK with this plan and we can do cleanup in January some time? > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18914: ------------------------------- Description: Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. [0] http://download.jboss.org/jbosstools/targetplatforms/ Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: {code} [DIR] 3.62.0.Final-SNAPSHOT/ [DIR] 3.72.0.Final-SNAPSHOT/ [DIR] 4.20.5.Final-SNAPSHOT/ [DIR] 4.20.6.Final-SNAPSHOT/ [DIR] 4.21.3.Final-SNAPSHOT/ [DIR] 4.21.4.Final-SNAPSHOT/ [DIR] 4.22.0.Final-SNAPSHOT/ [DIR] 4.22.1.Final-SNAPSHOT/ [DIR] 4.22.2.Final-SNAPSHOT/ {code} Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. [1] http://download.jboss.org/jbosstools/static/targetplatforms/ I believe we can also purge things like 4.40.0.Beta* from here [2]: [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. was: Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. [0] http://download.jboss.org/jbosstools/targetplatforms/ Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: {code} [DIR] 3.62.0.Final-SNAPSHOT/ [DIR] 3.72.0.Final-SNAPSHOT/ [DIR] 4.20.5.Final-SNAPSHOT/ [DIR] 4.20.6.Final-SNAPSHOT/ [DIR] 4.21.3.Final-SNAPSHOT/ [DIR] 4.21.4.Final-SNAPSHOT/ [DIR] 4.22.0.Final-SNAPSHOT/ [DIR] 4.22.1.Final-SNAPSHOT/ [DIR] 4.22.2.Final-SNAPSHOT/ {code} Then we can purge all the 4.{3?,4?}.*.*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. [1] http://download.jboss.org/jbosstools/static/targetplatforms/ I believe we can also purge things like 4.40.0.Beta* from here [2]: [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Fix For: 4.2.2.Final > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18899: ------------------------------------ Assign to Max to suggest a better solution or close this as Won't Fix. #triageIsFun > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18914: ------------------------------- Fix Version/s: 4.2.2.Final > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Fix For: 4.2.2.Final > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18914: ---------------------------------- Assignee: Nick Boldt > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18899: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18899?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18899: ------------------------------- Fix Version/s: 4.2.x > symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18899 > URL: https://issues.jboss.org/browse/JBIDE-18899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifa... contains the following: > {{{ > <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9"> > <child location="2014-12-06_19-43-15-B315/all/repo/"/> > <child location="2014-12-06_01-42-39-B314/all/repo/"/> > <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository> > }}} > Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-4... should exist - but it does not. > I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18876: ------------------------------------ Assigning to Denis to suggest an alternative to the process described by Mickael. > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18876: ---------------------------------- Assignee: Denis Golovin > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014