I always figured it would be available through the build file. When talking with James Mitchell (who is new to MyFaces) he said the myfaces-all.jar would be the first thing he would look for. So its probably best we include this in the official distro as well. See my later post containing a revised list.
sean On 5/27/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote: > Even if we don't distribute it, I think it would be convenient to have one > jar with everything (including the sandbox). > Maybe it's just a target in the build file, but for those of us using and > modifying myfaces, it's very convenient to update just one file in the > webapps, and have everything there. > > Sylvain. > > > On Fri, 2005-05-27 at 13:49 -0400, Sean Schofield wrote: > > I think a myfaces-all.jar will also contain the sandbox components - > > why would they not be in there? it is just necessary to clearly mark > > them as sandbox (e.g. using a new taglib, as was proposed by Sean) so > > that the users know what they get. > > My argument for not including them is that they are experimental. The > myfaces-all.jar will be part of the implementation bundle and subject > to official releases. I don't think we want to distribute the sandbox > stuff as anything official and putting it out on mirrors,etc. along > with myfaces-all.jar would give that impression. > > Best to have two jars if you're using the sandbox stuff in your > production system. myfaces-all.jar and myfaces-sandbox.jar. The > sandbox could be built using Ant or you could just grab the latest > nightly. > > Does anyone else have an opinion on that? > > > Martin > > sean > >
