March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10974) Use Xvfb for build jobs instead of Xvnc

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-10974: -------------------------------------- Summary: Use Xvfb for build jobs instead of Xvnc Key: JBIDE-10974 URL: https://issues.jboss.org/browse/JBIDE-10974 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Environment: any Reporter: Mickael Istria Assignee: Nick Boldt Xvfb is a minimalist in-memory X server, without VNC. For our use-case, Xvfb may be faster and may avoid some of the issues we have with Xvnc. A Jenkins plugin exists to use Xvfb in Jenkins: https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin It requires Xvfb to be install in the slaves we use of IC, and the plugin installed on Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
12
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2044: -------------------------------- Summary: .eclipseproduct file no longer refers to JBDS Key: JBDS-2044 URL: https://issues.jboss.org/browse/JBDS-2044 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 5.0.0.Beta2 Before (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar): {code} name=JBoss Developer Studio id=com.jboss.jbds.all version=5.0.0.v201202271832M-H79-Beta1 {code} After (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar): {code} name=Eclipse Platform id=org.eclipse.platform version=3.7.0 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9405) Add Preview step to maven profile dialog

by Max Rydahl Andersen (JIRA)

Add Preview step to maven profile dialog ---------------------------------------- Key: JBIDE-9405 URL: https://issues.jboss.org/browse/JBIDE-9405 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Especially for multiple projects it sometimes feel unsafe to click ok, suggest that we add a Preview... button similar to what is seen under Refactoring that will show the list of projects that will be changed/updated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-11077) Provide tests as reusable components for external testing

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11077: -------------------------------------- Summary: Provide tests as reusable components for external testing Key: JBIDE-11077 URL: https://issues.jboss.org/browse/JBIDE-11077 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt In order to make testing re-usable and to perform same tests on several environment without rebuilding them. Suggestion of implementation: Provide feature in component update-site and have an aggregated site for tests, the same way there is one for components (could be a nightly, a snapshot, a release...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
30
0 / 0

[JBoss JIRA] (JBDS-2049) hide jbpm.common feature from JBT/JBDS SOA Tooling site

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2049: -------------------------------- Summary: hide jbpm.common feature from JBT/JBDS SOA Tooling site Key: JBDS-2049 URL: https://issues.jboss.org/browse/JBDS-2049 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: Build, updatesite, jBPM, SOA Tooling / Platform Affects Versions: 5.0.0.Beta1-SOA Environment: Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 5.0.0.Beta1-SOA Attachments: screenshot0.png http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/3.3.indigo/ contains this exposed (categorized) feature: {code} org.jboss.tools.jbpm.common.feature 4.4.0.v20120229-2037-H52-Beta1 | AbridgedTools | SOATools {code} It could, however, hide this feature like it does for the jBPM jPDL feature: {code} jBPM jPDL Tools 3.2.1.v20120229-2037-H52-Beta1 org.jbpm.gd.jpdl.feature.feature.group {code} !screenshot0.png! Same is true for http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... -- feature is currently exposed but could be hidden. To make this happen, just need to remove the category designations for the feature in the appropriate site.xml files: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/... https://svn.jboss.org/repos/devstudio/trunk/product-soa/site/site.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
8
0 / 0

[JBoss JIRA] (JBIDE-9881) Improve error messages in Seam config xml for unresolved nodes

by Viacheslav Kabanovich (Created) (JIRA)

Improve error messages in Seam config xml for unresolved nodes -------------------------------------------------------------- Key: JBIDE-9881 URL: https://issues.jboss.org/browse/JBIDE-9881 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 1. Do not use term 'member', wherever possible replace it with 'field' or 'method', otherwise use 'field or method'. 2. Make message more informative, mention name of class in which field or method is not found. 3. In messages about unresolved method or constructor, add parameter types to method name, e.g. action(String), otherwise message may be ambiguous, if for example method action(Integer) exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7093) [Web Service wizard] Error creating web service top down

by Brian Fitzpatrick (JIRA)

[Web Service wizard] Error creating web service top down -------------------------------------------------------- Key: JBIDE-7093 URL: https://jira.jboss.org/browse/JBIDE-7093 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.1.GA Reporter: Brian Fitzpatrick Assignee: Feng Qian Attachments: BuscarExpedientePorPkWS.wsdl, jbosstools-diagnostics-20100917171023.zip The steps the customer describes are: - Hi, I need to create a web service implementation from a given WSDL (attached). So, I created a dynamic web project and when using the create web service wizard using JBossWS, in the second step (after pressing 'next' twice) I got the following error: Failed to generate implementation class org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:447) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) Darran tried both JBoss Enterprise AS 4.3.0CP06 & 5.0.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-9777) Seam config creates a duplicate bean

by Alexey Kazakov (JIRA)

Seam config creates a duplicate bean ------------------------------------ Key: JBIDE-9777 URL: https://issues.jboss.org/browse/JBIDE-9777 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects. EXECUTE: Open /seam-security-example-openid-rp/src/main/resources/META-INF/seam-beans.xml EXECUTE: Remove org.jboss.seam.security.external.openid.OpenIdRpInApplicationScopeProducer (line 25) to fix this XML. Save the file. FAILURE: There is a warning "A few beans (IdentityImpl) have the same EL name and the name is not resolvable [JSR-299 §5.3.1]" on /seam-security/src/main/java/org/jboss/seam/security/IdentityImpl.java IdentityImpl.java and seam-beans.xml are placed in different but dependent projects. In this case seam-security-example-openid-rp has two beans with the same name identity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-9855) Infinite cycle in parsing seam-beans.xml

by Viacheslav Kabanovich (Created) (JIRA)

Infinite cycle in parsing seam-beans.xml ---------------------------------------- Key: JBIDE-9855 URL: https://issues.jboss.org/browse/JBIDE-9855 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 EXECUTE: Create Seam Config project. EXECUTE: Replace content of beans.xml (or seam-beans.xml) with text {code} <?xml version="1.0" encoding="UTF-8"?> </ {code} EXECUTE: Save file. FAILURE: Progress shows job building CDI model that sticks forever. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9053) seam-registration examle from wolf test repo is incorrectly deployed

by Libor Zoubek (JIRA)

seam-registration examle from wolf test repo is incorrectly deployed --------------------------------------------------------------------- Key: JBIDE-9053 URL: https://issues.jboss.org/browse/JBIDE-9053 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M1 Environment: JBossTools 3.3.0 M1 on top of indigo 3.7 M6a, org.eclipse.m2e.core (0.13.0.201103291237), org.maven.ide.eclipse.wtp (0.13.0.201103231111) Reporter: Libor Zoubek Assignee: Fred Bricon Fix For: 3.3.0.M2 I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that component.xml (contained in registration-web project) is not deployed/added to archive. When deploying using mvn jboss:deploy components.xml gets into registration-ear.ear/jboss-seam-registration.war/WEB-INF but when deploying by JBossTools components.xml is missing there. I am not sure if it is a bug in tooling or bad configuraion in pom. I'll attach example project together with settings.xml for easy configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
17
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 March 2012