March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13739) CDI Support cannot be disabled if CDI Maven Configurator is installed and enabled

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13739?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13739: ---------------------------------------- What about the case when you have a non-JavaEE (or JavaEE) project and never touched CDI settings page for the project and then a cdi dependency is added? Will CDI support enabled automatically? > CDI Support cannot be disabled if CDI Maven Configurator is installed and enabled > --------------------------------------------------------------------------------- > > Key: JBIDE-13739 > URL: https://issues.jboss.org/browse/JBIDE-13739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: CDI, maven > Affects Versions: 4.0.1.Final > Reporter: Denis Golovin > Assignee: Fred Bricon > Fix For: 4.1.0.Alpha2 > > -- 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-13596) Test generated for new Seam action or form contains errors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13596?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-13596. ------------------------------------ Resolution: Done We fixed the settings page for Seam 2.3 projects for 4.1.0.Alpha2 only. We disabled tests creation there. > Test generated for new Seam action or form contains errors > ---------------------------------------------------------- > > Key: JBIDE-13596 > URL: https://issues.jboss.org/browse/JBIDE-13596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.0.0.Final, 4.0.1.Final > Environment: JBDS 6.0.0.GA, Seam 2.3.1.Final > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha2 > > > Even there is not option how to create test for new Seam action and form in "New Seam Web project wizard", there is following option, how you can create this test, which is then not valid at all: > 1. New -> Seam Action > 2. Click on the settings link in the dialog > 3. Mark checkbox "Create test" > This should be either disabled or you can use seam-gen ant solution and fetch test libraries from Seam runtime. > -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2503: --------------------------------- Fix Version/s: 6.0.1.GA (was: 6.0.x) > 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 > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-2503. ---------------------------------- Resolution: Done Fixed in JBIDE-13865 > 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 > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > 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] (JBIDE-13837) KB Builder does complete scanning of content of every jar file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13837: ---------------------------------------- https://github.com/jbosstools/jbosstools-javaee/pull/66 contains new JUnit tests only. We fixed the bug in master and 4.0.x (JST) but we also added a few additional tests to master for JavaEE module. So there is no need to respin JavaEE for this fix for 4.0.1. > KB Builder does complete scanning of content of every jar file > --------------------------------------------------------------- > > Key: JBIDE-13837 > URL: https://issues.jboss.org/browse/JBIDE-13837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: respin-b > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > Memory problem were reported https://community.jboss.org/message/804026#804026 > At present, KB builder scans for facelet taglibs everywhere in jar files, not only in META-INF folder. That results in complete loading of model objects for jar content, which otherwise would remain unloaded. Once loaded, it is not easy to release them, since objects are shared by projects referencing the same jar. > Complete scanning was implemented as fix for https://issues.jboss.org/browse/JBIDE-5764 in February 2010. > JSF implementation jsf-impl-2.0.1.jar contains facelet tag libraries in /com/sun/faces/metadata/taglib. > However, it is recommended that facelet taglib xml files be packaged into META-INF folder. It seems that jsf-impl-2.0.1.jar is a special case. I suggest that we stop doing complete scanning of all jars and do it only for JSF 2 implementation jar. -- 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-13746) BrowserSim: make standalone available for download/launch

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13746: ------------------------------------------ [PR#49|https://github.com/jbosstools/jbosstools-vpe/pull/49] is pushed to master as a part of [PR#50|https://github.com/jbosstools/jbosstools-vpe/pull/50] (contains a small fix from [~kmarmaliykov]). > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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-13746) BrowserSim: make standalone available for download/launch

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13746: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/48, https://github.com/jbosstools/jbosstools-vpe/pull/49, https://github.com/jbosstools/jbosstools-vpe/pull/50 (was: https://github.com/jbosstools/jbosstools-vpe/pull/48, https://github.com/jbosstools/jbosstools-vpe/pull/50) > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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-13746) BrowserSim: make standalone available for download/launch

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-13746: ------------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/48, https://github.com/jbosstools/jbosstools-vpe/pull/50 (was: https://github.com/jbosstools/jbosstools-vpe/pull/48, https://github.com/jbosstools/jbosstools-vpe/pull/49) > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- 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-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt reopened JBDS-2504: ------------------------------ > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Labels: respin-b > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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-2504) JBDS 6.0.1 central software updates contain Juno SR1 fix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2504?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2504. ---------------------------- Resolution: Won't Fix > JBDS 6.0.1 central software updates contain Juno SR1 fix > -------------------------------------------------------- > > Key: JBDS-2504 > URL: https://issues.jboss.org/browse/JBDS-2504 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, central > Affects Versions: 6.0.1.GA > Environment: JBDS 6.0.1.CR1a B354 > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.1.CR1a.core/devstudio-directory.xml > Reporter: Martin Malina > Assignee: Nick Boldt > Labels: respin-b > Fix For: 6.0.1.GA > > > Today I noticed that in the Software Updates tab of Central in JBDS 6.0.1 I can see the Juno SR1 performance fix. > Since JBDS 6.0.1 is based on SR2, this has nothing to do there. > Actually I was able to install this update because this build of JBDS is in fact based on Juno SR0 - I created JBDS-2505 for that. > Anyway, it should be removed from central for 6.0.1. -- 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