September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20843) enable automated cleanup for versionwatch reports

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20843: ---------------------------------- Summary: enable automated cleanup for versionwatch reports Key: JBIDE-20843 URL: https://issues.jboss.org/browse/JBIDE-20843 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 Reporter: Nick Boldt Currently, versionwatch dumps 4 log files into a folder; 1000s of builds later, the folder is unmanageable. So, migrate to use rsync.sh instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20836) Xcodebuild is failing with cordova-ios >= 3.9.0

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20836?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-20836: -------------------------------------- Fixed on master and PR for 4.3.x is https://github.com/jbosstools/jbosstools-aerogear/pull/148 > Xcodebuild is failing with cordova-ios >= 3.9.0 > ----------------------------------------------- > > Key: JBIDE-20836 > URL: https://issues.jboss.org/browse/JBIDE-20836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478645 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20779) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20779?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20779. ------------------------------ Resolution: Done * versionwatch updated to new version 0.4.100 (in prep for fixes in master such as JBDS-3531) * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat... upadted to include versions of JBDS (9|10) instead of (8|9) * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatc... >= 2879 * output: http://download.jboss.org/jbosstools/neon/snapshots/builds/devstudio.vers... * build-ci updated to 4.4.0.Alpha1 * new job created: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-ci_... * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-ci_4... >=1 * output: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20779 > URL: https://issues.jboss.org/browse/JBIDE-20779 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3532: ------------------------------------- That should do it, but I haven't tested it. > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20803 at 9/30/15 12:34 PM: -------------------------------------------------------------- {quote} a) it is mixing a stable release with snapshots {quote} Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA. But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't. {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152} jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi... {code} Looking at the section of the file I think you were referring to, I see that we've already fixed the problem you were reprting since the URL for JBDS IS discovery is now much simpler - https://devstudio.redhat.com/9.0/staging/updates/ {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L133-L141} ### when staging 9.0.0.GA (CR2) jboss.discovery.directory.url|devstudio|9.0.0.GA=https://devstudio.redhat... jboss.discovery.site.url|devstudio|9.0.0.GA=https://devstudio.redhat.com/... jboss.discovery.earlyaccess.site.url|devstudio|9.0.0.GA=https://devstudio... # 4.3.mars version of devstudio-earlyaccess.properties should be edited here, so the discovery job can fetch it: https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.GA=https://devstudio... # JBDSIS is not yet live so point at latest JBDS site instead #jboss.discovery.site.integration-stack.url|devstudio|9.0.0.GA=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/ jboss.discovery.site.integration-stack.url|devstudio|9.0.0.GA=https://dev... {code} Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file. was (Author: nickboldt): {quote} a) it is mixing a stable release with snapshots {quote} Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA. But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't. {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152} jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi... {code} Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20803: ------------------------------------ {quote} a) it is mixing a stable release with snapshots {quote} Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA. But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't. {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152} jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi... {code} Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ] Mickael Istria reassigned JBDS-3533: ------------------------------------ Assignee: Denis Golovin (was: Mickael Istria) > Unable to update/install the plug-ins > ------------------------------------- > > Key: JBDS-3533 > URL: https://issues.jboss.org/browse/JBDS-3533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Environment: Development > Reporter: Vikram Jammula > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.x > > Attachments: check Updates.png, security.jpg > > > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3532: -------------------------------------- Here is a suggested pull request to support the .pack.gz-less repositories without rebuilding anything: https://github.com/jbdevstudio/jbdevstudio-product/pull/342 I didn't yet see it at work, I'm trying it locally but it takes time. > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3532: ------------------------------------- Nick seems to be right, this is Jenkins project configuration issues, build itself does not have this problem. > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3532?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3532: ------------------------------------ The important thing is that we provide a clean install experience - no update notifications when there is no update - and no confusing version numbers and timestamps. Thx! > Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3532 > URL: https://issues.jboss.org/browse/JBDS-3532 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.CR2 > Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar > jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip > downloaded from > http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.... > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.GA > > > The update site zip has a later timestamp than what you get from the installer but it is still the same build. > So you can basically update to the same build because of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 September 2015