Hello everybody,
in my CI builds I like to suppress download messages. I do this by setting:
MAVEN_OPTS="-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=WARN
-Dorg.slf4j.simpleLogger.showDateTime=true -Djava.awt.headless=true"
Now when calling Maven 3.3.9 in
Github user asfgit closed the pull request at:
https://github.com/apache/maven-shared/pull/15
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
notice that we have a Wiki page for these:
https://cwiki.apache.org/confluence/display/MAVEN/Java+9+-+Jigsaw
The javadoc-plugin upgrade requirement is described: the fix in the upgrade is
intentional for Java 9, and not some coincidence :)
Regards,
Hervé
Le samedi 9 juillet 2016 13:59:30 Mark
when they will upgrade their dependency version, they'll recompile: I don't
really know where (if) this code is used, but I don't expect to get binary
compatibility issues in real life on this
yes, probably moving this whole cli/javatool somewhere else would be a better
choice: but I don't know
np
that's why we have dist-tool reports on Jenkins [1]: finding these little
forgotten steps were a nightmare before, but now, it's just about tracking
this job's failures :)
Regards,
Hervé
[1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/
Le samedi 9 juillet 2016 12:34
Hi Hervé,
This will already break backwards compatibility because the signature has
changed. In other words: projects using this method need to be recompiled;
they can't simply switch to this version.
So is it worth keeping this piece of code here?
Robert
On Sat, 09 Jul 2016 00:32:00 +020
Hi Hervé,
thanks for fixing that...simply missed that.
Kind regards
Karl Heinz
On 7/9/16 12:32 PM, hbout...@apache.org wrote:
Author: hboutemy
Date: Sat Jul 9 10:32:34 2016
New Revision: 1751994
URL: http://svn.apache.org/viewvc?rev=1751994&view=rev
Log:
SCM 1.9.5 released
Modified:
mav
After digging a bit deeper,
org.apache.maven.plugin.issues.Issue#getTitle is only referenced in
the changed GitHubDownloaderTestCase.
I changed the getter visibility to private (only test I had to adapt
was above GHDTC) and ran 'mvn -Prun-its clean verify' without issue.
In GH you may set a descr
Hello Robert,
firstly I just resurrected the state as it was before. The current
changes-plugin-release does not output the "title" of GH issues
anymore but the complete body which is not useable in a tabular
output.
I am a bit afraid, that there is a mismatch between JIRA and GitHub
here. JIRA's
