RE: ant 1.6, classloader, etc WAS: some cvs commit

2004-01-05 Thread dion
Brett Porter <[EMAIL PROTECTED]> wrote on 06/01/2004 11:35:42 AM: > > > Anyway, I'm ok with the change, but we should probably do > > it properly. > > I'm > > > > Can you expand on 'do it properly'? > > I would think we can push the optional JARs out to the plugins and make > MAVEN_HOME/lib a b

RE: ant 1.6, classloader, etc WAS: some cvs commit

2004-01-05 Thread Brett Porter
> 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. Fair enough. > > > Anyway, I'm ok with the change, but we should probably do > it properly. > I'm > > Can you expand on 'do it properly'? I

RE: ant 1.6, classloader, etc WAS: some cvs commit

2004-01-05 Thread dion
Brett Porter <[EMAIL PROTECTED]> 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 ta

RE: ant 1.6, classloader, etc WAS: some cvs commit

2004-01-05 Thread Brett Porter
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 plug