January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23677: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.Final > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23677: ------------------------------------ Assign to Fred for review and merge of PR. If you change the value of the default.value in the src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties, you can see what errors are reported to break the build. Only values that will be accepted for parent pom 4.4.3.AM2 are 4.4.3.AM2 or 4.4.3.AM2.Final. You can verify this by setting those values or can break the build by setting 4.4.4.foo or 4.4.2.bar, etc. > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.AM2 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23677: ---------------------------------- Assignee: Fred Bricon (was: Nick Boldt) > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.AM2 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23677: ------------------------------------ PR: https://github.com/jbosstools/jbosstools-base/pull/553 depends on https://github.com/jbosstools/jbosstools-maven-plugins/commit/157388bd6c1... > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[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 commented on JBTIS-870: ---------------------------------- Corrected - see https://github.com/jbdevstudio/jbdevstudio-product/pull/444 !install-soa1.png|thumbnail! !install-soa2.png|thumbnail! > 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)

8 years, 11 months

1
0
0 / 0

[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)

8 years, 11 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)

8 years, 11 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)

8 years, 11 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)

8 years, 11 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)

8 years, 11 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 January 2017