January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18869: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18860: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz, org.example.jbide18860_v3.zip > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12351) Remote JMX connection to servers cannot be established with IPv6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12351: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > Remote JMX connection to servers cannot be established with IPv6 > ---------------------------------------------------------------- > > Key: JBIDE-12351 > URL: https://issues.jboss.org/browse/JBIDE-12351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 3.3.0.Final > Environment: Fedora 17 32bit > EAP 6.0.0.GA > Reporter: Martin Malina > Labels: f2f2014 > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log: > {code} > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18958) Palette: Update ionic libs/links to 1.0.0.Beta14

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18958?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18958: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > Palette: Update ionic libs/links to 1.0.0.Beta14 > ------------------------------------------------ > > Key: JBIDE-18958 > URL: https://issues.jboss.org/browse/JBIDE-18958 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > http://ionicframework.com/blog/the-final-beta/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18862: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18177: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014 > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, restart.jpg > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18755) Autocomplete shows white on white using default RHEL7 theme

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18755: ---------------------------------------- Fix Version/s: 4.2.3.Final 4.3.0.Alpha1 (was: 4.3.x) (was: 4.2.2.Final) > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-18755 > URL: https://issues.jboss.org/browse/JBIDE-18755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Karel Piwko > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18810) 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18810?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18810: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18810 > URL: https://issues.jboss.org/browse/JBIDE-18810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.1.CR1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > 'Angular' plugin won't be loaded by default when Tern.java/AngularJS-eclipse will be moved to 0.7.x stream. > The 'angular' plug-in must be contributed as a default module by tern's nature adapter extension point explicitly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18841) Add/Remove CDI support when facet version is changed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18841?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18841: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > Add/Remove CDI support when facet version is changed > ---------------------------------------------------- > > Key: JBIDE-18841 > URL: https://issues.jboss.org/browse/JBIDE-18841 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi > Affects Versions: 4.2.1.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > We should enable (and remove ?) CDI support when version of project facet is changed, not only when it is activated. > Ie changing web facet from 3.0 to 3.1 or ejb facet to 3.2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18861: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) > module start action does not delete *.undeployed file > ----------------------------------------------------- > > Key: JBIDE-18861 > URL: https://issues.jboss.org/browse/JBIDE-18861 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > If you start Wildfly with all modules enabled and started. > Now use STOP action on an EAR module. > Now stop Wildfly. > Now start Wildfly (debug or run). > It will start up without the EAR module running, this is correct behavior at this point. > Now use START on EAR module. It fails to start at all. > This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up. > If you perform a "full publish" on the module that appears to cause it to start up as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015