May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1234) Installer could check OS architecture

by Jiri Peterka (JIRA)

Installer could check OS architecture ------------------------------------- Key: JBDS-1234 URL: https://jira.jboss.org/browse/JBDS-1234 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 3.0.1.GA Reporter: Jiri Peterka Fix For: 3.0.x Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- 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

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9021) CDI builder should be declared before WST validation builder in .project.

by Alexey Kazakov (JIRA)

CDI builder should be declared before WST validation builder in .project. ------------------------------------------------------------------------- Key: JBIDE-9021 URL: https://issues.jboss.org/browse/JBIDE-9021 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M1, 3.2.0.Final Reporter: Alexey Kazakov Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.0.M2, 3.2.x EXECUTE: Create any CDI project (don't enable CDI support!) EXECUTE: If there is no in .project yet then add it there: {code} <buildCommand> <name>org.eclipse.wst.validation.validationbuilder</name> <arguments> </arguments> </buildCommand> {code} EXECUTE: Enable CDI support for the project. EXECUTE: Open .project FAILURE: {code} <buildCommand> <name>org.jboss.tools.cdi.core.cdibuilder</name> <arguments> </arguments> </buildCommand> {code} is added to the end of <buildSpec> tag. ASSERT: org.jboss.tools.cdi.core.cdibuilder should be declared after org.eclipse.jdt.core.javabuilder but before org.eclipse.wst.validation.validationbuilder This is very important since if we have CDI builder declared after WST validator builder then CDI validation will be invoked before CDI builder completed building CDI model. It causes incorrect work of CDI validation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8927) WS Tester issues with JUnit tests after fixing JBDS-1602

by Brian Fitzpatrick (JIRA)

WS Tester issues with JUnit tests after fixing JBDS-1602 -------------------------------------------------------- Key: JBIDE-8927 URL: https://issues.jboss.org/browse/JBIDE-8927 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.2.1.CR1, 3.3.0.M2 This is a spinoff of JBIDE-8925. I still have to figure out why the tests testJBIDE6694 and testJBIDE6865 are failing for the WS Tester. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-1670) Seeing "Target runtime jboss-soa-p-5.0 Runtime is not defined." error - in spite of the name of the runtime being set - with JBDS + AS + JBossESB

by Len DiMaggio (JIRA)

Seeing "Target runtime jboss-soa-p-5.0 Runtime is not defined." error - in spite of the name of the runtime being set - with JBDS + AS + JBossESB ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1670 URL: https://issues.jboss.org/browse/JBDS-1670 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 JBoss AS 5.1 JBossESB 4.9 Reporter: Len DiMaggio Attachments: log, Screenshot-200.png, Screenshot-201.png, Screenshot-202.png, Screenshot-203.png, Screenshot-204.png With JBDS 4 GA + AS 5.1 GA and JBossESB 4.9, I'm seeing this issue with the ESB examples Regardless of whether the AS server runtime is named "jboss-soa-p-5.0 Runtime", this error is raised: Target runtime jboss-soa-p-5.0 Runtime is not defined. See attached screenshots and .log file -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBDS-1586) The Find... feature in the installer doesn't work on Mac OS X

by Martin Malina (JIRA)

The Find... feature in the installer doesn't work on Mac OS X ------------------------------------------------------------- Key: JBDS-1586 URL: https://issues.jboss.org/browse/JBDS-1586 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Martin Malina One page of the installer offers to find or add existing platforms/servers to JBDS. While Add... works fine, Find... doesn't. This problem is Mac OS X specific. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1661) EWP 5.1 not supported in the installer

by Martin Malina (JIRA)

EWP 5.1 not supported in the installer -------------------------------------- Key: JBDS-1661 URL: https://issues.jboss.org/browse/JBDS-1661 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.1.0.M1 Environment: jbdevstudio-product-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar Mac OS X 10.6 Snow Leopard Reporter: Martin Malina On page 5 of the installer - Select Platforms and Servers. If you browse and find your installation of Enterprise Web Platform 5.1, it will recognize it and sets the version to 5.1, but says in red: Version is not valid for selected Type. It turns out only version 5.0 is available in the drop-down menu. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1569) Missing license for Certified Thirparty software on extras update site

by Jiri Peterka (JIRA)

Missing license for Certified Thirparty software on extras update site ---------------------------------------------------------------------- Key: JBDS-1569 URL: https://issues.jboss.org/browse/JBDS-1569 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.0.0.GA Environment: JBDS 4.0.0.GA H178 Reporter: Jiri Peterka Update site: http://reports.qa.atl.jboss.com/binaries/RHDS/updates/stable/4.0.0.GA_ext... Certified Thirdparty Software 1.0.0.v20110215-1856-H236-GA com.jboss.jbds.product.extra.feature.feature.group [Enter License Description here.] is as a license text License should be added -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8735) Savara paretnt pom maintenenace

by Nick Boldt (JIRA)

Savara paretnt pom maintenenace ------------------------------- Key: JBIDE-8735 URL: https://issues.jboss.org/browse/JBIDE-8735 Project: Tools (JBoss Tools) Issue Type: Bug Components: Savara Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Gary Brown Priority: Blocker Fix For: 3.3.0.M1 Savara needs to use the JBT parent pom v0.0.2, so that it can benefit from the new profiles. > > > [WARNING] The requested profile > > > "jbosstools-nightly-staging-composite" could not be activated > > > because it does not exist. > > > [WARNING] The requested profile "unified.site" could not be > > > activated because it does not exist. > > > [WARNING] The requested profile "local.site" could not be activated > > > because it does not exist. > > > [WARNING] The requested profile "local.composite" could not be > > > activated because it does not exist. > > Note too that there's a site ref that's 404'd: > > > > [WARNING] No repository found at > http://download.jboss.org/jbosstools/builds/staging/pi4soa/all/repo/. > > This should perhaps be [0] instead? > > [0] > http://download.jboss.org/jbosstools/builds/staging/jbosstools-pi4soa-3.1... > > And as well, you're referencing an outdated dependency site [1]: > > [1] http://download.eclipse.org/releases/helios > > That should be Indigo (Eclipse 3.7, WTP 3.3), not Helios (Eclipse 3.6, > WTP 3.2), and should be the JBT composite dependencies mirror site > [2], > [3], not the pure eclipse.org site: > > [2] http://download.jboss.org/jbosstools/updates/indigo/ > [3] http://download.jboss.org/jbosstools/updates/helios/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9034) remove thirdaparty from branch since its making it impossible to import all plugins

by Max Rydahl Andersen (JIRA)

remove thirdaparty from branch since its making it impossible to import all plugins ----------------------------------------------------------------------------------- Key: JBIDE-9034 URL: https://issues.jboss.org/browse/JBIDE-9034 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Fix For: 3.2.1.CR1 thirdparty in root of jboss tools 3.2.x branch makes it impossible to import since it contains source features of org.apache.oro multiple times. README says it can be deleted - so lets do that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6528) test failures running with Tycho

by Nick Boldt (JIRA)

test failures running with Tycho -------------------------------- Key: JBIDE-6528 URL: https://jira.jboss.org/browse/JBIDE-6528 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt 152 test failures reported in latest Tycho build: From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... -- 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

14 years, 10 months

5
16
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 May 2011