GitHub user dejan2609 opened a pull request:
https://github.com/apache/maven/pull/120
[MNG-6206] display deprecation build warning in case when dependencies use
metaversions (LATEST or RELEASE)
JIRA ticket: [MNG-6206: We should produce a WARNING by using RELEASE,
LATEST as versions
Github user dejan2609 commented on the issue:
https://github.com/apache/maven/pull/119
New changes are pushed via new commit (all commits will be squashed into
one eventually).
Solution is tested across different Maven versions (**3.0.5**, **3.1.1**,
**3.2.5**, **3.3.9*
Github user ebourg commented on the issue:
https://github.com/apache/maven/pull/118
Thank you. The add-source trick is a bit problematic for the Debian
packaging because we don't build the source jars, but we can live with a Debian
specific patch using the shade plugin instead.
---
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/118
ideas added to the MNG-6196 branch in
https://github.com/apache/maven/commit/c2a8787eb7450cb28d7f08698788c5e58a3f8a02
: no monkey patch any more
I kept dependency:unpack+build-helper:add-source i
Hi Stephen,
I tried this command on Fedora
*$ ps start,command -p 2712*
* STARTED COMMAND*
*13:31:38 /usr/libexec/evolution-calendar..*
I have this activity because of issue SUREFIRE-1302. When Maven process is
killed the forked jvm should not leak; otherwise *mvn clean* would not
delete target
tibor_: @stephenc Hi Stephen. Would these two work on OSX the same like on
linux and freebsd?
tibor_: ps -o start,args -p 27000
tibor_: java -Dppid=$PPID ...
I'd need more context to answer
Sent from my iPhone
