Re: [PROPOSAL] lifecycle release
Peter Donald <[email protected]> Sat, 22 Mar 2003 12:16:53 +1100
| Newsgroups | gmane.comp.jakarta.avalon.phoenix.devel,gmane.comp.jakarta.turbine.maven.devel |
|---|---|
| Message-ID | <200303221216.53388.peter__48676.7187285752$1048294695@realityforge.org> |
On Thu, 20 Mar 2003 20:32, Niclas Hedhman wrote: > On Thursday 20 March 2003 16:28, Peter Donald wrote: > > On Thu, 20 Mar 2003 15:14, Niclas Hedhman wrote: > > > Also, if you are requiring me to have dedicated Ant tasks (not > > > everybody builds with Ant (strangely enough)) to be used when I dev= elop > > > my Avalon blocks/components, then you ARE raising the bar > > > significantly. > > > > whether it is ant tasks, commandline tools or maven plugins most peop= le > > use tools of one sort or another so I don't see that as a major barri= er > > of entry. In JDK1.5 it will be part of javac so then there will be 0 > > changes. > > Maybe you are more dense than I thought. hmmm. > Every project, looked at only from the perspective of such project, hav= e a > list of "Because..." a particular "oddity" should come to life and it i= s > often hard to come up with counter-argument. > The members of such project are so "self-occupied" (not trying to be ru= de, > just don't have a better word at the moment ) that they don't see the > "bigger picture". heh - the bigger picture is that this is the way all major technical path= s=20 look like going via ADD. It is native in C#, will be in Java and most maj= or=20 technical=20 > Finally, your assumption that JSR-175 will be included in JSR-176 is > perhaps a bit pre-mature. JSR-176 sure lists itself as targetting Tiger= , > but JSR-176 doesn't list 175. Given the political context in which it is developed I doubt it will not = be=20 part of Tiger. Especially given that the lead is one hell of a doer. --=20 Cheers, Peter Donald -------------------------------- These aren't the droids you're=20 looking for. Move along.=20 --------------------------------=20