March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13860) soa-p 5.3 is incorrectly detected as 5.2 (master)

by Petr Suchý (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13860?page=com.atlassian.jira.plugi... ] Petr Suchý resolved JBIDE-13860. -------------------------------- Labels: (was: respin-a) Resolution: Done > soa-p 5.3 is incorrectly detected as 5.2 (master) > ------------------------------------------------- > > Key: JBIDE-13860 > URL: https://issues.jboss.org/browse/JBIDE-13860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. > When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13857) JBoss EAP developer studio - Issue while adding custom capability

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13857?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13857: ------------------------------------------------- Chandrashekhar Tupe <c.tupe(a)tcs.com> made a comment on [bug 927147|https://bugzilla.redhat.com/show_bug.cgi?id=927147] Eclipse log file for exceptions and errors. > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBIDE-13857 > URL: https://issues.jboss.org/browse/JBIDE-13857 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Brian Leathem > > From the linked bugzilla: > {quote} > Description of problem: > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. > Version-Release number of selected component (if applicable):6.0.0 > How reproducible: > Create an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > Steps to Reproduce: > Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > > Actual results: > There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > {quote} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Chandrashekhar Tupe (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Chandrashekhar Tupe edited comment on JBDS-2503 at 3/26/13 5:38 AM: -------------------------------------------------------------------- Attached eclipse logs was (Author: c.tupe): Attached eclpise logs > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Chandrashekhar Tupe (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Chandrashekhar Tupe updated JBDS-2503: -------------------------------------- Attachment: logfile.txt > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Chandrashekhar Tupe (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Chandrashekhar Tupe edited comment on JBDS-2503 at 3/26/13 5:37 AM: -------------------------------------------------------------------- Attached eclipse logs was (Author: c.tupe): Attached eclpise logs > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Chandrashekhar Tupe (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Chandrashekhar Tupe commented on JBDS-2503: ------------------------------------------- Attached eclpise logs > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Chandrashekhar Tupe (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Chandrashekhar Tupe commented on JBDS-2503: ------------------------------------------- Attached eclpise logs > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13859) Fix dependencies on org.jboss.tools.ui.bot.ext to restrict version

by Martin Malina (JIRA)

Martin Malina created JBIDE-13859: ------------------------------------- Summary: Fix dependencies on org.jboss.tools.ui.bot.ext to restrict version Key: JBIDE-13859 URL: https://issues.jboss.org/browse/JBIDE-13859 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.1.0.Alpha1, 4.0.1.Final Reporter: Martin Malina Assignee: Martin Malina Fix For: 4.0.1.Final, 4.1.0.Alpha2 Our bot tests in https://github.com/jbosstools/jbosstools-integration-tests depend on bundle org.jboss.tools.ui.bot.ext . Most of the time we first install bot ext to the local repo (mvn install) and then run the given test (mvn verify). The problem is that the bot ext requirement is not strict about the version required, so many times the wrong version from local maven repo is used. For example you're trying to run a test from jbosstools-4.0.x branch so org.jboss.tools.ui.bot.ext version 4.0.x should be used, but if you installed 4.1.x version of bot ext on that machine in the past, it will use that one instead. This is not desired. So in branch jbosstools-4.0.x we need this in every test bundle manifest: org.jboss.tools.ui.bot.ext;bundle-version="[4.0.0,4.1.0)" For master (4.1.x) we need this: org.jboss.tools.ui.bot.ext;bundle-version="[4.1.0,4.2.0)" -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10588) Installing on top of plain Eclipse IDE JBoss Maven Seam Integration plugin breaks Maven integration for WTP

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10588?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-10588: ------------------------------------- Took another look at the issue this morning with the latest dev versions. m2e still can't instantiate SeamProjectConfigurator : * Plug-in "org.jboss.tools.maven.seam" was unable to instantiate class "org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator" * java.lang.IllegalArgumentException: Project facet jboss.portlet has not been defined. So, even though there's no direct code dependency to the portlet plugin, the portlet facet is expected to be loaded during class initialization (see https://github.com/jbosstools/jbosstools-central/blob/master/maven/plugin...) Simple fix is to handle the case where portlet is unavailable in the code, i.e. add some null checks here and there. > Installing on top of plain Eclipse IDE JBoss Maven Seam Integration plugin breaks Maven integration for WTP > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10588 > URL: https://issues.jboss.org/browse/JBIDE-10588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 3.3.0.M5 > Environment: Eclipse 3.7.1.20110916-0149, m2e 1.0.100.20110804-1717, m2e-wtp 0.14.0.20110928-2045 > Reporter: Rafal Krzewski > Assignee: Fred Bricon > Priority: Minor > Fix For: 3.3.x > > Attachments: JBIDE-10588-test-setup.p2f > > > After installing istalling JBoss Maven Seam Integration plugin from http://download.jboss.org/jbosstools/updates/development/indigo/ m2e-wtp configurator stopped working. Running Maven > Update Configuration produces to following error on any project that is using war or ejb packaging (ear is OK): > Project configurator "org.jboss.tools.maven.seam.configurator" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. > Additionally, maven-ejb-plugin and maven-war-plugin executions are reported as not covered by by lifecycle configuration. > I've checked with OSGi host console and org.jboss.tools.maven.seam bundle is deployed: > osgi> ss org.jboss.tools.maven.seam > id State Bundle > 774 ACTIVE org.jboss.tools.maven.seam_1.3.0.v20111209-0524-H40-M5 > The configurator extension is also deployed: > osgi> pt -v org.eclipse.m2e.core.projectConfigurators > Extension(s): > ------------------- > null [from org.jboss.tools.maven.seam] > <configurator> > id = org.jboss.tools.maven.seam.configurator > class = org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator > name = Seam > secondaryTo = org.maven.ide.eclipse.configuration.wtp.configurator > </configurator> > Alas, the configurator class cannot be instantiated. Eclipse error log contains the following: > Plug-in "org.jboss.tools.maven.seam" was unable to instantiate class "org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator". > An exception stack trace is not available. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13858) Detect future EAP 6 based server like SOA-P - master

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13858?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-13858. ----------------------------------- Labels: new_and_noteworthy (was: new_and_noteworthy respin-a) Resolution: Done > Detect future EAP 6 based server like SOA-P - master > ---------------------------------------------------- > > Key: JBIDE-13858 > URL: https://issues.jboss.org/browse/JBIDE-13858 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers, runtime-detection > Reporter: Martin Malina > Assignee: Len DiMaggio > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha2 > > > To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots. -- 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

13 years

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 2013