November 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-111) Adapt Teiid bot tests for running with Teiid 7.x and 8.x

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/JBTIS-111?page=com.atlassian.jira.plugin.... ] Lucie Fabrikova commented on JBTIS-111: --------------------------------------- - updated pom.xml - profiles AS5-teiid7, DV6-teiid8 created - ServerManagementTest tests both teiid versions > Adapt Teiid bot tests for running with Teiid 7.x and 8.x > -------------------------------------------------------- > > Key: JBTIS-111 > URL: https://issues.jboss.org/browse/JBTIS-111 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Lucie Fabrikova > Fix For: 4.1.0.Final > > > Apapt Teiid bot tests for running with both Teiid 7.x and Teiid 8.x (EDS 5.x and EDS 6.x). The Teiid Designer 8.2 supports this backward compatibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-175) Test Teiid Designer Server Management and Integration to JBDS/JBT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/JBTIS-175?page=com.atlassian.jira.plugin.... ] Lucie Fabrikova resolved JBTIS-175. ----------------------------------- Resolution: Done > Test Teiid Designer Server Management and Integration to JBDS/JBT > ----------------------------------------------------------------- > > Key: JBTIS-175 > URL: https://issues.jboss.org/browse/JBTIS-175 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > > - focus on feature-related improvements > - area of server management, integrating to JBDS/JBT > - create AS5.1 + teiid 7.7.x, EAP 6.1 + Teiid 8.4.x servers, switching between them to preview data (tables) and execute VDB's. Open/close projects > - performing preview/execute/deploy actions when 1) NO server defined 2) Server defined but not started -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15574) Wildfly management plugin getting unsupported class version unit test errors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15574?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15574. --------------------------------- Rob said: {quote} [05.11.13 12:22:46] Rob Stryker: basically, the easiest way to prove its not a bug anymore is to ensure startup and shutdown work [05.11.13 12:22:58] Rob Stryker: if shutdown works, then it means we have no mismatched java versions [05.11.13 12:23:05] Rob Stryker: in the past when the bug existed, the shutdown command would fail [05.11.13 12:23:16] Rob Stryker: because it woiuldnt even be able to execute hte command due to bad java version {quote} Both Wildfly Alpha4 and Beta1 start and stop alright. Closing. Verified in JBDS 7.1.0.Beta1b B493 > Wildfly management plugin getting unsupported class version unit test errors > ---------------------------------------------------------------------------- > > Key: JBIDE-15574 > URL: https://issues.jboss.org/browse/JBIDE-15574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > This should be fixed in wildfly beta. There is nothing that tools can do to fix this. The relevant server jars need to rebuilt with a lower class version. > https://issues.jboss.org/browse/WFLY-2072 > We will switch our unit tests to beta1 as soon as it is available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-187) Create Recursive XML Text Source Test

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/JBTIS-187?page=com.atlassian.jira.plugin.... ] Lucie Fabrikova resolved JBTIS-187. ----------------------------------- Resolution: Done > Create Recursive XML Text Source Test > ------------------------------------- > > Key: JBTIS-187 > URL: https://issues.jboss.org/browse/JBTIS-187 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.3 > Environment: Teiid Designer 8.x > Reporter: Andrej Podhradsky > Assignee: Lucie Fabrikova > Fix For: 4.1.3 > > > The test will include: > * Importing an XML schema > * Modeling recursive XML documents > * Setting up a connection to a text source > * Using the TEXTTABLE function to access the data in a relational fashion > * Creating and deploying a VDB > * Executing queries that return XML documents -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15830: ------------------------------------------ afaik jenkins plugin is here: https://github.com/openshift/jenkins-cloud-plugin > openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15830 > URL: https://issues.jboss.org/browse/JBIDE-15830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Brenton Leanhardt > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin. > In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling. > You can see this for details: > https://github.com/openshift/origin-server/blob/master/documentation/arch... > In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15683) remove all soa-tooling variables and profiles from JBT parent pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15683?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15683. --------------------------------- Nobody has complained about anything broken, so I'm closing this. > remove all soa-tooling variables and profiles from JBT parent pom > ----------------------------------------------------------------- > > Key: JBIDE-15683 > URL: https://issues.jboss.org/browse/JBIDE-15683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > It would appear that the various soa-tooling variables & profiles included in the JBT parent pom are no longer used, or needed, so we should purge them. > {quote} > (2013-10-16 11:14:15) nboldt: pleacu: do you use any of the "soa-tooling" variables (-D) or profiles (-P) in the JBT parent pom? > (2013-10-16 11:14:57) pleacu: nboldt: me no - I use it for nexus only - it defines some user IDs and such > (2013-10-16 11:15:55) nboldt: https://github.com/jbosstools/jbosstools-build/pull/114/files so all the stuff in there with "todo" and "pleacu" is prolly safe to delete? > (2013-10-16 11:16:52) pleacu: sure > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15830 at 11/5/13 5:36 AM: ------------------------------------------------------------------- sure I had a quick look at the docs, I read what should be used in theory.. But looking at the code it looks like there's no other explanation that there's no authKey being passed to the HttpClient (if there's a non-empty autKey, it's either using "OpenShift" or prepending it to the existing user-agent). Thus I was wondering if you had looked into the authKey being passed in while debugging the jenkins-plugin. Did you? was (Author: adietish): sure I had a quick look at the docs, I read what should be used in theory.. But looking at the code it looks like there's no other explanation that there's not authKey being passed to the HttpClient (if there's a non-empty autKey, it's either using "OpenShift" or prepending it to the existing user-agent). Thus I was wondering if you had looked into the authKey being passed in while debugging the jenkins-plugin. Did you? > openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15830 > URL: https://issues.jboss.org/browse/JBIDE-15830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Brenton Leanhardt > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin. > In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling. > You can see this for details: > https://github.com/openshift/origin-server/blob/master/documentation/arch... > In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15846) Error in Error Log while creating Dynamic Web Project with Seam facet

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15846?page=com.atlassian.jira.plugi... ] Radoslav Rábara commented on JBIDE-15846: ----------------------------------------- The project is successfully created and everything works, but why is there any error in Error Log? Try it in fresh workspace and do not forget to check JavaServer Faces. > Error in Error Log while creating Dynamic Web Project with Seam facet > --------------------------------------------------------------------- > > Key: JBIDE-15846 > URL: https://issues.jboss.org/browse/JBIDE-15846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Fix For: 4.2.x > > Attachments: seam error.jpg > > > Error shows in Error Log when creating Dynamic Web Project that uses Seam: > Can't get project name to initialize SeamInstallWizardPage for ModifyFacetedProjectWizard > (An exception stack trace is not available.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15826) Incorrect Constraint Problem for JSF composite component

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15826?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15826. ------------------------------- Verified with JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493 > Incorrect Constraint Problem for JSF composite component > -------------------------------------------------------- > > Key: JBIDE-15826 > URL: https://issues.jboss.org/browse/JBIDE-15826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jsf > Affects Versions: 4.1.0.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: respin-b > Fix For: 4.1.1.Beta1 > > > First at all we must have a preference page where we can disable this validation. > There should not be any validation which is imposible to disable. > Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule. > We have such preferences/quick fixes for our validation that extends common validation framework. > But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15830: --------------------------------------------- [~bleanhar] can you paste the *Exact* user agent ? And where is the code that jenkins uses ? > openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15830 > URL: https://issues.jboss.org/browse/JBIDE-15830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Brenton Leanhardt > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin. > In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling. > You can see this for details: > https://github.com/openshift/origin-server/blob/master/documentation/arch... > In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 November 2013