March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference - to resolve deployment errors

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-15888: --------------------------------- Summary: Update the Spring Archetype reference - to resolve deployment errors (was: Update the Spring Archetype reference) > Update the Spring Archetype reference - to resolve deployment errors > -------------------------------------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Fred Bricon > Labels: spring > Fix For: 4.1.2.Final > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16717) CLONE - Seam 2.3 Portlet deployment error on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16717?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16717: --------------------------------------- The Seam 2.3.2 portlet isn't compatible with portletbridge 3.3.1 on JPP 6.1. If you want to run it, you should use portletbridge 3.2.1. > CLONE - Seam 2.3 Portlet deployment error on JPP 6 > -------------------------------------------------- > > Key: JBIDE-16717 > URL: https://issues.jboss.org/browse/JBIDE-16717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.CR1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.2.CR1 > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16722) JMX connection hangs for remote EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16722?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16722: -------------------------------- Workaround Description: Ensure when using remote servers that your server adapter has the option "Expose your management port as the server's hostname" is checked, to ensure that your server is exposing its management port after being launched. Workaround: Workaround Exists > JMX connection hangs for remote EAP 6.2 > --------------------------------------- > > Key: JBIDE-16722 > URL: https://issues.jboss.org/browse/JBIDE-16722 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.CR1 > Environment: JBDS 7.1.1.CR1 B672 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > > I tried out JMX connection with a remote EAP 6.2. > I set up the server with default settings and started it. I was surprised to see that the IDE didn't ask me for password as is usual. Deployment worked. > So I tried Show in MBean Explorer. And that hanged once I expanded the server connection there - there was an Unhandled Event Loop error in the error log and the IDE has been eating up all of my CPU for about 10 mins now - I will have to kill it. > I know that this happened in the past when the tooling things the connection is established, but it isn't. One thing is finding out why it doesn't work now. But another thing we absolutely need fixed is the unhandled loop - this shouldn't happen under no circumstances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16722) JMX connection hangs for remote EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16722?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16722: ------------------------------------- Unfortunately, because this is not a regression, a workaround exists, and scheduling issues, this won't be able to make it into the 4.1.2 release. Sorry to all. > JMX connection hangs for remote EAP 6.2 > --------------------------------------- > > Key: JBIDE-16722 > URL: https://issues.jboss.org/browse/JBIDE-16722 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.CR1 > Environment: JBDS 7.1.1.CR1 B672 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > > I tried out JMX connection with a remote EAP 6.2. > I set up the server with default settings and started it. I was surprised to see that the IDE didn't ask me for password as is usual. Deployment worked. > So I tried Show in MBean Explorer. And that hanged once I expanded the server connection there - there was an Unhandled Event Loop error in the error log and the IDE has been eating up all of my CPU for about 10 mins now - I will have to kill it. > I know that this happened in the past when the tooling things the connection is established, but it isn't. One thing is finding out why it doesn't work now. But another thing we absolutely need fixed is the unhandled loop - this shouldn't happen under no circumstances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16722) JMX connection hangs for remote EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16722?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16722: -------------------------------- Labels: (was: respin-a) > JMX connection hangs for remote EAP 6.2 > --------------------------------------- > > Key: JBIDE-16722 > URL: https://issues.jboss.org/browse/JBIDE-16722 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.CR1 > Environment: JBDS 7.1.1.CR1 B672 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.2.CR1 > > > I tried out JMX connection with a remote EAP 6.2. > I set up the server with default settings and started it. I was surprised to see that the IDE didn't ask me for password as is usual. Deployment worked. > So I tried Show in MBean Explorer. And that hanged once I expanded the server connection there - there was an Unhandled Event Loop error in the error log and the IDE has been eating up all of my CPU for about 10 mins now - I will have to kill it. > I know that this happened in the past when the tooling things the connection is established, but it isn't. One thing is finding out why it doesn't work now. But another thing we absolutely need fixed is the unhandled loop - this shouldn't happen under no circumstances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16722) JMX connection hangs for remote EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16722?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16722: -------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.1.2.CR1) > JMX connection hangs for remote EAP 6.2 > --------------------------------------- > > Key: JBIDE-16722 > URL: https://issues.jboss.org/browse/JBIDE-16722 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.2.CR1 > Environment: JBDS 7.1.1.CR1 B672 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > > I tried out JMX connection with a remote EAP 6.2. > I set up the server with default settings and started it. I was surprised to see that the IDE didn't ask me for password as is usual. Deployment worked. > So I tried Show in MBean Explorer. And that hanged once I expanded the server connection there - there was an Unhandled Event Loop error in the error log and the IDE has been eating up all of my CPU for about 10 mins now - I will have to kill it. > I know that this happened in the past when the tooling things the connection is established, but it isn't. One thing is finding out why it doesn't work now. But another thing we absolutely need fixed is the unhandled loop - this shouldn't happen under no circumstances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16724) Clean up maven warnings related to 'building effective model' in jbosstools-javaee build

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-16724: ------------------------------------- Summary: Clean up maven warnings related to 'building effective model' in jbosstools-javaee build Key: JBIDE-16724 URL: https://issues.jboss.org/browse/JBIDE-16724 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.2.0.Alpha2 Reporter: Denis Golovin Assignee: Denis Golovin Build shows warnings: {code}[WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 376, column 12 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.extension.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 60, column 12 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.deltaspike.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 80, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING]{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16724) Clean up maven warnings related to 'building effective model' in jbosstools-javaee build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16724?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16724: ---------------------------------- Fix Version/s: 4.2.0.Beta1 > Clean up maven warnings related to 'building effective model' in jbosstools-javaee build > ---------------------------------------------------------------------------------------- > > Key: JBIDE-16724 > URL: https://issues.jboss.org/browse/JBIDE-16724 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Beta1 > > > Build shows warnings: > {code}[WARNING] > [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 376, column 12 > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.extension.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 60, column 12 > [WARNING] > [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.cdi.tests:org.jboss.tools.cdi.deltaspike.core.test:eclipse-test-plugin:1.6.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 80, column 12 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [WARNING]{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16717) CLONE - Seam 2.3 Portlet deployment error on JPP 6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16717?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16717: -------------------------------- Labels: (was: respin-a) > CLONE - Seam 2.3 Portlet deployment error on JPP 6 > -------------------------------------------------- > > Key: JBIDE-16717 > URL: https://issues.jboss.org/browse/JBIDE-16717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.CR1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.2.CR1 > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16717) CLONE - Seam 2.3 Portlet deployment error on JPP 6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16717?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16717: -------------------------------- Workaround Description: Use seam 2.3.2 Workaround: Workaround Exists > CLONE - Seam 2.3 Portlet deployment error on JPP 6 > -------------------------------------------------- > > Key: JBIDE-16717 > URL: https://issues.jboss.org/browse/JBIDE-16717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.CR1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.2.CR1 > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 March 2014