Hello Lars,
ignoring your second email, I felt like it is normal for the pom to ignore
the shaded dependencies. This is how Maven works.
For me, it should be the job of a SBOM (CycloneDX format or SPDX for
exemple) to keep the information of what the shaded jar contains.
This is the role of
Hello Tommy, Lasse and all,
as Lasse suggests it *may* be a good fit for classifiers. But I want to
emphasize that to my knowledge, the miscellaneous artifacts with different
classifiers sharing the same 'main' artifact HAVE TO BE INSTALLED OR
DEPLOYED AT THE SAME TIME. So if you deploy your
Thanks Tamas for all your work. I'll sure have a look (but not right now as
I'm in a train station on a phone). Just to mention a feature I missed
yesterday in m-d-p: ability to filter on classifiers including *wildcards*.
Because I have dependencies with this kind of classifiers: natives-win,
Hey !
First of all, for everyone asking more info to understand where the pom
values come from and how they are computed, I think a very useful command
is:
**
mvn org.apache.maven.plugins:maven-help-plugin:3.4.0:effective-pom
Hello Mantas,
I think you did not explain what you are trying to achieve. Or at least I
did not really understand.
Are you trying to lower the build time ?
If yes, then I would advise to use a Maven property for the configuration
in the root pom
Then most of your build could be run with
to add on Joseph answer: if you are in the B directory, then only B is in
the reactor (more or less meaning "the list of project being built by this
Maven invocation").
My rule of thumb is to never do that and always run from the root. If you
want to speedup the build and you know that only B has
The pom.xml will be automatically produced even without the '-DpomFile'
argument. But it will be very minimalist. PAssing your own pom allows to be
explicit regarding the dependencies, the licences etc...
Regards
Le dim. 4 févr. 2024 à 11:52, sandisks...@gmail.com
a écrit :
> use 'mvn
Hello all,
I have a large build that completes normally in single threaded build but
freezes in multithreaded builds. Problem is I do not know which module and
which plugin is frozen. The last logs that get displayed are the classic
end log for a given module and the logs always stop there. So I
n issue to have something to commit on, if anyone feels like
creating a PR.
Cheers
--
Alexander Kriegisch
https://scrum-master.de
Francois Marot schrieb am 11.01.2024 16:16 (GMT +07:00):
> Hello,
>
> First let me wish the Maven community a happy new year.
> I recently faced a pr
Hello,
First let me wish the Maven community a happy new year.
I recently faced a problem with the shade plugin generating randomly
different dependency-reduced-pom.xml.
The difference lies in exclusions defined in miscellaneous dependencies
randomly being missing in the pom.
This part of the
for the record, I find it simpler to hardcode it in the pom like this:
-Djava.library.path=...
Here is my pom:
org.codehaus.mojo
exec-maven-plugin
runUnobfuscated
java
${session.executionRootDirectory}/${buildDirectory}/natives/:${java.home}/lib/amd64/
For the record, Spring Boot has no hard requirement of using a 'parent'
pom. It is just a bit simpler and in most of the examples online.
But you can simply set the scope import in your dependencyManagement. This
works.
org.springframework.boot
spring-boot-dependencies
Hello Arno and Tamas
and thank you for the detailed and very interesting explanation.
One question arises though: is there any way to make Maven ignore the
origin ?
Have a good day
François
Le lun. 6 nov. 2023 à 13:20, Tamás Cservenák a écrit :
> Howdy,
>
> The Maven local repository
verage that for build cache issues?
>
> On Sun, Sept 24, 2023, 5:14 a.m. Francois Marot
> wrote:
>
> > Just a suggestion: you could use ci-friendly Maven to pass in a version
> > depending on the commit Id/sha1 on the command line. Like mvn
> > -Drevision=
> > More i
Just a suggestion: you could use ci-friendly Maven to pass in a version
depending on the commit Id/sha1 on the command line. Like mvn
-Drevision=
More info:
https://maven.apache.org/maven-ci-friendly.html
Regards
Le jeu. 21 sept. 2023, 15:49, Ben Tatham
a écrit :
> Hi,
> I'm loving the ideas
Hello Florent,
i'll suggest something while I know this is not exactly what you asked for.
But i'll try nevertheless, it may help :)
If you could change your requirements a bit to change the *version* instead
of the artifactId, then you could use the
ci-friendly concept in Maven (
You should get rif of all the dependencies and then test if your problem
has disappeared.
If yes, all good, and next time let Maven handle transitive dependencies
for you.
If no, then you have a real problem that maybe some people here will be
able to help you with.
But overriding all the
gt;
> On Fri, Jul 8, 2022 at 5:43 PM Francois Marot
> wrote:
>
> > I believe you used the shade maven plugin or equivalent.
>
>
> Yes
>
>
> > I faced this
> > problem multiple times and to my knowledge, there is no "good" solution.
> >
>
&
Hello Niels,
I believe you used the shade maven plugin or equivalent. I faced this
problem multiple times and to my knowledge, there is no "good" solution.
The problem is that Maven computes the dependency graph for all modules of
the reactor right at the start. But when the shade plugin
Hello Florent,
I have had this problem a few years ago, and from what I can remember it is
the expected behavior. Or at least this is the way it is right now.
Sorry, It is from memory and I do not have any link to share nor
explanation about it, but at least you know you are not alone !
Regards
Hello Clebert
I hope my comment will help you.
In my experience, using the shade plugin is tricky because the rule of
thumb I came up with is: "your shaded artifacts must be the last artifact
to be built in your multi modules Maven project".
Which can read "you must not depend onto your shaded
Michael, I do not agree. As a user and maintainer of the build chain in my
company, I think Maven would really benefit from an out of the box
solution. I think any user is susceptible to the bug by launching multiple
Maven instances at the same time on his computer. Bugs then encountered are
François
Le lun. 4 oct. 2021 à 21:22, Michael Osipov a écrit :
> Am 2021-10-04 um 14:31 schrieb Francois Marot:
> > Hello all,
> >
> > I would like clarifications on MNG-2802[*] that seems to be solved. If I
> > understand correctly it solves the problem where multiple
arently also is an Hazelcast-based version:
> https://maven.apache.org/resolver/maven-resolver-named-locks/index.html
>
> On Mon, Oct 4, 2021 at 2:32 PM Francois Marot
> wrote:
>
> > Hello all,
> >
> > I would like clarifications on MNG-2802[*] that seems to be so
Hello all,
I would like clarifications on MNG-2802[*] that seems to be solved. If I
understand correctly it solves the problem where multiple simultaneous
Maven executions shared the same local repository.
I have been keeping for years a bit of code in my Jenkinsfiles ensuring the
local repos
I thought preemptive=false is the default - but anyway, good that it
> works now for you.
>
> Gruß
> Bernd
>
> --
> https://Bernd.eckenfels.net
> ____
> From: Francois Marot
> Sent: Monday, August 30, 2021 4:43:33 PM
> To: Maven Users Li
mini/guide-http-settings.html#Example:_Using_Preemptive_Authentication
>
> Greetings
> Bernd
>
>
> --
> http://bernd.eckenfels.net<http://bernd.eckenfels.networks>
>
> Von: Francois Marot
> Gesendet: Friday, August 20, 2021 4:12:33 PM
&g
Hello Maven users,
I face a strange problem that I'd like to describe. I'm setting up a new
artifact repository and this is JFrog's Artifactory.
I have build freeze problems (which I still no have solved) so during my
investigations I found this in Artifactory's logs:
- - - - - - - - - - - - - -
Hello,
maybe the workaround indicated here will help you:
http://maven.40175.n5.nabble.com/Finding-SNAPSHOT-dependencies-without-compiling-first-td5998636.html#a5998639
But I'm not confident on the rasons why it works like this...
*- - - - -François Marot*
On Mon, 6 Jul 2020 at 23:16, Anton
elp 1]
> >>
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> >>
> >> /tmp/test-parent/child2 $ cat
> >>
> >>
> ~/.m2/repository/com/sample/child1/1.1.0-SNAPSHOT/child1-1.1.0-SNAPSHOT.pom
> >>
Hello,
I can confirm that you sample project works as intended once you add the
missing configuration for the flatten plugin. Without it the pom.xml
installed in your local repo are not correct because of the placeholders in
the .
I just copy pasted the content as explained here:
Hello all,
I have a simple requirement: I would like to determine very fast if my
multi-module project has any SNAPSHOT dependency.
First try was with the /mvn dependency:tree / command and grepping for the
word SNAPSHOT. But the dependency plugin seems to use the repository
dependencies, so it
Here is a self contained test in a single pom with no other files that
demonstrates the problem:
https://gist.github.com/fmarot/3bc638212e52ff1e0c55843c7fb6bbaa
The problem being that pre-existing env variable are not redefined even if
explicitly set in surefire.
--
Sent from:
Hello all,
just want to notify of a bug we found today when switching our surefire
version from 2.x.y to the latest 3.0.0-M4 (
https://blogs.apache.org/maven/entry/apache-maven-surefire-version-3 ). It
creates problems with environment variables which seem to be incorrectly
set. As a consequence,
Hello again (I'm active there today ;) ),
this time I'd like to tell you about a feature I would like, and maybe some
of you will have something to advise me.
I have to generate a report listing all my dependencies (and I have tooo
many !) and for each one I have to provide a little text
Hello all,
First of all thanks thanks and thanks again to the Maven devs, you rock !
Then a question:
is there a way to limit the dependency convergence check (in Maven enforcer
plugin -
https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
) to a given artifactId (or a list
I'm sorry to insist but nevertheless I insist ;). I may have misunderstood
the problem but as I understand it, the whole problem can be sumed up by:
" the fact that the repository adds a number at the end of the deployed
files is a problem because not all artifacts deployed from the same reactor
t related to the overall issue of
> https://issues.apache.org/jira/browse/MNG-6581
>
> Thanks,
> T
>
>
>
> On Fri, Sep 13, 2019 at 8:32 PM Francois Marot
> wrote:
>
> > can you tell us a little bit more about your problem please ?
> > You say &q
can you tell us a little bit more about your problem please ?
You say "Currently, artifact deployed as snapshot at Maven repository has
the following format: artifactId-version-timestamp-NN ". Do youmean the
filename in the repo ? If so, why is it a problem for you ?
Share more with us and I
I remember talking with Herve Boutemy at Devoxx FR and he told me about an
upgrade of the help:effective-pom (
https://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html )
that would not only display the effective pom but also for each line the
source pom where this value comes
Hi,
if you run multiple jobs concurrently but all are agnostic to one another (I
mean they only depend on Maven Central's non SNAPSHOT dependencies) and if
disk space is a problem then you can try to have a common local repo.
But if you want to play safe, you should use a per Jenkins executor
Sorry, seems my previous message missed the copy pasted content ! Here it is:
pipeline {
agent { node { label paramsMap.agentParam } }// the build will
only run on nodes (ie slaves) indicated
environment {
// To prevent simultaneous job working in the same
Hello, I suffered from similar symptoms until I adjusted the build to have
per-Jenkins-executor MAven cache. So in the end, my Maven configuration in
my Jenkins pipeline looks like this:
As you can see, I do not use any Jenkins-Maven plugin and Maven is
configured by hand. Hope it may help
Hi Nikki,
Regarding your question, I'm not sure of what is a "reactor of reactor"...
by 2 separate "projects" I mean 2 different build. Hence 2 different
"reactor".
As I understand it, the reactor is the sum of all Maven modules
participating in the build. Usually in the case of a multi-modules
ated projects, not part of the
same reactor build to prevent problems or surprise for newcomers.
Regards
Francois Marot
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To unsubscribe, e-mail: u
The new way to deal with such situation is described here:
https://maven.apache.org/maven-ci-friendly.html
0-SNAPSHOT
1.2.${revision}
and let Jenkins run Maven like this mvn deploy
-Drevision=${env.BUILD_NUMBER} (or maybe just $BUILD_NUMBER depending on the
way you run Jenkins)
--
Sent
Hi,
I have the same "problem" here which is not really a problem: I deploy the
parent pom (and the parent's parent and so on) and voila. As parent are only
pom, no real package or jars, this not really a problem.
But I think the Flatten Maven Plugin
https://www.mojohaus.org/flatten-maven-plugin/
Yaron is right: you may find problems in your build by NOT moving the
.m2/repository folder. You may discover that specific files were available
only in your local repo and not anywhere else (Maven Central or your local
proxy such as Archiva/Artifactory/Nexus). And this is a good time to
discover
I would guess that Ivy can work a lot better with Maven repositories than
Maven can with Ivy repositories. I would investigate a one-shot scripted
migration of your Ivy repo to a new Maven repo and force existing publishers
to the Ivy repo to configure Ivy to publish to the new Maven repo.
But I
Hi Alex,
maybe you could paste here the output logs of the failing execution. I'd
like them to be sure I understand the problem.
Cheers
Francois
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To
For the record, it seems like the "EXECUTOR_NUMBER" variable (
https://issues.jenkins-ci.org/browse/JENKINS-31391 ) should be available to
be able to easily specify a per-executor repo.
So something such as this should do the job:
mvn -Dmaven.repo.local=$JENKINS_HOME/.m2/$EXECUTOR_NUMBER/ ...
I regularly have the same problem on my Jenkins build server: either
"corrupted zip file" or "cannot find symbol" and the only explanation for me
was concurrent build. I has never thought of having Maven local repo
specific to an executor, thanks Bernd Eckenfels, that's a really good point
!
I was
What do you mean by "pushing maven-metadata.xml which can be corrupted" ?
Are you talking about https://issues.apache.org/jira/browse/MDEPLOY-221
which is solved in Maven 3.5.2 (even 3.5.1 I think) ?
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
Thanks Robert, Karl, I created a JIRA MNG-6336 here:
https://issues.apache.org/jira/browse/MNG-6336
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To unsubscribe, e-mail:
Thanks Robert, that makes sense. At least it explains why aggregator will not
work in my case.
Do you think my case is not so uncommon and I should open a bug, or I
misunderstood "the Maven way" and have to adapt ?
Regards
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
Thanks for your response Hervé,
I've made a sample plugin here:
https://github.com/fmarot/print-dummy-maven-plugin
When included in the "" section of a parent pom of a
multimodule Maven project, the behavior is shown: when running 'mvn
validate', "dummy" is printed for for each and every child
[Sorry, re-posting with correct formatting]
Hi all & happy new year !
I have a question regarding plugin development.
I have made a custom plugin and would like to make it's Mojo executed once
*and only once* in my whole reactor build. If I include it in my parent pom
(not in pluginManagement),
Hi all & happy new year !I have a question regarding plugin development.I
have made a custom plugin and would like to make it's Mojo executed once
*and only once* in my whole reactor build.If I include it in my parent pom
(not in pluginManagement), then by default it is executed once at the root
Thanks for the reply Olivier, but I don't think I can "attach" . Let me
explain:
Basically, I want to deploy someJar.jar and at the same time declare a
dependency:someJar.jar --> redist-cpp.zip
redist-cpp.zip is already stored in Archiva.
someJar.jar is not produced by Maven.
If I "attach"
Hello all,
I have a need to explain to a third party how to deploy a jar on my
repository (Archiva). But
- this jar is not generated by Maven (it contains DLLs to be loaded through
JNA)
- I'd like the third party to be able to declare dependencies of this jar
(some zip containing some DLLs). So
I'm no expert at all, but just to let you know: last time I tried the test
harness plugin, I also gave up... :(
I think some advocate to use the maven-invoker-plugin to test in real
conditions with much less dependency problems. You can have a look there:
Hi all,
I'm writing a plugin whose goal is to output a dependency graph *at the scm
level*. Meaning I don't really care about individual dependencies but about
the source control manager (git usually) where they come from.
I hope it will help to know in which order we must release all our
Hi Kevin,
I think you are facing more or less the same problem I faced before (
http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-amp-artifactId-but-different-classifiers-td5838931.html#a5838934
).
So to sum up:
- if you want to add 2 native artifacts differing by the
Hello everyone,
I wanted to advertise a "new" Maven plugin that may help you deal with
native dependencies (.so, .dll, or whatever, as you may find other uses).
It is forked from an existing but inactive plugin (
https://code.google.com/archive/p/mavennatives/ ) where I added a few
features.
I
Hello Pavan,
it's hard to tell exactly but in Eclipse (Eclipse JEE at least) if you
declare a tomcat instance in the "server" window, and import your maven
modules with m2e, you should be able to deploy to Tomcat without problems.
No more needs for command-line clean/install/deploy (as long as
I have kinda the sae project: 50 or so modules, 3 'leaf' artifacts (I coined
the term 'leaf' to designate the artifacts that will actually be shipping
outside.
For me those 3 artifacts share the fact they are each an obfuscated
über-jar, and each composed of a combination of the other artifacts.
OK all, so I've taken the not so clean but should solve my problem faster
road... I publish the 2 zips separatly on Archiva.
But now, my main build that declare dependencies on them both (as 'runtime')
seems to randomly fail, looking for one or the other. If I publish one of
the 2, the main build
OK, so Maven only sees the most recent one uploaded because on Archiva, the
maven-metadata.xml file is updated each time with the timestamp of the
most recent one (either *-linux or *-win). But the 2 qualified artifacts do
not share the same timestamp so one of those is not found leading to build
and should be false for the second call.
Jeff
On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot francois.ma...@gmail.com
wrote:
Thanks Sandra,
but I'm not sure I understand: I already use the -Dclassifier= parameter
in
the 2 command I copy/pasted above.
Do you mean setting linux/windows
Hello all,
I'm in the process of converting an existing build to Maven.
I have 2 Jenkins jobs building the same native library on 2 different
systems (win / lin). At the end of each one, I want to deploy them on my
Archiva repo.
So I execute the following commands :
On a Linux computer:
mvn
-Dclassifier. For the Linux build I would use
-Dclassifier=linux and for the Windows build -Dclassifier=win.
Best regards,
Sandra
Am 29.06.2015 um 09:53 schrieb Francois MAROT:
Hello all,
I'm in the process of converting an existing build to Maven. I have
2 Jenkins jobs building
Hi Dan,
I suggest you simply run this command:
mvn dependency:copy-dependencies
it will copy all dependencies of your project into ./target/dependencies (or
something similar, I don't exactly remember).
Then, after running mvn package, just start your program by using the
wildcard to list all
Thanks Graham, this makes a lot of sense and I totally agree this would be
the best. But as I also have to convince colleagues and to make compromises
I hope maybe someone knew a magical plugin ;)
and no, the data I work with is large and a whole and people do not want to
work with a small subset
Hi all,
I'm in the process of switching to Maven for a large ANT project and have a
question regarding my test data.
I'd like those data to be versionned and stored in the Maven repo. But
currently those data are huge (let's say a 1-2 gigabytes once zipped). So I
imagine that if stored in the
74 matches
Mail list logo
