September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-20985) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20985?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-20985. ------------------------------- Resolution: Rejected Since I haven't heard anything on this issue in a long time, I'm closing it. As far as I recall, almost every single error is 100% correct and has to do with errors in teh schema themselves. > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBIDE-20985 > URL: https://issues.jboss.org/browse/JBIDE-20985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.3.Final > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.1.AM2 > > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20985) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20985?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20985: -------------------------------- Fix Version/s: 4.5.1.AM2 (was: LATER) > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBIDE-20985 > URL: https://issues.jboss.org/browse/JBIDE-20985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.3.Final > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.1.AM2 > > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4358) include EAP 7.1 in devstudio 11 installer?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4358?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4358: ----------------------------------- This should be ready in the next week or two. [~dgolovin1] Is this doable? > include EAP 7.1 in devstudio 11 installer? > ------------------------------------------ > > Key: JBDS-4358 > URL: https://issues.jboss.org/browse/JBDS-4358 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, server, upstream > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.1.0.GA > > > EAP 7.1.0 is due in Sept/Oct 2017 > We should decide if we want to include that in the devstudio 11.1 & equivalent devsuite installers. > [~jeffmaury] [~mbenitez] [~tim.moran] [~jpallich] please vote +1 or -1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4160) Closing terminal opened during Container Development Environment start terminates vagrant process

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4160?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-4160. ------------------------------- Resolution: Won't Fix This can't be done. The terminal *is* the connection, and the act of closing it effectively closes the pipe / command. Since cdk3 won't be using terminal view, this is alright I guess. But cdk2 will just have to not close the terminal view =/ > Closing terminal opened during Container Development Environment start terminates vagrant process > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4160 > URL: https://issues.jboss.org/browse/JBDS-4160 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 10.1.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 11.1.0.AM2 > > > Closing terminal with running vagrant up command terminates startup process without any warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4358) include EAP 7.1 in devstudio 11 installer?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4358?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4358: ------------------------------ Fix Version/s: 11.1.0.GA (was: 11.x) > include EAP 7.1 in devstudio 11 installer? > ------------------------------------------ > > Key: JBDS-4358 > URL: https://issues.jboss.org/browse/JBDS-4358 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, server, upstream > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.1.0.GA > > > EAP 7.1.0 is due in Sept/Oct 2017 > We should decide if we want to include that in the devstudio 11.1 & equivalent devsuite installers. > [~jeffmaury] [~mbenitez] [~tim.moran] [~jpallich] please vote +1 or -1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4160) Closing terminal opened during Container Development Environment start terminates vagrant process

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4160?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4160: ------------------------------ Fix Version/s: 11.1.0.AM2 (was: 11.x) > Closing terminal opened during Container Development Environment start terminates vagrant process > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4160 > URL: https://issues.jboss.org/browse/JBDS-4160 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 10.1.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 11.1.0.AM2 > > > Closing terminal with running vagrant up command terminates startup process without any warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24991) Improve server port offset detection by inspecting configured system properties

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24991?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24991: ------------------------------------- To understand your usecase, I'm assuming you: 1) Create a new server in local+filesystem mode 2) Open teh server editor 3) Open the launch configuration 4) Add the sysprops you want to use to override the standalone.xml values 5) Save the launch configuration 6) Get annoyed that the server editor is not updated with the new values from the launch config The launch configuration pulls data from the server editor, and not the other way around. The server editor can pull data from the underlying xml files... but those xml files won't know what value is being passed into the sysprop. If you're going through the effort of customizing the launch configuration's VM args tab, then you also need to in to the server editor and update the port section. We cannot introduce a circular logic here without breaking the tools. What you're basically suggesting is that: 1) User requests launch config 2) Launch config tries to get ports from server editor 3) Server object tries to get ports from launch config sysprops. 4) Since launch config isn't made yet, a new launch config is created, and tries to get ports from server editor 5) Server object tries to get ports from launch config sysprops. 6) Since launch config isn't made yet, a new launch config is created, and tries to get ports from server editor 7) Server object tries to get ports from launch config sysprops. 8) etc etc etc. This would be an endless loop. Basically, you can change the xml file directly, and have your changes automatically detected. But if you are opening the launch config and adding custom flags, then you must also override the port section in the editor so the tooling knows what ports to access on the server. Does this make sense to you? > Improve server port offset detection by inspecting configured system properties > ------------------------------------------------------------------------------- > > Key: JBIDE-24991 > URL: https://issues.jboss.org/browse/JBIDE-24991 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Environment: JBDS11, WF10 > Reporter: Vsevolod Golovanov > Assignee: Rob Stryker > Fix For: 4.5.x > > > The default Wildfly standalone.xml config has port offset configured like this: > {code} > <socket-binding-group ... port-offset="${jboss.socket.binding.port-offset:0}"> > {code} > With the way our configuration process is set up we don't change that. Instead we add a system property to the same config file: > {code} > <system-properties> > <property name="jboss.socket.binding.port-offset" value="10"/> > </system-properties> > {code} > The problem is JBoss Tools doesn't detect this currently. It could be improved to inspect the port-offset attribute and find the corresponding system property value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24939: ------------------------------- Sprint: (was: devex #137 September 2017) > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions_sorted_no_featurejars_no_sources.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff.txt > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24939: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions_sorted_no_featurejars_no_sources.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff.txt > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4530) Work to remove all upstream 3rd party deps in the devstudio rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4530?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4530: ----------------------------- Fix Version/s: 11.1.0.AM3 (was: 11.1.0.AM2) > Work to remove all upstream 3rd party deps in the devstudio rpm > --------------------------------------------------------------- > > Key: JBDS-4530 > URL: https://issues.jboss.org/browse/JBDS-4530 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > This is a wrapper issue for a number of subtasks and linked issues related to eliminating the 3rd party plugins in the devstudio copr rpm, so that it can ultimately be built w/ brew. > Tasks include: > * add rpms already in Fedora to SCL/DevTools (eg., Datatools, WTP Dali/JPT) > * create new rpms in Fedora (buildship, recommenders/snipmatch, sapphire[1], m2e & extras[2], m2e-wtp & extras[3], tern.java) > * removal of old/duplicate versions in the target platform (javax.activation, guava, jetty, asm, aries > * ensure we're using the latest linuxtools/docker tools (including new features/plugins added for 6.1/6.1.1) > [1] may require contributing a Maven/Tycho build upstream to that project so we can then consume it in Koji/Brew > [2] m2e extras include: buildhelper, egit, mavenarchiver > [3] m2e.wtp extras include: jaxrs, jpa, jsf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017