Hello
I have a Maven Java project which produces a JAR (packaging = JAR). I am using
external SonarQube scanner to scan my source code (SonarQube is not configured
inside pom.xml). I am first building my project using "mvn clean package", then
I execute SonarQube Scanner on it.
The issue is that
mvn dependency:copy-dependencies might be your friend...
https://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
Am 11.11.20 um 10:16 schrieb Milan Tomic:
Hello
I have a Maven Java project which produces a JAR (packaging = JAR). I am using external
SonarQube scanne
Ranges can be used in released artifacts which I have done myself, but
it means you won't have reproducible builds. So be careful and be
aware if you use them...
>From your version range I assume you want any v6.7.x and newer but not
any v7.x release. So I would have done
[6.7.0,6.999.999)
I have
On 11.11.20 10:16, Milan Tomic wrote:
Hello
I have a Maven Java project which produces a JAR (packaging = JAR). I am using external
SonarQube scanner to scan my source code (SonarQube is not configured inside pom.xml). I
am first building my project using "mvn clean package", then I execute
So
as Tomo said:
1. version ranges make dependencies selection unstable: is it really
necessary? (I personnally never use because of the build instability it adds,
given I'm trying to go even beyond stable build: I'm working hard on
Reproducible Builds [1]. Then my experience on detailed behaviour
On 11/10/20 2:54 PM, Maxim Solodovnik wrote:
Hello Maven experts,
one sub-dependencies of our project has following
[6.7.0,7.0.0-SNAPSHOT)
I think you may want to use
[6.7.0, 6..)
instead.
- Florian
OpenPGP_0x8CAC2A9678548E35.asc
Description: application/pgp-keys
OpenPGP_sign
Hi users of Apache Maven,
We are working on MEAR-153 (https://issues.apache.org/jira/browse/MEAR-153)
to implement skinnyModules option for the Maven EAR Plugin.
Refer to https://github.com/apache/maven-ear-plugin/pull/24 for the changes
which can be used to try skinnyModules option which is a lo
Thanks for your answers
Unfortunately I feel the main question remains unanswered :(
I'll try to re-phrase it:
Is it possible to specify the range in a way it will check release versions
only
So if [1.0.0, 10.0.0) is specified
2.1.0-SNAPSHOT, 3.1.1-SNAPSHOT, etc. will NOT be checked?
by checki
On 11/11/20 2:47 PM, Maxim Solodovnik wrote:
Thanks for your answers
Unfortunately I feel the main question remains unanswered :(
I'll try to re-phrase it:
Is it possible to specify the range in a way it will check release versions
only
So if [1.0.0, 10.0.0) is specified
2.1.0-SNAPSHOT, 3.1.1
You may be able to configure/improve this by setting up your
repositories (eg the updatePolicy and type of artifacts) see
https://maven.apache.org/pom.html#repositories
-M
-
To unsubscribe, e-mail: users-unsubscr...@maven.ap
10 matches
Mail list logo