2007/9/13, Ted Husted <[EMAIL PROTECTED]>:
>
> Of course, sadly, Hibernate is under the LGPL, which the FSF insists
> is not compatible with the Apache License :(
You can use Apache Cayenne then :-)
Antonio
On 9/13/07, Jim Cushing <[EMAIL PROTECTED]> wrote:
> A Maven archetype should get you around any license/distribution
> issues,
Yes and no. We have to be careful to make it *very* clear to the
general public that by utilizing such a prototype they will be
creating an application that is not under
A Maven archetype should get you around any license/distribution
issues, provided the dependencies are in a public Maven repository.
Then, Maven will download the dependencies, such that they don't need
to be bundled. It's nice, but not necessary, that the plugins have
Maven POMs (for the s
Luckily Smart URLs is A2 ;)
I agree that providing a zip is probably better. I think ensuring that
out of the box things can be configured for maximum simplicity and make
it easy for developers to get up and running should be the goal. This
mostly comes down to documentation and not necessari
In our case, we might want to think about a struts-standard.zip or
struts-bundle.zip that contained the recommended plugins -and- their
dependencies. So, if we are including the Spring plugin, we would
include the spring.jar too. This could just be yet another artifact
that we post, like the struts
My only caution with a struts2-standard.jar is that the analogy to Spring
isn't accurate. Spring doesn't have a plug-in architecture (yet) and
including more classes doesn't affecting the running of the libraries. On
the contrary, Struts plug-ins are loaded automatically and hook themselves
into th
Henri also is fixing a lot of outstanding EL bugs in the taglibs project.
On 9/11/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> 2007/9/11, Don Brown <[EMAIL PROTECTED]>:
> >
> > As far as a replacement, personally, I'm more interested in
> > incorporating the "Unified EL", standardized by JS
