June 2015 - jbosstools-issues - Jboss List Archives

[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: ------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > 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.Beta2 > > > 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.15#6346)

10 years, 10 months

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 reassigned JBIDE-19387: ---------------------------------- Assignee: Paul Leacu (was: Nick Boldt) > 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: Paul Leacu > Fix For: 4.3.0.Beta2 > > > 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.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19702) installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19702?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19702: ------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > installFromCentral.sh should support installing from central site+plugin OR earlyaccess site+plugin > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-19702 > URL: https://issues.jboss.org/browse/JBIDE-19702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Today, installFromCentral.sh assumes two incorrect things: > a) central URL is always different than the JBT/JBDS site URL [no longer true, since JBT/JBDS & Central content are now co-located] > b) the plugin to parse for IUs is ONLY the central one, not the EA one [we should parse ONE or BOTH, depending on cmdline flag] > {code} > # get a list of IUs to install from the Central site (based on the discovery.xml -> plugin.jar -> plugin.xml) > CENTRAL_URL=${INSTALL_PLAN#*,} # includes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL > if [[ $CENTRAL_URL != $INSTALL_PLAN ]]; then > # echo $CENTRAL_URL > wget ${CENTRAL_URL} -q --no-check-certificate -N -O directory.xml > PLUGINJAR=`cat ${WORKSPACE}/directory.xml | egrep "org.jboss.tools.central.discovery_|com.jboss.jbds.central.discovery_" | sed "s#.\+url=\"$.\+$.jar\".\+#\1.jar#"` > # echo "Got $PLUGINJAR" > CENTRAL_URL=${SITES#*,} # excludes discovery.xml # echo CENTRAL_URL = $CENTRAL_URL > wget ${CENTRAL_URL}/${PLUGINJAR} -q --no-check-certificate -N -O plugin.jar > unzip -oq plugin.jar plugin.xml > ... > {code} > https://github.com/jbosstools/jbosstools-build-ci/blob/4.3.x/util/install... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17281: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.3.0.Beta2 > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and reduce clutter in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse > - etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19997) Add possibility to select interface and abstract class in New Batch Artifact wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19997?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19997: ---------------------------------------- Let's try Slava's solution and see how it looks. > Add possibility to select interface and abstract class in New Batch Artifact wizard > ----------------------------------------------------------------------------------- > > Key: JBIDE-19997 > URL: https://issues.jboss.org/browse/JBIDE-19997 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > I think that in every bigger enterprise project you would have your own implementation of batch interfaces and abstract classes. So the possibility to select them in the New Batch Artifact wizard would be very useful. > Maybe you could just put there interface and abstract class selection section from New Java Class wizard and pre-define the right batch classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17281: ---------------------------------- Description: The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and reduce clutter in jbosstools modules like: - remove <version>${tychoVersion}</version> - move jacoco plugin to tests/pom.xml - move update site manipulations to site/pom.xml - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse - etc. was: The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like: - remove <version>${tychoVersion}</version> - move jacoco plugin to tests/pom.xml - move update site manipulations to site/pom.xml - etc > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.3.0.Beta2 > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and reduce clutter in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse > - etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3374) Remove org.eclipse.cvs feature from JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3374?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3374: ----------------------------- CDW release: - (was: ?) > Remove org.eclipse.cvs feature from JBDS > ---------------------------------------- > > Key: JBDS-3374 > URL: https://issues.jboss.org/browse/JBDS-3374 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import feature="org.eclipse.cvs"/> > {quote} > I can't see any reason why we'd do that in 2015. > Burr Sutter, Len DiMaggio, Max Rydahl Andersen : is there any client requirement about CVS support? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3374) Remove org.eclipse.cvs feature from JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3374?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3374: ----------------------------- CDW devel_ack: - (was: ?) Status: New (was: New) So, the gist here is that: * Max says "keep it because still heavily used. If removed, it should be in Central." * Mus says "drop it because Eclipse dropped it, DON'T include in Central." Therefore, I'm inclined to reject this, and keep CVS in JBDS. > Remove org.eclipse.cvs feature from JBDS > ---------------------------------------- > > Key: JBDS-3374 > URL: https://issues.jboss.org/browse/JBDS-3374 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import feature="org.eclipse.cvs"/> > {quote} > I can't see any reason why we'd do that in 2015. > Burr Sutter, Len DiMaggio, Max Rydahl Andersen : is there any client requirement about CVS support? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18846: ------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19598: ---------------------------------- Assignee: Mickael Istria > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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