September 2014 - jbosstools-issues

[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 14.04, Eclipse 64 bit, Java 1.7 (was: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu, Eclipse 64 bit, 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 14.04, 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

[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 commented on JBIDE-18083: --------------------------------------- I can reproduce it, even on Ubuntu. See updated Steps to Reproduce. > 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 > 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

[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: ---------------------------------- Steps to Reproduce: 1. Run JBoss Tools 2. Open menu Window->Preferences 3. Select Server->Runtime Environments 4. Add new Server by pressing button "Add..." 5. Select Wildfly 8.x Runtime then press Next Pressing buttons "Environments..." and "Installed JREs..." changing background Preferences dialog, but focus remains on dialog "JBoss Runtime" > 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 > 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

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18083: --------------------------------------- I can replicate it under Ubuntu and it seems there is no relation to OS. > 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 > 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

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18083: ---------------------------------- Priority: Critical (was: Minor) > 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 > 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

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3141: ----------------------------------- That would be : {quote}mvn enforce:enforce{quote} http://maven.apache.org/enforcer/maven-enforcer-plugin/enforce-mojo.html > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3141: ----------------------------------- Basically they would run a specific mvn goal? what is the name of that goal? > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18128: ------------------------------------- I'm the developer of m2e-wtp so I know what happens when an exception/error shows up. Any error marker with the like of "One or more constraint have not been satisfied", associated with a more detailed error would cause the same kind of problem. If you take your original project, remove all classes and pages, obfuscate all names and only leave open source dependencies in your pom, we should be able to reproduce it. Hopefully. > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by fede pia (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] fede pia commented on JBIDE-18128: ---------------------------------- [~fbricon] Thanks Fred for pointing this out this is such a useful information. Just to let you know, I created the test project trying to reproduce the issue I had on the project I'm currently working on. As I commented Rob above, I can't send you my original project that's why I sent this test. The problem with Test is that it doesn't have the same issue since if I change web.xml to use version 3.0 it works fine, whilst on my project this change doesn't fix it. I was wondering if you could tell me how you found the solutions you stated in your comment, so I could try it here and analyze what could be the problem on the project. Thanks in advance > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18128: ------------------------------------- Sorry but your test project is borked, which explains why the jars are not deployed properly : - the main issue is your web.xml says servlet 2.5 but the project's Web Facet was set to 3.0. m2e-wtp tries to set the Web Facet from the web.xml level, so tries to downgrade it from 3.0 back to 2.5. Unfortunately, WTP throws an Exception when downgrading Facet. This prevents m2e-wtp from completing your project configuration, notably the Maven Classpath library is not onfigured for deployment, hence no jar is deployed. - Another issue is maven/m2e/JDT use target/classes to generate class files, but your project is configured to deploy build/classes instead, that's why many of your classes are missing from deployment The simplest solution is to delete your project from your workspace, then delete all .project, .classpath and .settings/ resources and finally reimport your project as a Maven project. Another alternative is to : - either change the servlet version in web.xml to use 3.0 or edit .settings/org.eclipse.wst.common.project.facet.core.xml and use <installed facet="jst.web" version="2.5"/> to downgrade from 3.0 - edit org.eclipse.wst.common.component and change <property name="java-output-path" value="/TestJboss/build/classes"/> to <property name="java-output-path" value="/TestJboss/target/classes"/> - Right-click on project and Maven> Update Configuration (or use the Alt-F5 shortcut) - force clean publish on your server > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.CR1 > > Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- 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