You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <bp...@f2network.com.au> on 2004/01/05 23:30:28 UTC
RE: ant 1.6, classloader, etc WAS: some cvs commit
If that's the case, can we assume that some tasks are missing where people
might expect them to be there?
Anyway, I'm ok with the change, but we should probably do it properly. I'm
happy to break compatibility in this case and not include any optional tasks
and push them out to the individual plugins that need them and include it in
the next release notes as a gotcha.
Jason, would pushing the junit task definition into the test plugin help
with the ant classloader problems with junit?
Cheers,
Brett
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Monday, 5 January 2004 4:05 PM
> To: Maven Developers List
> Subject: RE: cvs commit: maven/src/bin forehead.conf
>
>
> Jason van Zyl <jv...@maven.org> wrote on 05/01/2004 02:46:15 PM:
>
> > On Sun, 2004-01-04 at 22:26, Brett Porter wrote:
> > > That dependency list looks scary - is it really all needed?
> >
> > Yes, I agree that list of deps add while we are trying to get
> > something called 1.0 out the door is a little out of line.
>
> Do you realise that that is less (from a task angle) than what was in
> ant-optional.jar?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
RE: ant 1.6, classloader, etc WAS: some cvs commit
Posted by di...@multitask.com.au.
Brett Porter <bp...@f2network.com.au> wrote on 06/01/2004 09:30:28 AM:
> If that's the case, can we assume that some tasks are missing where
people
> might expect them to be there?
Yes, if people were using:
- the nextrexxc task
- the stylebook task
- the VisualAge for Java tasks
- Xalan1 as an XSL processor
- XSLP as an XSL processor
My call was that there would be almost no plugins written using these
tasks. I googled on maven plugin and the appropriate task before deciding.
> Anyway, I'm ok with the change, but we should probably do it properly.
I'm
Can you expand on 'do it properly'?
> happy to break compatibility in this case and not include any optional
tasks
> and push them out to the individual plugins that need them and include
it in
> the next release notes as a gotcha.
Optional tasks were always problematic for users of maven, as they have to
know the magic classloader syntax to make them available. Very few people
do.
There are also new tasks in Ant 1.6 we can use to make ssh etc easier.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org