September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16327) JaxrsFacetedProjectListener doesn't support JAX-RS 2.0

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16327?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16327. ----------------------------------- Verified with JBDS 8.0.0.CR1-v20140908-0906-B225 > JaxrsFacetedProjectListener doesn't support JAX-RS 2.0 > ------------------------------------------------------ > > Key: JBIDE-16327 > URL: https://issues.jboss.org/browse/JBIDE-16327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Final > Environment: Eclipse EE bundle 4.3.1 + JBoss Tools 4.1.1 > Reporter: Thomas Maslen > Assignee: Xavier Coulon > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR1 > > > More generally: JaxrsFacetedProjectListener supports exactly JAX-RS 1.1 but not 2.0? > (Perhaps that is intentional, and that's why various text labels in the public UI explicitly say "JAX-RS 1.1" rather than just "JAX-RS"?) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18286) Restore FakeTransactionManagerLookup for Hibernate 3.5

by Koen Aers (JIRA)

Koen Aers created JBIDE-18286: --------------------------------- Summary: Restore FakeTransactionManagerLookup for Hibernate 3.5 Key: JBIDE-18286 URL: https://issues.jboss.org/browse/JBIDE-18286 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18285) Error when expanding 'Database' node of hibernate configuration of Seam 2.3 project

by Koen Aers (JIRA)

Koen Aers created JBIDE-18285: --------------------------------- Summary: Error when expanding 'Database' node of hibernate configuration of Seam 2.3 project Key: JBIDE-18285 URL: https://issues.jboss.org/browse/JBIDE-18285 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18094: --------------------------------------- [~rob.stryker], can you advice how to test this? I started WildFly 8.1 in debug mode, deployed a war project and changed a class. I think the deployment was updated, but that's the same behavior as with normal running servers. How can I get the hot code dialog? I've never seen it. > Do not force restart modules when server is run in debug mode > ------------------------------------------------------------- > > Key: JBIDE-18094 > URL: https://issues.jboss.org/browse/JBIDE-18094 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: affects_documentation, new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, JBIDE-18094.png, JBIDE-18094_dialog.png, serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml, update_dialog_based_on_existing_hcr.png > > > The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically. > Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18130) JBDS doesn't follow/honor <module-alias> of jboss modules

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18130?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18130. --------------------------------- I have verified that this works properly in JBDS 8.0.0.CR1 B225 (I also checked that it does not work in Beta3). > JBDS doesn't follow/honor <module-alias> of jboss modules > --------------------------------------------------------- > > Key: JBIDE-18130 > URL: https://issues.jboss.org/browse/JBIDE-18130 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Takayuki Konishi > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: modalias.zip > > > JBDS 8 beta3 cannot resolve <module-alias> of jboss modules. For example, org.apache.log4j cannot resolved with these configurations [1][2][3]. They are valid; when I create a similar maven project, it can be deployed in EAP 6.3.0. > [1] > {code:title=MANIFEST.MF|borderStyle=solid} > Manifest-Version: 1.0 > Class-Path: > Dependencies: org.apache.log4j > {code} > [2] > {code} > import org.apache.log4j.Logger; > ... > public class SampleClass{ > private static final Logger logger = Logger.getLogger(SampleClass.class); > ... > {code} > [3] > {code:title=module.xml|borderStyle=solid} > <module-alias xmlns="urn:jboss:module:1.1" name="org.apache.log4j" target-name="org.jboss.log4j.logmanager"/> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16411. --------------------------------- I checked and version 0.16 is used in the current TP (http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...) so it seems alright. Closing. > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Labels: jbds711 > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17550: ---------------------------------------- I've tried Central a few times now and didn't even notice a delay where we could/should add another Progress Dialog. Is this issue still valid or maybe this was fixed together with another change on Central? I'm inclined to close this as "Cannot Reproduce" > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17550: ---------------------------------- Labels: f2f2014 (was: f2f2014 respin-b) > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17550: ---------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.0.CR1) > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18083: ---------------------------------- Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu, Eclipse 64 bit, Java 1.7 (was: Windows 7x6, Eclipse 64 bit version, java 1.7) > Issues in the new "Edit server runtime environment" window > ---------------------------------------------------------- > > Key: JBIDE-18083 > URL: https://issues.jboss.org/browse/JBIDE-18083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu, Eclipse 64 bit, Java 1.7 > Reporter: Wolfgang Knauf > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: server_runtime.png > > > See attached screenshot: there are three problems in the "Edit Server runtime environment" window. > a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused > b) same for the button "Installed JREs" > c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 2014