Am 2014-11-23 um 03:42 schrieb Hervé BOUTEMY:
IMHO, just open another Jira issue and make the proper fix (with existing ITs)
I head this in my too, the question is. How do we want to unify that.
Do we want everywhere:
g:a:v or Unnamed -- g:a:v?
That would count for the module report as well
Le dimanche 23 novembre 2014 10:27:12 Michael Osipov a écrit :
Am 2014-11-23 um 03:42 schrieb Hervé BOUTEMY:
IMHO, just open another Jira issue and make the proper fix (with existing
ITs)
I head this in my too, the question is. How do we want to unify that.
Do we want everywhere:
g:a:v
fixed
was both:
1. an existing IT weakness (missing distributionManagement section, which
cannot exist in real use case): I fixed the IT
2. and a change in output in case no name defined in module pom: I reverted to
previous algorithm (use artifactId) instead of ugly Unnamed g:a:v
Regards,
Gesendet: Samstag, 22. November 2014 um 19:02 Uhr
Von: Hervé BOUTEMY herve.bout...@free.fr
An: Maven Developers List dev@maven.apache.org
Betreff: Re: r1639526 in maven-project-info-reports breaks the build
fixed
was both:
1. an existing IT weakness (missing distributionManagement
@maven.apache.org
Betreff: Re: r1639526 in maven-project-info-reports breaks the build
fixed
was both:
1. an existing IT weakness (missing distributionManagement section, which
cannot exist in real use case): I fixed the IT
Thanks for the fix.
2. and a change in output in case no name
Michael,
The MPIR-279 fix broke the build (run with -Prun-its), it seems to me
like a real regression.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
