March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19081: --------------------------------------------- {markdown}Just started reviewing :){markdown} > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19081: ---------------------------------------- Comment: was deleted (was: {markdown}Just started reviewing :){markdown}) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19081: ---------------------------------------- Comment: was deleted (was: {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown}) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19081: --------------------------------------------- {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown} > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19081: --------------------------------------------- {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown} > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19081: ---------------------------------------- Comment: was deleted (was: {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown}) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19081: ---------------------------------------- Comment: was deleted (was: {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown}) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19081: --------------------------------------------- {markdown}Just started reviewing :) ![NodeGH](http://nodegh.io/images/octocat.png) *Sent from [GH](http://nodegh.io).*{markdown} > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Alpha2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18685) Sometimes the internal browser shows cached outdated content when using Show In Web Browser

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18685?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18685: ------------------------------------- I'd just like to note that step 6 isn't even necessary (though it does outline the issue more clearly). Even without starting the eap, it will still return content even when no server is up at all. This clearly indicates no request is even being made, and the internal browser implementations are pulling direct from their cache. > Sometimes the internal browser shows cached outdated content when using Show In Web Browser > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18685 > URL: https://issues.jboss.org/browse/JBIDE-18685 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Final > > > Sometimes "Show in web browser" on a server in Server View results in wrong content being shown. When you start EAP 6, open the home page in web browser, then stop EAP, start AS7, open the home page again (using Show In) and the browser will still show EAP's home page. > [~ljelinko] discovered this bug on Linux and I was able to reproduce it on OS X. > I understand that this might be a problem in Eclipse itself, that's up to you, Rob, to investigate :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3375) JBDS target platform zip contains both packed and unpacked artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3375?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3375: ---------------------------------- Details of the two approaches: {code} ... <build> <plugins> <plugin> <groupId>com.googlecode.maven-download-plugin</groupId> <artifactId>download-maven-plugin</artifactId> <version>1.2.1</version> <executions> <execution> <id>fetch-target-platform</id> <phase>generate-sources</phase> <goals> <goal>wget</goal> </goals> <configuration> <url>http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/${...</url> <unpack>true</unpack> <outputDirectory>target</outputDirectory> </configuration> </execution> </executions> </plugin> ...{code} or {code} ... <build> <plugins> <plugin> <groupId>org.eclipse.tycho.extras</groupId> <artifactId>tycho-p2-extras-plugin</artifactId> <version>${tychoVersion}</version> <executions> <execution> <phase>prepare-package</phase> <goals> <goal>mirror</goal> </goals> </execution> </executions> <configuration> <source> <repository> <url>http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/${...</url> <layout>p2</layout> </repository> </source> <destination>${project.build.directory}/</destination> <includeNonGreedy>false</includeNonGreedy> <includeFeatures>true</includeFeatures> <latestVersionOnly>false</latestVersionOnly> <mirrorMetadataOnly>false</mirrorMetadataOnly> <includePacked>false</includePacked> <compress>true</compress> <append>false</append> </configuration> </plugin> ... {code} > JBDS target platform zip contains both packed and unpacked artifacts > -------------------------------------------------------------------- > > Key: JBDS-3375 > URL: https://issues.jboss.org/browse/JBDS-3375 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, target-platform, updatesite > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > I've got two approaches now for including the JBDS target platform into the JBDS update site. > a) mirror the TP site - size on disk is 328M and the increase in size to JBDS update site is about 200M > b) wget the TP zip and unpack - size on disk after unzipping is 458M > So... not sure which approach is more efficient given the zip is a single file to download, but it's 130M (more than 1/3rd) larger. > If we can remove the packed (or unpacked) artifacts from the zip, we'd certainly win. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015