December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25127) [upstream] Work to improve webtools releng

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25127?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25127: ------------------------------- Sprint: devex #139 October 2017, devex #142 December 2017 (was: devex #139 October 2017, devex #141 December 2017) > [upstream] Work to improve webtools releng > ------------------------------------------ > > Key: JBIDE-25127 > URL: https://issues.jboss.org/browse/JBIDE-25127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > > Epic to track work done upstream at Eclipse for webtools project -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-531) Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-531?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-531: --------------------------- Sprint: devex #142 December 2017 > Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084] > ----------------------------------------------------------------------------------- > > Key: ERT-531 > URL: https://issues.jboss.org/browse/ERT-531 > Project: Eclipse Release Train > Issue Type: Task > Components: Community > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Critical > Labels: Hudson, bzira > > A few WTP plugins need to build with the old JDK and a WTP toolchains.xml is set up. It works fine with Maven 3.2.5 but fails with Maven 3.3.1. > The current investigation showed that instead of using the WTP specific toolchains.xml which is defined in the Hudson build configuration, a common toolchains /opt/public/common/maven-toolchains.xml is linked as the user toolchains. > genie.gef ~> ll ~/.m2 > [....] > lrwxrwxrwx 1 genie.gef tools.gef 37 23 févr. 04:05 settings.xml -> /opt/public/common/maven-settings.xml > lrwxrwxrwx 1 genie.gef tools.gef 39 23 févr. 04:05 toolchains.xml -> /opt/public/common/maven-toolchains.xml > I wonder how Maven 3.2.5 can pick up the customized toolchains but not 3.3.1. It would be great if Maven 3.3.1 can pick up the customized toolchains as 3.2.5. > At the same time, I wonder whether the common toolchains file can be changed to support IBM JDK 1.4. Its current JDK 1.4 points to the Sun's which is broken and generates compile errors. > <toolchain> > <type>jdk</type> > <provides> > <id>J2SE-1.4</id> > </provides> > <configuration> > <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome> > </configuration> > </toolchain> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Sprint: (was: devex #141 December 2017) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Sprint: devex #125 December 2016 (was: devex #125 December 2016, devex #141 December 2017) > [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25349) Renaming of existing CDK server adapter is not applied everywhere

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25349?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25349: ------------------------------- Sprint: devex #142 December 2017 > Renaming of existing CDK server adapter is not applied everywhere > ----------------------------------------------------------------- > > Key: JBIDE-25349 > URL: https://issues.jboss.org/browse/JBIDE-25349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24787: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.AM3) > Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.x > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24787) Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24787: ------------------------------------- Sprint: devex #137 September 2017 (was: devex #137 September 2017, devex #142 December 2017) > Wildfly (and other) Server adapter(s): provide defaults in code if docker image has no metadata, nor user settings are provided > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24787 > URL: https://issues.jboss.org/browse/JBIDE-24787 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter, wildfly > Fix For: 4.5.x > > > The changes in the PR for JBIDE-24184 is overhauling the server adapter(s) code. We should make sure that the updated code allows individual server adapters (we have per app-type - eap, wildfly, nodejs, etc.) can provide their own defaults in code. As discussed in the parent jira to this: https://issues.jboss.org/browse/JBIDE-24548?focusedCommentId=13428424&pag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25295) Cannot use minishift binary instead of CDK in CDK server adapter in IDE

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25295?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25295: ------------------------------- Sprint: devex #142 December 2017 > Cannot use minishift binary instead of CDK in CDK server adapter in IDE > ----------------------------------------------------------------------- > > Key: JBIDE-25295 > URL: https://issues.jboss.org/browse/JBIDE-25295 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.x > > Attachments: Screenshot_20171025_134414.png > > > I am curious what if user will want to use upstream minishift binary for CDK 3.x (3.2+) server adapter. It is not possible now. > Is there a reason for not allowing user to use upstream minishift binary? Before we did not distinguish between CDK 3.1 and 3.2, it was possible in my opinion. We lost this option when new adapter was added and we started to check CDK v.3.x.x version string for two CDK 3.1 and CDK 3.2 binaries. > [~rob.stryker] [~jeffmaury] [~mmalina] WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24961) New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24961?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24961: ------------------------------------- Sprint: devex #142 December 2017 (was: devex #141 December 2017) > New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24961 > URL: https://issues.jboss.org/browse/JBIDE-24961 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25434) Connection specific oc location taken even after override oc location is reset

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25434?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25434: ------------------------------- Sprint: devex #142 December 2017 > Connection specific oc location taken even after override oc location is reset > ------------------------------------------------------------------------------ > > Key: JBIDE-25434 > URL: https://issues.jboss.org/browse/JBIDE-25434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: openshift, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.5.x > > > ASSERT: have no oc binary configured at preferences > ASSERT: have an oc configured at the connection level and override set > EXEC: create a server adapter > ASSERT: no warning about oc version should be displayed > ASSERT: reset the oc override flag for the connection > EXEC: create a server adapter > ASSERT: a warning about oc should be set, but it is not -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017