RE: RC2

[Maczka Michal]

> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 06, 2004 10:51 AM
> To: Maven Developers List
> Subject: Re: RC2
> 
> 
> [EMAIL PROTECTED] wrote:
> > Maczka Michal <[EMAIL PROTECTED]> wrote on 05/02/2004 
> 09:59:36 PM:
> > 
> >>For example if cactus test cases were kept in separate, dedicated 
> > 
> > project
> > 
> >>this particular problem will almost disappear.
> > 
> > 
> > We do exactly this at the moment for our J2EE apps.
> 
> I should probably read the docs and all, but...
> 
> Is it possible to get Clover reports for Cactus tests? And what if the
> tested code comes from another maven project?
> 
> R.
> 

I agree with dIon that some things are alredy are usable, but what I was
trying to say is:
The level of integration between plugins for doing functional testing (aka
integration testing) is very poor.
But this is quite common problem in Maven.
This has nothing to do with Maven core or our bugs. 
It is rather a question of lack of common guidelines which will demonstrate
how to use such tools and generally
how to write a plugin from given category (e.g from categtory "code
generators" "ui testing")
This situation is natural and was inevitable as many ideas were growing up
with maven.




Michal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RC2

[Rafal Krzewski]

[EMAIL PROTECTED] wrote:
> Maczka Michal <[EMAIL PROTECTED]> wrote on 05/02/2004 09:59:36 PM:
> 
>>For example if cactus test cases were kept in separate, dedicated 
> 
> project
> 
>>this particular problem will almost disappear.
> 
> 
> We do exactly this at the moment for our J2EE apps.

I should probably read the docs and all, but...

Is it possible to get Clover reports for Cactus tests? And what if the
tested code comes from another maven project?

R.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RC2 - multiproject build issues?

[Florin Vancea]

What JDK? Is your system Locale different than en_US?
You know there's a bug in URLConnection, at least in 1.3.1.
The If-Modified-Since header is constructed with system Locale (as opposed
to being constructed with en_US). If system Locale is not en_US, the HTTP
server does not understand the timestamp required and always returns 200/OK,
therefore your (newer) local SNAPSHOT jar is overwritten.

As I look into the CVS repository, it seems that
org.apache.maven.util.HttpUtils was not patched against this issue.

I cannot easily give a diff, since I'm maintaining my own local altered
source copy, but if you think you're affected by that, here is the code
fragment I used in "public static void getFile(String, File, boolean,
boolean, String, String, String, String)":

//modify the headers
//NB: things like user authentication could go in here too.
if ( useTimestamp && hasTimestamp )
{
// FV: workaround the bug in JDK 1.3
// connection.setIfModifiedSince( timestamp );
java.text.SimpleDateFormat sdformat =
new java.text.SimpleDateFormat("EEE, dd MMM  HH:mm:ss 'GMT'",
java.util.Locale.US);
sdformat.setTimeZone(java.util.TimeZone.getTimeZone("GMT"));
connection.setRequestProperty("If-Modified-Since", sdformat.format(new
java.util.Date(timestamp)));
}
// prepare Java 1.1 style credentials
if ( username != null || password != null )

Look for the original comments in HttpUtils as a reference point.

HTH, Florin

- Original Message -
From: "Sean Timm" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 9:28 PM
Subject: RC2 - multiproject build issues?


> Using the latest RC2 bits, when I do a "maven
> multiproject:install-snapshot", it builds project A, but then when it
> builds project B (which has a dependency on project A), it downloads the
> snapshot from the remote repository rather than using the snapshot I
> just built for project A.  Is anyone else seeing this issue? (And, no,
> my system clock is not off)... :)
>
> -- Sean T.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[dion]

Maczka Michal <[EMAIL PROTECTED]> wrote on 05/02/2004 09:59:36 PM:
> For example if cactus test cases were kept in separate, dedicated 
project
> this particular problem will almost disappear.

We do exactly this at the moment for our J2EE apps.

> "Almost" as the problem is that Maven at the moment (I am speaking about
> default distribution not proprietary plugins) 
> is unable to work with the test cases (mostly based on extension of 
junit)
> kept main source tree. 

Well, yes it can

> It is also unable to create jars/uberjars from test source tree or even
> notice that test source tree is existing if there
> in no main source tree

Again, yes it can. We have 'Test Projects' where there is no source, just 
Unit Test source. This works well.

> I believe that when we will find structured standardized solution for
> organizing iu-tests most of such problems will really 
> disappear and that the quality of testing will be improved as at the 
moment
> maven doesn't really encourage such practices (they are very painful).

For me, maven does allow exactly that, and it's fairly easy. Our 'test 
projects' have dependencies for the tested code, no actual source code 
themselves, but unit test source trees.

--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 - multiproject build issues?

[dion]

"Sean Timm" <[EMAIL PROTECTED]> wrote on 06/02/2004 08:42:34 AM:

> Brett Porter [mailto:[EMAIL PROTECTED] wrote:
> > > Using the latest RC2 bits, when I do a "maven 
> > > multiproject:install-snapshot", it builds project A, but 
> > then when it 
> > > builds project B (which has a dependency on project A), it 
> > downloads 
> > > the snapshot from the remote repository rather than using 
> > the snapshot 
> > > I just built for project A.

I'm using RC2 and multiproject:install-snapshot on a daily basis, and all 
seems fine. It does (as is usual with SNAPSHOTs) go and check the remote 
repo for a later build, but in my case never downloads it.

--
dIon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 - multiproject build issues?

[Sean Timm]

I didn't have any luck finding anything in JIRA regarding multiproject
and snapshots.  There was an issue with snapshots in general, but that
works fine for me.  However, I've been using a modified jar plugin that
uses the artifact plugin rather than the defaults...  I'm starting to
wonder if it may have something to do with that, so I'm going to look
into it further (if I can manage to get a reproducible test case).

> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, February 05, 2004 2:48 PM
> To: 'Maven Developers List'
> Subject: RE: RC2 - multiproject build issues?
> 
> Hard to tell - but search JIRA first because I'm sure someone 
> would already have come across this if it's a problem.
> 
> Thanks,
> Brett
> 
> > -Original Message-
> > From: Sean Timm [mailto:[EMAIL PROTECTED]
> > Sent: Friday, 6 February 2004 8:43 AM
> > To: Maven Developers List
> > Subject: RE: RC2 - multiproject build issues?
> > 
> > 
> > Brett Porter [mailto:[EMAIL PROTECTED] wrote:
> > > > Using the latest RC2 bits, when I do a "maven 
> > > > multiproject:install-snapshot", it builds project A, but
> > > then when it
> > > > builds project B (which has a dependency on project A), it
> > > downloads
> > > > the snapshot from the remote repository rather than using
> > > the snapshot
> > > > I just built for project A.
> > > > Is anyone else seeing this issue? (And, no, my system 
> clock is not 
> > > > off)... :)
> > 
> > > Can you confirm this has changed since RC1?
> > > 
> > > That code hasn't changed, so I'd be surprised if this isn't an 
> > > existing issue, if not an environmental issue.
> > > 
> > > Having said that, it should go into JIRA if it is not 
> environmental 
> > > (search and see if there is one already!)
> > 
> > I saw this issue back in RC1, as well, but I never got a 
> fix on what 
> > was going on exactly.  The problem seems to go away if I go 
> into some 
> > of the subprojects manually and do an install-snapshot build 
> > first...quite strange.  I have no idea if it's environmental or not 
> > (all Windows here), but I'll go ahead and log the issue.  
> Would this 
> > be strictly a multiproject plugin issue, or does it have 
> something to 
> > do with the reactor?
> > 
> > -- Sean T.
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 - multiproject build issues?

[Brett Porter]

Hard to tell - but search JIRA first because I'm sure someone would already
have come across this if it's a problem.

Thanks,
Brett

> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 6 February 2004 8:43 AM
> To: Maven Developers List
> Subject: RE: RC2 - multiproject build issues?
> 
> 
> Brett Porter [mailto:[EMAIL PROTECTED] wrote:
> > > Using the latest RC2 bits, when I do a "maven
> > > multiproject:install-snapshot", it builds project A, but 
> > then when it
> > > builds project B (which has a dependency on project A), it
> > downloads
> > > the snapshot from the remote repository rather than using
> > the snapshot
> > > I just built for project A.
> > > Is anyone else seeing this issue? (And, no, my system clock is not
> > > off)... :)
> 
> > Can you confirm this has changed since RC1?
> > 
> > That code hasn't changed, so I'd be surprised if this isn't
> > an existing issue, if not an environmental issue.
> > 
> > Having said that, it should go into JIRA if it is not
> > environmental (search and see if there is one already!)
> 
> I saw this issue back in RC1, as well, but I never got a fix 
> on what was going on exactly.  The problem seems to go away 
> if I go into some of the subprojects manually and do an 
> install-snapshot build first...quite strange.  I have no idea 
> if it's environmental or not (all Windows here), but I'll go 
> ahead and log the issue.  Would this be strictly a 
> multiproject plugin issue, or does it have something to do 
> with the reactor?
> 
> -- Sean T.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: RC2 - multiproject build issues?

[Sean Timm]

Brett Porter [mailto:[EMAIL PROTECTED] wrote:
> > Using the latest RC2 bits, when I do a "maven 
> > multiproject:install-snapshot", it builds project A, but 
> then when it 
> > builds project B (which has a dependency on project A), it 
> downloads 
> > the snapshot from the remote repository rather than using 
> the snapshot 
> > I just built for project A.
> > Is anyone else seeing this issue? (And, no, my system clock is not 
> > off)... :)

> Can you confirm this has changed since RC1?
> 
> That code hasn't changed, so I'd be surprised if this isn't 
> an existing issue, if not an environmental issue.
> 
> Having said that, it should go into JIRA if it is not 
> environmental (search and see if there is one already!)

I saw this issue back in RC1, as well, but I never got a fix on what was
going on exactly.  The problem seems to go away if I go into some of the
subprojects manually and do an install-snapshot build first...quite
strange.  I have no idea if it's environmental or not (all Windows
here), but I'll go ahead and log the issue.  Would this be strictly a
multiproject plugin issue, or does it have something to do with the
reactor?

-- Sean T.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 - multiproject build issues?

[Brett Porter]

Can you confirm this has changed since RC1?

That code hasn't changed, so I'd be surprised if this isn't an existing
issue, if not an environmental issue.

Having said that, it should go into JIRA if it is not environmental (search
and see if there is one already!)

Cheers,
Brett

> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 6 February 2004 6:28 AM
> To: Maven Developers List
> Subject: RC2 - multiproject build issues?
> 
> 
> Using the latest RC2 bits, when I do a "maven 
> multiproject:install-snapshot", it builds project A, but then 
> when it builds project B (which has a dependency on project 
> A), it downloads the snapshot from the remote repository 
> rather than using the snapshot I just built for project A.  
> Is anyone else seeing this issue? (And, no, my system clock 
> is not off)... :)
> 
> -- Sean T.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: RC2

[Maczka Michal]

IMHO this particular issue: integration of cactus plugin  with eclipse
plugin is affected by the problem which is lying elsewhere.

The problem is that generally support for different type of testing then
unit testing is pratically not existing in maven.
For example if cactus test cases were kept in separate, dedicated project
this particular problem will almost disappear.
"Almost" as the problem is that Maven at the moment (I am speaking about
default distribution not proprietary plugins) 
is unable to work with the test cases (mostly based on extension of junit)
kept main source tree. 
It is also unable to create jars/uberjars from test source tree or even
notice that test source tree is existing if there
in no main source tree

I believe that when we will find structured standardized solution for
organizing iu-tests most of such problems will really 
disappear and that the quality of testing will be improved as at the moment
maven doesn't really encourage such practices (they are very painful).
For example for my current project I have developed a test suite which is
benchmarking performance of my application.
After every major change in the architecture I am using this test suite for
seeing how it is affecting the performance.
The same can be done for memory consumption etc. 

 
When test reports (and reports generally) will be promoted to artifacts if
will be possible
to track performace changes and make complex statistiacl analyzis of them. 
Also it should be possible to measure the performace of given application
with differnt configurations/set of components.
It think that this would be really cool. 

There is a lot of crazy ideas waiting for implementation. 
E.g. what about using genetic algorithms + continous integration system + iu
testing
for finding the optimal configuration of given application (e.g. size of
caches, number of connection to databases etc.)
The truth is that very rarly people have time for performace tuning and it
can be mostly automated. 
And I even doubt that human can do this better then genetic alogorithm if
the domain space for genetic algorithm is
correctly defined.




Michal
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 05, 2004 10:59 AM
> To: 'Maven Developers List'
> Subject: RE: RC2
> 
> 
> I think I was the guilty person on this one...
> 
> I wanted to run maven eclipse and get my cactus code 
> registered as source
> code.  If this coupling is undesirable, then the property
> maven.eclipse.classpath.include could be used instead:
> 
> maven.eclipse.classpath.include src/test-cactus
> 
> Eric
> 
> > -Original Message-
> > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, February 05, 2004 3:51 AM
> > To: 'Maven Developers List'
> > Subject: RE: RC2
> >
> >
> > Hi Jason,
> >
> > > -Original Message-
> > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > Sent: 03 February 2004 22:12
> > > To: Maven Developers List
> > > Subject: RE: RC2
> > >
> > > On Tue, 2004-02-03 at 15:35, Vincent Massol wrote:
> > > > > -Original Message-
> > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > > Sent: 03 February 2004 01:04
> > > > > To: Maven Developers List
> > > > > Subject: RE: RC2
> > > > >
> > > > > There's also a bug in the eclipse plugin which causes 
> it to fail
> > > > without
> > > > > cactus being present.
> > > > >
> > > > > I've 'fixed' it locally by commenting out the cactus
> > support. What
> > do
> > > > you
> > > > > think we should do? Is there an easy way now to test for the
> > existence
> > > > of
> > > > > a plugin? Or do we add the cactus plugin as a dependency?
> > > >
> > > > I think we have 2 options:
> > > >
> > > > 1/ As you say, make it optional by checking the existence of the
> > cactus
> > > > plugin (or adding the cactus plugin as a dependency)
> > > >
> > > > 2/ Modifying the eclipse plugin implementation and making it
> > pluggable.
> > > > We would then move the logic related to Cactus in the
> > cactus plugin.
> > > >
> > > > I'm not sure there's enough cactus-related plugin logic 
> to warrant
> > > > option 2. However, I'm sure we'll need to support other
> > "extensions"
> > of
> > > > the eclipse plugin for other tools so it might make sense
> > to

RE: RC2

[Eric Pugh]

I think I was the guilty person on this one...

I wanted to run maven eclipse and get my cactus code registered as source
code.  If this coupling is undesirable, then the property
maven.eclipse.classpath.include could be used instead:

maven.eclipse.classpath.include src/test-cactus

Eric

> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 05, 2004 3:51 AM
> To: 'Maven Developers List'
> Subject: RE: RC2
>
>
> Hi Jason,
>
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 03 February 2004 22:12
> > To: Maven Developers List
> > Subject: RE: RC2
> >
> > On Tue, 2004-02-03 at 15:35, Vincent Massol wrote:
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > Sent: 03 February 2004 01:04
> > > > To: Maven Developers List
> > > > Subject: RE: RC2
> > > >
> > > > There's also a bug in the eclipse plugin which causes it to fail
> > > without
> > > > cactus being present.
> > > >
> > > > I've 'fixed' it locally by commenting out the cactus
> support. What
> do
> > > you
> > > > think we should do? Is there an easy way now to test for the
> existence
> > > of
> > > > a plugin? Or do we add the cactus plugin as a dependency?
> > >
> > > I think we have 2 options:
> > >
> > > 1/ As you say, make it optional by checking the existence of the
> cactus
> > > plugin (or adding the cactus plugin as a dependency)
> > >
> > > 2/ Modifying the eclipse plugin implementation and making it
> pluggable.
> > > We would then move the logic related to Cactus in the
> cactus plugin.
> > >
> > > I'm not sure there's enough cactus-related plugin logic to warrant
> > > option 2. However, I'm sure we'll need to support other
> "extensions"
> of
> > > the eclipse plugin for other tools so it might make sense
> to have a
> > > pluggable implementation.
> > >
> > > For 1/, would the following work:
> > >
> > > 
> >
> > Can I ask why there exists such a dependency in the first place?
> >
> > I'm just curious because obviously in some context the cactus plugin
> is
> > providing some functionality, just wondering how and what and if a
> > cleaner way can be found as I'm sure this situation would arise in
> > relationships among other plugins.
>
> Actually I don't know. I'm not the one who made this coupling between
> Eclipse plugin and Cactus plugin. I've just had a look at the plugin
> source code and it appears there is a conditional test:
>
>property='cactus.src.dir' />
>   
> 
>   
>
> and then, depending on whether cactus sources are present, the
> .classpath file for Eclipse is modified to add the cactus sources and
> the cactus jar is added to the project's classpath.
>
> The need is not only for Cactus. It is the same for example
> for Aspects.
> Thus we could also imagine the same for the aspectj plugin, etc.
>
> I guess we can continue with this coupling as it is light and provided
> we test for the existence of the plugin. Solution 2/ is better but I
> feel it is too heavyweight (for now at least). What do you think?
>
> Thanks
> -Vincent
>
> >
> > > Thanks
> > > -Vincent
> > >
> > > > --
> > > > dIon Gillard, Multitask Consulting
> > > > Blog:  http://blogs.codehaus.org/people/dion/
> > > >
> > > >
> > > >
> > > > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004
> 10:39:16
> > > AM:
> > > >
> > > > > Thanks.
> > > > >
> > > > > > -Original Message-
> > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > > > Sent: Tuesday, 3 February 2004 10:46 AM
> > > > > > To: Maven Developers List
> > > > > > Subject: Re: RC2
> > > > > >
> > > > > >
> > > > > > I just found one in the new batch file and fixed it.
> > > > > >
> > > > > > There's also a classloader issue when I try to run
> > > > > > multiproject:site for
> > > > > > maven-plugins.
> > > > > >
> > > > > > Will retest it after th

RE: RC2

[Vincent Massol]

Hi Jason,

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 03 February 2004 22:12
> To: Maven Developers List
> Subject: RE: RC2
> 
> On Tue, 2004-02-03 at 15:35, Vincent Massol wrote:
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: 03 February 2004 01:04
> > > To: Maven Developers List
> > > Subject: RE: RC2
> > >
> > > There's also a bug in the eclipse plugin which causes it to fail
> > without
> > > cactus being present.
> > >
> > > I've 'fixed' it locally by commenting out the cactus support. What
do
> > you
> > > think we should do? Is there an easy way now to test for the
existence
> > of
> > > a plugin? Or do we add the cactus plugin as a dependency?
> >
> > I think we have 2 options:
> >
> > 1/ As you say, make it optional by checking the existence of the
cactus
> > plugin (or adding the cactus plugin as a dependency)
> >
> > 2/ Modifying the eclipse plugin implementation and making it
pluggable.
> > We would then move the logic related to Cactus in the cactus plugin.
> >
> > I'm not sure there's enough cactus-related plugin logic to warrant
> > option 2. However, I'm sure we'll need to support other "extensions"
of
> > the eclipse plugin for other tools so it might make sense to have a
> > pluggable implementation.
> >
> > For 1/, would the following work:
> >
> > 
> 
> Can I ask why there exists such a dependency in the first place?
> 
> I'm just curious because obviously in some context the cactus plugin
is
> providing some functionality, just wondering how and what and if a
> cleaner way can be found as I'm sure this situation would arise in
> relationships among other plugins.

Actually I don't know. I'm not the one who made this coupling between
Eclipse plugin and Cactus plugin. I've just had a look at the plugin
source code and it appears there is a conditional test:

  
  

  

and then, depending on whether cactus sources are present, the
.classpath file for Eclipse is modified to add the cactus sources and
the cactus jar is added to the project's classpath.

The need is not only for Cactus. It is the same for example for Aspects.
Thus we could also imagine the same for the aspectj plugin, etc.

I guess we can continue with this coupling as it is light and provided
we test for the existence of the plugin. Solution 2/ is better but I
feel it is too heavyweight (for now at least). What do you think?

Thanks
-Vincent

> 
> > Thanks
> > -Vincent
> >
> > > --
> > > dIon Gillard, Multitask Consulting
> > > Blog:  http://blogs.codehaus.org/people/dion/
> > >
> > >
> > >
> > > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004
10:39:16
> > AM:
> > >
> > > > Thanks.
> > > >
> > > > > -Original Message-
> > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > > Sent: Tuesday, 3 February 2004 10:46 AM
> > > > > To: Maven Developers List
> > > > > Subject: Re: RC2
> > > > >
> > > > >
> > > > > I just found one in the new batch file and fixed it.
> > > > >
> > > > > There's also a classloader issue when I try to run
> > > > > multiproject:site for
> > > > > maven-plugins.
> > > > >
> > > > > Will retest it after the latest bootstrap and file a Jira
> > > > > report if it
> > > > > still exists.
> > > > > --
> > > > > dIon Gillard, Multitask Consulting
> > > > > Blog:  http://blogs.codehaus.org/people/dion/
> > > > >
> > > > >
> > > > >
> > > > > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004
> > > > > 09:51:37 AM:
> > > > >
> > > > > > Only 2 bugs to go:
> > > > > > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > > > > >
> > > > > <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&r
> > > > eport=roadmap>
> > > > > &report=roadmap
> > > > >
> > > > > I'll try and knock them off in the next day or so.
> > > > >
> > > > > Anyone have any plugin bugs they wish to have fixed before we
> > release
> > > > RC2?
>

RE: RC2 - Clover?

[Brett Porter]

There's already an issue filed - I thought it was working alternatively, but
I'll bump it back to RC2.

- Brett

> -Original Message-
> From: Sean Timm [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 5 February 2004 10:51 AM
> To: Maven Developers List
> Subject: RC2 - Clover?
> 
> 
> Is anyone successfully using Clover with the RC2 bits?  I'm 
> getting the following error when I try and do a "maven clover:report":
> 
> Reference maven.test.compile.src.set not found.
> 
> Also, some tags are getting echoed out when the task starts, 
> so I assume they're not being recognized.  I'm seeing the 
> following output:
> 
>  ncy-handle
> > dependency-handle>clover:on:
> 
> Looking at the code, these calls are outside of any goal 
> tags.  I moved them into clover:on to see if it would help 
> anything.  It did make the echoed tag bit go away, but I 
> still got the reference error.
> 
> -- Sean T.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: RC2 bootstrapping failure

[Brett Porter]

This is correct behaviour. Linkcheck should not fail because it can't
resolve a link - it reports it. It probably should not spit exceptions to
the build though...

- Brett

> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, 4 February 2004 6:46 PM
> To: Maven Developers List
> Subject: RE: RC2 bootstrapping failure
> 
> 
> Hello again,
> 
> I recognized, that Aspectwerkz is currently excluded, but now 
> I have an exception testing the xdoc-plugin. From the log I 
> believe that not the test itself fails, but the link 
> validation mechanism. It seems that a request done with 
> httpunit fails and httpunit will alway throw an exception in 
> this situation, that is not captured.
> 
> Regads,
> Jörg
> 
>  snip 
> ...
>  [exec] +
>  [exec] | Testing Maven XDoc Plug-in
>  [exec] | Memory: 53M/65M
>  [exec] +
> 
>  [exec] clean:
> 
> 
> 
>  [exec] plugin:test:
> 
>  [exec] plugin:test:
> 
>  [exec] plugin:test:
> 
>  [exec] plugin:test:
> 
>  [exec] plugin:test:
>  [exec] clean:clean:
>  [exec] [delete] Deleting directory 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target
> 
>  [exec] clean:
> 
>  [exec] test-xdoc:
>  [exec] xdoc:init:
>  [exec] [mkdir] Created dir: 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\g
> enerated-xdocs
>  [exec] [mkdir] Created dir: 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\docs
> 
>  [exec] xdoc:register-reports:
>  [exec] maven-jdepend-plugin:register:
> 
>  [exec] maven-checkstyle-plugin:register:
> 
>  [exec] maven-changes-plugin:register:
> 
>  [exec] maven-changelog-plugin:register:
> 
>  [exec] maven-developer-activity-plugin:register:
> 
>  [exec] maven-file-activity-plugin:register:
> 
>  [exec] maven-license-plugin:register:
> 
>  [exec] maven-javadoc-plugin:register:
> 
>  [exec] maven-jxr-plugin:register:
> 
>  [exec] maven-junit-report-plugin:register:
> 
>  [exec] maven-linkcheck-plugin:register:
> 
>  [exec] maven-tasklist-plugin:register:
> 
> 
>  [exec] xdoc:generate-from-pom:
>  [exec] [echo] Generating xdocs from POM ... 
> 
>  [exec]  
>  [exec] 
>  [exec] 
>  [exec] 
>  [exec] xdoc:transform:
>  [exec] xdoc:init:
> 
>  [exec] xdoc:copy-resources:
>  [exec] [copy] Copying 3 files to 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\d
> ocs\style
>  [exec] [copy] Copying 89 files to 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\d
> ocs\images
>  [exec] About to use JSL stylesheet file:/C:/Dokumente 
> und 
> Einstellungen/jos/.maven/plugins/maven-xdoc-plugin-1.6-SNAPSHO
> T/plugin-resources/site.jsl
> 
>  [exec] xdoc:init:
> 
>  [exec] xdoc:copy-user-resources:
> 
>  [exec] xdoc:init:
> 
>  [exec] xdoc:jelly-init:
> 
>  [exec] xdoc:register-reports:
>  [exec] maven-jdepend-plugin:register:
> 
>  [exec] maven-checkstyle-plugin:register:
> 
>  [exec] maven-changes-plugin:register:
> 
>  [exec] maven-changelog-plugin:register:
> 
>  [exec] maven-developer-activity-plugin:register:
> 
>  [exec] maven-file-activity-plugin:register:
> 
>  [exec] maven-license-plugin:register:
> 
>  [exec] maven-javadoc-plugin:register:
> 
>  [exec] maven-jxr-plugin:register:
> 
>  [exec] maven-junit-report-plugin:register:
> 
>  [exec] maven-linkcheck-plugin:register:
> 
>  [exec] maven-tasklist-plugin:register:
> 
> 
>  [exec] xdoc:jelly-transform:
>  [exec] [echo] Generating 
> C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/d
> ocs/cvs-usage.html from 
> C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\g
> enerated-xdocs\cvs-usage.xml
>  [exec] [echo] Generating 
> C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/d
ocs/dependencies.html from C:\Work\Apps\Maven>
\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\dep
> endencies.xml
>  [exec] [echo] Generating 
> C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/d
ocs/index.html from C:\Work\Apps\Maven\maven->
plugins\xdoc\src\plugin-test\target\generated-xdocs\index.xml
>  [exec] [echo] Generating 
> C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/d
> ocs/issue-tracking.html fr

RE: RC2 - Inheritance Question

[Sean Timm]

Hold that thought...I'm an idiot...built the wrong branch.  Let me build
anew before bothering you again with my trivial stupidities... ;)

> -Original Message-
> From: Sean Timm 
> Sent: Wednesday, February 04, 2004 12:05 PM
> To: [EMAIL PROTECTED]
> Subject: RC2 - Inheritance Question
> 
> I've got a project-base.xml file that sets up my basic, 
> generic information (including build/SourceDirectory).  I've 
> got a project-component.xml that extends this but does not 
> contain the build node at all.  I then have a 
> component-specific project.xml that extends 
> project-component.xml.  My expectation is that the  
> node info would be inherited from project-base.xml, but this 
> does not appear to be the case.  When I try and do a "maven 
> jar", I get the following output:
> 
> No java source files to compile.
> resources or todir was null
> 
> However, if I modify project.xml to extend project-base.xml 
> (rather than
> project-component.xml) and do a "maven jar", it works.  So is 
> this a "feature", and inheritance is only supported for one 
> level, or is this a bug?
> 
> Thanks!
> 
> -- Sean T.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 bootstrapping failure

[Jörg Schaible]

Hello again,

I recognized, that Aspectwerkz is currently excluded, but now I have an exception 
testing the xdoc-plugin. From the log I believe that not the test itself fails, but 
the link validation mechanism. It seems that a request done with httpunit fails and 
httpunit will alway throw an exception in this situation, that is not captured.

Regads,
Jörg

 snip 
...
 [exec] +
 [exec] | Testing Maven XDoc Plug-in
 [exec] | Memory: 53M/65M
 [exec] +

 [exec] clean:



 [exec] plugin:test:

 [exec] plugin:test:

 [exec] plugin:test:

 [exec] plugin:test:

 [exec] plugin:test:
 [exec] clean:clean:
 [exec] [delete] Deleting directory 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target

 [exec] clean:

 [exec] test-xdoc:
 [exec] xdoc:init:
 [exec] [mkdir] Created dir: 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs
 [exec] [mkdir] Created dir: 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\docs

 [exec] xdoc:register-reports:
 [exec] maven-jdepend-plugin:register:

 [exec] maven-checkstyle-plugin:register:

 [exec] maven-changes-plugin:register:

 [exec] maven-changelog-plugin:register:

 [exec] maven-developer-activity-plugin:register:

 [exec] maven-file-activity-plugin:register:

 [exec] maven-license-plugin:register:

 [exec] maven-javadoc-plugin:register:

 [exec] maven-jxr-plugin:register:

 [exec] maven-junit-report-plugin:register:

 [exec] maven-linkcheck-plugin:register:

 [exec] maven-tasklist-plugin:register:


 [exec] xdoc:generate-from-pom:
 [exec] [echo] Generating xdocs from POM ... 

 [exec]  
 [exec] 
 [exec] 
 [exec] 
 [exec] xdoc:transform:
 [exec] xdoc:init:

 [exec] xdoc:copy-resources:
 [exec] [copy] Copying 3 files to 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\docs\style
 [exec] [copy] Copying 89 files to 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\docs\images
 [exec] About to use JSL stylesheet file:/C:/Dokumente und 
Einstellungen/jos/.maven/plugins/maven-xdoc-plugin-1.6-SNAPSHOT/plugin-resources/site.jsl

 [exec] xdoc:init:

 [exec] xdoc:copy-user-resources:

 [exec] xdoc:init:

 [exec] xdoc:jelly-init:

 [exec] xdoc:register-reports:
 [exec] maven-jdepend-plugin:register:

 [exec] maven-checkstyle-plugin:register:

 [exec] maven-changes-plugin:register:

 [exec] maven-changelog-plugin:register:

 [exec] maven-developer-activity-plugin:register:

 [exec] maven-file-activity-plugin:register:

 [exec] maven-license-plugin:register:

 [exec] maven-javadoc-plugin:register:

 [exec] maven-jxr-plugin:register:

 [exec] maven-junit-report-plugin:register:

 [exec] maven-linkcheck-plugin:register:

 [exec] maven-tasklist-plugin:register:


 [exec] xdoc:jelly-transform:
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/cvs-usage.html from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\cvs-usage.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/dependencies.html 
from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\dependencies.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/index.html from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\index.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/issue-tracking.html 
from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\issue-tracking.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/mail-lists.html from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\mail-lists.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/maven-reports.html 
from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\maven-reports.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/project-info.html 
from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\project-info.xml
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/team-list.html from 
C:\Work\Apps\Maven\maven-plugins\xdoc\src\plugin-test\target\generated-xdocs\team-list.xml
 [exec] Transforming user supplied documentation.
 [exec] [echo] Generating 
C:/Work/Apps/Maven/maven-plugins/xdoc/src/plugin-test/target/docs/tes

RE: RC2

[Jason van Zyl]

On Tue, 2004-02-03 at 15:35, Vincent Massol wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: 03 February 2004 01:04
> > To: Maven Developers List
> > Subject: RE: RC2
> > 
> > There's also a bug in the eclipse plugin which causes it to fail
> without
> > cactus being present.
> > 
> > I've 'fixed' it locally by commenting out the cactus support. What do
> you
> > think we should do? Is there an easy way now to test for the existence
> of
> > a plugin? Or do we add the cactus plugin as a dependency?
> 
> I think we have 2 options:
> 
> 1/ As you say, make it optional by checking the existence of the cactus
> plugin (or adding the cactus plugin as a dependency)
> 
> 2/ Modifying the eclipse plugin implementation and making it pluggable.
> We would then move the logic related to Cactus in the cactus plugin. 
> 
> I'm not sure there's enough cactus-related plugin logic to warrant
> option 2. However, I'm sure we'll need to support other "extensions" of
> the eclipse plugin for other tools so it might make sense to have a
> pluggable implementation.
> 
> For 1/, would the following work:
> 
> 

Can I ask why there exists such a dependency in the first place?

I'm just curious because obviously in some context the cactus plugin is
providing some functionality, just wondering how and what and if a
cleaner way can be found as I'm sure this situation would arise in
relationships among other plugins.

> Thanks
> -Vincent
> 
> > --
> > dIon Gillard, Multitask Consulting
> > Blog:  http://blogs.codehaus.org/people/dion/
> > 
> > 
> > 
> > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 10:39:16
> AM:
> > 
> > > Thanks.
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, 3 February 2004 10:46 AM
> > > > To: Maven Developers List
> > > > Subject: Re: RC2
> > > >
> > > >
> > > > I just found one in the new batch file and fixed it.
> > > >
> > > > There's also a classloader issue when I try to run
> > > > multiproject:site for
> > > > maven-plugins.
> > > >
> > > > Will retest it after the latest bootstrap and file a Jira
> > > > report if it
> > > > still exists.
> > > > --
> > > > dIon Gillard, Multitask Consulting
> > > > Blog:  http://blogs.codehaus.org/people/dion/
> > > >
> > > >
> > > >
> > > > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004
> > > > 09:51:37 AM:
> > > >
> > > > > Only 2 bugs to go:
> > > > > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > > > >
> > > > <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&r
> > > eport=roadmap>
> > > > &report=roadmap
> > > >
> > > > I'll try and knock them off in the next day or so.
> > > >
> > > > Anyone have any plugin bugs they wish to have fixed before we
> release
> > > RC2?
> > > >
> > > > I will also merge CVS back to HEAD when I next have the
> opportunity.
> > > >
> > > > Cheers,
> > > > Brett
> > > >
> > > > --
> > > > Brett Porter
> > > > Team Leader, Core Systems
> > > > f2 network ~ everything essential
> > > >
> > >
> > >
> > >
> -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Vincent Massol]

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 03 February 2004 01:04
> To: Maven Developers List
> Subject: RE: RC2
> 
> There's also a bug in the eclipse plugin which causes it to fail
without
> cactus being present.
> 
> I've 'fixed' it locally by commenting out the cactus support. What do
you
> think we should do? Is there an easy way now to test for the existence
of
> a plugin? Or do we add the cactus plugin as a dependency?

I think we have 2 options:

1/ As you say, make it optional by checking the existence of the cactus
plugin (or adding the cactus plugin as a dependency)

2/ Modifying the eclipse plugin implementation and making it pluggable.
We would then move the logic related to Cactus in the cactus plugin. 

I'm not sure there's enough cactus-related plugin logic to warrant
option 2. However, I'm sure we'll need to support other "extensions" of
the eclipse plugin for other tools so it might make sense to have a
pluggable implementation.

For 1/, would the following work:



Thanks
-Vincent

> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
> 
> 
> 
> Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 10:39:16
AM:
> 
> > Thanks.
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, 3 February 2004 10:46 AM
> > > To: Maven Developers List
> > > Subject: Re: RC2
> > >
> > >
> > > I just found one in the new batch file and fixed it.
> > >
> > > There's also a classloader issue when I try to run
> > > multiproject:site for
> > > maven-plugins.
> > >
> > > Will retest it after the latest bootstrap and file a Jira
> > > report if it
> > > still exists.
> > > --
> > > dIon Gillard, Multitask Consulting
> > > Blog:  http://blogs.codehaus.org/people/dion/
> > >
> > >
> > >
> > > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004
> > > 09:51:37 AM:
> > >
> > > > Only 2 bugs to go:
> > > > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > > >
> > > <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&r
> > eport=roadmap>
> > > &report=roadmap
> > >
> > > I'll try and knock them off in the next day or so.
> > >
> > > Anyone have any plugin bugs they wish to have fixed before we
release
> > RC2?
> > >
> > > I will also merge CVS back to HEAD when I next have the
opportunity.
> > >
> > > Cheers,
> > > Brett
> > >
> > > --
> > > Brett Porter
> > > Team Leader, Core Systems
> > > f2 network ~ everything essential
> > >
> >
> >
> >
-
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Tim Anderson]

Yes. Namespace mapping won't work without it.

-Tim

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 3 February 2004 11:41 AM
> To: Maven Developers List
> Subject: RE: RC2
>
>
> Done.
>
> Is it worth a release of the plugin?
> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
>
>
>
> "Tim Anderson" <[EMAIL PROTECTED]> wrote on 03/02/2004 10:42:35 AM:
>
> > It would be nice if the patch attached to
> > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCASTOR-2
> > was applied before rc2 is released.
> >
> > It enables castor to locate its castorbuilder.properties file,
> > to configure the mapping of namespaces for imported schemas to
> > java packages.
> >
> > Thanks,
> >
> > Tim
> >
> > > -Original Message-
> > > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, 3 February 2004 9:52 AM
> > > To: Maven Developers List ([EMAIL PROTECTED])
> > > Subject: RC2
> > >
> > >
> > > Only 2 bugs to go:
> > > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > > <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&repor
> > > t=roadmap>
> > > &report=roadmap
> > >
> > > I'll try and knock them off in the next day or so.
> > >
> > > Anyone have any plugin bugs they wish to have fixed before we release
> RC2?
> > >
> > > I will also merge CVS back to HEAD when I next have the opportunity.
> > >
> > > Cheers,
> > > Brett
> > >
> > > --
> > > Brett Porter
> > > Team Leader, Core Systems
> > > f2 network ~ everything essential
> > >
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[dion]

Done.

Is it worth a release of the plugin?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/



"Tim Anderson" <[EMAIL PROTECTED]> wrote on 03/02/2004 10:42:35 AM:

> It would be nice if the patch attached to
> http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCASTOR-2
> was applied before rc2 is released.
> 
> It enables castor to locate its castorbuilder.properties file,
> to configure the mapping of namespaces for imported schemas to
> java packages.
> 
> Thanks,
> 
> Tim
> 
> > -Original Message-
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, 3 February 2004 9:52 AM
> > To: Maven Developers List ([EMAIL PROTECTED])
> > Subject: RC2
> >
> >
> > Only 2 bugs to go:
> > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> >  > t=roadmap>
> > &report=roadmap
> >
> > I'll try and knock them off in the next day or so.
> >
> > Anyone have any plugin bugs they wish to have fixed before we release 
RC2?
> >
> > I will also merge CVS back to HEAD when I next have the opportunity.
> >
> > Cheers,
> > Brett
> >
> > --
> > Brett Porter
> > Team Leader, Core Systems
> > f2 network ~ everything essential
> >
> >
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[dion]

There's also a bug in the eclipse plugin which causes it to fail without 
cactus being present.

I've 'fixed' it locally by commenting out the cactus support. What do you 
think we should do? Is there an easy way now to test for the existence of 
a plugin? Or do we add the cactus plugin as a dependency?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/



Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 10:39:16 AM:

> Thanks.
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, 3 February 2004 10:46 AM
> > To: Maven Developers List
> > Subject: Re: RC2
> > 
> > 
> > I just found one in the new batch file and fixed it.
> > 
> > There's also a classloader issue when I try to run 
> > multiproject:site for 
> > maven-plugins.
> > 
> > Will retest it after the latest bootstrap and file a Jira 
> > report if it 
> > still exists.
> > --
> > dIon Gillard, Multitask Consulting
> > Blog:  http://blogs.codehaus.org/people/dion/
> > 
> > 
> > 
> > Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 
> > 09:51:37 AM:
> > 
> > > Only 2 bugs to go: 
> > > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > > 
> > <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&r
> eport=roadmap>
> > &report=roadmap
> > 
> > I'll try and knock them off in the next day or so.
> > 
> > Anyone have any plugin bugs they wish to have fixed before we release
> RC2?
> > 
> > I will also merge CVS back to HEAD when I next have the opportunity.
> > 
> > Cheers,
> > Brett
> > 
> > --
> > Brett Porter
> > Team Leader, Core Systems
> > f2 network ~ everything essential
> > 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RC2

[Jason van Zyl]

On Mon, 2004-02-02 at 17:51, Brett Porter wrote:
> Only 2 bugs to go:
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> 
> &report=roadmap
>  
> I'll try and knock them off in the next day or so.

Awesome!

> Anyone have any plugin bugs they wish to have fixed before we release RC2?

We should really consider restricting the plugins we're releasing with
the core and rely on the download mechanism.
 
> I will also merge CVS back to HEAD when I next have the opportunity.
>  
> Cheers,
> Brett
>  
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
>  

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Tim Anderson]

It would be nice if the patch attached to
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCASTOR-2
was applied before rc2 is released.

It enables castor to locate its castorbuilder.properties file,
to configure the mapping of namespaces for imported schemas to
java packages.

Thanks,

Tim

> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 3 February 2004 9:52 AM
> To: Maven Developers List ([EMAIL PROTECTED])
> Subject: RC2
>
>
> Only 2 bugs to go:
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
>  t=roadmap>
> &report=roadmap
>
> I'll try and knock them off in the next day or so.
>
> Anyone have any plugin bugs they wish to have fixed before we release RC2?
>
> I will also merge CVS back to HEAD when I next have the opportunity.
>
> Cheers,
> Brett
>
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Brett Porter]

Thanks.

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 3 February 2004 10:46 AM
> To: Maven Developers List
> Subject: Re: RC2
> 
> 
> I just found one in the new batch file and fixed it.
> 
> There's also a classloader issue when I try to run 
> multiproject:site for 
> maven-plugins.
> 
> Will retest it after the latest bootstrap and file a Jira 
> report if it 
> still exists.
> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
> 
> 
> 
> Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 
> 09:51:37 AM:
> 
> > Only 2 bugs to go: 
> > http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> > 
> <http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030&r
eport=roadmap>
> &report=roadmap
> 
> I'll try and knock them off in the next day or so.
> 
> Anyone have any plugin bugs they wish to have fixed before we release
RC2?
> 
> I will also merge CVS back to HEAD when I next have the opportunity.
> 
> Cheers,
> Brett
> 
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RC2

[dion]

I just found one in the new batch file and fixed it.

There's also a classloader issue when I try to run multiproject:site for 
maven-plugins.

Will retest it after the latest bootstrap and file a Jira report if it 
still exists.
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/



Brett Porter <[EMAIL PROTECTED]> wrote on 03/02/2004 09:51:37 AM:

> Only 2 bugs to go:
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
> 

> &report=roadmap
> 
> I'll try and knock them off in the next day or so.
> 
> Anyone have any plugin bugs they wish to have fixed before we release 
RC2?
> 
> I will also merge CVS back to HEAD when I next have the opportunity.
> 
> Cheers,
> Brett
> 
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Arnaud Heritier]

I only want to update the PDF Plugin properties doc.

I'll send a patch tonight.

Arnaud.

> -Message d'origine-
> De : Brett Porter [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 2 février 2004 23:52
> À : Maven Developers List ([EMAIL PROTECTED])
> Objet : RC2
> 
> Only 2 bugs to go:
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030
>  p>
> &report=roadmap
> 
> I'll try and knock them off in the next day or so.
> 
> Anyone have any plugin bugs they wish to have fixed before we release RC2?
> 
> I will also merge CVS back to HEAD when I next have the opportunity.
> 
> Cheers,
> Brett
> 
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Brett Porter]

Thanks guys.

I'd like to fix
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1073

Then check the 5 or so remaining bugs to see whether they are still
occurring (these were ones I didn't file), then RC2 should be ready to roll.

Any additional testing people could do would be great. maven site works for
all reports I've seen and there is only one incompatibility with
classloaders that is easy to fix in the client code.

Cheers,
Brett


> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 29 January 2004 6:18 AM
> To: Maven Developers List
> Subject: Re: RC2
> 
> 
> me too.
> 
> The release in near!!!
> 
> Emmanuel
> 
> - Original Message - 
> From: "Vincent Massol" <[EMAIL PROTECTED]>
> To: "'Maven Developers List'" <[EMAIL PROTECTED]>
> Sent: Wednesday, January 28, 2004 6:47 PM
> Subject: RE: RC2
> 
> 
> > Yes, I agree, thank you Brett!
> > 
> > -Vincent
> >  
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: 28 January 2004 14:21
> > > To: [EMAIL PROTECTED]
> > > Subject: RC2
> > > 
> > > Just a quick email to thank Brett on the good work he's done for 
> > > RC2.
> > > 
> > > It's starting to look like we're almost there!
> > > --
> > > dIon Gillard, Multitask Consulting
> > > Blog:  http://blogs.codehaus.org/people/dion/
> > > 
> > > 
> > > 
> > > 
> 
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: RC2

[Emmanuel Venisse]

me too.

The release in near!!!

Emmanuel

- Original Message - 
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: "'Maven Developers List'" <[EMAIL PROTECTED]>
Sent: Wednesday, January 28, 2004 6:47 PM
Subject: RE: RC2


> Yes, I agree, thank you Brett!
> 
> -Vincent
>  
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: 28 January 2004 14:21
> > To: [EMAIL PROTECTED]
> > Subject: RC2
> > 
> > Just a quick email to thank Brett on the good work he's done for RC2.
> > 
> > It's starting to look like we're almost there!
> > --
> > dIon Gillard, Multitask Consulting
> > Blog:  http://blogs.codehaus.org/people/dion/
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2

[Vincent Massol]

Yes, I agree, thank you Brett!

-Vincent
 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 28 January 2004 14:21
> To: [EMAIL PROTECTED]
> Subject: RC2
> 
> Just a quick email to thank Brett on the good work he's done for RC2.
> 
> It's starting to look like we're almost there!
> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RC2 and Plugin cache

[Brett Porter]

Yes. That's next on the list once I remove the remaining classloader bug.

- Brett

> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 22 January 2004 1:40 AM
> To: [EMAIL PROTECTED]
> Subject: RC2 and Plugin cache
> 
> 
> Brett or Dion,
> 
> Could we reactivate plugin cache in maven rc2 for accelerated 
> maven load?
> 
> Emmanuel
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: rc2 unstable

[Brett Porter]

> The only thing I would like to preserve from my branch is the 
> werkz stuff. For the most part I have completely rewritten 
> the core as a series of components which can be integrated 
> piece wise post 1.0 along with Wagon and this will definitely 
> make developing Maven easier.
> 
> If you work on rc2 then I'll focus on testing the new 
> components, getting the coverage up and moving stuff into 
> CVS. Wagon will be the first piece to land, most likely in a few days.
> 
> > If so, I might embellish a bit, put it on
> > the wiki, and make sure JIRA is setup appropriately.
> 
> +1
> 

Sounds like a good plan. I'll get to the roadmap sometime this week.

Thanks,
Brett

RE: rc2 unstable

[Jason van Zyl]

On Mon, 2003-11-17 at 17:12, Brett Porter wrote:
> Jason gave a good explanation, but I'll give a shorter one with some
> clairifications:
> 
> 1) RC2 unstable is what should be 1.0 RC2 once merged with HEAD. After that,
> bugfixes and a 1.0 release.
> 2) RC2 unstable only contains fixes for the multiple creation of Jelly
> contexts and ant projects for plugins, butting back to one ant project in
> total per goal attainment and one context per plugin per execution. This
> fixes the reactor memory leak. It was largely based on Jason's branch,
> although isolated to changes in the plugin manager, obviously.
> 3) all the other stuff Jason did is good cleanup/refactoring and will make
> Maven easier to embed (and more importantly understand and develop on :),
> and it seems it will all be rolled into post-1.0 now, 1 piece at a time
> while we ensure everything continues to work as it used to.
> 4) I implemented property inheritence within the current Jelly
> infrastructure. It hasn't received much testing yet, but should work. It
> also inherits multiple levels of the POM, maven.xml and the properties.
> There is a test project in the branch.
> 
> Hope this is less confusing :)
> 
> Are we all in agreeance that 1) and 3) are basically the roadmap for
> maven-core through 1.0 and 1.1? 

+1

The only thing I would like to preserve from my branch is the werkz
stuff. For the most part I have completely rewritten the core as a
series of components which can be integrated piece wise post 1.0 along
with Wagon and this will definitely make developing Maven easier.

If you work on rc2 then I'll focus on testing the new components,
getting the coverage up and moving stuff into CVS. Wagon will be the
first piece to land, most likely in a few days.

> If so, I might embellish a bit, put it on
> the wiki, and make sure JIRA is setup appropriately.

+1

> Cheers,
> Brett
> 
> > -Original Message-
> > From: Vincent Massol [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, 18 November 2003 2:20 AM
> > To: 'Maven Developers List'
> > Subject: RE: rc2 unstable
> > 
> > 
> > Guys, sorry to ask again but I have trouble understanding 
> > what's in those branches. What is the status with properties 
> > inheritance? Is that in rc2 unstable? Is it going to be 
> > rolled in anytime soon? What is rc2 unstable? Is it based on 
> > a completely new Maven core (plexus). If so, how could you 
> > merge it with head without breaking everything?
> > 
> > Thanks
> > -Vincent (a bit confused :-))
> > 
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: rc2 unstable

[Brett Porter]

Jason gave a good explanation, but I'll give a shorter one with some
clairifications:

1) RC2 unstable is what should be 1.0 RC2 once merged with HEAD. After that,
bugfixes and a 1.0 release.
2) RC2 unstable only contains fixes for the multiple creation of Jelly
contexts and ant projects for plugins, butting back to one ant project in
total per goal attainment and one context per plugin per execution. This
fixes the reactor memory leak. It was largely based on Jason's branch,
although isolated to changes in the plugin manager, obviously.
3) all the other stuff Jason did is good cleanup/refactoring and will make
Maven easier to embed (and more importantly understand and develop on :),
and it seems it will all be rolled into post-1.0 now, 1 piece at a time
while we ensure everything continues to work as it used to.
4) I implemented property inheritence within the current Jelly
infrastructure. It hasn't received much testing yet, but should work. It
also inherits multiple levels of the POM, maven.xml and the properties.
There is a test project in the branch.

Hope this is less confusing :)

Are we all in agreeance that 1) and 3) are basically the roadmap for
maven-core through 1.0 and 1.1? If so, I might embellish a bit, put it on
the wiki, and make sure JIRA is setup appropriately.

Cheers,
Brett

> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 18 November 2003 2:20 AM
> To: 'Maven Developers List'
> Subject: RE: rc2 unstable
> 
> 
> Guys, sorry to ask again but I have trouble understanding 
> what's in those branches. What is the status with properties 
> inheritance? Is that in rc2 unstable? Is it going to be 
> rolled in anytime soon? What is rc2 unstable? Is it based on 
> a completely new Maven core (plexus). If so, how could you 
> merge it with head without breaking everything?
> 
> Thanks
> -Vincent (a bit confused :-))
> 

RE: rc2 unstable

[Jason van Zyl]

On Mon, 2003-11-17 at 10:20, Vincent Massol wrote:
> Guys, sorry to ask again but I have trouble understanding what's in
> those branches. 

In rc1-refactor I attempted to fix everything which included making
Maven a bean, removing Jelly/Ant from all code except the plugin
manager, classloader separation, removal of betwixt with xpp3, proper
inheritance across the board and a reimplementation of the plugin cache
manager. I finished and everything bootstrapped but there is a show
stopping problem pre/post goals as a result of me revamping the way
werkz handled goals. The changes in Werkz are necessary in order to
isolate the classloader a particular plugin uses.

I still think all of these things are required but currently I don't
really care that much about my branch as all I really want is something
we can call 1.0. Ultimately all of the code is going to be replaced in a
piecewise fashion with well tested components.

> What is the status with properties inheritance? 

It works in my branch because I removed Jelly from equation which makes
things easy. These bits I might merge into Brett's branch because you
need to remove Jelly/Ant from the process or it's just plain nasty.

> Is that
> in rc2 unstable? 

Not sure what Brett has working but I still see Jelly stuff in there.

> Is it going to be rolled in anytime soon? 

Brett's going as fast as he can, and I will make one last attempt at
fixing the problems in my branch as I can build anything with it there
are just some glitches with in my handling of goals which is ultimately
going to need to be fixed anyway I just want to do it after 1.0.

> What is rc2
> unstable? Is it based on a completely new Maven core (plexus).

No, neither branches are based on Plexus but I'm going to start bring
pieces over bit by bit that are.

>  If so,
> how could you merge it with head without breaking everything?

With the branches I imagine we might have to do something empirical like
setup DamageControl with a set of projects using the old and new code.
Due to the nature of the code even with tests something will likely go
awry.

What I want to do is start using small components and Wagon will be the
first one. Wagon is actually neither bound to Maven or Plexus but is a
general artifact handling library which is small and currently stands at
~100% coverage. I also have small components for the core of Maven and
they will also have close to ~100% coverage. It will be the only way to
bring the code to some level of sanity. And these small bits of code can
be introduced one at time as it is obvious that my massive rewrite of
one blob with another blob didn't work.

All artifact handling will be done with Wagon. So small artifact
handlers can be written and tested so we can gradually removed the
untested crap (which I take entire responsibility for in having not
insisted on better testing practices) with components like Wagon which
themselves are tested and are easier to test with.

> Thanks
> -Vincent (a bit confused :-))
> 
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 17 November 2003 15:33
> > To: Maven Developers List
> > Subject: RE: rc2 unstable
> > 
> > On Sun, 2003-11-16 at 16:49, Brett Porter wrote:
> > > Status update: I believe I now have all of the plugin context issues
> > licked.
> > > I haven't had a chance to fully test my last set of changes, but I
> > > identified the problem.
> > >
> > > Jason, how did your work on the werkz code go on the weekend?
> > 
> > I worked on Plexus and Wagon all weekend. I'm afraid to start on that
> > Maven branch because it will inevitably mean I won't look at anything
> > else for a span of days.
> > 
> > But I think our work in the separate branches is primarily
> complementary
> > and originally comes from the branch I'm working on so whatever bits
> and
> > pieces go in don't really matter. I won't attempt to fix the werkz
> > problem until I can replicate it the problem with a test. I am also
> not
> > averse to rolling in more changes post 1.0. If most of the memory leak
> > is taken care I think everyone will be happy with that.
> > 
> > > This leaves some very minor things left to fix and some more testing
> > before
> > > the RC2 branch is (hopefully!) fully functional again with all
> existing
> > > plugins/projects, unless they seriously abused the way the old
> system
> > > worked.
> > >
> > > >From there, I'd like to attempt to reimplement plugin caching (the
> old
> > > technique was incompatible) before RC2 is made available to reduce
> the
> > > startup time again.
> > 
> > I d

RE: rc2 unstable

[Vincent Massol]

Guys, sorry to ask again but I have trouble understanding what's in
those branches. What is the status with properties inheritance? Is that
in rc2 unstable? Is it going to be rolled in anytime soon? What is rc2
unstable? Is it based on a completely new Maven core (plexus). If so,
how could you merge it with head without breaking everything?

Thanks
-Vincent (a bit confused :-))

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2003 15:33
> To: Maven Developers List
> Subject: RE: rc2 unstable
> 
> On Sun, 2003-11-16 at 16:49, Brett Porter wrote:
> > Status update: I believe I now have all of the plugin context issues
> licked.
> > I haven't had a chance to fully test my last set of changes, but I
> > identified the problem.
> >
> > Jason, how did your work on the werkz code go on the weekend?
> 
> I worked on Plexus and Wagon all weekend. I'm afraid to start on that
> Maven branch because it will inevitably mean I won't look at anything
> else for a span of days.
> 
> But I think our work in the separate branches is primarily
complementary
> and originally comes from the branch I'm working on so whatever bits
and
> pieces go in don't really matter. I won't attempt to fix the werkz
> problem until I can replicate it the problem with a test. I am also
not
> averse to rolling in more changes post 1.0. If most of the memory leak
> is taken care I think everyone will be happy with that.
> 
> > This leaves some very minor things left to fix and some more testing
> before
> > the RC2 branch is (hopefully!) fully functional again with all
existing
> > plugins/projects, unless they seriously abused the way the old
system
> > worked.
> >
> > >From there, I'd like to attempt to reimplement plugin caching (the
old
> > technique was incompatible) before RC2 is made available to reduce
the
> > startup time again.
> 
> I did reimplement the searching and caching in a different plugin
> manager that had a number of tests and fixed the problem where the old
> plugin manager didn't find dependencies properly. It was a source file
> with a set of diagrams outlining the possible dependencies between
> goals, prereqs and other plugins.
> 
> > Cheers,
> > Brett
> >
> > > -Original Message-
> > > From: Brett Porter
> > > Sent: Thursday, 13 November 2003 8:20 AM
> > > To: 'Maven Developers List'
> > > Subject: RE: rc2 unstable
> > >
> > >
> > > Done. I noticed you already did the plugins in CVS - I
> > > thought this was only on your copy. Cool. Much cleaner now.
> > > Will also make any merging later a helluva lot easier.
> > >
> > > Current status: the pluginVar tag is not working properly in
> > > a reactor, because project.context != context.project in some
> > > cases (it seems projects have multiple contexts). I need to
> > > draw this up and figure out where the double mapping crept in.
> > >
> > > This means touchstone runs regularly, but not via maven test
> > > in the base directory (eg bootstrap).
> > >
> > > Cheers,
> > > Brett
> > >
> --
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
> 
>   -- Jacques Ellul, The Technological Society
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: rc2 unstable

[Jason van Zyl]

On Sun, 2003-11-16 at 16:49, Brett Porter wrote:
> Status update: I believe I now have all of the plugin context issues licked.
> I haven't had a chance to fully test my last set of changes, but I
> identified the problem.
> 
> Jason, how did your work on the werkz code go on the weekend?

I worked on Plexus and Wagon all weekend. I'm afraid to start on that
Maven branch because it will inevitably mean I won't look at anything
else for a span of days.

But I think our work in the separate branches is primarily complementary
and originally comes from the branch I'm working on so whatever bits and
pieces go in don't really matter. I won't attempt to fix the werkz
problem until I can replicate it the problem with a test. I am also not
averse to rolling in more changes post 1.0. If most of the memory leak
is taken care I think everyone will be happy with that.

> This leaves some very minor things left to fix and some more testing before
> the RC2 branch is (hopefully!) fully functional again with all existing
> plugins/projects, unless they seriously abused the way the old system
> worked.
> 
> >From there, I'd like to attempt to reimplement plugin caching (the old
> technique was incompatible) before RC2 is made available to reduce the
> startup time again.

I did reimplement the searching and caching in a different plugin
manager that had a number of tests and fixed the problem where the old
plugin manager didn't find dependencies properly. It was a source file
with a set of diagrams outlining the possible dependencies between
goals, prereqs and other plugins.

> Cheers,
> Brett
> 
> > -Original Message-
> > From: Brett Porter 
> > Sent: Thursday, 13 November 2003 8:20 AM
> > To: 'Maven Developers List'
> > Subject: RE: rc2 unstable
> > 
> > 
> > Done. I noticed you already did the plugins in CVS - I 
> > thought this was only on your copy. Cool. Much cleaner now. 
> > Will also make any merging later a helluva lot easier.
> > 
> > Current status: the pluginVar tag is not working properly in 
> > a reactor, because project.context != context.project in some 
> > cases (it seems projects have multiple contexts). I need to 
> > draw this up and figure out where the double mapping crept in.
> > 
> > This means touchstone runs regularly, but not via maven test 
> > in the base directory (eg bootstrap).
> > 
> > Cheers,
> > Brett
> > 
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: rc2 unstable

[Brett Porter]

Status update: I believe I now have all of the plugin context issues licked.
I haven't had a chance to fully test my last set of changes, but I
identified the problem.

Jason, how did your work on the werkz code go on the weekend?

This leaves some very minor things left to fix and some more testing before
the RC2 branch is (hopefully!) fully functional again with all existing
plugins/projects, unless they seriously abused the way the old system
worked.

>From there, I'd like to attempt to reimplement plugin caching (the old
technique was incompatible) before RC2 is made available to reduce the
startup time again.

Cheers,
Brett

> -Original Message-
> From: Brett Porter 
> Sent: Thursday, 13 November 2003 8:20 AM
> To: 'Maven Developers List'
> Subject: RE: rc2 unstable
> 
> 
> Done. I noticed you already did the plugins in CVS - I 
> thought this was only on your copy. Cool. Much cleaner now. 
> Will also make any merging later a helluva lot easier.
> 
> Current status: the pluginVar tag is not working properly in 
> a reactor, because project.context != context.project in some 
> cases (it seems projects have multiple contexts). I need to 
> draw this up and figure out where the double mapping crept in.
> 
> This means touchstone runs regularly, but not via maven test 
> in the base directory (eg bootstrap).
> 
> Cheers,
> Brett
> 

RE: rc2 unstable

[Brett Porter]

Done. I noticed you already did the plugins in CVS - I thought this was only
on your copy. Cool. Much cleaner now. Will also make any merging later a
helluva lot easier.

Current status: the pluginVar tag is not working properly in a reactor,
because project.context != context.project in some cases (it seems projects
have multiple contexts). I need to draw this up and figure out where the
double mapping crept in.

This means touchstone runs regularly, but not via maven test in the base
directory (eg bootstrap).

Cheers,
Brett

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 11 November 2003 9:26 AM
> To: Maven Developers List
> Subject: RE: rc2 unstable
> 
> 
> On Mon, 2003-11-10 at 16:21, Brett Porter wrote:
> > Jason,
> > 
> > Just 1 question regarding this. How did you go about doing 
> this merge?
> 
> Most of the plugins were removed from HEAD so I simply did 
> the same thing in the branch. I have yet to merge the core 
> plugins together.
> 
> > There's been a fair few changes on HEAD and it would be 
> worth a merge. 
> > I'm happy to do it - I think I originally stated I'd do this once a 
> > week, but I didn't quite get around to that :)
> 
> Sure, go for it.
> 
> > Basically I'll just do:
> > cvs update -j HEAD (on the branch)
> > cvs tag MAVEN_RC2_UNSTABLE-merge-1 (on the trunk)
> > 
> > Anyone have a problem with this?
> 
> +1
> 
> > Of course this means that at the end of the day the branch 
> cannot be 
> > merged to the trunk because all of the trunk changes will conflict. 
> > However, we are basically working with an inverted trunk/branch 
> > scenario here, and as long as all trunk changes are merged to the 
> > branch at the final point, the files can just be copied as is and 
> > committed onto the trunk to do an effective merge of the branch.
> > 
> > Cheers,
> > Brett
> > 
> > > -Original Message-
> > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, 10 November 2003 5:43 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: rc2 unstable
> > > 
> > > 
> > > On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> > > > Howdy Brett,
> > > > 
> > > > I'm just bootstrapping rc2 unstable now and I'm going to
> > > try and knock
> > > > off a couple of the items on list 1. Is there anything 
> we need to
> > > > merge from HEAD? Possibly with the switch over of the plugins?
> > > 
> > > I'm syncing up the plugins now between the HEAD and
> > > rc2-unstable branch. This will be much easier now with most 
> > > of the plugins separated.
> > > 
> > > BTW: is the multiproject plugin supposed to be moved to 
> > > maven-plugins?
> > > 
> > > --
> > > jvz.
> > > 
> > > Jason van Zyl
> > > [EMAIL PROTECTED]
> > > http://tambora.zenplex.org
> > > 
> > > In short, man creates for himself a new religion of a
> > > rational and technical order to justify his work and to be 
> > > justified in it.
> > >   
> > >   -- Jacques Ellul, The Technological Society
> > > 
> > > 
> > > 
> 
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > 
> -- 
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a 
> rational and technical order to justify his work and to be 
> justified in it.
>   
>   -- Jacques Ellul, The Technological Society
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: rc2 unstable

[Jason van Zyl]

On Mon, 2003-11-10 at 16:21, Brett Porter wrote:
> Jason,
> 
> Just 1 question regarding this. How did you go about doing this merge? 

Most of the plugins were removed from HEAD so I simply did the same
thing in the branch. I have yet to merge the core plugins together.

> There's been a fair few changes on HEAD and it would be worth a merge. I'm
> happy to do it - I think I originally stated I'd do this once a week, but I
> didn't quite get around to that :)

Sure, go for it.

> Basically I'll just do:
> cvs update -j HEAD (on the branch)
> cvs tag MAVEN_RC2_UNSTABLE-merge-1 (on the trunk)
> 
> Anyone have a problem with this?

+1

> Of course this means that at the end of the day the branch cannot be merged
> to the trunk because all of the trunk changes will conflict. However, we are
> basically working with an inverted trunk/branch scenario here, and as long
> as all trunk changes are merged to the branch at the final point, the files
> can just be copied as is and committed onto the trunk to do an effective
> merge of the branch.
> 
> Cheers,
> Brett
> 
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> > Sent: Monday, 10 November 2003 5:43 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: rc2 unstable
> > 
> > 
> > On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> > > Howdy Brett,
> > > 
> > > I'm just bootstrapping rc2 unstable now and I'm going to 
> > try and knock 
> > > off a couple of the items on list 1. Is there anything we need to 
> > > merge from HEAD? Possibly with the switch over of the plugins?
> > 
> > I'm syncing up the plugins now between the HEAD and 
> > rc2-unstable branch. This will be much easier now with most 
> > of the plugins separated.
> > 
> > BTW: is the multiproject plugin supposed to be moved to maven-plugins?
> > 
> > -- 
> > jvz.
> > 
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://tambora.zenplex.org
> > 
> > In short, man creates for himself a new religion of a 
> > rational and technical order to justify his work and to be 
> > justified in it.
> >   
> >   -- Jacques Ellul, The Technological Society
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: rc2 unstable

[Brett Porter]

Jason,

Just 1 question regarding this. How did you go about doing this merge? 

There's been a fair few changes on HEAD and it would be worth a merge. I'm
happy to do it - I think I originally stated I'd do this once a week, but I
didn't quite get around to that :)

Basically I'll just do:
cvs update -j HEAD (on the branch)
cvs tag MAVEN_RC2_UNSTABLE-merge-1 (on the trunk)

Anyone have a problem with this?

Of course this means that at the end of the day the branch cannot be merged
to the trunk because all of the trunk changes will conflict. However, we are
basically working with an inverted trunk/branch scenario here, and as long
as all trunk changes are merged to the branch at the final point, the files
can just be copied as is and committed onto the trunk to do an effective
merge of the branch.

Cheers,
Brett

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 10 November 2003 5:43 AM
> To: [EMAIL PROTECTED]
> Subject: Re: rc2 unstable
> 
> 
> On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> > Howdy Brett,
> > 
> > I'm just bootstrapping rc2 unstable now and I'm going to 
> try and knock 
> > off a couple of the items on list 1. Is there anything we need to 
> > merge from HEAD? Possibly with the switch over of the plugins?
> 
> I'm syncing up the plugins now between the HEAD and 
> rc2-unstable branch. This will be much easier now with most 
> of the plugins separated.
> 
> BTW: is the multiproject plugin supposed to be moved to maven-plugins?
> 
> -- 
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a 
> rational and technical order to justify his work and to be 
> justified in it.
>   
>   -- Jacques Ellul, The Technological Society
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: rc2 unstable

[Jason van Zyl]

On Sun, 2003-11-09 at 17:09, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 10/11/2003 05:42:46 AM:
> 
> > On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> > > Howdy Brett,
> > > 
> > > I'm just bootstrapping rc2 unstable now and I'm going to try and knock
> > > off a couple of the items on list 1. Is there anything we need to 
> merge
> > > from HEAD? Possibly with the switch over of the plugins?
> > 
> > I'm syncing up the plugins now between the HEAD and rc2-unstable branch.
> > This will be much easier now with most of the plugins separated.
> > 
> > BTW: is the multiproject plugin supposed to be moved to maven-plugins?
> 
> I didn't move that one, as it makes it easier to build all of 
> maven-plugins if it's already installed.

Hokey doke.

> > 
> > -- 
> > jvz.
> 
> --
> dIon Gillard, Multitask Consulting
> Blog:  http://blogs.codehaus.org/people/dion/
> Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: rc2 unstable

[dion]

Jason van Zyl <[EMAIL PROTECTED]> wrote on 10/11/2003 05:42:46 AM:

> On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> > Howdy Brett,
> > 
> > I'm just bootstrapping rc2 unstable now and I'm going to try and knock
> > off a couple of the items on list 1. Is there anything we need to 
merge
> > from HEAD? Possibly with the switch over of the plugins?
> 
> I'm syncing up the plugins now between the HEAD and rc2-unstable branch.
> This will be much easier now with most of the plugins separated.
> 
> BTW: is the multiproject plugin supposed to be moved to maven-plugins?

I didn't move that one, as it makes it easier to build all of 
maven-plugins if it's already installed.

> 
> -- 
> jvz.

--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: rc2 unstable

[Jason van Zyl]

On Sun, 2003-11-09 at 13:08, Jason van Zyl wrote:
> Howdy Brett,
> 
> I'm just bootstrapping rc2 unstable now and I'm going to try and knock
> off a couple of the items on list 1. Is there anything we need to merge
> from HEAD? Possibly with the switch over of the plugins?

I'm syncing up the plugins now between the HEAD and rc2-unstable branch.
This will be much easier now with most of the plugins separated.

BTW: is the multiproject plugin supposed to be moved to maven-plugins?

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]