How about surrounding the packaging with spaces, there's enough room and
it looks friendlier to me.
On Fri, 22 Dec 2017 15:35:30 +0100, Hervé BOUTEMY
wrote:
as discussed on IRC, split information in 2 separate parts:
- project groupId + artifactId coordinates in header
- packaging in foot
as discussed on IRC, split information in 2 separate parts:
- project groupId + artifactId coordinates in header
- packaging in footer (not part of coordinates)
to me, the result is now ok to merge (after squashing...)
no objection from anybody?
Regards,
Hervé
Le vendredi 22 décembre 2017, 11:
Thanks, done.
On Fri, 22 Dec 2017 13:40:31 +0100, Stephen Connolly
wrote:
+1
On Fri 22 Dec 2017 at 09:57, Robert Scholte wrote:
Hi,
introduction of the ProjectArtifactsCache introduced a critical issue
where cached reactor projects are never updated, and which cause build
failure or in
+1
On Fri 22 Dec 2017 at 09:57, Robert Scholte wrote:
> Hi,
>
> introduction of the ProjectArtifactsCache introduced a critical issue
> where cached reactor projects are never updated, and which cause build
> failure or in worst case successful builds with corrupt artifacts in case
> there's som
thanks for the feedback: greatly appreciated
Le vendredi 22 décembre 2017, 10:38:51 CET Bernd Eckenfels a écrit :
> Hello,
>
> (Not a Release showstopper I guess)
yes, but a recurring issue: people see documentation fixes while voting. Any
idea on how to get feedback/fixes earlier?
>
> There i
Now MNG-6308 looks fine to me. If you agree you can merge it.
Robert
On Sun, 10 Dec 2017 20:46:38 +0100, Hervé BOUTEMY
wrote:
Le dimanche 10 décembre 2017, 19:26:53 CET Robert Scholte a écrit :
On Sun, 10 Dec 2017 18:38:55 +0100, Stephen Connolly
wrote:
> On Sun 10 Dec 2017 at 17:12, Ro
Hi,
introduction of the ProjectArtifactsCache introduced a critical issue
where cached reactor projects are never updated, and which cause build
failure or in worst case successful builds with corrupt artifacts in case
there's some aggregation activities.
https://issues.apache.org/jira/br
Hello,
(Not a Release showstopper I guess)
There is some text about maven3 report shortcomings which has a jira link which
is marked as fixed, maybe the documentation needs an update, too?
https://issues.apache.org/jira/browse/MPDF-41
https://gitbox.apache.org/repos/asf?p=maven-pdf-plugin.git;a
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317620&version=1238&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPDF%20AND%20status
%20%3D%20Open%20ORDER%20BY%20
