Bug 852647

Summary:	maven-surefire: rebase F18 to version 2.12.3
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	maven-surefire	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	akurtako, java-sig-commits, jcapik, mizdebsk, sochotni
Target Milestone:	---	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.12.4-2	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-23 07:57:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	871788

Description Upstream Release Monitoring 2012-08-29 08:15:31 UTC

Latest upstream release: 2.12.3
Current version in Fedora Rawhide: 2.12
URL: http://repo2.maven.org/maven2/org/apache/maven/surefire/surefire/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Mikolaj Izdebski 2012-08-29 14:31:32 UTC


*** This bug has been marked as a duplicate of bug 845289 ***

Comment 2 Roland Grunberg 2012-09-25 21:08:12 UTC

I see that maven-surefire-0:2.12.2-1.fc19.noarch is in rawhide, but is there a plan to update to 2.12.3 ?

Comment 3 Mikolaj Izdebski 2012-09-25 21:20:52 UTC

> I see that maven-surefire-0:2.12.2-1.fc19.noarch is in rawhide, but is there
> a plan to update to 2.12.3 ?

Yes. 2.12.2 was submited by mistake instead of 2.12.3.

Comment 4 Mikolaj Izdebski 2012-09-25 21:43:35 UTC

2.12.3-1 pushed to rawhide.
Thank you for catching and reporting this.

Comment 5 Roland Grunberg 2012-09-26 18:57:13 UTC

I've tested 2.12.3 out by building Tycho against it and then using that to build other packages that make use of tycho-surefire. Things seem to be working fine. Can this be pushed to f18 as well, or does the fact that there exist api breaking changes from 2.12.1 -> 2.12.2 -> 2.12.3 prevent this ?

Comment 6 Mikolaj Izdebski 2012-10-05 00:15:10 UTC

*** Bug 861402 has been marked as a duplicate of this bug. ***

Comment 7 Mikolaj Izdebski 2012-10-05 02:17:57 UTC

(In reply to comment #5)
> I've tested 2.12.3 out by building Tycho against it and then using that to
> build other packages that make use of tycho-surefire. Things seem to be
> working fine. Can this be pushed to f18 as well, or does the fact that there
> exist api breaking changes from 2.12.1 -> 2.12.2 -> 2.12.3 prevent this ?

Despite only micro version difference there seem to be some quite big changes. I will try to upgrade surefire in F18 it it will be possible.

Comment 8 Mikolaj Izdebski 2012-10-18 16:48:59 UTC

Version 2.12.3 is needed by Tycho in F18.
Reopening and moving to F18 on Rolands request.

Comment 9 Mikolaj Izdebski 2012-10-19 07:28:00 UTC

Since version 2.12.1 maven-surefire needs maven-plugin-tools >= 3.0 (because of support for annotations), but Fedora 18 has maven-plugin-tools 2.7.

I can't update maven-plugin-tools to new major version because fedora 18 is frozen. The change is too big and it could easily break some things. Therefore I can't easily update maven-surefire in F18. Update would require backporting javadoc tags from older version and replacing annotations with them.

Comment 10 Alexander Kurtakov 2012-10-19 08:23:30 UTC

Not having maven-plugin-tools 2.0 in Fedora 18 will be a showstopper for any update of maven plugin during Fedora 18 lifecycle because most new plugins make use of annotations. As Fedora 18 is not released yet I would ask you to reconsider instead of make any update of maven plugin practically impossible.

Comment 11 Stanislav Ochotnicky 2012-10-19 14:34:29 UTC

Maven plugin tools are required only as BRs so all packages that are currently built would keep working. Worst case new version might generate incorrect metadata, or builds would start failing. I believe at this point it's fairly safe to update m-p-t, since all major features are already built :-)

Comment 12 Mikolaj Izdebski 2012-10-22 09:29:40 UTC

Ok then. I will update maven-plugin-tools in Fedora 18 and then maven-surefire.

Comment 13 Mikolaj Izdebski 2012-10-26 12:45:23 UTC

2.12.4-2 pushed for F18.

Comment 14 Fedora Update System 2012-10-26 13:01:16 UTC

maven-surefire-2.12.4-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/maven-surefire-2.12.4-2.fc18

Comment 15 Fedora Update System 2012-10-26 19:40:36 UTC

Package maven-surefire-2.12.4-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing maven-surefire-2.12.4-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16946/maven-surefire-2.12.4-2.fc18
then log in and leave karma (feedback).

Comment 16 Fedora Update System 2012-11-23 07:57:34 UTC

maven-surefire-2.12.4-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.