May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14654: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/143, https://github.com/jbosstools/jbosstools-openshift/pull/152 (was: https://github.com/jbosstools/jbosstools-openshift/pull/143) > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14639) Add ability to prevent repository references from being included in repositories mirrored from a TP

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14639?page=com.atlassian.jira.plugi... ] Rob Cernich resolved JBIDE-14639. --------------------------------- Resolution: Won't Fix Resolving this issue. Sounds like it needs to be addressed upstream. > Add ability to prevent repository references from being included in repositories mirrored from a TP > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-14639 > URL: https://issues.jboss.org/browse/JBIDE-14639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Rob Cernich > Assignee: Nick Boldt > > JBT-IS builds a repo of "extra" dependencies. When this repo is created, it contains repository references to the jboss.org requirements p2 mirrors, which prevent the mirrored repository from being used with jbds releases (which is what I assume the purpose of the mirrored repository is for). -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14639) Add ability to prevent repository references from being included in repositories mirrored from a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14639?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14639: ------------------------------------ Ah, my mistake. Not sure if you can mirror w/o including references, since that's the way p2 creates a mirror. However, you can remove references immediately after mirroring, simply by removing the chunk of XML that contains the <references>. Here's an ant script that you could call via antrun plugin from your pom, which uses XSLT to find and remove the entire <references> node in the content.xml: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Add ability to prevent repository references from being included in repositories mirrored from a TP > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-14639 > URL: https://issues.jboss.org/browse/JBIDE-14639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Rob Cernich > Assignee: Nick Boldt > > JBT-IS builds a repo of "extra" dependencies. When this repo is created, it contains repository references to the jboss.org requirements p2 mirrors, which prevent the mirrored repository from being used with jbds releases (which is what I assume the purpose of the mirrored repository is for). -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14639) Add ability to prevent repository references from being included in repositories mirrored from a TP

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14639?page=com.atlassian.jira.plugi... ] Rob Cernich updated JBIDE-14639: -------------------------------- Assignee: Nick Boldt (was: Rob Cernich) > Add ability to prevent repository references from being included in repositories mirrored from a TP > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-14639 > URL: https://issues.jboss.org/browse/JBIDE-14639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Rob Cernich > Assignee: Nick Boldt > > JBT-IS builds a repo of "extra" dependencies. When this repo is created, it contains repository references to the jboss.org requirements p2 mirrors, which prevent the mirrored repository from being used with jbds releases (which is what I assume the purpose of the mirrored repository is for). -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14639) Add ability to prevent repository references from being included in repositories mirrored from a TP

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14639?page=com.atlassian.jira.plugi... ] Rob Cernich commented on JBIDE-14639: ------------------------------------- No, it's not the associate sites. It's in the content.xml produced by the "mirror-target-to-repo" mojo, here: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... The repository created by that has repo references within it, for example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Hope that helps. > Add ability to prevent repository references from being included in repositories mirrored from a TP > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-14639 > URL: https://issues.jboss.org/browse/JBIDE-14639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Rob Cernich > Assignee: Nick Boldt > > JBT-IS builds a repo of "extra" dependencies. When this repo is created, it contains repository references to the jboss.org requirements p2 mirrors, which prevent the mirrored repository from being used with jbds releases (which is what I assume the purpose of the mirrored repository is for). -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-14711. ------------------------------------ Resolution: Rejected Ok, so I didn't read the mail carefully, sneak in the download.jboss.org/jbosstools directory and did not find this build. Now it's more clear to me, and this bug is actually a bug in my reading of the mail ;) > Promotion process/script loses build metadata? > ---------------------------------------------- > > Key: JBIDE-14711 > URL: https://issues.jboss.org/browse/JBIDE-14711 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.Beta2 > > > When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile. > Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component. > We should copy metadata along with update-sites. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-14711: ---------------------------------- Assignee: Mickael Istria (was: Nick Boldt) As per the email I sent announcing Beta1b, here's the folder with the build & metadata: http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core/ Updates go in /updates/ Builds go in /builds/ Also... Discovery goes in /discovery/ Requirements go in /updates/requirements/ Target Platforms go in /targetplatforms/ > Promotion process/script loses build metadata? > ---------------------------------------------- > > Key: JBIDE-14711 > URL: https://issues.jboss.org/browse/JBIDE-14711 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.Beta2 > > > When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile. > Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component. > We should copy metadata along with update-sites. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13379) BrowserSim: implement support of the LiveReload protocol

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13379?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-13379. ------------------------------- > BrowserSim: implement support of the LiveReload protocol > -------------------------------------------------------- > > Key: JBIDE-13379 > URL: https://issues.jboss.org/browse/JBIDE-13379 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > There is https://github.com/livereload/livereload-js which could help. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13040) Enable individual emails in Jenkins based on Git changes

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13040?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13040: --------------------------------------------- seems to work now....at least on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... should we try enable it again ? > Enable individual emails in Jenkins based on Git changes > -------------------------------------------------------- > > Key: JBIDE-13040 > URL: https://issues.jboss.org/browse/JBIDE-13040 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Mickael Istria > Priority: Critical > Fix For: 4.1.x > > > Now we have moved to Git, we can probably re-enable individual mailing from Jenkins. Previous issue appeared to be an issue with SVN plugin, which we don't use any longer. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14711) Promotion process/script loses build metadata?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14711: ----------------------------------- Assignee: Nick Boldt (was: Mickael Istria) Component/s: Build/Releng updatesite > Promotion process/script loses build metadata? > ---------------------------------------------- > > Key: JBIDE-14711 > URL: https://issues.jboss.org/browse/JBIDE-14711 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng, updatesite > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.1.0.Beta2 > > > When promoting an aggregation build to nightly, metadata disappear. The only metadata available is the build ID (that we can read in qualifier) but this is not enough as Jenkins build are volatile. > Loss of these metadata makes that it's not possible to find out which commit was used to build an aggregated component. > We should copy metadata along with update-sites. -- 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

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2013