On Mon, Dec 12, 2011 at 8:01 PM, Brett Porter wrote:
> On 10/12/2011, at 9:44 AM, Benson Margulies wrote:
>
>> On the substance of the original problem:
>>
>> user runs 'mvn site:site'
>>
>> site:site finds javadoc and checkstyle, trigger a forked lifecycle to
>> generate sources.
>>
>> In this pa
On 10/12/2011, at 9:44 AM, Benson Margulies wrote:
> On the substance of the original problem:
>
> user runs 'mvn site:site'
>
> site:site finds javadoc and checkstyle, trigger a forked lifecycle to
> generate sources.
>
> In this particular case, 'generate-sources' in module 'b' depends on
> r
On the substance of the original problem:
user runs 'mvn site:site'
site:site finds javadoc and checkstyle, trigger a forked lifecycle to
generate sources.
In this particular case, 'generate-sources' in module 'b' depends on
running out through 'process-classes' in module 'a'. b has a
compile-s
On 12/08/2011 06:34 AM, Benson Margulies wrote:
In the test case, there's a maven plugin which declares various maven
2 components as provided dependencies, notably the
DefaultArtifactResolver. So, my IDE keeps trying (I think) to show me
the source to the 2.2.1 version even though, since I'm run
Olivier,
You're pointing at the original problem: that process-classses doesn't
get included in the forked lifecycle.
I'm trying to start with the second problem: that the resolver gives a
bogus answer.
--benson
On Thu, Dec 8, 2011 at 11:05 AM, Olivier Lamy wrote:
> 2011/12/8 Benson Margulies
Brett,
What are you debugging in these days?
On Thu, Dec 8, 2011 at 12:31 PM, Brett Porter wrote:
> Are you running Maven from the IDE, or using the "mvnDebug" remote debugging?
>
> If you have the Maven projects open, and then attach to a Maven process built
> from those sources, you should
Are you running Maven from the IDE, or using the "mvnDebug" remote debugging?
If you have the Maven projects open, and then attach to a Maven process built
from those sources, you should be able to trace into them instead - or at least
set a breakpoint in there.
Been ages since I used Eclipse t
2011/12/8 Benson Margulies :
> I want to see if I can chase MNG-5214 to its lair. I need a little bit
> of coaching to get the debugging process going.
>
> In the test case, there's a maven plugin which declares various maven
> 2 components as provided dependencies, notably the
> DefaultArtifactRes
I want to see if I can chase MNG-5214 to its lair. I need a little bit
of coaching to get the debugging process going.
In the test case, there's a maven plugin which declares various maven
2 components as provided dependencies, notably the
DefaultArtifactResolver. So, my IDE keeps trying (I think)
I took a run at JXR-88, and ended up creating JXR-89, which claims
that aggregation is not functional at all in JXR at the moment. I'd be
happy to be proved confused.
On Sun, Jun 19, 2011 at 4:33 AM, Hervé BOUTEMY wrote:
> I opened MNG-5119 to track this. We can use the Wiki too [2], if useful at
I opened MNG-5119 to track this. We can use the Wiki too [2], if useful at any
time.
I already did some minor improvements and published 3.0.4-SNAPSHOT site [3]
(sync pending) to see the actual state, to be compared with 3.0.3 [4]
I'm starting to test ideas on shared components, since they are t
Returning to the very start of this thread:
Now that I seem to have caught up with my current box of itches on
plugins for the moment, I'd be more than happy to join this parade.
Could some more experience committer grab a defect JIRA that has a
some value to it, throw it up here on the list, and
While we have a good standard for plugin site organization [1] that was
debated a few years ago to improve Maven documentation, we have nothing for
components. And the actual state is not good: see Maven core, where even
simplest description of every component is not done but inherited from
par
Hi all,
Long time lurker, I'm de-lurking because I like to harp on a bit about
how to run a successful open source project (based off Karl Fogel's
teachings at http://producingoss.org) - got to love opinionated
lurkers right? ;p
My comments in-line below:
>> * Open up access to the community som
a good candidate for a proposal? [1]
Yes, improving logging and its documentation would be useful.
Regards,
Hervé
[1] https://cwiki.apache.org/confluence/display/MAVEN/Proposals
Le vendredi 10 juin 2011, Ralph Goers a écrit :
> On Jun 9, 2011, at 2:45 PM, Benson Margulies wrote:
> > I'd like t
well if you are i18n-ing your logging messages you should always include a
code in the log message, that way you just google the code and presto
changeo you have your answer...
what I find is there is a logging level above which it makes sense to
i18n... usually somewhere around info/warn, but bel
i18n discussion is moot for the _logger_ backend (but
certainly a valuable feature for a Error-Message system).
LieGrue,
strub
--- On Sat, 6/11/11, Clark, Gil W. wrote:
> From: Clark, Gil W.
> Subject: Re: Get thee to the Core...
> To: "Maven Developers List"
> Date: Sa
de
>>>>for
>>>> logging, IMO...but it's more of a wish-list item than anything else.
>>>>
>>>> In short, yes, let's think about switching to a better logging
>>>>framework. We
>>>> can deprecate the plexus log
s, let's think about switching to a better logging
>>>framework. We
>>> can deprecate the plexus logger, and eventually get rid of it!
>>>
>>>>
>>>> We would need to do some compat code anyway, but I'm not sure if it
>>>>pa
Are there any other log4j-2.0 activities?
If not, then why not move it to the trunk (or an official 2.0 branch)?
I will give it a try.
LieGrue,
strub
--- On Sat, 6/11/11, Ralph Goers wrote:
> From: Ralph Goers
> Subject: Re: Get thee to the Core...
> To: "Maven Developers
Well, I make no guarantee that it is done "right". I do guarantee that if you
want to help I'll welcome it.
On Jun 11, 2011, at 12:12 AM, Stephen Connolly wrote:
> I'll take a look... I'm keen to see logging done right
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mist
; --- On Sat, 6/11/11, Ralph Goers wrote:
>
>> From: Ralph Goers
>> Subject: Re: Get thee to the Core...
>> To: "Maven Developers List"
>> Date: Saturday, June 11, 2011, 5:43 AM
>> I'm not sure what you are after
>> John. Logback provides a form
I'll take a look... I'm keen to see logging done right
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 11 Jun 2011 06:50, "Ralph Goers" wrote:
: Ralph Goers
> Subject: Re: Get thee to the Core...
> To: "Maven Developers List"
> Date: Saturday, June 11, 2011, 5:43 AM
> I'm not sure what you are after
> John. Logback provides a formatter where you can do
>
> logger.debug("Hello, {}", "John&quo
e plexus logger, and eventually get rid of it!
>>>
>>>>
>>>> We would need to do some compat code anyway, but I'm not sure if it pays
>>>> off to restrict ourself. At least not after I saw that even the
>>>> LoggerManager uses System.err
rs in place...
>
> So I'd favour slf4j. We don't need a 'perfect' solution - we just need
> something better than we had in place ;)
>
> LieGrue,
> strub
>
> --- On Fri, 6/10/11, Jochen Wiedmann wrote:
>
>> From: Jochen Wiedmann
>&
gger, and eventually get rid of it!
>>
>>>
>>> We would need to do some compat code anyway, but I'm not sure if it pays
>>> off to restrict ourself. At least not after I saw that even the
>>> LoggerManager uses System.err.println:
>>>
>>
ict ourself. At least not after I saw that even the LoggerManager
>> uses System.err.println:
>>
>> // TODO: use a logger!
>> System.err.println( "There was no such logger '" + key + "' " + hashCode() +
>> "." );
>>
>>
On 2011-06-09 23:45, Benson Margulies wrote:
> I'd like to offer a small suggestion.
>
> One of the big barriers to maven happiness is the difficulty of
> understanding, in some cases, why it does what it does.
>
> This suggests to me three efforts that might offer an opportunity to
> learn core
HI all,
Just my 2 cents :
Main problem with jumping into Maven core development is understanding of
internal architecture and core parts. Also this affects development of
plugins. Thus IMO improving this can definitely animate Maven ecosystem
(Core, Core Plugins, Mojo, ...) in general.
Another po
; From: Jochen Wiedmann
> Subject: Re: Get thee to the Core...
> To: "Maven Developers List"
> Date: Friday, June 10, 2011, 3:46 PM
> On Fri, Jun 10, 2011 at 5:43 PM,
> Stephen Connolly
>
> wrote:
>
> > but having seen my mistakes I think
> >
On Fri, Jun 10, 2011 at 5:43 PM, Stephen Connolly
wrote:
> but having seen my mistakes I think
> I have a better handle on the right path to take!
Strange enough, that's almost definitely what Ceki Gülcü would say ... :-)
--
Capitalism is the astounding belief that the most wickedest of men
w
t code anyway, but I'm not sure if it pays
>>> off to restrict ourself. At least not after I saw that even the
>>> LoggerManager uses System.err.println:
>>>
>>> // TODO: use a logger!
>>> System.err.println( "There was no such logge
/ TODO: use a logger!
>> System.err.println( "There was no such logger '" + key + "' " + hashCode()
>> + "." );
>>
>> dumdidum :)
>>
>> LieGrue,
>> strub
>>
>>
>> --- On Fri, 6/10/11, Ralph Goers wrote:
System.err.println( "There was no such logger '" + key + "' " + hashCode() +
"." );
dumdidum :)
LieGrue,
strub
--- On Fri, 6/10/11, Ralph Goers wrote:
From: Ralph Goers
Subject: Re: Get thee to the Core...
To: "Maven Developers List"
Date:
ogger!
System.err.println( "There was no such logger '" + key + "' " + hashCode() +
"." );
dumdidum :)
LieGrue,
strub
--- On Fri, 6/10/11, Ralph Goers wrote:
> From: Ralph Goers
> Subject: Re: Get thee to the Core...
> To: "Maven Developer
On Jun 9, 2011, at 2:45 PM, Benson Margulies wrote:
> I'd like to offer a small suggestion.
>
> One of the big barriers to maven happiness is the difficulty of
> understanding, in some cases, why it does what it does.
>
> This suggests to me three efforts that might offer an opportunity to
> le
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Friday, 10 June 2011 10:12 AM
> To: Maven Developers List
> Subject: Re: Get thee to the Core...
>
> Simone, can you please do one favour for me...
>
> Can you plea
Simone, can you please do one favour for me...
Can you please try
svn mkdir https://svn.apache.org/repos/asf/maven/sandbox/trunk/simone-test
-m "a test of sandbox access by a non-maven committer"
and if that works then
svn rm https://svn.apache.org/repos/asf/maven/sandbox/trunk/simone-test
-m "
On Fri, Jun 10, 2011 at 6:56 AM, Simone Tripodi
wrote:
> I don't know how internals work, if you have something to share I can read to
> get more confident I would really appreciate it
I think that's the nub of the problem for a lot of people.
We can hack a plugin but we don't understand how core
I'd like to offer a small suggestion.
One of the big barriers to maven happiness is the difficulty of
understanding, in some cases, why it does what it does.
This suggests to me three efforts that might offer an opportunity to
learn core code without drowning.
1: take up slf4j, and thus allow co
Thanks a lot Stephen!!!
As I previously wrote before, my main issue is that even I'm quiet
familiar with maven and basic APIs (I can develop plugins) I don't
know how internals work, if you have something to share I can read to
get more confident I would really appreciate it, then I'll request of
c
FYI Simone, our sandbox is supposed to be open for all _APACHE_
committers, so if you want to work on stuff you can just fork what you
are working on into the sandbox to show us your "skills of a hacker"
rather than having to live in patch land
On 9 June 2011 22:17, Simone Tripodi wrote:
> Hi guy
Hi guys,
I just accidentally and quickly had a look at the thread (got
interested because saw Olivier in :P) and since I'm interested on
contributing - and have been playing with @Inject & Guice extensions
for a while[1][2][3][4][5] - I could provide my help.
My BIG issue is I don't know Maven core
2011/6/9 John Casey :
> CC'ing dev@: I hope the PMC doesn't mind.
>
> We've been spending some time on-and-off talking about how we can open up
> development in the Maven core, and see if we can attract some fresh minds
> and ideas. I'd like to copy a list of some things we've been talking about,
>
Looks interesting... I didn't want to work any more this afternoon anyway. ;)
On Jun 9, 2011, at 2:34 PM, Anders Hammar wrote:
>> Why not allow an expanded dialect for the pom files (if it's not already in
>> progress)? By that I mean open-up the format via some sort of plugin
>> mechanism or c
> Why not allow an expanded dialect for the pom files (if it's not already in
> progress)? By that I mean open-up the format via some sort of plugin
> mechanism or core support so pom files could be written in other languages
> aside from XML. Perhaps something like JSON? I'm no JSON expert, but
Hello,
I've only been lurking on the dev@ list for a couple of months, so, some of
these may have already been asked, shot-down, stomped on like a cockroach, etc.
but I've used maven for a couple of years now and wondered I caveat my
requests/suggestions with: These could already be inten
CC'ing dev@: I hope the PMC doesn't mind.
We've been spending some time on-and-off talking about how we can open
up development in the Maven core, and see if we can attract some fresh
minds and ideas. I'd like to copy a list of some things we've been
talking about, and open it up to anyone her
49 matches
Mail list logo
