August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15328) Fixing Arquillian tests

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15328?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15328: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Fixing Arquillian tests > ----------------------- > > Key: JBIDE-15328 > URL: https://issues.jboss.org/browse/JBIDE-15328 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.0.Final > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > There are two issues: > 1) The CreateDeploymentMethodTest test, introduced by JBIDE-14779, isn't included into the build > 2) The CheckArquillianModificationsTest test, introduced by JBIDE-15030, creates, but doesn't remove a project. The project can't be removed because the test opens, but doesn't close an inputstream. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14430) Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14430?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14430: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ? > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14430 > URL: https://issues.jboss.org/browse/JBIDE-14430 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > can't we detect if there is more than one DeploymentContainer for Run As > Arquillian test or is that too slow ? > Or at least show which profile is enabled or something to give user an idea what he is currently running with. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14527) Add source option to 'generate deployment method' on abstract classes

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14527?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14527: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Add source option to 'generate deployment method' on abstract classes > --------------------------------------------------------------------- > > Key: JBIDE-14527 > URL: https://issues.jboss.org/browse/JBIDE-14527 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > {code} > @RunWith(Arquillian.class) > public abstract class AbstractTest > { > @Test > public void testa() {} > } > {code} > This should show no warning on 'missing deployment method' since it's a common pattern to have @Test's in a superclass with multiple sub classes that define deployments, but it's also a common pattern to have the deployment defined in a super class and multiple sub classes with different testing scenarios. > Given a abstract class > When there is no deployment method > Then give the 'source' option to 'generate deployment method' -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15173) Typo: cheatsheets > cheat sheets

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15173?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15173: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Typo: cheatsheets > cheat sheets > -------------------------------- > > Key: JBIDE-15173 > URL: https://issues.jboss.org/browse/JBIDE-15173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.CR1 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1 > > Attachments: Central_CheatSheets.png > > > Typo under Window > Preferences > JBoss Tools > Project Examples (screen capture attached): > 'Show included *cheatsheet(s)*' > 'Show included *cheat sheet(s)*' > Cheat sheet is two words. For example, see 'Help > Cheat Sheets' -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15388) Compute whether to publish or not based on output signature rather than commits

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-15388: -------------------------------------- Summary: Compute whether to publish or not based on output signature rather than commits Key: JBIDE-15388 URL: https://issues.jboss.org/browse/JBIDE-15388 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: LATER [Assuming we already have reproducible qualifiers...] Currently, the CI jobs publish the output of a build if a change was detected in the Git repo since last publication. However there are some case not correctly supported: * Job configuration changed and caused changes in build output. In that case, we would like build output to be re-published, but it won't happen * Job source changed but not build output (eg a change in a pom.xml or any non-included file), then we don't need to republish output whereas current mechanism would republish it. instead, it would make sense to compare what's already published and what is to publish in order to decide or not whether this has to be published. Looking at signatures of update site zip would probably be enough. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14526) Add 'quick fix' to 'warning missing deployment method'

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14526?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14526: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Add 'quick fix' to 'warning missing deployment method' > ------------------------------------------------------ > > Key: JBIDE-14526 > URL: https://issues.jboss.org/browse/JBIDE-14526 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Given no deployment method > When 'warning missing deployment method' > Then add 'quick fix' open to 'generate deployment method' -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15197: --------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.x) (was: 4.2.x) > Wizard for exporting mobile application out of a Hybrid Mobile project > ---------------------------------------------------------------------- > > Key: JBIDE-15197 > URL: https://issues.jboss.org/browse/JBIDE-15197 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries. > We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15197) Wizard for exporting mobile application out of a Hybrid Mobile project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-15197. ---------------------------------- Resolution: Done > Wizard for exporting mobile application out of a Hybrid Mobile project > ---------------------------------------------------------------------- > > Key: JBIDE-15197 > URL: https://issues.jboss.org/browse/JBIDE-15197 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries. > We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2746) On a Full Publish LiveReload refreshes the browser before the application is fully restarted

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2746?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2746: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 3.0.2.GA > On a Full Publish LiveReload refreshes the browser before the application is fully restarted > -------------------------------------------------------------------------------------------- > > Key: JBDS-2746 > URL: https://issues.jboss.org/browse/JBDS-2746 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Pete Muir > > I can't quite tell if the same problem exists for Incremental Publish. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2746) On a Full Publish LiveReload refreshes the browser before the application is fully restarted

by Pete Muir (JIRA)

Pete Muir created JBDS-2746: ------------------------------- Summary: On a Full Publish LiveReload refreshes the browser before the application is fully restarted Key: JBDS-2746 URL: https://issues.jboss.org/browse/JBDS-2746 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Reporter: Pete Muir I can't quite tell if the same problem exists for Incremental Publish. -- 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, 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 August 2013