June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19560) Display Container info/inspect in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19560?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19560: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Display Container info/inspect in properties view > ------------------------------------------------- > > Key: JBIDE-19560 > URL: https://issues.jboss.org/browse/JBIDE-19560 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19559?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19559: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Display Docker daemon info in properties view > --------------------------------------------- > > Key: JBIDE-19559 > URL: https://issues.jboss.org/browse/JBIDE-19559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19540) Forge runtime version is not aligned with its eclipse plugin version

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19540?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-19540. ------------------------------- Resolution: Won't Fix In the 4.3.x stream the plugin org.jboss.tools.forge2.runtime has been removed. The former contents of it are now all in the plugin org.jboss.tools.forge.runtime of which the major version is now bumped to 2.0.0 and not following the actual library versions anymore. In the 4.2.x stream we will not bother to fix this issue anymore as its not crucial and just a minor thing. > Forge runtime version is not aligned with its eclipse plugin version > -------------------------------------------------------------------- > > Key: JBIDE-19540 > URL: https://issues.jboss.org/browse/JBIDE-19540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Minor > Fix For: 4.3.0.Beta1 > > > Forge 2 runtime included with JBDS 8.1.0.CR1 is 2.15.1 and for JBDS 8.1.0.GA it's 2.15.2, but in both cases the plugin version is org.jboss.tools.forge2.runtime_2.15.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19865) Webservices and Rest New and Noteworthy for 4.3.0.Beta1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19865?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19865: ------------------------------------- Assignee: Brian Fitzpatrick Brian, do you have anything for the N&N ? > Webservices and Rest New and Noteworthy for 4.3.0.Beta1 > ------------------------------------------------------- > > Key: JBIDE-19865 > URL: https://issues.jboss.org/browse/JBIDE-19865 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19883: --------------------------------------- done for webservices > purge .cvsignore files from JBT project repos > --------------------------------------------- > > Key: JBIDE-19883 > URL: https://issues.jboss.org/browse/JBIDE-19883 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel, build, cdi, central, common/jst/core, esb, hibernate, jbpm, jmx, jsf, jsp/jsf/xml/html source editing, maven, seam2, server, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > > Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged. > {code} > ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore > ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore > ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore > ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore > ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore > ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore > ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore > ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore > ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore > ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore > ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore > ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore > ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore > ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore > ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore > ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore > ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore > ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore > ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore > ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore > ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore > ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore > ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore > ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore > ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore > ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore > ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore > ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore > ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore > ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore > ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore > ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore > ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore > ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore > ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore > ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore > ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-649) Adding the intros to the docs published in the community

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-649?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-649: ------------------------------------ Created a PR for this, troubleshooting with Xavier's help and managed to cherry pick what I wanted. > Adding the intros to the docs published in the community > -------------------------------------------------------- > > Key: TOOLSDOC-649 > URL: https://issues.jboss.org/browse/TOOLSDOC-649 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Supriya Bharadwaj > Assignee: Misha Ali > > Add these introductions to the community versions of the doc -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-649) Adding the intros to the docs published in the community

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-649?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-649: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/402 > Adding the intros to the docs published in the community > -------------------------------------------------------- > > Key: TOOLSDOC-649 > URL: https://issues.jboss.org/browse/TOOLSDOC-649 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Supriya Bharadwaj > Assignee: Misha Ali > > Add these introductions to the community versions of the doc -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18142) Fixing sonar issues in RS (not WS) code

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18142?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18142: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Fixing sonar issues in RS (not WS) code > --------------------------------------- > > Key: JBIDE-18142 > URL: https://issues.jboss.org/browse/JBIDE-18142 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.Beta2 > > > Fixing issues found by the sonar pass in the JAX-RS tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18377?page=com.atlassian.jira.plugi... ] Mustafa Musaji commented on JBIDE-18377: ---------------------------------------- [~rob.stryker] [~mhusnain] Can we include some documentation around this new feature please and it's limitations? > 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.Beta1 > > > 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.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18101) API updates

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18101?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18101: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > API updates > ----------- > > Key: JBIDE-18101 > URL: https://issues.jboss.org/browse/JBIDE-18101 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.Beta2 > > > Unify the JaxrsElement builders to provide the same methods: > - buildTransient() > - buildInMetamodel(JaxrsMetamodel) > Also, simplify the JaxrsElement#update() method (code could be simpler, with less if/else blocks) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015