January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-870) Summarize all features which will be installed in the installer wizard

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-870?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-870: ----------------------------- Attachment: install-soa1.png install-soa2.png > Summarize all features which will be installed in the installer wizard > ---------------------------------------------------------------------- > > Key: JBTIS-870 > URL: https://issues.jboss.org/browse/JBTIS-870 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > Attachments: devstudio-is-installer.png, inst1.png, inst1.png, install-soa1.png, install-soa2.png, jbdsis_installer_summary.png > > > I suggest to summarize all features which will be installed in Summary page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-326) UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-326?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-326. ------------------------------- Fix Version/s: Neon.3 (4.6) Resolution: Done > UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007] > ----------------------------------------------------------------------- > > Key: ERT-326 > URL: https://issues.jboss.org/browse/ERT-326 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.3 (4.6) > > > Created attachment 262788 > Add button have different label than other Add buttons > Add button in expose ports part of dialog "Run a Docker Image" have label "Add", but other Add buttons in this wizard have label "Add..."(Link containers, Data Volumes and Environment variables). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-326) UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-326?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-326: --------------------------------- Assignee: Jeff Johnston > UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007] > ----------------------------------------------------------------------- > > Key: ERT-326 > URL: https://issues.jboss.org/browse/ERT-326 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Trivial > Labels: Docker, bzira > > Created attachment 262788 > Add button have different label than other Add buttons > Add button in expose ports part of dialog "Run a Docker Image" have label "Add", but other Add buttons in this wizard have label "Add..."(Link containers, Data Volumes and Environment variables). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-326) UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-326?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-326: ------------------------------ Sprint: devex #126 January 2017 > UI: Unify Add button labels in "Run a Docker Image" dialog [EBZ#497007] > ----------------------------------------------------------------------- > > Key: ERT-326 > URL: https://issues.jboss.org/browse/ERT-326 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Trivial > Labels: Docker, bzira > > Created attachment 262788 > Add button have different label than other Add buttons > Add button in expose ports part of dialog "Run a Docker Image" have label "Add", but other Add buttons in this wizard have label "Add..."(Link containers, Data Volumes and Environment variables). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016, devex #127 February 2017 (was: devex #115 May 2016, devex #116 June 2016) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.Final > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23317: ------------------------------- Sprint: devex #120 September 2016, devex #125 December 2016, devex #127 February 2017 (was: devex #120 September 2016, devex #125 December 2016, devex #126 January 2017) > Create and use Oxygen.M5 target platform > ---------------------------------------- > > Key: JBIDE-23317 > URL: https://issues.jboss.org/browse/JBIDE-23317 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM1 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23515: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Create and use Neon.2 target platform > ------------------------------------- > > Key: JBIDE-23515 > URL: https://issues.jboss.org/browse/JBIDE-23515 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.3.Final > > > Once available in December, we should move up to Neon.2 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017