Le sam. 18 avr. 2020 à 21:52, Hervé BOUTEMY a
écrit :
> sorry, I'm a user of none, and Tomcat was the only one cited: happy to get
> feedback from people doing and hosting wars.
> Nobody asked for reproducible wars, perhaps I'm just trying to do too much
> while I'm not building such artifacts my
sorry, I'm a user of none, and Tomcat was the only one cited: happy to get
feedback from people doing and hosting wars.
Nobody asked for reproducible wars, perhaps I'm just trying to do too much
while I'm not building such artifacts myself...
I know there are many implementation of war hosting.
Hervé, can you clarify why you mention so strongly tomcat?
Just out of my head tomcat, undertow, vertx, netty, camel, all cxf
transports (including standalone, talend sdk, wildfly, tomee, meecrowave,
restlet, quarkus, helidon, jetty, resin, play, akka-http, xnio and much
more are affected at war a
SNAPSHOTs and releases are similar from certain points of view and different
from others: what interests me is that we vote on releases, which are the only
official states we publish (as a source-release.zip tarball disconnected from
scm), but we don't do it on SNAPSHOTs, which are only intermed
Snapshot or releases are not different until you force a pre-release step
to hardcode the timestamp in the pom which would defeat release process
until done in release plugin IMHO.
Using scm meta is not that bad in that aspect.
Side note: this is not a war plugin issue and affects jar plugin too c
keeping SNAPSHOTs reproducible with calculated value for timestamp is an
option that can be chosen by some people
assuming SNAPSHOTs are not reproducible seems a reasonable option: requirement
for reproducible SNAPSHOTs is really different from requirement for releases
IMHO, the misc strategies
Hi everyone,
I got the same issue for my current work webapps (not at archive level but
docker image level - I'm using jib and it enforces a "constant" timestamp).
I solved it by using last commit timestamp as file timestamp. Indeed it can
miss a "strict" cache hit but globally it is a good compro
everything is documented in the Git migration Wiki page [1]
gives a link to the documentation for the bundles themselves [2]
and if you look at our full sources descriptor [3]
you'll see corresponding line:
pointing to the git2svn mirror [4]
Regards,
Hervé
[1] https://cwiki.apache.org/confluenc
Le vendredi 17 avril 2020, 22:20:11 CEST Michael Osipov a écrit :
> Am 2020-04-17 um 22:00 schrieb herve.bout...@free.fr:
> > Reproducible Builds is now implemented in many plugins: it's time to work
> > on reproducible war files.
> >
> > I created MWAR-432 issue and implemented classical Reproduc
