Hi, Dennis,
I'd suggest the following approach:
- Write a small stub that replaces Logger.getLogger(), so that a small
facade is returned, which behaves like JUL,
but uses the Maven logger internally.
- Use the shade plugin to ensure that Logger.getLogger is redirected
to your stub.
That
GitHub user ananich opened a pull request:
https://github.com/apache/maven/pull/31
Mac OS X - way of getting JAVA_HOME location
Based on [man
page](https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/java_home.1.html)
You can merge this pull
2014-11-14 21:19 GMT+01:00 Kristian Rosenvold kristian.rosenv...@gmail.com:
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20750styleName=projectId=11126
This puts the 2.5.X range at an accumulated 73 bug fixes; this release
contains a few regressions from
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20750styleName=projectId=11126
This puts the 2.5.X range at an accumulated 73 bug fixes; this release
contains a few regressions from 2.5 and 2.5.1.
Most notable for this release are:
Rewritten duplicate handling
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/26
---
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
Hi,
+1 from me...
Kind regards
Karl Heinz Marbaise
On 11/18/14 5:01 PM, Kristian Rosenvold wrote:
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20750styleName=projectId=11126
This puts the 2.5.X range at an accumulated 73 bug fixes; this release
contains a
Hi All,
I would like to get your help. I am still trying to explain that very large
commercial company (don't mean ASF) should not have one hotspot POM with
only one dependencyManagement (DM). One DM is too weak rule, i would say.
My arguments are that one DM section will not fit to the needs of
My strategy is for the corporate POM to contain the fundamental settings
like locking down maven plugins and any global legal stuff. Then each
department should come up with their own POM under that, then the same for
each project.
Cheers,
Paul
On Tue, Nov 18, 2014 at 12:26 PM, tibor17
Thx Paull
This I am basically trying to explain them as well. They are newbies and the
funny thing is that they are ignoring us. My proposal was to serve a contact
of Maven PMC experts so that they would pay for new environment, build
process, POM structures, and CI systems setup but again with no
This I am basically trying to explain them as well. They are newbies and
the
funny thing is that they are ignoring us. My proposal was to serve a
contact
of Maven PMC experts so that they would pay for new environment, build
process, POM structures, and CI systems setup but again with no
Hello there,
I need 2 more binding votes :-)
Regards
Mirko
--
Sent from my mobile
On Nov 15, 2014 12:52 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
tested with Maven 3.0.5, 3.1.1, 3.2.1, 3.2.2, 3.2.3 are done.
so +1 from me...
Kind regards
Karl Heinz Marbaise
On 11/14/14
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/71
[SUREFIRE-757] Project encoding properties is not checked
Only added a hint to setup property referenced by
${project.reporting.outputEncoding}.
You can merge this pull request into a Git
+1
On 15 November 2014 08:16, Mirko Friedenhagen mfriedenha...@apache.org wrote:
Hi,
We solve 3 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140version=20557
Bug
* [MPMD-192] Regression MPMD-89 is showing up with Maven 2.2.1 again
for maven-pmd-plugin-3.3
After I wrote my response, I realized that I neglected the whole dependency
management aspect. +1 with Anders. I am with him. There is no need to lock
down dependencies in any corporate/division POM. Those are product concerns
which are appropriate to use dependency management. Oh and I use BOMs
14 matches
Mail list logo
