May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12972) Add FestAssert to the TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12972?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12972: ------------------------------------ Added to JBoss Tools Locus: https://github.com/nickboldt/jbosstools-locus/commit/1fa4842d050663333f1e... Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... >=6 Update Site from which to install and verify it works as you'd expect: http://download.jboss.org/jbosstools/builds/staging/jbosstools-locus.site... > Add FestAssert to the TP > ------------------------ > > Key: JBIDE-12972 > URL: https://issues.jboss.org/browse/JBIDE-12972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Affects Versions: 4.0.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > It would be great if we could use in our tests. We would have to add it to our target platform (TP) for our plugins to use it. > Reason: FestAssert provides us with a Fluent API to write test assertions. > License and owner: Apache License 2.0 / http://code.google.com/p/fest/ > Original repository: (not an Eclipse bundle yet). Source and binaries available on Maven (https://repository.jboss.org/nexus/content/groups/public/org/easytesting/... and https://repository.jboss.org/nexus/content/groups/public/org/easytesting/...) > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/fest-assert ? > Source: https://github.com/alexruiz/fest-assert-1.x > Affected projects: LiveReload for now, JAX-RS in the future > Required in devstudio: No for now (if LiveReload is considered incubation) > Type of dependency: testing > List of bundles added/removed: fest-assert, fest-util > Fest-assert provides a fluent API to perform asertions in JUnit tests. It is also nice to use when the objects to tests are collections. > To convince you of the interest of fest-assert, here are a few syntax examples: > - In LiveReload-test plugin: > {code} > assertThat(new String(modifiedContent)).doesNotContain(addition + "</body>"); > {code} > - a more complete example of usage in openShift-java-client (not an Eclipse plugin, though, but it gives an idea of the chained assertions that can be performed) > {code} > assertThat(new GearGroupsAssert(gearGroups)) > .assertGroup(0).hasUUID().hasGears() > .assertGear(0).hasId().hasState(); > {code} > - in case of assertion failure on such a statement: > {code} > Assertions.assertThat(commands).hasSize(2); > {code} > the exception message will look like this: > {code} > java.lang.AssertionError: expected size:<2> but was:<1> for <['{"command":"reload","path":null,"liveCSS":true}']> > at org.fest.assertions.Fail.failure(Fail.java:228) > at org.fest.assertions.Assert.failure(Assert.java:149) > at org.fest.assertions.GroupAssert.hasSize(GroupAssert.java:89) > at org.jboss.tools.livereload.internal.service.LiveReloadCommandGeneratorTestCase.shouldGenerateCommandForIndexHtmlFileAfterSingleChange(LiveReloadCommandGeneratorTestCase.java:45) > at ... > {code} > See more examples here: http://code.google.com/p/fest/#Fluent_Assertions -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14384) Quick Fix for missing beans.xml file problem which creates the missing file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14384?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14384: ----------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.x) > Quick Fix for missing beans.xml file problem which creates the missing file > --------------------------------------------------------------------------- > > Key: JBIDE-14384 > URL: https://issues.jboss.org/browse/JBIDE-14384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: CreateFileBeansXML1.png, CreateFileBeansXML2.png > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-82) Modify the staging repository for target platform distribution management.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-82?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-82. ----------------------------- Fix Version/s: 4.0.0 4.1.0 Resolution: Done Target platform distribution management url updated - 4.0.0.Final and 4.1.0 (master). https://github.com/jbosstools/jbosstools-integration-stack/commit/3cf62e1... https://github.com/jbosstools/jbosstools-integration-stack/commit/2f81170... > Modify the staging repository for target platform distribution management. > -------------------------------------------------------------------------- > > Key: JBTIS-82 > URL: https://issues.jboss.org/browse/JBTIS-82 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.0.0, 4.1.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.0.0, 4.1.0 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14395) openshift should enable scaling by default in UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14395?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14395: --------------------------------------------- yes - something to align with openshift team on when/where this makes sense. > openshift should enable scaling by default in UI > ------------------------------------------------ > > Key: JBIDE-14395 > URL: https://issues.jboss.org/browse/JBIDE-14395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14363: --------------------------------------------- common feature would need splitting up then - it is currently a big bag of mixed ui/core and has very little to zero documentation and API's aren't exactly stable and changes often (xmodel especially). Trying to create a true common/core here. i'm not against the idea of leaving it in common but then we need to find a way to guarantee the old commons stuff does not leak into it. > Creation of 'core' component in base > ------------------------------------ > > Key: JBIDE-14363 > URL: https://issues.jboss.org/browse/JBIDE-14363 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements: > 1) Only code designed for re-use can live there > 2) Only fully and properly java-doc'd code can live there > 3) Only code for use by TWO OR MORE components can live there. > 4) Addition of dependencies for this component will be strictly regulated > 5) Code must be properly tested and have tests cases demonstrating it. > 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example: > {code} > org.jboss.tools.core.platform > org.jboss.tools.core.platform.ui > org.jboss.tools.core.wtp > org.jboss.tools.core.wtp.ui > {code} > Bundles such as these would require test bundles, as well as features that keep them separate. > {code} > org.jboss.tools.core.platform.feature > org.jboss.tools.core.wtp.feature > {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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14395) openshift should enable scaling by default in UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14395?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14395: ------------------------------------------ [~maxandersen] we should offer this before GA so that it's available for Demoing in June, right? > openshift should enable scaling by default in UI > ------------------------------------------------ > > Key: JBIDE-14395 > URL: https://issues.jboss.org/browse/JBIDE-14395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12137) openshift server adapter should show progress of git push while running

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12137?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12137: ------------------------------------------ @Nick: yes I saw it, thanks! > openshift server adapter should show progress of git push while running > ----------------------------------------------------------------------- > > Key: JBIDE-12137 > URL: https://issues.jboss.org/browse/JBIDE-12137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Beta1 > > Attachments: openshift-6.ogv > > > Please bring back that the progress monitor shows the git progress instead of just showing console output in the end -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14398) New Collapsible Set wizard

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-14398: --------------------------------------------- Summary: New Collapsible Set wizard Key: JBIDE-14398 URL: https://issues.jboss.org/browse/JBIDE-14398 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html source editing Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Beta1 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14363: --------------------------------------- {quote}org.jboss.tools.core.platform org.jboss.tools.core.platform.ui org.jboss.tools.core.wtp org.jboss.tools.core.wtp.ui{quote} if common.core is peeled off and all deps to egit, wtp and other modules would be moved out to {code}org.jboss.tools.common.egit.* org.jboss.tools.common.wst.* org.jboss.tools.common.jst.* org.jboss.tools.common.jdt.* {code} No new component with duplicate name "core" and for now we could keep using common feature to deliver common.* and then introduce new common.(wst|jdt|new-module).feature. > Creation of 'core' component in base > ------------------------------------ > > Key: JBIDE-14363 > URL: https://issues.jboss.org/browse/JBIDE-14363 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements: > 1) Only code designed for re-use can live there > 2) Only fully and properly java-doc'd code can live there > 3) Only code for use by TWO OR MORE components can live there. > 4) Addition of dependencies for this component will be strictly regulated > 5) Code must be properly tested and have tests cases demonstrating it. > 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example: > {code} > org.jboss.tools.core.platform > org.jboss.tools.core.platform.ui > org.jboss.tools.core.wtp > org.jboss.tools.core.wtp.ui > {code} > Bundles such as these would require test bundles, as well as features that keep them separate. > {code} > org.jboss.tools.core.platform.feature > org.jboss.tools.core.wtp.feature > {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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14363: --------------------------------------- {quote}org.jboss.tools.core.platform.ui org.jboss.tools.core.wtp.ui{quote} This is looking not right, from eclipse perspective core - is non UI related functionality, so core and ui in one name looks wrong to me. Why not leverage what we have now and just peel off common, common.core, common.ui instead of creating new bundles? > Creation of 'core' component in base > ------------------------------------ > > Key: JBIDE-14363 > URL: https://issues.jboss.org/browse/JBIDE-14363 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements: > 1) Only code designed for re-use can live there > 2) Only fully and properly java-doc'd code can live there > 3) Only code for use by TWO OR MORE components can live there. > 4) Addition of dependencies for this component will be strictly regulated > 5) Code must be properly tested and have tests cases demonstrating it. > 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example: > {code} > org.jboss.tools.core.platform > org.jboss.tools.core.platform.ui > org.jboss.tools.core.wtp > org.jboss.tools.core.wtp.ui > {code} > Bundles such as these would require test bundles, as well as features that keep them separate. > {code} > org.jboss.tools.core.platform.feature > org.jboss.tools.core.wtp.feature > {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

12 years, 11 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 May 2013