September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17938) No local processes in JMX Navigator when Eclipse is run with java 7

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17938?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17938. --------------------------------- This works properly for me now with both java 7 and 8 as eclipse runtimes. Verified in JBDS 8.0.0.CR1 B225 > No local processes in JMX Navigator when Eclipse is run with java 7 > ------------------------------------------------------------------- > > Key: JBIDE-17938 > URL: https://issues.jboss.org/browse/JBIDE-17938 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3b B193 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > When I install and run JBDS with java 7, there are no local processes shown in the JMX navigator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17884) Use pom properties to (en/di)sable m2e configurators

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17884?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17884. ------------------------------------ All subtasks has been verified. > Use pom properties to (en/di)sable m2e configurators > ---------------------------------------------------- > > Key: JBIDE-17884 > URL: https://issues.jboss.org/browse/JBIDE-17884 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.2.0.Beta3 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > > m2e-wtp, m2e-apt, m2e-wro4j use pom properties to enable or disable the natching m2e configurators. This might be a solution to address JBIDE-17827 > affected configurators are : > * CDI > * Seam > * Portlet > * Hibernate -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18290) Core tests update site missing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18290?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18290: ---------------------------------- Workaround Description: Until we agree on the right url to use, one can override the url when running maven like this: -Djbosstools-tests-site =http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-sites.aggregate.coretests-site_4.2.luna/all/repo/ > Core tests update site missing > ------------------------------ > > Key: JBIDE-18290 > URL: https://issues.jboss.org/browse/JBIDE-18290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Mickael Istria > > In the root pom of our integration tests repo [1] we have been using this url for jbosstools core tests site: > http://download.jboss.org/jbosstools/updates/nightly/coretests/${jbosstoo... > which resolves to: > http://download.jboss.org/jbosstools/updates/nightly/coretests/4.2.luna > This worked in the past, but now gives 404. What is the correct url? > I found this, but it's under builds/, so I think that's not what we should use: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... > [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17931) Disable automatic Hibernate configuration via pom property

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17931?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17931. ------------------------------------ verified in JBDS 8.0.0.CR1-v20140908-0906-B225 > Disable automatic Hibernate configuration via pom property > ---------------------------------------------------------- > > Key: JBIDE-17931 > URL: https://issues.jboss.org/browse/JBIDE-17931 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.2.0.Beta3 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy, respin-b > Fix For: 4.2.0.Beta3 > > > similar to JBIDE-17885 with <m2e.hibernate.activation> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18181) Errors when hibernate.cfg.xml not at classpath root

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18181?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-18181. -------------------------------- Verified with JBDS 8.0.0.CR1a. No errors after expanding the Hibernate Console Configuration tree. > Errors when hibernate.cfg.xml not at classpath root > --------------------------------------------------- > > Key: JBIDE-18181 > URL: https://issues.jboss.org/browse/JBIDE-18181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599, Hibernate 4.1.12 > Reporter: Luke Maurer > Assignee: Koen Aers > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR1 > > > If a project keeps its hibernate.cfg.xml anywhere besides the root of the classpath, Hibernate Tools will not recognize it. In the Hibernate Configurations tree, expanding either Session Factory or Database gives an error ending in “/hibernate.cfg.xml not found”. (The Configuration subtree appears to work.) > As a workaround, if I go into the directory holding WEB-INF/classes (i.e. where compiled Java bytecode goes) and symlink hibernate.cfg.xml there, it seems to work. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18290) Core tests update site missing

by Martin Malina (JIRA)

Martin Malina created JBIDE-18290: ------------------------------------- Summary: Core tests update site missing Key: JBIDE-18290 URL: https://issues.jboss.org/browse/JBIDE-18290 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.2.0.CR1 Reporter: Martin Malina Assignee: Mickael Istria In the root pom of our integration tests repo [1] we have been using this url for jbosstools core tests site: http://download.jboss.org/jbosstools/updates/nightly/coretests/${jbosstoo... which resolves to: http://download.jboss.org/jbosstools/updates/nightly/coretests/4.2.luna This worked in the past, but now gives 404. What is the correct url? I found this, but it's under builds/, so I think that's not what we should use: http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2919) Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2919?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-2919: -------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.CR2) > Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8 > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2919 > URL: https://issues.jboss.org/browse/JBDS-2919 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: server > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 8.0.0.CR1 > > > Moving to 8.0.0.CR1 (as agreed with [~maxandersen]) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17827) "Missing beans.xml" in a Seam project

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17827?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17827. ------------------------------------ > "Missing beans.xml" in a Seam project > ------------------------------------- > > Key: JBIDE-17827 > URL: https://issues.jboss.org/browse/JBIDE-17827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, seam2 > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > In an imported Seam 2.3 project, there's a warning: > _Missing beans.xml file in the project contactlist-ejb. This file is required for bean archives \[JSR-299 §12.1\] contactlist-ejb_ > Seam projects don't need a beans.xml file. -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18083: -------------------------------- Labels: respin-b (was: ) > 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 > Labels: respin-b > Fix For: 4.2.0.CR1 > > 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18083: -------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.CR2) > 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 > Labels: respin-b > Fix For: 4.2.0.CR1 > > 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

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