June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20529: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > Labels: xtriage > Fix For: 4.5.x > > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19454) Malformed strings when starting a remote host via localhost

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19454?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19454: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Malformed strings when starting a remote host via localhost > ----------------------------------------------------------- > > Key: JBIDE-19454 > URL: https://issues.jboss.org/browse/JBIDE-19454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > This is strange. > When I create a remote WildFly 8.2 server on a remote server (I use a SSH-only remote host), everything works fine. > But when I try to create a remote host that is actually localhost and then start WildFly, I get errors because some of the strings are broken. > This is in the console in Eclipse: > {code} > echo $PWD'>' > echo $PWD'>' > java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-nattura:/ rasp$ > nattura:/ rasp$ cd / > echo $PWD'>' > echo $PWD'>' > java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.janattura:/ rasp$ > nattura:/ rasp$ echo $PWD'>' > echo $PWD'>' > java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne&/> > nattura:/ rasp$ echo $PWD'>' > /> > java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne& > eeeeeeeeTOOLnattura:/ rasp$ java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xm s64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net. preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.serve r.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.he adless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2. 0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jboss qa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-D jboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.log manager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/ jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa /runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.j boss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base .dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne& > > eeeeeeeeTOOLS_SERVER_START_CMD:WildFly 8 remote localhost:"$! > 13:51:37,472 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final > java.lang.IllegalStateException: JBAS018702: Server base directory does not exist: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java > at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:365) > at org.jboss.as.server.Main.determineEnvironment(Main.java:262) > at org.jboss.as.server.Main.main(Main.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > nattura:/ rasp$ > {code} > The correct path to the server is /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final as was set up. But for some reason, some of the strings are wrong in the startup command. Most notably this: -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java > PS: I'm on OS X, so it might have something to do with that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-12161: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Deploy application to JBoss AS 7 in domain mode > ----------------------------------------------- > > Key: JBIDE-12161 > URL: https://issues.jboss.org/browse/JBIDE-12161 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.CR1 > Environment: Any. > Reporter: Humberto Ferreira da Luz Jr. > Assignee: Rob Stryker > Labels: f2f2012 > Fix For: 4.5.x > > > I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode. > We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21456) Remove central themes plugin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21456?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21456: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Remove central themes plugin > ---------------------------- > > Key: JBIDE-21456 > URL: https://issues.jboss.org/browse/JBIDE-21456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Priority: Minor > Fix For: 4.5.x > > > The central themes are not used nor have received any updates for 3+ years. > I suggest we remove them. > Reason I noticed them was I noticed we have weird packages in https://github.com/jbosstools/jbosstools-central/tree/master/central/plug.... > There is probably a reason why but since we don't even use or update the themes why don't > we just remove them ? > [~mickael_istria] any comments ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19593?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19593: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Minor UI issues in "Configure Repositories" wizard on OSX > --------------------------------------------------------- > > Key: JBIDE-19593 > URL: https://issues.jboss.org/browse/JBIDE-19593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Fred Bricon > Priority: Minor > Labels: uxp > Fix For: 4.5.x > > > On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels. > This was fixed for Windows/Linux in 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6554) Export configuration to orm.xml file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6554?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-6554: ------------------------------ Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Export configuration to orm.xml file > ------------------------------------ > > Key: JBIDE-6554 > URL: https://issues.jboss.org/browse/JBIDE-6554 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.5.x > > > Need to create exporter and templates to export orm.xml like hbm files are exported now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21833) Evaluate typescript.java for inclusion

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21833?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21833: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Evaluate typescript.java for inclusion > -------------------------------------- > > Key: JBIDE-21833 > URL: https://issues.jboss.org/browse/JBIDE-21833 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Reporter: Gorkem Ercan > Fix For: 4.5.x > > > Evaluate typescript.java[1] for inclusion on a JBoss tools release. > Also look at angular-eclipse[2] > [1] https://github.com/angelozerr/typescript.java > [2] https://github.com/angelozerr/angular2-eclipse -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17805) Missing RichFaces maven archetypes

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17805?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-17805: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Missing RichFaces maven archetypes > ---------------------------------- > > Key: JBIDE-17805 > URL: https://issues.jboss.org/browse/JBIDE-17805 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Juraj Húska > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta3, 4.5.x > > > There is no RichFaces archetype available for selection, when trying to create a maven project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-11172: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Database Development: Postgres 9.1 tables are not listed > -------------------------------------------------------- > > Key: JBIDE-11172 > URL: https://issues.jboss.org/browse/JBIDE-11172 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Environment: Mac OS X Lion > Reporter: Burr Sutter > Assignee: Koen Aers > Priority: Critical > Fix For: 4.5.x > > Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar > > > Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18525) Investigate how to do module deployment ordering properly with management api

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18525?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18525: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Investigate how to do module deployment ordering properly with management api > ----------------------------------------------------------------------------- > > Key: JBIDE-18525 > URL: https://issues.jboss.org/browse/JBIDE-18525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > This is a followup of JBIDE-18373 which was originally about deployment via management api not handling "mark as deployable" files properly. This was fixed, but there's still a problem of ordering. The use case here was a seam project deployed to EAP 6.3. There are three parts: > 1. Seam project war > 2. database driver jar > 3. datasource xml > When you click "Add and Remove..." on the server in server view, it will sometimes be deployed in the wrong order and fail to deploy. > Specifically, when you click "Add All" in the dialog, it will not work, whereas if you click "Add" for each of the three resources, it will deploy alright. > As Rob pointed out, it can get really tricky to guess the right ordering. > See JBIDE-18373 for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 2017