April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18742: ------------------------------- Sprint: Sprint #2 April 2015 > Only rely on rsync to publish new aggregate (remove other comparators) > ---------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015) > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19387) improve integration of integration stack jars into staged JBT / JBDS sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19387: ------------------------------- Sprint: Sprint #2 April 2015 > improve integration of integration stack jars into staged JBT / JBDS sites > -------------------------------------------------------------------------- > > Key: JBIDE-19387 > URL: https://issues.jboss.org/browse/JBIDE-19387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.2.3.Beta1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > I have this error in error log after startup of JBT: > {noformat:title=Cannot download bundle at http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin...: http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:441) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:398) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:322) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/jbosst... is pointing to non-existing http://download.jboss.org/jbosstools/discovery/staging/4.2.3.Beta1/plugin... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19018) JBT Central Discovery staging site contains early access child site in its composite*.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19018: ------------------------------- Sprint: Sprint #1 April 2015 > JBT Central Discovery staging site contains early access child site in its composite*.xml > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19018 > URL: https://issues.jboss.org/browse/JBIDE-19018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early access site into the main update site, so anyone using that site as an update site (rather than simply as the back end to Central) will see EA content as if it's from Central. > If we stop publishing this staging discovery site that includes EA content, the release process will need to be updated to pull the EA plugin from another place. > Related to JBIDE-18984 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Sprint: Sprint #2 April 2015 > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19449: ------------------------------- Sprint: Sprint #2 April 2015 > p2.director install script is finding non-IU IUs to install > ----------------------------------------------------------- > > Key: JBIDE-19449 > URL: https://issues.jboss.org/browse/JBIDE-19449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > p2.director install script is finding non-IU IUs to install such as: > {code}eclipse.buildId > java.version{code} > {code} > list.ius: > [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ... > [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties > {code} > Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Reason: here's what's in the plugin.list.properties file: > {code} > !SESSION 2015-03-13 18:06:15.934 ----------------------------------------------- > eclipse.buildId=4.5.0.I20150203-1300 > java.version=1.8.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233 > !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi > org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. > ch.qos.logback.classic=1.0.7.v20121108-1250 > ch.qos.logback.core=1.0.7.v20121108-1250 > ... > tern.server.nodejs=0.9.0.201502141213 > ternjs=0.9.0.201502141213 > Operation completed in 183432 ms. > {code} > So we need to filter out the header garbage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19449: ------------------------------- Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015) > p2.director install script is finding non-IU IUs to install > ----------------------------------------------------------- > > Key: JBIDE-19449 > URL: https://issues.jboss.org/browse/JBIDE-19449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > p2.director install script is finding non-IU IUs to install such as: > {code}eclipse.buildId > java.version{code} > {code} > list.ius: > [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ... > [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties > {code} > Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Reason: here's what's in the plugin.list.properties file: > {code} > !SESSION 2015-03-13 18:06:15.934 ----------------------------------------------- > eclipse.buildId=4.5.0.I20150203-1300 > java.version=1.8.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233 > !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi > org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. > ch.qos.logback.classic=1.0.7.v20121108-1250 > ch.qos.logback.core=1.0.7.v20121108-1250 > ... > tern.server.nodejs=0.9.0.201502141213 > ternjs=0.9.0.201502141213 > Operation completed in 183432 ms. > {code} > So we need to filter out the header garbage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19416) JBDS update site zip should not include both packed and unpacked artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19416?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19416: ------------------------------- Sprint: Sprint #2 April 2015 > JBDS update site zip should not include both packed and unpacked artifacts > -------------------------------------------------------------------------- > > Key: JBIDE-19416 > URL: https://issues.jboss.org/browse/JBIDE-19416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.3.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.3.0.Beta1 > > > JBDS 8.1.0.Beta1 update site zip is 524M and contains both packed (.pack.gz) and regular jars; no need to include both. Ideally we'd include ONLY the packed ones. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19458) Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19458?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19458: ------------------------------- Sprint: Sprint #1 April 2015 > Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion" > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19458 > URL: https://issues.jboss.org/browse/JBIDE-19458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Max wants that: > * the parameter we use in Jenkins be *jbosstools_site_stream* (underscores) and that > * the maven processes all use *jbosstools-site-stream* (dashes) > Because > * Max feels that using a different parameter in Jenkins than the value in the parent pom is more consistent & less likely to cause problems, vs. > * renaming the variable so that both use the same underscored name of jbosstools_stream. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3351: ----------------------------- Sprint: Sprint #1 April 2015 > Copyright notice refers to 2014, not 2015 > ----------------------------------------- > > Key: JBDS-3351 > URL: https://issues.jboss.org/browse/JBDS-3351 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Trivial > Fix For: 9.0.0.Alpha2 > > > The copyright notice for 9.0.0.Alpha1 reads: > ==================================== > Version: 9.0.0.Alpha1 > Build id: Alpha1-v20150216-1042-B11 > Build date: 20150216-1042 > Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved. > ==================================== > ------> Shouldn't this refer to 2004-2015? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 April 2015