Yeah sure, definitely take your time.

Hmmm....I've already bugged apache legal enough about it that I think I
won't try and push it too much. More or less it ended up being that by
default anyone who downloads apache software should expect that everything
is completely free (as much as ASF 2 license allows at least) without worry
or hassle about anything else...So...If we want to build something that
~depends~ on non apache safe licenses we have to make very sure that users
understand this as clearly as possible.

I have no idea how an alert feature like that would work :) I have a feeling
the maven people might want to add it as an official maven plugin if there's
a chance any other project might want to do similar licensing things.

The easiest solution would be a very simple maven plugin that just prints
out whatever text you configure it to print out with, with the option of the
user having accepted/not accepted what you presented to them. Something like
a console-based modal dialog. (sort of? )

On 7/11/06, D&J Gredler <[EMAIL PROTECTED]> wrote:

If there's no rush, I think I'll take a couple of weeks and do it at a
leisurely pace. The SF project is Maven2-based, so the docs should
transfer
nicely. Do you know of any Maven "license alert" examples that I can draw
from? Also, the Hibernate dependencies have a scope of "provided" (i.e.
the
user has to provide the Hibernate jars at runtime if they want to use the
Hibernate integration features), though I don't know if that makes a
difference.

On 7/11/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
>
> I forgot to answer your original question.
>
> No rush on getting it done by the end of the week, not much will change
> other than us having documentation for most of the important items.
Final
> is
> probably still a ways off.
>
> Also, there are a few caveats to adding this in that you should be aware
> of:
>
> -) Should go in tapestry-contrib , think you already know that.
>
> -) Should come with maven2 compliant documentation. You should be able
to
> find this in the root documentation directory under src/site .
>
> -) The not so fun part, we'll need the contrib build step(ie via maven2
)
> to
> do some sort of interactive confirmation on the command line, only for
the
> first time contrib is built. This is to satisy the ASF requirements for
> having anything built that might rely on outside un-friendly ASF license
> code...Like lgpl and hibernate. The confirmation step only needs to have
> text in it that says something along the lines of "Some portions of the
> library you are building contain non apache 2.0 licensed code. This
> includes
> hibernate library dependencies which use an LGPL license. Please confirm
> that you understand. "
>
> Something like that. You really don't have to go through all of this
> trouble
> if you don't want to, but since I'd have to do it one way or the other
if
> we
> included your code I'd rather shift the burden to you :)
>
> If you decide to keep the code in an outside library I would
understand...
> We don't make the rules..
>
> On 7/10/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
> >
> > George Lucas is waiting in the wings for them to get bought by Red Hat
> > before suing them ;-)
> >
> > On 7/11/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > >
> > > Ah...Wicket.... I don't know how I feel about frameworks that are
> named
> > > after star wars characters..
> > >
> > > http://en.wikipedia.org/wiki/Wicket_W._Warrick
> > >
> > > On 7/10/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Ah, I think it was Wicket that ditched OGNL...
> > > >
> > > > On 7/11/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > I think that was someone else. I'm going to resist the very
large
> > urge
> > > > and
> > > > > just keep my mouth shut about what I think of webwork
controlling
> > > > OGNL...
> > > > >
> > > > > On 7/10/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > I thought WebWork had recently stopped using OGNL in favor of
a
> > > > > homebrewed
> > > > > > solution... or was that a different framework?
> > > > > >
> > > > > >
> > > > > > On 7/11/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > > > > > >
> > > > > > > Ahh....I hadn't noticed that you had added in validation
> > handling.
> > > > > Looks
> > > > > > > pretty slick so far.
> > > > > > >
> > > > > > > I worry about adding components into the library unless an
> > active
> > > > > > > committer
> > > > > > > is going to take responsibility for maintaining them - and
the
> > > > likely
> > > > > > JIRA
> > > > > > > issues they produce...But I guess even worse than that is
not
> > > > applying
> > > > > > > patches that look good so...
> > > > > > >
> > > > > > > Can you create a new patch that works off of tapestry
4.1trunk
> > ;)
> > > ?
> > > > > > >
> > > > > > > P.S. Something came over me and I think I found a pretty
easy
> > way
> > > to
> > > > > > make
> > > > > > > a
> > > > > > > small modification to OGNL that would make it possible to
> > > > definitively
> > > > > > > know
> > > > > > > a target properties type, even if it is null. The only
problem
> > is
> > > > that
> > > > > > > OGNL
> > > > > > > seems to be in the hands of opensymphony/webwork right now
and
> > > I've
> > > > > not
> > > > > > > seen
> > > > > > > much response to any forum posts I've written. Oh well...
> > > > > > >
> > > > > > > On 7/10/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I just wanted to send the list a quick heads up in view of
> our
> > > > > > previous
> > > > > > > > discussion: I've moved BeanForm to a separate SF project (
> > > > > > > > http://beanform.sourceforge.net/), uploaded it to Tassel,
> and
> > > have
> > > > > > > marked
> > > > > > > > the patch (
http://issues.apache.org/jira/browse/TAPESTRY-965
> )
> > > > > > obsolete.
> > > > > > > I
> > > > > > > > still think this would be a useful component to have in
> > Contrib,
> > > > and
> > > > > > can
> > > > > > > > create an updated patch at some point in the future.
> > > > > > > >
> > > > > > > > I think I've addressed all the issues raised in previous
> > > > discussions
> > > > > > on
> > > > > > > > this
> > > > > > > > list (see the docs at the website), but would be happy for
> any
> > > > > further
> > > > > > > > critique. This applies especially to the rendering
> hierarchy.
> > > > Thanks
> > > > > > for
> > > > > > > > all
> > > > > > > > the advice and direction given thus far.
> > > > > > > >
> > > > > > > > Take care,
> > > > > > > >
> > > > > > > > Daniel Gredler
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Jesse Kuhnert
> > > > > > > Tacos/Tapestry, team member/developer
> > > > > > >
> > > > > > > Open source based consulting work centered around
> > > > > > > dojo/tapestry/tacos/hivemind.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Jesse Kuhnert
> > > > > Tacos/Tapestry, team member/developer
> > > > >
> > > > > Open source based consulting work centered around
> > > > > dojo/tapestry/tacos/hivemind.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tacos/Tapestry, team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind.
> > >
> > >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.
>
>




--
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.

Reply via email to