On Sunday 21 August 2005 10:11 pm, David Crossley wrote:
We cannot create a dependency on an LGPL library.
The terms go beyond those of the Apache License.
Forrest doesn't need to depend on JRat. Its only a tool for profiling. Is
there no provision for including optional code under a different
Tim Williams wrote:
This is essentially what I was hoping the Developers Guide would
eventually be.
Tim refers to site-author/content/xdocs/developer-guide.xml
We talked a while ago about providing such documentation
and today we both added our partially finished work.
So now there is
Diwaker Gupta wrote:
David Crossley wrote:
We cannot create a dependency on an LGPL library.
The terms go beyond those of the Apache License.
Forrest doesn't need to depend on JRat. Its only a tool for profiling. Is
there no provision for including optional code under a different
On 8/17/05, David Crossley [EMAIL PROTECTED] wrote:
Tim Williams wrote:
Ross Gardler wrote:
David Crossley wrote:
However there are two potential problems there:
What if the new person refused to submit the CLA?
I cannot see why - it doesn't take away any of
their
Hi devs,
last time I called the vote was because we discussed the same issue with
a slightly different outcome. Anyway, we ended the last vote with a new
proposal:
1 - seed-simple (basic site with minimal content, ideal for starting
your own site)
- I would prefer seed-basic.
2 -
Tim Williams wrote:
David Crossley wrote:
Tim Williams wrote:
This is essentially what I was hoping the Developers Guide would
eventually be.
Tim refers to site-author/content/xdocs/developer-guide.xml
We talked a while ago about providing such documentation
and today we both
Thorsten Scherler wrote:
Another thing is that lenya 1.4.x brings publication templating through
the usecase-fw (framework). That means that through a webinterface you
can invoke the seeding of new publications. In general the usecase-fw is
a very interesting component of lenya. IMO forrest
On 8/22/05, David Crossley [EMAIL PROTECTED] wrote:
Diwaker Gupta wrote:
So here's what I have right now:
o I can do a simple ./build.sh jar.debug -- this creates a debug version
of
Forrest. When you next run Forrest, the data will be automatically logged.
Where and how and what to
David Crossley wrote:
... snip ...
This is actually not correct. The editor needs to not touch whitespace at
all (unless to format new files). Existing whitespace needs to be left as-is
otherwise there will be complex diffs when the devloper contributes a patch.
We need to gradually cleanup
Ability to edit properties in Site.xml and tabs.xml editors
---
Key: FOR-641
URL: http://issues.apache.org/jira/browse/FOR-641
Project: Forrest
Type: New Feature
Components: Tool: Eclipse config
sorry for late responding to your questions! was busy
[Note I am confused about this publication-sitemap.xmap file. Does
publication in its title mean the publication of documents, or is it
the publication that make up a Lenya site? I suspect it is the later
very confusing!]
I agree it is a
Thorsten Scherler wrote:
On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Author: thorsten
Date: Thu Aug 18 17:44:00 2005
New Revision: 233401
...
Added:
David Crossley wrote:
Ross Gardler wrote:
I've not thought through the implications of this. I'm pretty sure that
moving tools out is a good idea (notice I suggest a tools subdirectory
when moving eclipse, that was for a reason ;-) feel free to rubbish the
idea though (or even agree with it
Anil Ramnanan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-636?page=all ]
Anil Ramnanan updated FOR-636:
--
Attachment: org.apache.forrest.repository.200805.zip
This splits the repository browser into two plugins. One plugin contains code
Anil Ramnanan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-636?page=all ]
Anil Ramnanan updated FOR-636:
--
Attachment: org.apache.forrest.repository.200805.zip
This splits the repository browser into two plugins. One plugin contains code
Anil Ramnanan wrote:
With creative commons licences it is extremely important to take a
close look at the license options as there are a variety of different
flavours that are explained very well at their website
http://creativecommons.org/.
Share Alike. If you alter, transform, or build upon
On 8/22/05, Ross Gardler [EMAIL PROTECTED] wrote:
Thorsten Scherler wrote:
On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Author: thorsten
Date: Thu Aug 18 17:44:00 2005
New Revision: 233401
...
Added:
forrest -projecthelp does not work when run from the root folder of Windows.
-
Key: FOR-642
URL: http://issues.apache.org/jira/browse/FOR-642
Project: Forrest
Type: Bug
Components: Launch
On Mon, 2005-08-22 at 18:13 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Author: thorsten
Date: Thu Aug 18 17:44:00 2005
New Revision: 233401
...
Added:
Ferdinand Soethe wrote:
If the share alike option is selected then this license is probably
not compatible with the Apache License.
There's a pretty good comparison of important open source licences at
http://www.unt.edu/benchmarks/archives/2003/august03/copyright.htm.
--
Ferdinand
On Mon, 2005-08-22 at 16:29 -0400, Tim Williams wrote:
Assuming I understand what this is doing, I don't immediately see why
this couldn't be done with either the locationmap or a
ResourceExistsSelector in the sitemap itself.
We had the ResourceExistsSelector in the views sitemaps (and some
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
I've not thought through the implications of this. I'm pretty sure that
moving tools out is a good idea (notice I suggest a tools subdirectory
when moving eclipse, that was for a reason ;-) feel free to rubbish the
idea
Anil Ramnanan wrote:
David Crossley wrote:
It depends. The main thing is that we cannot add anything
that has retrictions beyond the terms of the Apache License.
Please direct us to an example of something that you want
to include and to their license conditions.
Here is an example of
Ferdinand Soethe wrote:
There's a pretty good comparison of important open source licences at
http://www.unt.edu/benchmarks/archives/2003/august03/copyright.htm.
Careful, that is old and only addresses the previous
version of the Apache License.
-David
Ferdinand Soethe wrote:
With creative commons licences it is extremely important to take a
close look at the license options as there are a variety of different
flavours that are explained very well at their website
http://creativecommons.org/.
Anil Ramnanan wrote:
Share Alike. If you
[
http://issues.apache.org/jira/browse/FOR-641?page=comments#action_12319673 ]
David Crossley commented on FOR-641:
Applied patch.220508.diff (15 kb)
There were some minor troubles because your svn client seems to include your
local pathnames in the
I am going to use this example to help explain some
of the problems with line-endings.
Ross, svn log shows that you added the initial
MANIFEST.MF file.
It already had mixed line endings. (By the way,
that makes me wonder about the origin of the code.)
If Ross' svn client was configured to
David Crossley wrote:
The dos2unix stuff is discussed:
http://cocoon.apache.org/community/committer.html
http://www.apache.org/dev/version-control.html#https-svn
http://svnbook.red-bean.com/en/1.0/ch07s02.html (svn:eol-style)
And http://marc.theaimsgroup.com/?l=forrest-devm=112476910519010
Addi wrote:
I am willing to help with the cleanup. I don't know what the best way
to organize and execute is though. Could I just post to the list that I
am cleaning xyz dir today and please don't do any commits.
It is more than just no commits. Also needs no developers
to be doing any
29 matches
Mail list logo
