I thought Sakai had switched to ECL 2.0. It turns out Sakai Board has
decided we *will* switch to ECL 2.0 but it is not yet implemented. Any
Sakai contribution can be released using ECL 2.0 while the licensing
machine grinds fine and of course the authors can release their work
themselves under whatever additional license(s) they like.
John
On 8 Apr 2008, at 13:09, Ian Boston wrote:
Vincent,
your right, sorry, *if* (in the unlikely event that) anyone wants it,
I will relicense it as ECL2 of AL2 (after checking with all the
copyright holders.... there have been some patches from one person)
However, its not that hard to recreate and the ideas are almost
certainly out in the public.
Ian
On 8 Apr 2008, at 12:22, Vincent Siveton wrote:
Hi Ian,
Happy to see you there :)
2008/4/6, Ian Boston <[EMAIL PROTECTED]>:
[SNIP]
The license on all of this is Educational Community License which is
compatible with A2, so you could just take it if you wanted or
look at it
I am not a Lawyer but Sakai is distributed under ECL1 [1], *not* ECL2
(which is AL2 compatible).
Cheers,
Vincent
[1]
http://sakaiproject.org/index.php?option=com_content&task=view&id=132&Itemid=261
[2] http://www.opensource.org/licenses/ecl2.php
and take the ideas...its very simple and extends the basic maven-
war-plugin.
There is also something very similar in the deployment plugin
used by
Apache Pluto.
but this is just the way I have done it... officially, maven is
not really
targeted at deployment to app servers.
Ian
On 6 Apr 2008, at 13:10, Alejandro Rivero wrote:
2008/4/6 Santiago Gala <[EMAIL PROTECTED]>:
Doh! forget it. I needed to do mvn *install* (which actually
does not
install anything) to copy them to the hidden storage under my
home.
Now I mention it, I whould thank to know some maven magic for this,
non for cp but for scp.
Point is, we installed all the shindig in a server machine, and our
people are more of php/py/etc than of java. As it happens,
Eclipse can
do remote debug of a maven-jetty conumdrum without needing any new
plug-in beyond the default "java project" mode, but we need to do
an
"mvn package" and scopy the xxx-source.jar file into Eclipse scope.
Some instructions for debug could actually do a pair of lines in
the
README, after the hint of mnv jetty:run-war.
Alejandro