@Slawomir: It is mainly due to some dependencies like jdepndency which is
java 8 only so the plugin is overall java 8 now.
@Tibor: changing a 7 to a 8 in a pom, hope it does not take us a day ;)
If we say it is java 8, it will not change much but if we say it is java 7
we must revert a few things
Can we cut a new release of m-shade-p?
Is there any pending bug fix or improvement that you want to include in the
release?
Cheers
Tibor
In my company, I also used 1GB for Xmx of Java Heap for the Jenkins JVM and
it was enough.
The subprocesses like Maven need to have much more memory to allocate for
themself rather than Jenkins JVM.
T
On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier wrote:
> I am looking at our builds and I try t
What's the cost of this task? A day?
Do you want to include it in the release version 3.4.0?
On Wed, Jul 21, 2021 at 8:09 AM Romain Manni-Bucau
wrote:
> Hi all,
>
> shade plugin pom defines java version to 7 (1.7) but it uses streams which
> are java 8 only, should javaVersion property be upda
Hi,
very interesting case but I can't see 1.8 streams in
https://github.com/apache/maven-shade-plugin/tree/master
Can you point where you found it?
By the way, maybe it's time to start switching plugins to 1.8 ...
śr., 21 lip 2021 o 08:09 Romain Manni-Bucau
napisał(a):
> Hi all,
>
> shade pl
ok Gavin
Thanks for your feedback
It's what I wanted to be sure, I didn't want to break something you are
maintaining
On Wed, Jul 21, 2021 at 6:47 PM Gavin McDonald wrote:
> Hi Arnaud
>
> Surem feel free to tweak the node configs directly, these configs are not
> in version control or puppet.
>
Hi Arnaud
Surem feel free to tweak the node configs directly, these configs are not
in version control or puppet.
On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier wrote:
> I am looking at our builds and I try to understand why our agents are
> often disconnected during the builds.
> We have in g
I am looking at our builds and I try to understand why our agents are often
disconnected during the builds.
We have in general a stacktrace like
maven6 was marked offline: Connection was broken: java.io.IOException:
Pipe closed after 0 cycles
at
org.apache.sshd.common.channel.ChannelPiped
dependabot[bot] opened a new pull request #40:
URL: https://github.com/apache/maven-artifact-transfer/pull/40
Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.5 to 1.7.32.
Commits
See full diff in https://github.com/qos-ch/slf4j/commits";>compare view
I am not sure about the setup
AFAICS we don't use any JDK installer (
https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
different JDKs are supposed to be installed directly on the agent ?
I am not sure how it was done on the previous environment
On Sun, Jul 18, 2021 at 5:30 PM
10 matches
Mail list logo
