1 - yes
2 - yes (Maven tries hard to simplify things for users, but heh)
3 - yes, model ordering matters, most easily checked with `mvn
help:effective-pom`, so to say if depency A is before dependency B in
effective POM, same should be true for classpath as well.
HTH
T
PS: Sorry for bloated
Wow, so this stuff is literally "hot off the press"! Is this likely to end up
in the 3.x series, or need to upgrade to 4?
Also, once it goes in, can this please be documented somewhere more "official"
than a release notes thingy?
-Original Message-
From: Tamás Cservenák
Sent:
Thank you! I think my main takeaway here is that things (1) in flux (and
hopefully will improve in Maven 4) and (2) a bit complicated but
(3) I can still guarantee something comes first by listing it as the first
thing in the pom (is that right?)
Thanks once more!
Mark.
-Original
And here it is:
https://github.com/apache/maven/pull/1212
To have this tested, first build this
https://github.com/apache/maven-resolver/pull/322
then this:
https://github.com/apache/maven/pull/1212
And you will end up with maven:
- that fully delegates to resolver classpath ordering (removed
Re-sending... didn't go through I think:
In the release notes for Maven 2.0.9:
http://people.apache.org/~jvanzyl/maven-3.1.1/docs/2.0.9/release-notes.html
It says: "introduced deterministic ordering of dependencies on the classpath.
In the past, natural set ordering was used and this lead to odd
I'm kind of glad you didn't notice ... I appreciated a peek behind the scenes :)
Re: effective POM ... THANK YOU for that bit of info.
You just saved me some un-countably large number of hours
-Original Message-
From: Tamás Cservenák
Sent: Thursday, July 27, 2023 11:34 AM
To: Maven
What a coincidence...
I just started looking at an old issue (was looking at some edge cases)
where even reproducer exists and tackles similar topic:
https://issues.apache.org/jira/browse/MNG-6357
Then I went to maven sources and resolver sources to ensure what is
happening.
Sadly, maven is not
Hello again
I wrote a test case with a very small Maven project (only trivial code)
reproducing the problem and a README.md file explaining the problem. The
Maven behavior is then reproduced on the command-line, and the expected
behavior provided by a command-line too. Unless there is some
The Apache Maven team is pleased to announce the release of the
Maven Indexer 7.0.4
https://maven.apache.org/maven-indexer/
Release Notes - Maven Indexer - Version 7.0.4
** Improvement
* [MINDEXER-195] - New Search API backend: remoterepository
** Task
* [MINDEXER-194] - Upgrade to
Maven says it can’t find
org.mule.tests.plugin:mule-tests-component-plugin:jar:mule-plugin:4.2.1 at
https://repository-master.mulesoft.org/nexus/content/repositories/releases/
I can’t find it myself either, because there is no tests directory under
If you browse their repo, you can see that 4.2.1 is indeed missing:
https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/tests/mule-tests/
Just use dependencyManagement to override the version or exclude it
(if it is transitive) from its parent dependency and add it
Hi,
Im using maven as part of my mulesoft anytime studio platform.
When I run the below command from command prompt I get the error below.
Let me know how to resolve this error.
Command:
maven -U clean install
Error:
[ERROR] Failed to execute goal on project mule-connectivity-parent: Could not
On Thu, Jul 27, 2023 at 3:33 PM Laird Nelson wrote:
> Now I'm running Surefire 3.1.2 and noting that this all no longer seems
> necessary: running mvn test -Dx=y without any special XML to "turn it into"
> a System property works fine (my test can assert
> System.getProperty("x").equals("y")).
>
I dimly remember that once upon a time many years ago you had to explicitly
specify the system properties to be made available to your JUnit tests
running under Surefire:
y
(The documentation for this element reads in total: "List of System
properties to pass to a provider.")
That is,
14 matches
Mail list logo
