December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13289) Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13289?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-13289: ---------------------------------- Component/s: testing > Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup > ------------------------------------------------------------------------------------------- > > Key: JBIDE-13289 > URL: https://issues.jboss.org/browse/JBIDE-13289 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing > Reporter: Lukáš Fryč > Assignee: Snjezana Peco > > {{-Darquillian.debug=true}} allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system. > There is sample call tree for debugging Warp client-side [full tree|https://gist.github.com/4270739]: > {code} > ... > (E) Before > (I) TestContextHandler.createSuiteContext > (I) TestContextHandler.createClassContext > (E) TestClass > (I) TestContextHandler.createTestContext > (I) ContainerEventController.createBeforeContext > (O) DroneConfigurator.configureDrone > (O) TestInstanceEnricher.enrich > (E) BeforeEnrichment > (E) RequireProxy > (O) ProxyObserver.requireProxy > (E) StartProxy > (O) ProxyObserver.startProxy > (E) AfterEnrichment > (O) ClientBeforeAfterLifecycleEventExecuter.on > (E) Test > (I) TestContextHandler.createSuiteContext > ... > {code} > Similarly for container. > ---- > The problem with debugging is that people need to setup VM arguments in Container Configuration > and then setup JUnit/TestNG VM arguments for each *executed test specifically*. > ---- > This button switch in toolbar should allow to add {{-Darquillian.debug=true}} to executed test (either JUnit or TestNG) and also into container configuration. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13289) Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13289?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-13289: ------------------------------------- Assignee: Snjezana Peco > Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup > ------------------------------------------------------------------------------------------- > > Key: JBIDE-13289 > URL: https://issues.jboss.org/browse/JBIDE-13289 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Lukáš Fryč > Assignee: Snjezana Peco > > {{-Darquillian.debug=true}} allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system. > There is sample call tree for debugging Warp client-side [full tree|https://gist.github.com/4270739]: > {code} > ... > (E) Before > (I) TestContextHandler.createSuiteContext > (I) TestContextHandler.createClassContext > (E) TestClass > (I) TestContextHandler.createTestContext > (I) ContainerEventController.createBeforeContext > (O) DroneConfigurator.configureDrone > (O) TestInstanceEnricher.enrich > (E) BeforeEnrichment > (E) RequireProxy > (O) ProxyObserver.requireProxy > (E) StartProxy > (O) ProxyObserver.startProxy > (E) AfterEnrichment > (O) ClientBeforeAfterLifecycleEventExecuter.on > (E) Test > (I) TestContextHandler.createSuiteContext > ... > {code} > Similarly for container. > ---- > The problem with debugging is that people need to setup VM arguments in Container Configuration > and then setup JUnit/TestNG VM arguments for each *executed test specifically*. > ---- > This button switch in toolbar should allow to add {{-Darquillian.debug=true}} to executed test (either JUnit or TestNG) and also into container configuration. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13289) Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup

by Lukáš Fryč (JIRA)

Lukáš Fryč created JBIDE-13289: ---------------------------------- Summary: Switch-button for enabling -Darquillian.debug=true for unit tests' and container's VM setup Key: JBIDE-13289 URL: https://issues.jboss.org/browse/JBIDE-13289 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Lukáš Fryč {{-Darquillian.debug=true}} allow more insight into test lifecycle and drastically improves debugging experience by outputting call tree of Arquillian event system. There is sample call tree for debugging Warp client-side [full tree|https://gist.github.com/4270739]: {code} ... (E) Before (I) TestContextHandler.createSuiteContext (I) TestContextHandler.createClassContext (E) TestClass (I) TestContextHandler.createTestContext (I) ContainerEventController.createBeforeContext (O) DroneConfigurator.configureDrone (O) TestInstanceEnricher.enrich (E) BeforeEnrichment (E) RequireProxy (O) ProxyObserver.requireProxy (E) StartProxy (O) ProxyObserver.startProxy (E) AfterEnrichment (O) ClientBeforeAfterLifecycleEventExecuter.on (E) Test (I) TestContextHandler.createSuiteContext ... {code} Similarly for container. ---- The problem with debugging is that people need to setup VM arguments in Container Configuration and then setup JUnit/TestNG VM arguments for each *executed test specifically*. ---- This button switch in toolbar should allow to add {{-Darquillian.debug=true}} to executed test (either JUnit or TestNG) and also into container configuration. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13059) test the RichFaces Kitchensink archetype upgrade

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13059?page=com.atlassian.jira.plugi... ] Brian Leathem commented on JBIDE-13059: --------------------------------------- Promoted out of staging. It should be in maven central by the end of the day. > test the RichFaces Kitchensink archetype upgrade > ------------------------------------------------ > > Key: JBIDE-13059 > URL: https://issues.jboss.org/browse/JBIDE-13059 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: central > Affects Versions: 4.0.0.Beta1 > Reporter: Brian Leathem > Assignee: Fred Bricon > Priority: Critical > Labels: exampleswarnings > Fix For: 4.0.0.Final > > Attachments: richfaces.png, richfaces1.png > > > RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository. > The archetype will be promoted out of staging when JBoss tools QA is complete. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12955) bogus relativePath's after git migration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12955?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12955: ------------------------------------ https://github.com/jbosstools/jbosstools-maven-plugins/pull/1 applied. > bogus relativePath's after git migration > ---------------------------------------- > > Key: JBIDE-12955 > URL: https://issues.jboss.org/browse/JBIDE-12955 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 4.0.0.CR1 > > > I noticed that after git migration we got a few "skewed" relativePath references. > Without relativePath then its hard/tricky to test changes in parent pom without having to mvn install it for every change, and the build will also fail if without network access - thus I suggest we get these fixed. > I think my patches are clean but i'll just for good measure open a pullrequest for the ones with more than just a simple change in the root pom.xml. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13287) examples URLs should use major/minor/service/milestone convention

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13287: ---------------------------------- Summary: examples URLs should use major/minor/service/milestone convention Key: JBIDE-13287 URL: https://issues.jboss.org/browse/JBIDE-13287 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Instead of {code:title=http://download.jboss.org/jbosstools/examples/} project-examples-community-4.0.GA.xml project-examples-jbds60.xml project-examples-maven-4.0.GA.xml project-examples-shared-4.0.GA.xml ... {code} We should consider using something like 6/1/0/Alpha1/project-examples*.xml -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13288) discovery URLs should use major/minor/service/milestone convention

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13288: ---------------------------------- Summary: discovery URLs should use major/minor/service/milestone convention Key: JBIDE-13288 URL: https://issues.jboss.org/browse/JBIDE-13288 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Instead of {code:title=http://download.jboss.org/jbosstools/examples/} project-examples-community-4.0.GA.xml project-examples-jbds60.xml project-examples-maven-4.0.GA.xml project-examples-shared-4.0.GA.xml ... {code} We should consider using something like 6/1/0/Alpha1/project-examples*.xml -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13288) discovery URLs should use major/minor/service/milestone convention

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13288?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13288: ------------------------------- Description: Instead of https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml We should consider using something like https://devstudio.jboss.com/discovery/6/1/0/Alpha1/devstudio-directory.xml was: Instead of {code:title=http://download.jboss.org/jbosstools/examples/} project-examples-community-4.0.GA.xml project-examples-jbds60.xml project-examples-maven-4.0.GA.xml project-examples-shared-4.0.GA.xml ... {code} We should consider using something like 6/1/0/Alpha1/project-examples*.xml > discovery URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------- > > Key: JBIDE-13288 > URL: https://issues.jboss.org/browse/JBIDE-13288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Instead of > https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml > We should consider using something like > https://devstudio.jboss.com/discovery/6/1/0/Alpha1/devstudio-directory.xml -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13288) discovery URLs should use major/minor/service/milestone convention

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13288?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13288: ------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > discovery URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------- > > Key: JBIDE-13288 > URL: https://issues.jboss.org/browse/JBIDE-13288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Instead of > https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml > We should consider using something like > https://devstudio.jboss.com/discovery/6/1/0/Alpha1/devstudio-directory.xml -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13288) discovery URLs should use major/minor/service/milestone convention

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13288?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13288: ------------------------------- Component/s: central (was: project-examples) > discovery URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------- > > Key: JBIDE-13288 > URL: https://issues.jboss.org/browse/JBIDE-13288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Instead of > https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml > We should consider using something like > https://devstudio.jboss.com/discovery/6/1/0/Alpha1/devstudio-directory.xml -- 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, 4 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 December 2012