Juan Jose Pablos wrote:
It was setup like that so you do not need to copy images accross. I
think that it was used just for the skin. If we move already the skin
out (under /skin) then we should put them within the content directory
as they are conten as well.
OK so unless anybody objects,
Ferdinand Soethe wrote:
Juan Jose Pablos wrote:
It was setup like that so you do not need to copy images accross. I
think that it was used just for the skin. If we move already the skin
out (under /skin) then we should put them within the content directory
as they are conten as well.
OK so
Can you remind us what the thread was about, preferably by summarising
the outstanding issues, or if that is too much work by providing a link
to the archives.
This is the original thread:
http://marc.theaimsgroup.com/?t=11017215271r=1w=2
with this being the original idea
Currently
David Crossley wrote:
So if someone can change the build system so that this file
gets picked up by Java from a different location, then fine.
Yeah, I saw that. But I understood Nicola saying someplace else hat
could be done? Can it? Who knows what is needed?
--
Ferdinand Soethe
On Wed, 2005-05-11 at 09:07 +0200, Ferdinand Soethe wrote:
Can you remind us what the thread was about, preferably by summarising
the outstanding issues, or if that is too much work by providing a link
to the archives.
This is the original thread:
forrest.properties to become forrest-properties.xml
-1
forrest.properties should become forrest.xml like Nicola suggested
because it is the main configuration file for forrest like maven.xml for
maven. ;-)
I can't see this as such a good reason to do it the same.
In my view:
If more
Ferdinand Soethe wrote:
I think we should keep build/ as top-level because that is most common
in cocoon related projects. Everything that you now describe is part of
some kind of build.
I will make this point one last time and then keep quiet about it.
I'd rather you didn't keep quiet. Your
Ferdinand Soethe wrote:
forrest.properties to become forrest-properties.xml
-1
forrest.properties should become forrest.xml like Nicola suggested
because it is the main configuration file for forrest like maven.xml for
maven. ;-)
I can't see this as such a good reason to do it the same.
In my
What happened to the outcome of this thread? Will 0.7 have the change
in directory structure, is it postponed till 0.8 or did it die
somewhere along the road?
I'd be very interested to reduce the path to xdocs and remove the
one level layer difference between xdocs and content soon.
What can I
Ferdinand Soethe wrote:
What happened to the outcome of this thread? Will 0.7 have the change
in directory structure, is it postponed till 0.8 or did it die
somewhere along the road?
I'd be very interested to reduce the path to xdocs and remove the
one level layer difference between xdocs and
Ferdinand Soethe wrote:
What happened to the outcome of this thread? Will 0.7 have the change
in directory structure, is it postponed till 0.8 or did it die
somewhere along the road?
I'd be very interested to reduce the path to xdocs and remove the
one level layer difference between xdocs
Ferdinand Soethe wrote:
Hi Nicola,
NKB Yes, I'm the initial author of that task :-)
So is it agreed to implement the new structure like this:
my-project/
conf/
forrest.properties
skinconf.xml
site.xml
tabs.xml
content/
Hi Nicola,
NKB Yes, I'm the initial author of that task :-)
So is it agreed to implement the new structure like this:
my-project/
conf/
forrest.properties
skinconf.xml
site.xml
tabs.xml
content/
13 matches
Mail list logo
