You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Wendell Beckwith <wb...@gmail.com> on 2006/09/10 06:11:08 UTC

2.1 Trunk and lack of debug output

Is there a problem with executing the 2.1 trunk code with the -X or --debug
options?  I have 2 separate trunk checkouts, one from a week ago and one I
just built.  Both builds seem to work fine with the exception that it is
impossible to get debug output out of them it I pass --debug or -X on the
command line.

Wb

Re: 2.1 Trunk and lack of debug output

Posted by Jason van Zyl <ja...@maven.org>.
On 10 Sep 06, at 6:11 AM 10 Sep 06, Wendell Beckwith wrote:

> Is there a problem with executing the 2.1 trunk code with the -X or  
> --debug
> options?  I have 2 separate trunk checkouts, one from a week ago  
> and one I
> just built.  Both builds seem to work fine with the exception that  
> it is
> impossible to get debug output out of them it I pass --debug or -X  
> on the
> command line.
>

The real problem is in plexus-logging which needs to be able to  
change thresholds dynamically (there have been a few discussions  
here). I changed the construction of the container so that the  
logging threshold is changed later in DefaultMaven but it doesn't work.

I also have a branch where I'm doing a logging cleanup and  
configuration cleanup in which I'm using the DefaultPlexusContainer  
directly instead of the Embedder. I'm not free to do anything until  
Wednesday next week (in Oslo at JavaZone) but if you want to fix it  
ping and I can tell you exactly what to look at or create a JIRA  
issue and I can put comments in that.

> Wb

Jason van Zyl
jason@maven.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: 2.1 Trunk and lack of debug output

Posted by Wendell Beckwith <wb...@gmail.com>.
Partially fixed here, http://jira.codehaus.org/browse/MNG-2554, with the
supplied patch.  This restores debug logging to the mojos, but not maven
itself.  There are comments in the code that that logging for maven has
already been initialized before the request appears and that it will need to
be fixed.  May take a look at that piece later, later.

Wb


On 9/10/06, Wendell Beckwith <wb...@gmail.com> wrote:
>
> Thanks Brett, I guess I'll need to debug this later today as it's annoying
> that it's not happening.  I hopefully will submit a patch if I get to it
> before someone else does.
>
> Wb
>
>
>
> On 9/10/06, Brett Porter <br...@apache.org> wrote:
> >
> > I think that's a known issue on trunk.
> >
> > On 10/09/2006, at 2:11 PM, Wendell Beckwith wrote:
> >
> > > Is there a problem with executing the 2.1 trunk code with the -X or
> > > --debug
> > > options?  I have 2 separate trunk checkouts, one from a week ago
> > > and one I
> > > just built.  Both builds seem to work fine with the exception that
> > > it is
> > > impossible to get debug output out of them it I pass --debug or -X
> > > on the
> > > command line.
> > >
> > > Wb
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>

Re: 2.1 Trunk and lack of debug output

Posted by Wendell Beckwith <wb...@gmail.com>.
Thanks Brett, I guess I'll need to debug this later today as it's annoying
that it's not happening.  I hopefully will submit a patch if I get to it
before someone else does.

Wb


On 9/10/06, Brett Porter <br...@apache.org> wrote:
>
> I think that's a known issue on trunk.
>
> On 10/09/2006, at 2:11 PM, Wendell Beckwith wrote:
>
> > Is there a problem with executing the 2.1 trunk code with the -X or
> > --debug
> > options?  I have 2 separate trunk checkouts, one from a week ago
> > and one I
> > just built.  Both builds seem to work fine with the exception that
> > it is
> > impossible to get debug output out of them it I pass --debug or -X
> > on the
> > command line.
> >
> > Wb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: 2.1 Trunk and lack of debug output

Posted by Brett Porter <br...@apache.org>.
I think that's a known issue on trunk.

On 10/09/2006, at 2:11 PM, Wendell Beckwith wrote:

> Is there a problem with executing the 2.1 trunk code with the -X or  
> --debug
> options?  I have 2 separate trunk checkouts, one from a week ago  
> and one I
> just built.  Both builds seem to work fine with the exception that  
> it is
> impossible to get debug output out of them it I pass --debug or -X  
> on the
> command line.
>
> Wb

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org