September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24909) CDI New and Noteworthy for 4.5.1.AM2

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24909?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24909. -------------------------------- Verified, closing. > CDI New and Noteworthy for 4.5.1.AM2 > --------------------------------------------------- > > Key: JBIDE-24909 > URL: https://issues.jboss.org/browse/JBIDE-24909 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.1.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed CDI JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for CDI, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for CDI by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24908 #comment Create N&N for CDI 4.5.1.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for CDI for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25009) Migrate Installer and RPM tests to RedDeer 2

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25009?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-25009: -------------------------------------- Realised that I forgot to migrate Central-RPM-UI test. PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/144 > Migrate Installer and RPM tests to RedDeer 2 > -------------------------------------------- > > Key: JBIDE-25009 > URL: https://issues.jboss.org/browse/JBIDE-25009 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM3 > > > We have to migrate Installer, BYOE, Central and RPM the tests to RD2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugi... ] Wolfgang Knauf updated JBIDE-25095: ----------------------------------- Description: When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet). To make this code compile, two jar files are required: %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar I think the runtime should add them by default. was: When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [link Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet). To make this code compile, two jar files are required: %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar I think the runtime should add them by default. > WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path > ----------------------------------------------------------------------------- > > Key: JBIDE-25095 > URL: https://issues.jboss.org/browse/JBIDE-25095 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Reporter: Wolfgang Knauf > Priority: Minor > > When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet). > To make this code compile, two jar files are required: > %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar > %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar > I think the runtime should add them by default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created JBIDE-25095: -------------------------------------- Summary: WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path Key: JBIDE-25095 URL: https://issues.jboss.org/browse/JBIDE-25095 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: server Affects Versions: 4.5.0.Final Reporter: Wolfgang Knauf Priority: Minor When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [link Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet). To make this code compile, two jar files are required: %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar I think the runtime should add them by default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25094) Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25094?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-25094: ------------------------------ Fix Version/s: 4.5.1.AM3 > Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn' > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25094 > URL: https://issues.jboss.org/browse/JBIDE-25094 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.5.1.AM2 > Reporter: Koen Aers > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25094) Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn'

by Koen Aers (JIRA)

Koen Aers created JBIDE-25094: --------------------------------- Summary: Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn' Key: JBIDE-25094 URL: https://issues.jboss.org/browse/JBIDE-25094 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 4.5.1.AM2 Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25094) Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25094?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-25094: --------------------------------- Assignee: Koen Aers > Remove unused imports in 'org.jboss.tools.hibernate.jpt.core.internal.context.HibernateColumn' > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25094 > URL: https://issues.jboss.org/browse/JBIDE-25094 > Project: Tools (JBoss Tools) > Issue Type: Task > Affects Versions: 4.5.1.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24764 at 9/22/17 4:07 PM: ------------------------------------------------------------- Latest speculation: maybe we're having issues because slaves are being used for more than one concurrent build, and the fuse tools build doesn't like to share. Only example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or real-weight job being run in parallel with jbosstools-fuse_master. !two_jobs_in_parallel.png|thumbnail! If flyweight jobs are in fact to blame here, I can prevent flyweights that run matrixes from running on rhel7-devstudio-releng. Or, we could play around with concurrent build throttling but this isn't something in use on fusesource jenkins so might be a waste of time: !throttle-concurrent.png|thumbnail! was (Author: nickboldt): Latest speculation: maybe we're having issues because slaves are being used for more than one concurrent build, and the fuse tools build doesn't like to share. Only example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or real-weight job being run in parallel with jbosstools-fuse_master. !two_jobs_in_parallel.png|thumbnail! > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png, fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png, fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, throttle-concurrent.png, two_jobs_in_parallel.png > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24764: ------------------------------- Attachment: throttle-concurrent.png > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png, fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png, fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, throttle-concurrent.png, two_jobs_in_parallel.png > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24764 at 9/22/17 4:05 PM: ------------------------------------------------------------- Latest speculation: maybe we're having issues because slaves are being used for more than one concurrent build, and the fuse tools build doesn't like to share. Only example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or real-weight job being run in parallel with jbosstools-fuse_master. !two_jobs_in_parallel.png|thumbnail! was (Author: nickboldt): Latest speculation: maybe we're having issues because slaves are being used for more than one concurrent build, and the fuse tools build doesn't like to share. Only example seen so far of a rhel7-devstudio-releng slave being used for parallel jobs is this one, which shows a flyweight and a real job started in parallel. No proof yet of a fly- or real-weight job being run in parallel with jbosstools-fuse_master. > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png, fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png, fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, two_jobs_in_parallel.png > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- 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