That was great advice, Bernd. I never was aware of that goal before,
mostly using the 'analzye' and 'tree' goals. I also see that it is
possible not use includes and excludes, i.e. to just purge what annoys
you and not a whole 60 GB or so local repo. For reference:
On Sat, 26 Mar 2022 at 2:06 pm, Nils Breunese wrote:
> Olivier Lamy wrote:
>
> > should be 1.7 not 1.17 ;)
>
> No, 1.7 is for Java 7. For Java 17 it should be just 17.
The email subject says “ question java 1.7 support”
But yeah should be simply 17
Use release flag rather than sources and
Olivier Lamy wrote:
> should be 1.7 not 1.17 ;)
No, 1.7 is for Java 7. For Java 17 it should be just 17.
Nils.
> On Sat, 26 Mar 2022 at 13:48, Alexander Ushakov <
> alexander.ushakov.em...@gmail.com> wrote:
>
>> Hello!
>>
>> I am trying to play with Apache Kafka and craft next pom.xml
>>
should be 1.7 not 1.17 ;)
On Sat, 26 Mar 2022 at 13:48, Alexander Ushakov <
alexander.ushakov.em...@gmail.com> wrote:
> Hello!
>
> I am trying to play with Apache Kafka and craft next pom.xml
>
> ```xml
>
> xmlns="http://maven.apache.org/POM/4.0.0;
>
Alexander Ushakov wrote:
>
>org.apache.maven.plugins
>maven-compiler-plugin
>3.1
>
> 1.17
> 1.17
>
>
>
> (…)
>
> results with error
>
> ```
> [ERROR] Failed to execute goal
>
Hello!
I am trying to play with Apache Kafka and craft next pom.xml
```xml
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
streams.examples
-U works on release artifacts as well. Alternatively you can delete the version
(either manually in the filesystem or with a maven
dependency:purge-local-repository).
I think the Never-policy was not meant to deal with errors, it is more about
immutability of the actual releases.
Gruss
Bernd
Hi fellow Maven users,
I have used Maven for 10 years or more and I’m writing with a first. I have a
project which was set up in Jenkins with a settings.xml that has updatePolicy
set to “never” for a certain repository.
I have experienced that when Maven 3.3.9 fails to resolve an artifact for
