Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So I'd like to change that to be able to customize mojo logging.
My first is idea is mojo with logger name ${groupId}:${artifactId} (ie
On Thu, Nov 15, 2012 at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So I'd like to change that to be able to customize mojo logging.
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So I'd like to change that to be able to customize mojo logging.
My
On Thu, Nov 15, 2012 at 8:30 AM, Jason van Zyl ja...@tesla.io wrote:
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
On Nov 15, 2012, at 8:33 AM, Benson Margulies bimargul...@gmail.com wrote:
On Thu, Nov 15, 2012 at 8:30 AM, Jason van Zyl ja...@tesla.io wrote:
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So
On Thu, Nov 15, 2012 at 8:30 AM, Jason van Zyl ja...@tesla.io wrote:
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug
Hello,
not a Maven-developer, but here are my thoughts: I think Jason's
solution using package.class conventions is more standard. When
someone asks for help, telling them to call (assuming -L would be the
option to set the loggers):
mvn -L
This is simply one of the pros for a logging framework which is domain specific
logging. I'll add it to the list.
On Nov 15, 2012, at 9:00 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hello,
not a Maven-developer, but here are my thoughts: I think Jason's
solution using
On Nov 15, 2012, at 8:40 AM, Gary Gregory garydgreg...@gmail.com wrote:
On Thu, Nov 15, 2012 at 8:30 AM, Jason van Zyl ja...@tesla.io wrote:
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's
I can see arguments on both sides of this question of how to pick the
logging ID. I'll start with my corner.
The convention of having a logger for each class, named after the
class, is just that. A convention. It serves well in many cases.
However, in my opinion, it threatens to become a sort of
On Nov 15, 2012, at 11:08 AM, Benson Margulies bimargul...@gmail.com wrote:
I can see arguments on both sides of this question of how to pick the
logging ID. I'll start with my corner.
The convention of having a logger for each class, named after the
class, is just that. A convention. It
2012/11/15 Benson Margulies bimargul...@gmail.com:
I can see arguments on both sides of this question of how to pick the
logging ID. I'll start with my corner.
The convention of having a logger for each class, named after the
class, is just that. A convention. It serves well in many cases.
On Thu, Nov 15, 2012 at 11:25 AM, Jason van Zyl ja...@tesla.io wrote:
On Nov 15, 2012, at 11:08 AM, Benson Margulies bimargul...@gmail.com wrote:
I can see arguments on both sides of this question of how to pick the
logging ID. I'll start with my corner.
The convention of having a logger
It looks like Markers[1] are supported in SLF4J and can be used in conjunction
with the class name to gain another axis of control:
[1] http://www.slf4j.org/apidocs/org/slf4j/Marker.html
So this is probably the way it should be done as you don't lose the hierarchy
and if you want an additional
+1
2012/11/15 Dennis Lundberg denn...@apache.org:
Hi,
We solved 29 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126styleName=Htmlversion=18308
There are still a couple of issues left in JIRA:
Hi,
I'd like to release Maven Compiler 3.0
We fixed 9 issues.
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18537styleName=TextprojectId=11130Create=Create
Staging repository:
https://repository.apache.org/content/repositories/maven-040/
If you're doing down this way, I would strongly recommend the ability not
only to log specific packages, but to be able to set their logging level as
well.
For example, from WebSphere:
Check this link for the same:
http://forums.gradle.org/gradle/topics/nexus_login_error_after_update_from_1_0_m
ilestone_5_to_1_0_milestone_6
Kamlesh
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
+1
Regards,
Hervé
Le jeudi 15 novembre 2012 00:11:45 Dennis Lundberg a écrit :
Hi,
We solved 29 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126styleName=H
tmlversion=18308
There are still a couple of issues left in JIRA:
Le jeudi 15 novembre 2012 08:30:11 Jason van Zyl a écrit :
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So
+1 for the idea
other complementary ideas:
- groupId is not really useful, plugins's artifactId is in general sufficient
- I'd add goal name
- dot separator, since this is the classical separator in every java logging
implementations (due to the classical class name as logger pattern)
- add
21 matches
Mail list logo
