November 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3239) JBDS 8.0.1 - requires a respin to pull in latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3239?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3239: ----------------------------- Labels: respin-a (was: ) > JBDS 8.0.1 - requires a respin to pull in latest build > ------------------------------------------------------ > > Key: JBDS-3239 > URL: https://issues.jboss.org/browse/JBDS-3239 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build > Affects Versions: 8.0.1.CR1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Labels: respin-a > Fix For: 8.0.1.CR1, 8.0.1.GA > > > When I installed the 8.0.1 build on Monday: > Version: 8.0.1.CR1 > Build id: CR1-v20141124-0512-B333 > Build date: 20141124-0512 > I quickly discovered that new updates were available here: > JBoss Developer Studio (Branded Product) > 8.0.1.CR1-v20141124-0632-B334 > We will need a respin to pull in this build. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18833: ------------------------------------ Long blarg short: Max wants an URL with *updates* in it, /updates/nightly/luna/ [1] to point to a composite of the latest nightly *builds* for the luna stream, because the stable URL [2] we've had for ages is too much effort to type or remember. And sees no problem mixing the concept of builds and updates in the same URL. So I've recreated a /luna/ one that points to the correct nightly builds folder. Hooray! [1] http://download.jboss.org/jbosstools/updates/nightly/luna/ [2] http://download.jboss.org/jbosstools/builds/nightly/core/4.2.luna/ And we need a more detailed list of process/steps to perform when moving the new master branch to a new Eclipse baseline. We forgot this step, as well as the step of updating composite install and p2.director jobs to use Mars.M3 instead of Luna.SR1/Luna.R. Probably missed more stuff too. I personally feel that the creation of these symlinks is pointless, because they're just redirects for the lazy. What we really need is a page listing all the URLs for target platforms, builds, update sites, etc. in a single place, a la https://projects.eclipse.org/list-of-projects. I believe this was raised at the F2F but I can't recall if there's a JIRA opened for this. [~maxandersen] do you know if there's a JIRA for that? Can you link it from here? > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18837: --------------------------------------------- [~fbricon] when *should we need to* do this with in a micro release outside development builds where we are necessarily bumping foundation to get the version updated ? I'm not following in which case we would ever need such hard lock in ? I assume you mean for between luna and mars (different release trains ?) Then A) sure - but the updatesite won't have anything else (not perfect but means wont have the problem) B) this is not needed for 4.2.1.CR1 afaics ? > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Labels: respin-a > Fix For: 4.2.1.CR1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18833: ---------------------------------------- The main advantage of symlinks over composite is that it allows to directly browse the repository and see the index.html. Depending on how much we care about that, it may be acceptable to use composite*.xml files instead of symlink. I don't have an opinion on what's better for this use-case. > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18833: --------------------------------------------- so in short, if http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... is the internal build url used for publishing 4.2.x and http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... was the old one then yes this is what makes sense to put here as a composite site (or symbolic link but thats less easier to track) > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- [~mickael_istria] https://github.com/jbosstools/jbosstools-build-ci/pull/117 is what I was suggesting to fix yesterday. Makes the artifact id more unique and follow conventions. See comments on PR/commit for details. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18772: ---------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-ci/pull/116, https://github.com/jbosstools/jbosstools-build-ci/pull/117 (was: https://github.com/jbosstools/jbosstools-build-ci/pull/116) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18772: --------------------------------------------- i'm making a PR to cleanup the naming I mentioned yesterday. Probably nicer to get that in place before rolling out to all jobs. Will link it asap. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18833: --------------------------------------------- It should point to what eventually be the next thing we are testing/developing to land in staging for this release train. If there are multiple branches active then I can't think of one case where not one of them is what we are testing. Also I can't recall when we ever had more than one branch for one release train. And if we do - then sure, then one of them is the next and the others "special cases" which for those involved will be aware of where the out will be put. But for 99.999% of our usage outside ci builds these vanity urls are what we have and are posting for simple ease of use and least surprises. That is at least the intention but for some reason every new release train we expose our internal naming uneccessarily. > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18845) Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18845?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-18845. ----------------------------------- Resolution: Duplicate Issue A duplicate of JBIDE-18795. Now birt builds correctly. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_mast... > Birt depends on Hibernate 3.8, but 4.0.1 is available in JBT > ------------------------------------------------------------ > > Key: JBIDE-18845 > URL: https://issues.jboss.org/browse/JBIDE-18845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build, hibernate, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > > org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires org.hibernate.eclipse.libs 3.8.0. But the latest nightly site for Hibernate from master branch [1] contains no such IU. > [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_... > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT > [ERROR] Missing requirement: org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 requires 'bundle org.hibernate.eclipse.libs 3.8.0' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.birt.feature.feature.group 1.7.0.Alpha1-v20141006-1612-B585 depends on: org.jboss.tools.birt.oda.ui [1.7.0.Alpha1-v20141006-1612-B585] > [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.3.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.0-SNAPSHOT depends on: org.jboss.tools.birt.feature.feature.group 0.0.0 > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.birt.oda.ui 1.7.0.Alpha1-v20141006-1612-B585 to bundle org.hibernate.eclipse.libs 3.8.0.; No solution found because the problem is unsatisfiable.] -> [Help 1] > {code} > Due to this problem, the JBT aggregate builds are failing: > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > NOTE: This issue may be a duplicate of JBIDE-18795. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

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 November 2014