Hello list
some time ago I wrote that I would like to upload Scopes in the sandbox,
and I wrote about the problems with a LGPL-licensed library dependency.
Now that library has changed license to CPL:
http://htmlparser.sourceforge.net/license.html
In the sourceforge.net news it says:
http://sour
Licensing issues are not the least little bit off topic :)
I'm not sure if the policy is final yet, but under the latest proposed
draft I've found, a release can import CPL binaries, which I expect is
all that we would want in this case.
* http://people.apache.org/~cliffs/3party.html
-Ted.
On
Ted Husted ha scritto:
a release can import CPL binaries, which I expect is
all that we would want in this case.
Yes it is, thanks a lot! Anyway i'm still not ready to put it in the
sandbox, since I would like to clean Scopes a bit.
Ciao
Antonio
I'm receiving the following build failure/compile error in the most
recent s2 trunk. This occurs AFTER removing the xwork snapshot from my
local repo to force maven to grab the absolute latest.
/projects/open-source/struts2-clean/integration/src/main/java/org/apache/struts2/s1/ActionFormValid
On 9/25/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
I'm receiving the following build failure/compile error in the most
recent s2 trunk. This occurs AFTER removing the xwork snapshot from my
local repo to force maven to grab the absolute latest.
/projects/open-source/struts2-clean/integration
Hmmm.
I don't get any errors building core or api - just integration. I tried
to duplicate your error by rolling back versions of xwork, but I couldn't.
It looks to me like the ScopedModelDriven class was just checked in last
night (along with the scoped interceptor which was moved from s2 t
My bad - I hadn't checked in the xwork changes. Remove your xwork jar
from your local maven repository and try again. Wait an hour or so
after this message to allow the OpenSymphony CruiseControl system to
build and deploy the latest snapshot.
Don
Wendy Smoak wrote:
On 9/25/06, David H. De
Thanks! Worked like a charm from source.
David
Don Brown wrote:
My bad - I hadn't checked in the xwork changes. Remove your xwork jar
from your local maven repository and try again. Wait an hour or so
after this message to allow the OpenSymphony CruiseControl system to
build and deploy the
labelposition=left does not work (the label is always on the right).
Attached is a revision to template/css_xhtml/checkbox.ftl which fixes
this problem. http://www.nabble.com/file/148/checkbox.ftl checkbox.ftl
HTML BEFORE THE FIX:
I forgot to add the code that makes sure there are no slashes in the
actionId name.
First, should I only exclude slashes? Or should I only allow letters and
numbers?
Second, where should the checking go? I notice there is no pattern
checking in any of the Config classes; so this will be blaz
10 matches
Mail list logo