Hi All,
I was wondering whether the statement that lack of system properties
expansion in maven.config has be done by design and it is rather unlikely
to change it is still valid (MNG-5930, commented by Jason). Below a link to
the tiny change that would help me with i.e. MNG-4686, even the more nar
Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/88
@hboutemy - changes were made as per discussion. Please review and sign off.
Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/91
Closing this PR, as Herve mentions this won't be usable on the console. I
think this ticket can be descoped.
I am happy to reopen again, if it is required to.
---
If your project is set up f
Github user rajivpjs closed the pull request at:
https://github.com/apache/maven/pull/91
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/maven-shared/pull/10
---
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
These will both confuse people. Mercury is a failed project from the past here
and no one will know what the project is from the name Caduceus. Please, let’s
use a real word that best represents (yes, maybe not ideal) what the library
will do.
> On Aug 8, 2016, at 4:22 PM, Robert Scholte wrote
Github user rkorpachyov closed the pull request at:
https://github.com/apache/maven-plugins/pull/51
---
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 feat
GitHub user sschuberth opened a pull request:
https://github.com/apache/maven-plugins/pull/90
Do not enable failOnMissingClassifierArtifact by default
In the docs it says the default is "false", which also is the safer choice,
so align the actual initialization with the "defaultV