Am 01.02.19 um 00:33 schrieb Ricardo Wurmus:
> Hartmut Goebel writes:
>> The drawback of this approach is: This only works within the
>> build-system. Since within a normal environment or profile, there will
>> be no such unison repo. Thus for every day's work, users will still
>> download artifac
Hartmut Goebel writes:
>> and have a phase to build a union of these with symlinks. Hopefully,
>> maven will follow the symlinks.
>
> The drawback of this approach is: This only works within the
> build-system. Since within a normal environment or profile, there will
> be no such unison repo. T
Hartmut Goebel writes:
> * Debian stores the files in a system repository structured like
> above, see [9]. (Thought this seem not to be done for all packages,
> |e.g.|||[6] and [7] do not include ||these maven-repo files.)
> * Debian provides a script "mvn-debian" [8] which seem to
Hi,
Am 31.01.19 um 18:06 schrieb Julien Lepiller:
Here are my 2cent:
> We found that we need more plugins to be able to build maven projects, and
> that requires some metadata in the jar file. This metadata is generated by
> maven-plugin-tools-generators, and maybe we can write a thin java wra
Le 31 janvier 2019 11:00:42 GMT+01:00, Hartmut Goebel
a écrit :
>H Julien,
>
>as promised I've spend some time on a maven build system (as always
>when
>regarding maven it was much more time than expected). I did not yet
>create a build-system but want to share my insights so we can decide
>how
>
H Julien,
as promised I've spend some time on a maven build system (as always when
regarding maven it was much more time than expected). I did not yet
create a build-system but want to share my insights so we can decide how
to proceed further. If I'm wrong on some points, please feel free to
corre
