November 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2732: ------------------------------- Fix Version/s: (was: 8.0.0.Alpha1) (was: 7.1.0.GA) > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > It would be interesting to know which connectors/plugins gets installed from central -- 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-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15847: ------------------------------------- Fix Version/s: 4.1.1.CR1 (was: 4.1.1.Beta1) > OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect > ------------------------------------------------------------------------- > > Key: JBIDE-15847 > URL: https://issues.jboss.org/browse/JBIDE-15847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > -- 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-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15847 at 11/4/13 9:00 AM: ------------------------------------------------------------------- Even though this seems be caused by a "misconfigured" I'll provide a simple fix where I store the username that the backend reports to me once the connection is validated. We're thus using what the backend is reporting vs. what the user entered. {quote} (02:44:06 PM) maxandersen: adietisheim: so yeah, I wuold do the "rename" and if some user complain one day I would add a "userenteredLogin" or simply just show a warning dialog that username != actual username ? {quote} was (Author: adietish): Even though this seems be caused by a "misconfigured" I'll provide a simple fix where I store the username that the backend reports to me once the connection is validated. We're thus using what the backend is reporting vs. what the user entered. > OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect > ------------------------------------------------------------------------- > > Key: JBIDE-15847 > URL: https://issues.jboss.org/browse/JBIDE-15847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > -- 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-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15847: ------------------------------------------ Even though this seems be caused by a "misconfigured" I'll provide a simple fix where I store the username that the backend reports to me once the connection is validated. We're thus using what the backend is reporting vs. what the user entered. > OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect > ------------------------------------------------------------------------- > > Key: JBIDE-15847 > URL: https://issues.jboss.org/browse/JBIDE-15847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > -- 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] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip

by Jim Rigsbee (JIRA)

[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ] Jim Rigsbee commented on JBDS-2555: ----------------------------------- It would be nice to be able to suppress JBDS from trying to hit the Internet at all - similar to the mvn -o option. In certain circumstances, like a JBoss classroom we have to assume that we will always be disconnected. In this scenario, JBoss Central would not try to load blogs, etc. As a matter of fact these features could be suppressed and not displayed at all. I was not aware that some of these scripts/zips were available. For IS and other tools besides the standard update site it would be nice if they were distributed in the same place - with JBDS. > JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip > ---------------------------------------------------------------------------- > > Key: JBDS-2555 > URL: https://issues.jboss.org/browse/JBDS-2555 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, updatesite > Reporter: Jiri Pallich > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1, 7.1.0.CR1 > > > Offline Usage of JBoss Central (Customers without or very slow Internet access) > On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline). > Related to: https://issues.jboss.org/browse/JBDS-2535 -- 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-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15847 at 11/4/13 8:45 AM: ------------------------------------------------------------------- The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user(a)redhat.com>*. According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On* {quote} 01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers? (01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this (01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments (01:44:28 PM) bleanhar: it's now the default (01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config? (01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided (01:45:59 PM) bleanhar: I'll follow up with IT (02:43:15 PM) bleanhar: adietish: I just verified with IT that they do _not_ have 'KrbLocalUserMapping On' set. That explains why @redhat.com is being appended to the usernames. {quote} was (Author: adietish): The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user(a)redhat.com>*. According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On* {quote} 01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers? (01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this (01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments (01:44:28 PM) bleanhar: it's now the default (01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config? (01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided (01:45:59 PM) bleanhar: I'll follow up with IT {quote} > OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect > ------------------------------------------------------------------------- > > Key: JBIDE-15847 > URL: https://issues.jboss.org/browse/JBIDE-15847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > -- 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-15841) package-info.java in managed package in persistence.xml causes StackOverflowError

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15841?page=com.atlassian.jira.plugi... ] Jiri Peterka resolved JBIDE-15841. ---------------------------------- Resolution: Done > package-info.java in managed package in persistence.xml causes StackOverflowError > --------------------------------------------------------------------------------- > > Key: JBIDE-15841 > URL: https://issues.jboss.org/browse/JBIDE-15841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Final > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > A customer reported stackoverflow errors occuring when importing one of his maven projects. > After investigation, it appears the SO is caused by HibernatePackageInfoImpl > {noformat} > java.lang.StackOverflowError > at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450) > at org.eclipse.core.runtime.Path.computeSegments(Path.java:467) > at org.eclipse.core.runtime.Path.initialize(Path.java:602) > at org.eclipse.core.runtime.Path.<init>(Path.java:163) > at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326) > at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894) > at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453) > at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95) > at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245) > {noformat} > The simplest setup to reproduce involves creating a JPA project (Hibernate Platform 2), and adding the following files : > {code:title=persistence.xml } > <?xml version="1.0" encoding="UTF-8"?> > <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"> > <persistence-unit name="jpa"> > <class>foo.bar.model</class> > </persistence-unit> > </persistence> > {code} > {code:title=package-info.java} > package foo.bar.model; > {code} -- 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] (TOOLSDOC-420) Need to reference the JIRA 'advanced' search option - as the JIRA interface has changed

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-420: ------------------------------------- Summary: Need to reference the JIRA 'advanced' search option - as the JIRA interface has changed Key: TOOLSDOC-420 URL: https://issues.jboss.org/browse/TOOLSDOC-420 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: Installation Guide Environment: Build Name: 22485, Release Notes 7.1.0-7.1-7.1.0 Build Date: 01-11-2013 17:01:22 Topic ID: 24018-549260 [Latest] Reporter: Len DiMaggio Assignee: Michelle Murray Priority: Minor Title: Resolved Issues Describe the issue: Can we change this: {quote} To view information about issues resolved in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following search query as one line: {quote} To this: {quote} To view information about issues resolved in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following search query as one line using the advanced query option: {quote} Suggestions for improvement: Additional information: -- 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-15848) JSF Portal Project XML Problem

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ] Radoslav Rábara commented on JBIDE-15848: ----------------------------------------- It works when the JavaServer Faces's version is lower than 2.2. I'll update steps to reproduce. > JSF Portal Project XML Problem > ------------------------------ > > Key: JBIDE-15848 > URL: https://issues.jboss.org/browse/JBIDE-15848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, portal-gatein > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 > Reporter: Radoslav Rábara > Priority: Blocker > Fix For: 4.1.1.Beta1 > > Attachments: jsf - Error.jpg, jsf - show details.jpg > > > Creating JSF Portal Project ends with error: > Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). > Type: XML Error, Resource: faces-config.xml -- 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-15848) JSF Portal Project XML Problem

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-15848: ------------------------------------ Steps to Reproduce: STEP: create Dynamic Web Project with following attributes: Dynamic web module version: 2.5 Configuration: <custom> (Dynamic Web Module, Java, JavaServer Faces [version: 2.2], JBoss Core Portlet, JBoss JSF Portlet) Portlet Implementation Library: Portlet Target Runtime Provider (default) JSF Implementation Library: Library Provided by Target Runtime (default) JSFPortlet Implementation Library: JSF Portletbridge Runtime Provider (default) Portletbridge Runtime: /path/JBossPortletBridge-3.2.1.Final ASSERT: There is no error. FAIL: There is one error. was: STEP: create Dynamic Web Project with following attributes: Dynamic web module version: 2.5 Configuration: <custom> (Dynamic Web Module, Java, JavaServer Faces, JBoss Core Portlet, JBoss JSF Portlet) Portlet Implementation Library: Portlet Target Runtime Provider (default) JSF Implementation Library: Library Provided by Target Runtime (default) JSFPortlet Implementation Library: JSF Portletbridge Runtime Provider (default) Portletbridge Runtime: /path/JBossPortletBridge-3.2.1.Final ASSERT: There is no error. FAIL: There is one error. > JSF Portal Project XML Problem > ------------------------------ > > Key: JBIDE-15848 > URL: https://issues.jboss.org/browse/JBIDE-15848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, portal-gatein > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 > Reporter: Radoslav Rábara > Priority: Blocker > Fix For: 4.1.1.Beta1 > > Attachments: jsf - Error.jpg, jsf - show details.jpg > > > Creating JSF Portal Project ends with error: > Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). > Type: XML Error, Resource: faces-config.xml -- 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