April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13929) Cannot install m2 facet when jst.seam facet is missing

by Rob Cernich (JIRA)

Rob Cernich created JBIDE-13929: ----------------------------------- Summary: Cannot install m2 facet when jst.seam facet is missing Key: JBIDE-13929 URL: https://issues.jboss.org/browse/JBIDE-13929 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Final Reporter: Rob Cernich Assignee: Fred Bricon An IllegalArgumentException is produced when loading MavenFacetInstallPage when the jst.seam facet is missing. One should be able to install the m2 facet regardless of whether or not seam tooling is installed. This is the line where the exception is thrown: public static final IProjectFacet SEAM_FACET = ProjectFacetsManager.getProjectFacet(SEAM_FACET_ID); This should be moved to a static init block to either catch the exception or check to see if the facet is defined first. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13928: ------------------------------- Description: In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. [1] https://devstudio.jboss.com/updates/7.0-development/extras/4.30.1/composi... was: In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. [1] http://download.jboss.org/jbosstools/updates/kepler/extras/ > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/4.30.1/composi... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13928: ------------------------------- Description: In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. [1] https://devstudio.jboss.com/updates/7.0-development/extras/ was: In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. [1] https://devstudio.jboss.com/updates/7.0-development/extras/4.30.1/composi... > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13926) Re-add "Sources" category to aggregator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13926?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13926. -------------------------------- Resolution: Done Source category added to * JBT 4.1.0.Alpha2x and master branch, * JBDS 7.0.0.Alpha2x & master branch > Re-add "Sources" category to aggregator > --------------------------------------- > > Key: JBIDE-13926 > URL: https://issues.jboss.org/browse/JBIDE-13926 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Sources category was made empty to not appear with bad names in p2 UI. However, now we have better labels, we should re-enable it. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13928: ---------------------------------- Summary: Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? Key: JBIDE-13928 URL: https://issues.jboss.org/browse/JBIDE-13928 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, UpStream Affects Versions: 4.1.0.Alpha2 Reporter: Nick Boldt Assignee: Fred Bricon In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. [1] http://download.jboss.org/jbosstools/updates/kepler/extras/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13854) intermittent install-grinder test failures caused by SIGSEGV

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugi... ] Vojtech Juranek commented on JBIDE-13854: ----------------------------------------- Hi, dsp06 is RHEL 5.3 while all dev* and vmg* RHEL5 machines are RHEL 5.6 or higher. However, the version of xulrunner, which contains xpcom lib, installed on dsp06 is xulrunner-10.0.4-1.el5_8, which is same version as on other machines (some have xulrunner-10.0.5-1.el5_8, but many has xulrunner-10.0.4-1.el5_8 as well). So maybe some incompatibility in libs which xpcom depends on? > intermittent install-grinder test failures caused by SIGSEGV > ------------------------------------------------------------ > > Key: JBIDE-13854 > URL: https://issues.jboss.org/browse/JBIDE-13854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86..., this build failed: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console} > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest > Command-line arguments: -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug > !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646 > !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages > Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest > Application Started: 24573 > log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher). > log4j:WARN Please initialize the log4j system properly. > !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217 > !MESSAGE Internal browser is not available: XPCOM error 0x80004003 > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688 > # > # JRE version: 6.0_43-b01 > # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0x8b9b] > # > # An error report file with more information is saved as: > # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13926) Re-add "Sources" category to aggregator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13926?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13926: ---------------------------------- Assignee: Nick Boldt > Re-add "Sources" category to aggregator > --------------------------------------- > > Key: JBIDE-13926 > URL: https://issues.jboss.org/browse/JBIDE-13926 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Sources category was made empty to not appear with bad names in p2 UI. However, now we have better labels, we should re-enable it. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13924) Filter LiveReload messages on changed file extension

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13924?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-13924 at 4/4/13 3:28 PM: --------------------------------------------------------------- Only accepting the following file extensions: "html", "htm", "css", "js", "gif", "png", "jpg", "jpeg", "bmp", "ico" was (Author: xcoulon): Only accepting: "html", "htm", "css", "js", "gif", "png", "jpg", "jpeg", "bmp", "ico" > Filter LiveReload messages on changed file extension > ---------------------------------------------------- > > Key: JBIDE-13924 > URL: https://issues.jboss.org/browse/JBIDE-13924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > LiveReload refresh/reload commands should only be sentot browsers if the following types of file changed: > - htm/html > - css > - js > - images (png, gif, jpg, jpeg) > other types of file should be ignored -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13924) Filter LiveReload messages on changed file extension

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13924?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-13924: --------------------------------------- Only accepting: "html", "htm", "css", "js", "gif", "png", "jpg", "jpeg", "bmp", "ico" > Filter LiveReload messages on changed file extension > ---------------------------------------------------- > > Key: JBIDE-13924 > URL: https://issues.jboss.org/browse/JBIDE-13924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > LiveReload refresh/reload commands should only be sentot browsers if the following types of file changed: > - htm/html > - css > - js > - images (png, gif, jpg, jpeg) > other types of file should be ignored -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13924) Filter LiveReload messages on changed file extension

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13924?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-13924. ----------------------------------- Assignee: Xavier Coulon Resolution: Done done > Filter LiveReload messages on changed file extension > ---------------------------------------------------- > > Key: JBIDE-13924 > URL: https://issues.jboss.org/browse/JBIDE-13924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > LiveReload refresh/reload commands should only be sentot browsers if the following types of file changed: > - htm/html > - css > - js > - images (png, gif, jpg, jpeg) > other types of file should be ignored -- 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, 2 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 April 2013