March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13746) BrowserSim: make standalone available for download/launch

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13746: ----------------------------------- Job is mirrored here: https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_Trunk/job... >From this job, you can access the browsersim.jar (which is the same as the one pushed to Nexus). I think that's enough to close this jira. If you agree, I let you do so. If you have ideas of improvements, please open new Jiras. > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11065: ----------------------------------- I updated the pull request to fix some issues: * Missing README => DONE with usage of "additionalWebResources" of generate-facade-mojo config * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. => DONE with a copy of the zipped repo to site_assembly.zip at the end of the Maven build * Uncategorized feature still here: DONE by setting "removeDefaultCategory" to true in generate-facade-mojo config * fetchZips should only be on site/ and soa-site/ => DONE removed goal from unrelated poms. Still TODO * Missing results.html > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13877) Test the RichFaces Kitchensink archetype upgrade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13877?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13877: ------------------------------------- Enterprise version doesn't build with the enterprise repo @ http://maven.repository.redhat.com/techpreview/all/ * jboss-javaee-6.0-with-hibernate:pom:1.0.4.Final-redhat-1 missing from http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/jboss-ja... * jboss-javaee-6.0-with-tools:pom:1.0.4.Final-redhat-1 missing from http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/jboss-ja... * org.richfaces:richfaces-bom:pom:4.3.1.Final-redhat-1 missing from http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface... I dunno what the exampleswarning label is supposed to mean here, but there are still a lot of unused imports warnings in eclipse. > Test the RichFaces Kitchensink archetype upgrade > ------------------------------------------------ > > Key: JBIDE-13877 > URL: https://issues.jboss.org/browse/JBIDE-13877 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: central > Reporter: Brian Leathem > Assignee: Fred Bricon > Labels: exampleswarnings > > RichFaces kitchensink archetype 4.3.1.Final-1 is currently in a JBoss staging repository. RichFaces QA of the archetype is complete. > The archetype will be promoted out of staging when JBoss tools QA is complete. > Staging repository: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12237) Improve UI of Runtimes dialog

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12237?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-12237: ---------------------------------- Fix Version/s: (was: 4.0.x) > Improve UI of Runtimes dialog > ----------------------------- > > Key: JBIDE-12237 > URL: https://issues.jboss.org/browse/JBIDE-12237 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 3.3.0.Final > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.1.x > > Attachments: dialog.jpg, JBIDE-12237-download-dialog.png > > > On Runtime detection preferences screen there is a Download button that displays runtimes available for download. The dialog showing those runtimes can be improved, for example: > * shrink the table and put it into group called Available runtimes or Runtimes available for download > * change the name of the dialog according to previous point > * maybe it is not necessary to display the id in this table (does it have any value for the user?) > * the file size might have - what about adding it into the table? > * when double clicking the table row, invoke the same action as on OK button > * what about changing the OK button to Select or Download? > * what about converting the dialog to some kind of wizard since after clicking "OK" another page is displayed -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11065 at 3/28/13 5:27 AM: ----------------------------------------------------------------- False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip * Uncategorized feature still here * fetchZips should only be on site/ and soa-site/ Other; * We could get rid of the site.xml file, which is useless. was (Author: mickael_istria): False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here * fetchZips should only be on site/ and soa-site/ Other; * We could get rid of the site.xml file, which is useless. > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11065 at 3/28/13 5:23 AM: ----------------------------------------------------------------- False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here * fetchZips should only be on site/ and soa-site/ Other; * We could get rid of the site.xml file, which is useless. was (Author: mickael_istria): False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here * fetchZips should only be on site/ and soa-site/ > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13739?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13739 at 3/28/13 5:16 AM: -------------------------------------------------------------- no, you still have to run Maven > Project Update for non-JavaEE projects. I know the behavior is inconsistent between non-JavaEE and JavaEE projects, but I wanted to limit the CPU overhead of scanning each workspace project for CDI whenever *any* change is detected in a project. Let's say it's a trade-off. was (Author: fbricon): no, you still have to run Maven > Project Update for non-JavaEE projects. I know the beahvior is inconsistent between non-JavaEE and JavaEE projects, but I wanted to limit the CPU overhead of scanning each workspace project for CDI whenever *any* change is detected in a project. Let's say it's a trade-off. > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-11065 at 3/28/13 4:37 AM: ----------------------------------------------------------------- False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here * fetchZips should only be on site/ and soa-site/ was (Author: mickael_istria): False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11065?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-11065: ----------------------------------- False issues (WONTFIX or already fix): * No category.xml => the category.xml file is useless in a p2 repo, and I'm not aware of anything the consumes it except p2 publish * XML aggregation metadata now are "entry" instead of "property": This is neither a bug nor an improvement. It's the default serialization of java.util.Properties. As nothing is tied to the format of this file, this output is as good as the previous one. True issues (to be fixed): * Missing README * Missing results.html * site_assembly.zip renamed to <artifactId>_<version>.zip => Already supported by publish.sh. * Uncategorized feature still here > Replace build.xml by a Maven plugin > ----------------------------------- > > Key: JBIDE-11065 > URL: https://issues.jboss.org/browse/JBIDE-11065 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: jbide11065-screenshot-fixed-version.png, jbide11065.png > > > In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13596) Test generated for new Seam action or form contains errors

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13596?page=com.atlassian.jira.plugi... ] Tomas Remes commented on JBIDE-13596: ------------------------------------- I am not sure how much is the JBDS 6.0.1.CR1 release relevant, but I still think that this is the problem, because the test creation isn't disabled properly. I am still able to produce invalid (not compilable) tests, following exactly these steps described here. IMHO this should be fixed or resolved also in 4.0.1.Final. > 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

12 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013