IMHO, we still use 1.0.0 just because we forgot to upgrade in every place: even
the reference documentation still points to 1.0.0 [1], I'll update the doc
the 2 new parameters introduced for Maven 3 [2] are so cryptic: I don't know if
anybody use them...
Regards,
Hervé
[1] https://maven.apache
The Apache Maven team is pleased to announce the release of the
Apache Maven JAR Plugin Version 3.1.0.
https://maven.apache.org/plugins/maven-jar-plugin/
Important Note:
* Maven 3.X only
* JDK 7 minimum requirement
You should specify the version in your project's plugin configuration:
see also the comment at
https://issues.jenkins-ci.org/browse/JENKINS-44543?focusedCommentId=331874&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-331874
"(jenkins jobs don't have a terminal that jansi recognizes)."
On Tue, Apr 10, 2018 at 3:39 PM Arnaud Héritier
yes it's strange. With Jenkins I had the same problem.
I had to use a pipeline script like :
node {
stage('Prepare') {
git '
https://github.com/jenkins-demo/simple-maven-project-with-tests.git'
}
stage('Build') {
withMaven(maven: 'Maven 3.5.3', mavenOpts: '-Djansi.force=true'
GitHub user tivrfoa opened a pull request:
https://github.com/apache/maven-site/pull/16
Fix link to Ant example
I think the second link is refering to this file:
https://maven.apache.org/ant/build-a2.xml
You can merge this pull request into a Git repository by running:
$ g
I found differences of enabled JANSI between Windows/Ubuntu regarding
combination with "-B".
This is minimum configuration per platform if you want to enable JANSI
together with using -B:
Windows: mvn -B -Dstyle.color=always
Ubuntu: mvn -B -Dstyle.color=always and MAVEN_OPTS=-Djansi.force=true
Was
Why we do not use Version 1.1.0 of Settings XML?
The latest Maven dist has 1.0.0.
Do we have a reason to use older version 1.0.0?
There are some differences regarding repo layout and proxy default value.
Cheers
Tibor
