From: "Morgan Delagrange" <[EMAIL PROTECTED]> > So far only Bob has voiced a concern with preparing to > release a Jelly beta, and I believe his only concern > is whether or not to release it under the Commons > umbrella. So I'm going to start raising some release > issues, and I'll steer clear of anything relating to > packaging for now, just in case someone wants to > propose moving Jelly soon. (Personally, I'm +0 on the > idea; sounds like potentially good exposure for Jelly, > but it doesn't scratch any itches for me. I still > volunteer as release manager, regardless of Jelly's > location in Jakarta.)
Although I'm not a Jellier, I think that the length of the dependency list gives a clue that Jelly is not really a commons component, but an integration one like Ant. (Of course Ant isn't in Jakarta anymore....) > http://jakarta.apache.org/commons/sandbox/jelly/dependencies.html > > Holy cow. It's not the number of dependencies that > concerns me, it's the number of dependencies based on > snapshots and alphas. My first reaction is that Jelly will probably always be at the forefront of technologies, so this isn't a problem that will just go away. > Regardless of how we structure the JARs and the CVS > repository, I think we should focus on identifying > dependencies specific to Jelly and the core tag > library, and once we have a solid list we should try > to obtain as many released versions as we can manage. > I'm uncomfortable releasing Jelly based on beta > dependencies, and I think including snapshots is > completely unworkable. I'm hopeful that we can get a new [lang] release out fairly soon. That should remove one from your list. Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
