On Tue, 2004-10-26 at 04:23, Vincent Massol wrote: > > 2.Release a temporary 1.7 version (like Milestone 1) > > I'd prefer a 1.7 final. This is the strategy that we've usually followed in > Cactus and thanks to our strong test suite we've never had any major issue. > We can always follow it by a 1.7.1 bug fix release if need be.
The problem, im my opinion, is that we should have a 1.6.2 that fixes a lot of the recent issues (like the JDK 1.5 related ones), but it's too late now (as we should have forked before) > That said, I'm also ok with a 1.7-beta/rc1 if you feel strongly about it > (we've had one in the past too). Yes, I think we need some intermediate release. > Now, who wants to be the release manager? :-) It's a relatively involved > process but I could it with someone else the first time if need be. Or I > could do it myself if nobody volunteers. I'd like to volunteer, but I'm afraid I won't have time for it in this upcoming week. > Yeah, I remember we discussed this with Chris some time back but we never > really saw the need to have this third module. What do you think would be > the benefit? Is there a benefit in not having the Maven plugin depend on the > Ant plugin? I see 3 reasons: 1.Sometimes looks like the Maven plugin and Ant tasks are not the same, i.e., it's hard to realize how the plugin is passing arguments to the task (I can't remember an example, but it happened at least twice with me) 2.Isn't there a recommendation to remove Ant (and even Jelly) dependencies on maven plugins? If we move the logic to Cargo, it would be simpler to move the plugin logic to POJOS and then just use Jelly to wrap the taglib 3.When I have to debug/analyze the plugin, I think it's harder to understand what goes on inside the ant tasks than it would be in a POJO. > How do we distribute that third module? As yet another jar? In > that case it's more cumbersome for end users which I'd rather not (it's not > a problem for Maven users but it is for Ant users). Wouldn't we be distributing Cargo separated anyway? Actually, I haven't even thought about this module being an independent jar; my original idea was just a logical layer packaged on Cactus' jar. -- Felipe > > > > > > Is that ok with everyone? > > > > Yes. > > Cool, thanks > > -Vincent > > > --------------------------------------------------------------------- > 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]
