March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25774) Create New and Noteworthy for 4.5.3.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25774?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25774: ------------------------------- Story Points: 8 > Create New and Noteworthy for 4.5.3.AM3 > --------------------------------------- > > Key: JBIDE-25774 > URL: https://issues.jboss.org/browse/JBIDE-25774 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.3.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.3.AM2) > [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.3.AM3 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Sprint: devex #139 October 2017, devex #146 March 2018 (was: devex #139 October 2017) > [release] Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.3.AM3 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25585) release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25585?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25585: ------------------------------- Fix Version/s: 4.6.0.AM1 > release webtools site for Eclipse 4.8 Photon to so WTP 3.10 discovery upstream can find it > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25585 > URL: https://issues.jboss.org/browse/JBIDE-25585 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM1, 4.6.0.Final > > > Need a semi-working placeholder (even if it's a CI build) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > Once we release 4.6.0.Final, we can then update the symlink to point here: > http://download.jboss.org/jbosstools/photon/stable/updates/ > Upstream issue: > https://bugs.eclipse.org/529801 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25750) fix-versions pulls wrong versions of IUs from wtp repo when updating .target file

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25750?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25750: ------------------------------- Sprint: devex #145 February 2018, devex #146 March 2018 (was: devex #145 February 2018) > fix-versions pulls wrong versions of IUs from wtp repo when updating .target file > --------------------------------------------------------------------------------- > > Key: JBIDE-25750 > URL: https://issues.jboss.org/browse/JBIDE-25750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.5.3.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > > For 4.71.x, using tychoVersion=1.1.0 and jbossTychoPluginsVersion=1.1.0-SNAPSHOT in the root pom of jbosstools-target-platforms, I can validate and mirror the TP locally. > For 4.72.x, same thing. > But for 4.73.x, I get incorrect versions of the wtp feature.groups. > {code} > + <unit id="org.eclipse.jst.enterprise_ui.feature.feature.group" version="3.9.2.v201802222200"/> > + <unit id="org.eclipse.jst.web_core.feature.feature.group" version="3.9.1.v201802222200"/> > + <unit id="org.eclipse.jst.web_ui.feature.feature.group" version="3.9.0.v201802222200"/> > + <unit id="org.eclipse.wst.ws_ui.feature.feature.group" version="3.8.1.v201802222200"/> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4603) RPM should depend on tern rpmbuildship/gradle rpms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4603?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4603. ---------------------------- Resolution: Won't Do > RPM should depend on tern rpmbuildship/gradle rpms > -------------------------------------------------- > > Key: JBDS-4603 > URL: https://issues.jboss.org/browse/JBDS-4603 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.3.0.AM2 > > > RPM should depend on upstream buildship & grade tooling commons rpm(s). Depends on getting this done in Fedora and devtools channel first. > See https://github.com/gradle/tooling-commons > We probably want to contribute a maven-based build for this too, so that we can use it in the RPMs rather than needing to use gradle to build the rpms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4612) RPM should depend on o.j.t.maven.apt and o.j.t.maven.sourcelookup features from upstream RPMs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4612?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4612. ---------------------------- Resolution: Won't Do > RPM should depend on o.j.t.maven.apt and o.j.t.maven.sourcelookup features from upstream RPMs > --------------------------------------------------------------------------------------------- > > Key: JBDS-4612 > URL: https://issues.jboss.org/browse/JBDS-4612 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.3.0.AM2 > > > RPM should depend on upstream o.j.t.maven.apt and o.j.t.maven.sourcelookup. Depends on getting this done in Fedora (Koji) and devtools (Brew) first. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25736: ------------------------------- Sprint: devex #145 February 2018, devex #146 March 2018 (was: devex #145 February 2018) > deprecate features from JBoss Tools with low usage / low development > -------------------------------------------------------------------- > > Key: JBIDE-25736 > URL: https://issues.jboss.org/browse/JBIDE-25736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > Attachments: Screenshot 2018-03-02 14.51.03.png > > > This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked. > * jbosstools-portlet > * jbosstools-aerogear > * jbosstools-browsersim > * jbosstools-livereload > * {color:red}-jbosstools-webservices-{color} > * {color:red}-jbosstools-javaee-{color} > * {color:red}-jbosstools-forge-{color} > These projects could be *removed*, since they were deprecated some time ago: > * jbosstools-freemarker > * jbosstools-arquillian > For supporting arguments, see this doc (RH only, sorry): > https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4598) Can jbosstools/devstudio depend on a single version of Guava?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4598?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4598: ----------------------------- Fix Version/s: 11.3.0.AM2 (was: 11.x) > Can jbosstools/devstudio depend on a single version of Guava? > ------------------------------------------------------------- > > Key: JBDS-4598 > URL: https://issues.jboss.org/browse/JBDS-4598 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm, target-platform, updatesite > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.3.0.AM2 > > > Currently the devstudio RPM depends on Guava 15, 18 and 21 (all three are in the devstudio TP). Can we depend on just the latest, which is going to be 23 in Fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=1481219 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4598) Can jbosstools/devstudio depend on a single version of Guava?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4598?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4598. ---------------------------- Resolution: Won't Do > Can jbosstools/devstudio depend on a single version of Guava? > ------------------------------------------------------------- > > Key: JBDS-4598 > URL: https://issues.jboss.org/browse/JBDS-4598 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm, target-platform, updatesite > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.3.0.AM2 > > > Currently the devstudio RPM depends on Guava 15, 18 and 21 (all three are in the devstudio TP). Can we depend on just the latest, which is going to be 23 in Fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=1481219 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 March 2018