January 2015 - jbosstools-dev - Jboss List Archives

Should we use @Ignore in non-runnable JUnit test classes, instead of <include> in pom? (was: JUnit Tests)

by Nick Boldt

No, because then AbstractTest* and TemplateTest* classes would run, and they shouldn't be. You can set your own <include> entries in your root pom. Then all your projects' tests will inherit those new rules. -- We may also have some older JUnit 3 tests (from the JDK 1.4 era?) that might still be set to run with older JRE environments, where @annotations are not supported. If I'm wrong on that, and we no longer support running tests w/ old runtimes, then yes, we could consider adding @Ignores to all the tests which shouldn't be run, instead of using the "All" and "Suite" naming conventions. -- I've cc:'d the jbosstools-dev list because a wider audience might be able to comment better on if it's time to move to using @ignore instead of using restrictive patterns when running JUnits w/ Surefire in Tycho/Maven builds. N On 01/22/2015 02:08 PM, Daniel Florian wrote: > Guys, > > We currently have to add each JUnit test class to a test suite file called AllTests.java. If a test does not get added to this test suite it does not get run. > > I think the pom has this: > > <includes> > <include>**/AllTests.class</include> > <include>**/*AllTests*.class</include> > <include>**/*AllBotTests*.class</include> > <include>**/*TestSuite*.class</include> > </includes> > > Could we add: > > <include>**/Test*.class</include> > <include>**/*Test.class</include> > > So that we wouldn't need an AllTests.java. Other projects can keep using the test suite approach. > > With JUnit's @Ignore it is easy to stop a test from being run. > > wdyt? > > Thanks, > > Dan > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

7
19
0 / 0

4.2.x is now open for 4.2.3 (that will be included in Developer Studio 8.1)

by Max Rydahl Andersen

Hi, Just a heads up that now that we have tagged and released 4.2.2, the jbosstools-4.2.x branch are open for issues related to 4.2.3. This 4.2.3 is planned to be what is included in JBoss Developer Studio 8.1. Please be aware that this version is intended to backwards compatible with the 4.2 releases; especially consideration is to be sure we do not break Integration stack in context of changed dependencies or any API they use. Thus as always, take care in what changes you do, have a jira for each work so QE/docs are aware and don't be afraid to ask for more than one review of PRs if any doubts. Happy 8.1! /max http://about.me/maxandersen

11 years, 1 month

2
2
0 / 0

ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.2.Final ]

by Mickael Istria

Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called jbosstools, also often called origin $ git tag jbosstools-4.2.2.Final FETCH_HEAD $ git push jbosstools jbosstools-4.2.2.Final -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 1 month

8
7
0 / 0

ACTION REQUIRED: 1 issue with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3321 https://issues.jboss.org/browse/JBDS-3321 Summary: Rest Quick Start Exception ava.lang.ClassNotFoundException: com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 4:20:01.133105 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

11 years, 1 month

1
0
0 / 0

JBoss Tools 4.2.2.Final is available

by Mickael Istria

This is a maintenance release of JBoss Tools aimed atEclipse Luna users. Eclipse Marketplace: https://marketplace.eclipse.org/content/jboss-tools-luna Update Site: http://download.jboss.org/jbosstools/updates/development/luna/ Update Site Zips: http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.x/ Installation instructions: http://tools.jboss.org/downloads/installation.html New + Noteworthy (subject to change): http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.2.Final.html Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 1 month

1
0
0 / 0

Build target platform for master

by Denis Golovin

It there any better way to rebuild targetplatform for master? Now I can trigger only https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... which rebuilds luna branch and master. Checking out Revision 462adddbb6433a7fdba00b2d94faf081d445dbdc (origin/4.50.x) Triggering(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!rhts,jbdevstudio,4.41.3.CR1-SNAPSHOT <https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat...> Triggering(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!rhts,jbdevstudio,4.50.0.Alpha1-SNAPSHOT <https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat...> Triggering(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!rhts,jbosstools,4.41.3.CR1-SNAPSHOT <https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat...> Triggering(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!rhts,jbosstools,4.50.0.Alpha1-SNAPSHOT <https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat...> which is twice more than I need. Thanks Denis

11 years, 1 month

4
4
0 / 0

Re: [jbosstools-dev] Hot products from Dongda

by Eva

11 years, 1 month

1
0
0 / 0

ACTION REQUIRED: 1 issue with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3318 https://issues.jboss.org/browse/JBDS-3318 Summary: Hibernate/Persistence.next Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please ensure this issue has a proper component set. Last Update: 18:43:59.913012 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=%28filter%3D%27ds_lint_nocomponent%2...

11 years, 2 months

1
0
0 / 0

JBoss Tools Core 4.2.2.Final bits available for QE testing

by Mickael Istria

As always, these are not FINAL bits, but preliminary results for QE & community testing. Not for use by customers or end users. Update site: http://download.jboss.org/jbosstools/updates/staging/luna/ Target platforms: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... Until the above target platform site is released, you may need to add it to Eclipse to resolve dependencies at install time. Once released, dependencies will be found automatically from here: * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ (latest release) * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.4... (upcoming milestone) * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... (upcoming milestone) New + noteworthy (subject to change): * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... * http://tools.jboss.org/documentation/whatsnew/ Schedule: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 2 months

2
2
0 / 0

Security for in TP 4.41.2.CR1-SNAPSHOT: JGit

by Mickael Istria

Hi, Some of you may be aware that a vulnerability was found in most Git clients (including JGit): https://bugs.eclipse.org/bugs/show_bug.cgi?id=456947 In order to not propagate this vulnerability, we've updated the target platform 4.41.2.CR1-SNAPSHOT to ship a fixed version of EGit/JGit. Parent pom 4.2.2-SNAPSHOT will be updated to consume the modified 4.41.2.CR1-SNAPSHOT target-platform. Jobs for jbosstools-4.2.x branch will be updated to consume and ship the modified 4.41.2.CR1-SNAPSHOT target-platform. Then, when we have made the necessary test to validate that our change has the expected effect on JBoss Tools and JBoss Developer Studio, we'll release this 4.41.2.CR1-SNAPSHOT target-platform as a 4.41.2.Final, re-update parent pom and jobs, and we'll be able to proceed with staging of JBT 4.2.2/JBDS 8.0.2. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 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-dev January 2015