Hi,
This looks to be a nice feature!
I have more concern on this new dependency.
Do we really want to depend on a single person project? [1]
What is the future of this project? If I look at the history groupId
namespace has changed recently from org.sonatype to com.planet57. [2]
So is it stable (in
Am 2016-06-11 um 13:27 schrieb Hervé BOUTEMY:
if someone has an objection, just tell and we can easily revert
Hervé,
thank you for the hard work.
I not sure wether this is related to recent changes to master or Maven
Core ITs master but I cannot pass ITs with 3.3.9
Maven: Apache Maven 3.3.
Github user manouti commented on the issue:
https://github.com/apache/maven-archetype/pull/9
Hello ptahchiev,
Thanks for the response. Yes seems to target this requested feature. I'm
fine if you would like to close this PR (I've linked to the Jira issue in the
SO question).
---
Am 2016-06-11 um 15:25 schrieb Anders Hammar:
Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing
some clear docs about how it is supposed to work from now on. Specifically
for the plugin I assume that the idea is that the release profile to use
should be specified explicitly?
Well I always end up with multiple release profiles because different orgs
need different GPG signing keys etc...
On Saturday, 11 June 2016, Anders Hammar wrote:
> Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing
> some clear docs about how it is supposed to work from now
Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing
some clear docs about how it is supposed to work from now on. Specifically
for the plugin I assume that the idea is that the release profile to use
should be specified explicitly? Also, if the releaseProfile in the
super-POM is
if someone has an objection, just tell and we can easily revert
Regards,
Hervé
Le samedi 11 juin 2016 11:26:10 hbout...@apache.org a écrit :
> Repository: maven
> Updated Branches:
> refs/heads/master 427f18c3a -> 644ac9c40
>
>
> [MNG-6038] use Gossip slf4j provider (with level color support
Github user hboutemy commented on a diff in the pull request:
https://github.com/apache/maven/pull/81#discussion_r66704747
--- Diff:
maven-embedder/src/main/java/org/apache/maven/cli/logging/impl/gossip/ColorRenderer.java
---
@@ -0,0 +1,165 @@
+package org.apache.maven.cli.log
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/81
I just committed the code, slightly modified since Maven general color
support was added in MNG-3507 (after extracting some code from this provider)
I tested with core ITs and fixed one little issu
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/81
---
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 enable
Ok, so adding to section in POM would be an acceptable path to
a solution?
Consider the following:
scm:hg:https://bitbucket.org/greatness/ambiance
scm:hg:https://bitbucket.org/greatness/ambiance
https://bitbucket.org/greatness/ambiance
bitbucke
Ah sorry...
did saw this issue is already scheduled on 3.0...
Kind regards
Karl Heinz
On 6/11/16 9:00 AM, Karl Heinz Marbaise wrote:
Hi,
This will break backward compatibility in a minor version which is not a
good idea..This something for 3.0.0
Marking as deprecated good idea...but chan
Hi,
This will break backward compatibility in a minor version which is not a
good idea..This something for 3.0.0
Marking as deprecated good idea...but changing the default...Hm..
Kind regards
Karl Heinz Marbaise
On 6/10/16 11:20 PM, micha...@apache.org wrote:
Author: michaelo
Date: Fr
13 matches
Mail list logo
