March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} > Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > So we could use this to create composite sites in folders like: > * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date) > But also to point to remote (/stable/) URLs from pointer sites, like: > * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd) > * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1) > * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup of devstudio RPM after installing from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4488: -------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > Very slow initial startup of devstudio RPM after installing from Central > ------------------------------------------------------------------------ > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Assignee: Jeff MAURY > Priority: Minor > Fix For: 11.x > > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4321: -------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > Unable to start Devstudio without -clean after install of any stuff from RH Central > ----------------------------------------------------------------------------------- > > Key: JBDS-4321 > URL: https://issues.jboss.org/browse/JBDS-4321 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.4.0.AM2 > Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7 > Reporter: Lukáš Valach > Assignee: Jeff MAURY > Fix For: 11.x > > Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt > > > When I install something from Red Hat Central and then start Devstudio without -clean then I get this error: > {code} > !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689 > !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi > !STACK 0 > java.lang.NullPointerException > {code} > There are multiple errors but this one seems to be common for multiple items. > And this window appear: > !Start_without_clean.png|thumbnail! > There is easy workaround but user won't start Devstudio with -clean and many of them could be upset. > Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean. > CC: [~psrna] [~vkadlcik] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-20177. -------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) Resolution: Won't Do > migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20177 > URL: https://issues.jboss.org/browse/JBIDE-20177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > If we can migrate this logic into the mojo... > {code} > if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then > {code} > ... we'll be able to remove this step in all jobs: > {code} > <hudson.tasks.Maven> > <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets> > <mavenName>maven-3.2.5</mavenName> > <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip > outputDirectory=${WORKSPACE}/sources > trimVersion=true > mdep.stripClassifier=true > mdep.stripVersion=true</properties> > <usePrivateRepository>false</usePrivateRepository> > <settings class="jenkins.mvn.DefaultSettingsProvider"/> > <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/> > </hudson.tasks.Maven> > {code} > ... and instead, just pass in those vars to maven: > {code} > -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing} > -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo > -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17838: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > Make discovery-site a Maven module > ---------------------------------- > > Key: JBIDE-17838 > URL: https://issues.jboss.org/browse/JBIDE-17838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central-update > Affects Versions: 4.2.0.Beta3 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.3.Final > > > Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25127) [upstream] Work to improve webtools releng

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25127?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25127. -------------------------------- Fix Version/s: 4.5.3.Final (was: 4.6.0.AM1) Resolution: Done This is pretty much done. > [upstream] Work to improve webtools releng > ------------------------------------------ > > Key: JBIDE-25127 > URL: https://issues.jboss.org/browse/JBIDE-25127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > Epic to track work done upstream at Eclipse for webtools project -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17608) improve p2diff's URI handling to support relative path folder and zips

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17608?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17608. ------------------------------ Resolution: Won't Do > improve p2diff's URI handling to support relative path folder and zips > ---------------------------------------------------------------------- > > Key: JBIDE-17608 > URL: https://issues.jboss.org/browse/JBIDE-17608 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: LATER > > > Instead of having to type: > {code} > p2diff file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target/jbtearlyaccess-multiple.target.repo/ file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target_FULL/jbtearlyaccess-multiple.target.repo/ > {code} > I'd like to see it work for > {code} > p2diff target target2 > or > p2diff site.zip site2.zip > {code} > So we need a few things: > a) find the nested repo in the specified folder (if not in `pwd` look in child folders for a p2 repo or repo zip) > b) better error reporting if the specified folders aren't repos or don't contain repos (right now p2diff does NOTHING if it doesn't like the URIs stated > c) if a local path exists, prepend file:// onto the file path so it behaves like a p2 URI > d) if a local repo zip found then prepend jar:file:// and append !/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24182. -------------------------------- Fix Version/s: 4.6.0.AM1 (was: 4.6.x) Resolution: Won't Do > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM1 > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25598) TP: update target platform & Central to Oxygen.3a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25598?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25598: ------------------------------- Sprint: devex #145 February 2018, devex #146 March 2018, devex #147 April 2018 (was: devex #145 February 2018, devex #146 March 2018) > TP: update target platform & Central to Oxygen.3a > ------------------------------------------------- > > Key: JBIDE-25598 > URL: https://issues.jboss.org/browse/JBIDE-25598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final, 4.5.x > > > Switch to the latest Oxygen.3. Bits will be available starting in 4.5.3.AM2 sprint but won't be GA until 4.5.3.AM3 sprint. Then we'll move up to Oxygen.3a and Jetty 9.4.9 [1] for the Final/GA sprint. > Also need to update to Spring 3.9.3 [2] in Central. > [1] http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.4.9.v201803... > [2] http://dist.springsource.com/release/TOOLS/update/e4.7 > May need an update to 9.4.10 if it's released soon (bug fix in Fedora - ping Mat for details) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-533?page=com.atlassian.jira.plugin.sy... ] Nick Boldt closed ERT-533. -------------------------- Resolution: Done > enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533] > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ERT-533 > URL: https://issues.jboss.org/browse/ERT-533 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) > > > As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately. > We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines. > For this to work, we need two things: > a) all components must build with Tycho 1.0 > b) a staging and stable URL must be provided against which to compare versions. > The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build: > * http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-201... > * http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222... > It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 March 2018