February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19221) Add Fest Assert to Locus

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19221?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-19221. --------------------------------- Release Notes Text: duplicate of JBIDE-19220 Resolution: Duplicate Issue > Add Fest Assert to Locus > ------------------------ > > Key: JBIDE-19221 > URL: https://issues.jboss.org/browse/JBIDE-19221 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: locus > Reporter: Xavier Coulon > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19221) Add Fest Assert to Locus

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19221?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19221: ------------------------------------- Resolution: (was: Duplicate Issue) Assignee: Xavier Coulon > Add Fest Assert to Locus > ------------------------ > > Key: JBIDE-19221 > URL: https://issues.jboss.org/browse/JBIDE-19221 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: locus > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19221) Add Fest Assert to Locus

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19221?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19221: ---------------------------------- Release Notes Text: (was: duplicate of JBIDE-19220) > Add Fest Assert to Locus > ------------------------ > > Key: JBIDE-19221 > URL: https://issues.jboss.org/browse/JBIDE-19221 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: locus > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19219) Install Grinder doesn't support Oomph popups

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19219?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19219: ---------------------------------------- Need to try the org.eclipse.oomph.setup.skip system property. > Install Grinder doesn't support Oomph popups > -------------------------------------------- > > Key: JBIDE-19219 > URL: https://issues.jboss.org/browse/JBIDE-19219 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > > With the introduction of Oomph, install-grinder now faces many popups and pages that it doesn't know how to deal with. > Either we have to rework it to support Oomph, or we have to find a way to disable Oomph. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19220) Add AssertJ to the TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19220?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19220: ----------------------------------- Component/s: locus > Add AssertJ to the TP > --------------------- > > Key: JBIDE-19220 > URL: https://issues.jboss.org/browse/JBIDE-19220 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: locus, target-platform > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > > It would be great if we could use in our tests. We would have to add it to our target platform (TP) for our plugins to use it. > Reason: AssertJ provides us with a Fluent API to write test assertions. > License and owner: Apache License 2.0 / https://github.com/joel-costigliola/assertj-core/blob/master/LICENSE.txt > Original repository: (not an Eclipse bundle yet). Source and binaries available on Maven (http://search.maven.org/#artifactdetails|org.assertj|assertj-core|1.7.1|b...) > Source: https://github.com/joel-costigliola/assertj-core > Affected projects: LiveReload and JAX-RS in the future > Required in devstudio: No, only used for testing purpose > Type of dependency: testing > List of bundles added: assertj-core > This issue is a replacement for JBIDE-12972 since AssertJ aims at replacing FestAssert which is not moving anymore. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18377) Automatically add the dependencies specified in jboss-deployment-structure.xml to build path

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18377?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18377: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Automatically add the dependencies specified in jboss-deployment-structure.xml to build path > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18377 > URL: https://issues.jboss.org/browse/JBIDE-18377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > I am deploying a dynamic web project to EAP 6 using JBDS 6+. My project's build path includes the JRE System Library, EAP 6 Runtime, and Web App Libraries (the WEB-INF/lib folder). I also have a jboss-deployment-structure.xml file that defines additional module dependencies such as the following: > <jboss-deployment-structure> > <deployment> > <dependencies> > <module name="org.slf4j" /> > <module name="org.apache.log4j" /> > </dependencies> > </deployment> > </jboss-deployment-structure> > The problem is, the slf4j and log4j modules are not included in the project's build path. While the server resolves them correctly at runtime because of the jboss-deployment-structure.xml file, Eclipse doesn't include them. So the following declaration in the Java code would result in a build error because org.apache.log4j cannot be resolved to a type: > private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(Example.class); > Please note that the project has configured correctly the JBoss Server Runtime which points to a valid JBoss directory, and the module dependencies are properly installed in the server. > The dependencies specified in the jboss-deployment-structure.xml are some private modules installed at the server side but not included in the server runtime by default. > So, is there a way to automatically add the jboss-deployment-structure module dependencies to the Eclipse build path? So far, I've been unable to find a way to do this. > I have found a few workarounds, but none of them are ideal, and they seem to completely miss the point of module-based dependencies: > - Customize the Default Classpath Entries for the server runtime. This is not acceptable because it must be done in each developer's workspace – and possibly per project since projects may have different, conflicting dependencies. > - Add the libraries to WEB-INF/lib. This is not acceptable because it defeats the purpose of server modules. > - Add the libraries to a user library for the project. This could work, but it's very inconvenient, because each developer on the team would have to add the jars to the user libraries in their workspaces. > Here can find the discussion of exact same issue https://developer.jboss.org/thread/203309?tstart=0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18348: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Add support for WildFly 9 > ------------------------- > > Key: JBIDE-18348 > URL: https://issues.jboss.org/browse/JBIDE-18348 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS. > I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue. > Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow. > Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18274: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname > ------------------------------------------------------------------------------- > > Key: JBIDE-18274 > URL: https://issues.jboss.org/browse/JBIDE-18274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Alpha2 > > Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png > > > This is a follow up of JBIDE-17935 . > Previously, Rob fixed this: > {quote} > I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here. > {quote} > But in this rare case it still fails for me. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17698) Server view could show all deployed modules, obtained from the server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17698: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Server view could show all deployed modules, obtained from the server > --------------------------------------------------------------------- > > Key: JBIDE-17698 > URL: https://issues.jboss.org/browse/JBIDE-17698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > Pavol Srna pointed out to me that when he deletes a project in workspace while it's deployed on a running AS7, it disappears from the server view and he can't undeploy it from Eclipse. > I understand that this is somewhat expected, but we have a suggestion: Could the server view get its deployed modules from the server via the management api and use that to show the modules? Similar to what the web console of AS7/WildFly/EAP6 shows. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18497: -------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015