February 2017 - jbosstools-issues

[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.4.4.AM1 (was: 4.4.3.Final) > 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.4.4.AM1 > > > 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.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4263: ---------------------------------- * Atlassian Connector shouldn't be accessible in Central - it was removed. JBDS-4191... apparently the devstudio update site was not moved to 4.62.0.Final (JBIDE-23652). Fixed. No more Atlassian in the JBDS IS update site. * PMD: {code}org.osgi.framework.BundleException: Error starting module. Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Layout Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Layout cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057 {code} * Integration Stack no longer has any EA components so you shouldn't be seein anything available to install: {code}!MESSAGE Option -i requires an argument.{code} * AngularJS, Arquillian: probably related to using the wrong target platform and old version of devstudio 10.2 in the composite site [1]. Please try again. [1] https://devstudio.redhat.com/10.0/stable/updates/compositeArtifacts.xml (had devstudio 10.2 and TP 4.61 instead opf devstudio 10.3 and TP 4.62) Of the above issues the only one that concerns me is PMD. Please re run your tests using the correct update sites. 1. https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... is a superset of https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c... so no need to run tests against BOTH. 2. sites with _master in the URL are now for Oxygen, not Neon. So they shouldn't be used to test the 10.x rpms. Instead use the _4.4.neon URLs as noted above. 3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging [2] and stable [3] sites? [2] https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... [3] https://devstudio.redhat.com/10.0/stable/updates/ > Problems after install from Red Hat Central into rh-eclipse46-devstudio > ----------------------------------------------------------------------- > > Key: JBDS-4263 > URL: https://issues.jboss.org/browse/JBDS-4263 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 10.4.0.AM1 > > Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23652: ------------------------------------ Additionally, while http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... was updated to 4.4.3.Final / 4.62.0.Final, it seems that https://devstudio.redhat.com/10.0/stable/updates/compositeArtifacts.xml was not updated when [~mat.booth] released the bits yesterday. So I've manually updated them: https://github.com/jbdevstudio/jbdevstudio-website/commit/1562af3b3914ef4... > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.3.Final > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23768: ------------------------------------ So, because the workflow is different for snapshots and releases, I've done this in the parent pom jobs: {code} pom=${WORKSPACE}/sources/parent/pom.xml pomVersion=$(grep "<version>" ${pom} | head -1 | sed -e "s#.*<version>$.\+$</version>.*#\1#") echo "pomVersion=${pomVersion}" > ${WORKSPACE}/env.properties # eg., 4.4.4.Final MVN="/qa/tools/opt/maven3-latest/bin/mvn -Dmaven.repo.local=${WORKSPACE}/.repository/" pushd ${WORKSPACE}/sources/parent/ if [[ ${pomVersion} == *"-SNAPSHOT" ]]; then ${MVN} deploy else ${MVN} clean deploy -DskipRemoteStaging=true -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to local" ${MVN} nexus-staging:deploy-staged -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to stage + close" ${MVN} nexus-staging:release -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: release" fi{code} > Publish tagged version of jboss tools parent pom to public repository > --------------------------------------------------------------------- > > Key: JBIDE-23768 > URL: https://issues.jboss.org/browse/JBIDE-23768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.Final, 4.4.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.Final > > > it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release. > i'm talking about org.jboss.tools:parent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23768 at 2/24/17 1:31 PM: ------------------------------------------------------------- Quick blog post about this: https://divby0.blogspot.ca/2017/02/streamline-nexus-releases-with-nexus.html Example of a job being configured to do deploy, stage, close, and release all in one: https://github.com/jbdevstudio/jbdevstudio-ci/commit/4eec3c1f152569bb05fe... was (Author: nickboldt): Quick blog post about this: https://divby0.blogspot.ca/2017/02/streamline-nexus-releases-with-nexus.html > Publish tagged version of jboss tools parent pom to public repository > --------------------------------------------------------------------- > > Key: JBIDE-23768 > URL: https://issues.jboss.org/browse/JBIDE-23768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.Final, 4.4.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.Final > > > it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release. > i'm talking about org.jboss.tools:parent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23768: ------------------------------------ Quick blog post about this: https://divby0.blogspot.ca/2017/02/streamline-nexus-releases-with-nexus.html > Publish tagged version of jboss tools parent pom to public repository > --------------------------------------------------------------------- > > Key: JBIDE-23768 > URL: https://issues.jboss.org/browse/JBIDE-23768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.Final, 4.4.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.Final > > > it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release. > i'm talking about org.jboss.tools:parent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4229: -------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.GA) > If updating CDK installation error reported > ------------------------------------------- > > Key: JBDS-4229 > URL: https://issues.jboss.org/browse/JBDS-4229 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Jeff MAURY > Labels: cdk, installer > Fix For: 10.4.0.AM1 > > Attachments: nstall.log > > > If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23768: ------------------------------------ Parent pom 4.4.3.Final and 4.3.2.Final are released: https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~pare... https://repository.jboss.org/nexus/#nexus-search;gav~org.jboss.tools~pare... Note that I had to make a couple minor changes to the pom to make it releasable: https://github.com/jbosstools/jbosstools-build/commit/1076708e273c81c6c12... Also figured out how to stage and release in a job [1], without having to go into Nexus to manually close & release stuff. Just had to add *org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7* to parent pom [2]. [1] https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven... [2] https://github.com/jbosstools/jbosstools-build/commit/403cf6c53cfa147e39f... So... in future we can make nexus releases so much easier/faster with this plugin. I'll write up the solution in more detail. cc: [~pleacu] [~mickael_istria] > Publish tagged version of jboss tools parent pom to public repository > --------------------------------------------------------------------- > > Key: JBIDE-23768 > URL: https://issues.jboss.org/browse/JBIDE-23768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.Final, 4.4.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.Final > > > it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release. > i'm talking about org.jboss.tools:parent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4123) Progress sometimes not updating for multiple file downloads

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4123?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4123: ------------------------------------- It seems so, I also saw this while testing with local dm server. It is not easy to replicate though. > Progress sometimes not updating for multiple file downloads > ----------------------------------------------------------- > > Key: JBDS-4123 > URL: https://issues.jboss.org/browse/JBDS-4123 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.4.0.AM1 > > > Namely for CDK, sometimes the progress doesn't register that it should start. The handler that should set the correct values does not seem to fire properly every time. The result is a progress bar stuck on 0% for the entirety of the download. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4123) Progress sometimes not updating for multiple file downloads

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4123?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4123: -------------------------------- Fix Version/s: 10.4.0.AM1 > Progress sometimes not updating for multiple file downloads > ----------------------------------------------------------- > > Key: JBDS-4123 > URL: https://issues.jboss.org/browse/JBDS-4123 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.4.0.AM1 > > > Namely for CDK, sometimes the progress doesn't register that it should start. The handler that should set the correct values does not seem to fire properly every time. The result is a progress bar stuck on 0% for the entirety of the download. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017