+1
On Mon, 4 Nov 2019 at 06:04, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12345956=Text
>
> There are still a couple of issues left in JIRA:
>
>
Hi,
> but the format of the timestamp is completely different ... doesn't that
> matter?
I don't think so; at least I don't think the Bnd-LastModified header is
meant to be parsed by machines.
But I have _removeheaders>Bnd-* (yes, wildcards are
supported) in my , so what do I know...
> I was
Hi all,
And I might want to add, that includes pom, jar, sources jar, javadoc,
release-asembly and fat-jars ...
Currently applying these changes to other apache projects as an experiment.
So is anyone already working on the release plugin?
Chris
Von:
Hi all,
so today I made sure the LastModified and the Creator username are omitted and
now the Apache PLC4X build had a 100% reproducible build (at least on my one
machine) ... will be checking this out on other machines.
Chris
Am 04.11.19, 10:12 schrieb "Christofer Dutz" :
Hi Andreas,
Thanks. I've rewritten the PR under the assumption that all version
ranges are "hard". Please take another look. (PTAL)
On Fri, Nov 1, 2019 at 7:54 PM Stephen Connolly
wrote:
>
> On Fri 1 Nov 2019 at 21:37, Elliotte Rusty Harold
> wrote:
>
> > Pass 1:
> >
Hi Andreas,
but the format of the timestamp is completely different ... doesn't that matter?
I was currently going for the option number 1 with removing the header.
In order to be 100% happy with this, I would prefer a setup where the normal
mechanisms are used if no maven.build.outputTimestap
Christofer Dutz wrote:
> Well I have a new candidate:
>
> maven-bundle-plugin
>
> Creates: Bnd-LastModified in the MANIFEST.MF
>
> Gotta find out a way to either suppress that entry (Would be great if it
> could consume the same property)
<_removeheaders>Bnd-LastModified
