October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20993: ------------------------------------ /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting *sigh* I will remove the symlinks on download.jboss.org and assume you are OK with keeping them on devstudio.redhat.com. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I completely get what you mean. I opened the jira to get the misleading 9.0 and 10.0 folders removed ASAP. Can we get that fixed independent on what scripts optimizations you might want to do in future ? I don't see whether you use neon or 10.0 that this changes anything. You still need *one* variable for the stream. Whether that is called 10.0 or neon should not change anything. The exact same number segments are there - I simply do not get why it matters if one is 10.0 or neon nor why you need symlinks for this. Your scripts just need one thing <property name="stream">10.0</property> <property name="stream">neon</property> And you then use ${stream} in the locations that needs this separated out. then there are zero differences, except exact same difference that you need devstudio.redhat.com in one, and download.jboss.org in another. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21001: ------------------------------------ New PRs to show how jbosstools-jst could depend on the EA TP (which contains 3rd party stuff only). Note that the EA TP is currently ONLY AngularJS but some day it could contain more. (It used to also contain Tern.) https://github.com/jbosstools/jbosstools-jst/pull/544 https://github.com/jbosstools/jbosstools-jst/pull/545 Note the fluffed up instructions and comments -- think people might see it this way? :D > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21003: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 Docker Tools 4.2.0 is targeting Mars, correct? [~xcoulon]? > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21003: -------------------------------------- Assignee: Nick Boldt > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21003: ------------------------------------- Summary: Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 Key: JBIDE-21003 URL: https://issues.jboss.org/browse/JBIDE-21003 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.3.x Reporter: Jeff Cantrill *Reason:* update linuxtools.docker to expose ImageSearch wizard *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 *Version:* .... *License and owner:* ... *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* Leave empty *Include Sources:* Yes *Affected JBoss Tools components:* jbosstools-openshift *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} If applicable: *non-p2 repository:* ... *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20957. ---------------------------------- Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground] > ------------------------------------------------------------ > > Key: JBIDE-20957 > URL: https://issues.jboss.org/browse/JBIDE-20957 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20947: -------------------------------------- Assignee: Nick Boldt (was: Rob Stryker) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 > ----------------------------------------------- > > Key: JBIDE-20947 > URL: https://issues.jboss.org/browse/JBIDE-20947 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20993: ------------------------------------ You misunderstand me. I was suggesting that instead of using: * /mars/ and /neon/ for JBT and * /9.0/ and /10.0/ for JBDS (see how they're different?) we could instead use: * /mars/ and /neon/ for JBT and * /mars/ and /neon/ for JBDS (see how they're the same?). So, no more symlinks would be needed, since it'd be the same path segment on both servers. That said, obviously the stable URL for JBDS 9 would have to stay as https://devstudio.redhat.com/9.0/stable/updates/ But we could have this for JBDS 10: https://devstudio.redhat.com/neon/stable/updates/ https://devstudio.redhat.com/neon/development/updates/ https://devstudio.redhat.com/neon/staging/updates/ https://devstudio.redhat.com/neon/snapshots/updates/ which would map nicely to the URLs for JBT 4.4: http://download.jboss.org/jbosstools/neon/stable/updates/ http://download.jboss.org/jbosstools/neon/development/updates/ http://download.jboss.org/jbosstools/neon/staging/updates/ http://download.jboss.org/jbosstools/neon/snapshots/updates/ -- As to where/how I have scripts which require a different variable depending on which product is being published/released, well, here's an example: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/po... (uses devstudioReleaseVersion = 10.0) vs. https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (uses eclipseReleaseName = neon) If they both used *eclipseReleaseName* in the path, there'd be fewer places to have the code deviate. Similarly the release guide for JBT/JBDS, pushing bits to (or from staging) uses nearly-identical scriptlets to copy bits around. But to further automate that via an actual script, we need more synchronicity between the releases so less things are different and the same script can be used for multiple purposes. Thus a script like https://github.com/jbosstools/jbosstools-build-ci/pull/137/files could simply use `-eclipseReleaseName neon` instead of needing a different path segment for JBDS. --- So, TL;DR: are you cool with these URLs for JBDS 10? Or do you need to see a /10.0/ path segment in there instead of /neon/ (cc: [~akazakov] ) ? https://devstudio.redhat.com/neon/stable/updates/ https://devstudio.redhat.com/neon/development/updates/ https://devstudio.redhat.com/neon/staging/updates/ https://devstudio.redhat.com/neon/snapshots/updates/ > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20565) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20565?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20565. --------------------------------- Resolution: Done Fixed in master/4.3.x > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-20565 > URL: https://issues.jboss.org/browse/JBIDE-20565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015