April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3367) Offline update from 8.0.x fails in installing FeedHenry

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3367: ----------------------------- Sprint: Sprint #2 April 2015 > Offline update from 8.0.x fails in installing FeedHenry > ------------------------------------------------------- > > Key: JBDS-3367 > URL: https://issues.jboss.org/browse/JBDS-3367 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 8.1.0.Beta1 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Updating from 8.0.0, 8.0.1 and 8.0.2 from the update zip causes the following error: > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > Missing requirement: org.jboss.tools.feedhenry.ui 1.0.0.Beta1-v20150225-2159-B85 requires 'bundle org.jboss.tools.vpe.cordovasim.eclipse 3.6.2' but it could not be found > Cannot satisfy dependency: > From: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85) > To: org.jboss.tools.feedhenry.ui [1.0.0.Beta1-v20150225-2159-B85] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18914: ------------------------------- Sprint: Sprint #2 April 2015 > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3286: ----------------------------- Sprint: Sprint #1 April 2015 > Remove Seam tooling from default JBDS installation > -------------------------------------------------- > > Key: JBDS-3286 > URL: https://issues.jboss.org/browse/JBDS-3286 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, installer, requirements, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already). > [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3208: ----------------------------- Sprint: Sprint #1 April 2015 > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3191: ----------------------------- Sprint: Sprint #2 April 2015 > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3163: ----------------------------- Sprint: Sprint #1 April 2015 > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3200: ------------------------------------- I am not familiar with it, but I guess it is a matter of enrollment in apple dev program and signing the installer jar. Does that sound right? > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18236) Produce better doc for project leads for how to build their component in Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18236?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18236: ------------------------------- Sprint: Sprint #2 April 2015 > Produce better doc for project leads for how to build their component in Jenkins > -------------------------------------------------------------------------------- > > Key: JBIDE-18236 > URL: https://issues.jboss.org/browse/JBIDE-18236 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Max wants a page with links to all the /build pages for all the Jenkins jobs for a given stream, ie., 4.2.luna, 4.3.mars, master. > This could be awestructed adoc, or just static HTML a la http://download.jboss.org/jbosstools/builds/cascade pages. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16970: ------------------------------- Sprint: Sprint #2 April 2015 > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19331) Links to JBDS release notes broken

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19331?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19331. --------------------------------- Verified. > Links to JBDS release notes broken > ---------------------------------- > > Key: JBIDE-19331 > URL: https://issues.jboss.org/browse/JBIDE-19331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.2.1.Final > > > This page has a link to release notes which is broken: > http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html > It points to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > The same problem happens for JBDS 8.0.1 and 8.0.0. > The correct link is e.g.: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > So it seems we just need to trim off the trailing index.html . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 April 2015