September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15431) Increment version for jbosstools-vpe module

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15431?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15431: ---------------------------------- Attachment: vpe-api-cahnges.html > Increment version for jbosstools-vpe module > ------------------------------------------- > > Key: JBIDE-15431 > URL: https://issues.jboss.org/browse/JBIDE-15431 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Attachments: vpe-api-cahnges.html > > -- 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-15267) Cannot build jbosstools-vpe from scratch with -DskipTests option

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15267?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-15267: --------------------------------------- cherry-picked commit cee05d3 and pushed to 4.1.x branch > Cannot build jbosstools-vpe from scratch with -DskipTests option > ---------------------------------------------------------------- > > Key: JBIDE-15267 > URL: https://issues.jboss.org/browse/JBIDE-15267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Yahor Radtsevich > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > download for jar required in compilation should never be skipped by -DskipTests or any other maven system properties, because compilation fails in this case -- 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-15267) Cannot build jbosstools-vpe from scratch with -DskipTests option

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15267?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15267: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 > Cannot build jbosstools-vpe from scratch with -DskipTests option > ---------------------------------------------------------------- > > Key: JBIDE-15267 > URL: https://issues.jboss.org/browse/JBIDE-15267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Yahor Radtsevich > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > download for jar required in compilation should never be skipped by -DskipTests or any other maven system properties, because compilation fails in this case -- 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-14530) Support 'Arquillian Cruiser' in standard 'Outline' view

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14530?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14530: --------------------------------------- {quote} ...to have arquillian cruiser react to selections in java editor... {quote} The feature you are talking about, would, in my opinion, require a separate jira. We already have the "Link with Editor" action within the Arquillia Cruiser view and should only specify additional requirements. {quote} ...extend the outline in the project explorer... {quote} We couldn't extend the Java Outline page this way. If you mean that we add a specific Arquillian content to the Project Explorer - that is possible to do, but also isn't related to this jira. Anyway, if we don't want to extend the Java Editor, we can't contribute to the standard Outline View. > Support 'Arquillian Cruiser' in standard 'Outline' view > ------------------------------------------------------- > > Key: JBIDE-14530 > URL: https://issues.jboss.org/browse/JBIDE-14530 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.1.x > > > Would it be possible to extend the normal 'Outline' view to specially handle 'Deployment methods' and add the option to continue drilling down into the content of the defined archive? -- 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-15431) Increment version for jbosstools-vpe module

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-15431: ------------------------------------- Summary: Increment version for jbosstools-vpe module Key: JBIDE-15431 URL: https://issues.jboss.org/browse/JBIDE-15431 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: visual-page-editor-core Affects Versions: 4.1.1.Alpha1 Reporter: Denis Golovin -- 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-15398) CDI Builder is sloooow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15398: ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2724: --------------------------------------- Just to note that one or two screen captures in JBDS 7.0.0 User Guide will be outdated if 'Testing' becomes 'Utilities' (likewise splitting Web and Mobile development). If everyone is happy with them staying outdated then I have no objections to the change. New screen captures will be taken for 7.1 docs to reflect the changes. > Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2724 > URL: https://issues.jboss.org/browse/JBDS-2724 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery > Reporter: Burr Sutter > Attachments: JBDS7_central.png > > > We should make it easier to work with jenkins for our devops users. > Start by including the Jenkins plugin (from Max: Mylyn build plugin) -- 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-15398) CDI Builder is sloooow

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15398: ----------------------------------------------- My first suspect was lack of memory, and stack traces attached prove that VM wastes too much time on simple checks in JDT. Screen from memory analyser shows that Maven and JDT are responsible for most memory used. CDI needs memory too, and when it is deficient, VM works quite slow. I started new workspace with 2Gb and could not import all projects at the first attempt, I got OutOfMemoryException long before Java and CDI build started. Killing Eclipse couple of times, and deleting/imporing partly configured projects again, I managed to get to Java build at last. After that CDI build was performed in about 20 minutes, even while in severe want of memory. Then I looked into what code takes most time during the build. Amazingly, it turned to be just two auxiliary methods: CDICoreNature.getAllAnnotations() DefinitionContext.getAnnotation(String) that took 15 minutes out of 20. There are a lot of dependences in Wildfly workspace, and each project lists all projects on which it depends. When iterating over such project dependencies, these two methods showed almost factorial growth of time on the depth of the dependency graph. > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.x > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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] (JBDS-2735) Ensure the Forge 1 wizards work well

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2735: ----------------------------------- [~mmurray]no, we won't drop JSF scaffolding in JBDS 7.x and unlikely in JBDS 8. JSF is still a very popular option for building web UIs. AngularJS will be where we focus people's attention - more the recommendation - but JSF will be with us for a long time to come. > Ensure the Forge 1 wizards work well > ------------------------------------ > > Key: JBDS-2735 > URL: https://issues.jboss.org/browse/JBDS-2735 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge > Reporter: Burr Sutter > -- 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-15398) CDI Builder is sloooow

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15398: ------------------------------------------ Attachment: MemoryUsedOnWildflyBuild.png > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.x > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013