Thanks for the alert. We have all been getting this for some time.
Even worse, it makes itself appear to be sent by people we know and
trust. Even more worse, the "senders" then get hammered by recipients'
mail agents telling us that we have sent a virus. I hope that we don't
get blacklisted. Watch
[EMAIL PROTECTED] wrote:
> upayavira2003/07/01 22:03:52
>
> Added: src/documentation/xdocs/userdocs/concepts redirection.xml
> Log:
> Added docs on redirection
> Fixed typo in modules doc
>
> Please review this doc - it's my first, and I'd
> like to know I'm doing it right.
Welcome Reinhard, and thanks for the overview of you and your
excellent ambitions.
Reinhard Pötz wrote:
>
> Apart from Cocoon I'm on the way to become a Certified Transactional
> Analyst (this has nothing to do with IT as many people believe but
> more with psychology), ...
Then you might als
Upayavira wrote:
> [EMAIL PROTECTED] wrote:
>
> ...
> > Revert the previous revision. It is the concern of the stylesheets
> > to show the release status.
> ...
> > -
> > +
>
> Should this be @[EMAIL PROTECTED]
Absolutely. My mistake - thanks for spotting this. Fixed now.
--David
Carsten Ziegeler wrote:
> David Crossley wrote:
>
> > Anyway, what do you think of the other issue - the idea of getting rid
> > of Cocoon's validate-xdocs target?
>
> +1 if forrest does this for us it's ok
Okay, i will tidy that up in the next few days unless
Carsten Ziegeler wrote:
> David Crossley wrote:
>
> > We also do some specific validation of certain core configuration
> > using RELAX NG and the Jing task. This works fine for validating
> > the cocoon.roles file (note it has an internal DTD subset). We were
> >
On 2003-03-30, Geoff Howard wrote:
> Is there any strategy for making the xml fragments in
> src/targets well-formed so editors don't barf on them?
That sounds like a good idea and makes me itch.
What do you think needs to be done?
Is it just that the multiple elements need
to be wrapped in a c
Joerg Heinicke wrote:
> I validated the file using jEdit - I hope it did it correctly.
> 'validate-xdocs' does not work at the moment. From the messages
> yesterday I guess you know this, but here is the message:
Oh damn. I was sure that worked for me yesterday. I was obviously
mistaken becaus
Steven Noels wrote:
> David Crossley wrote:
>
> > We need to add a section that says how/when a sub-project is deemed
> > ready to leave incubation.
>
> Gee. That sounds as untangible as the criteria upon which proposals are
> judged before they can actually go int
Carsten Ziegeler wrote:
> David Crossley wrote:
> >
> > Why do we need DTDs to be included here? If they need to be in Cocoon
> > CVS, then shouldn't they be in WEB-INF/entities.
> >
> The validate-xdocs task validates all our documents and uses the
> DTD
Carsten Ziegeler wrote:
> David Crossley wrote:
> >
> > Why do we need DTDs to be included here? If they need to be in Cocoon
> > CVS, then shouldn't they be in WEB-INF/entities.
>
> The validate-xdocs task validates all our documents and uses the
> DTDs from
Stefano Mazzocchi wrote:
> David Crossley wrote:
>
> > I think that we need a document that clearly explains what it
> > means to be a "Cocoon sub-project under incubation".
> >
> > This would go at the top-level of the cocoon website and help to
>
[EMAIL PROTECTED] wrote:
> cziegeler2003/06/25 06:33:25
>
> Modified:src/targets docs-build.xml
>src/documentation/xdocs/developing/portal index.xml
> Added: src/documentation/xdocs/dtd document-v11.dtd
> document-v12.mod ISOnum.pen ISOtech
Welcome Reinhard.
As you know the new account has been established.
The next step is to sign and send in the Contributors License
Agreement (CLA). Then set up your CVS access over SSH and put
a ~/.forward file at your cvs.apache.org home directory to
forward your @apache.org email.
There are some
Jeff Turner wrote:
> As most of you probably saw, there's a thread on cocoon-dev suggesting
> that Forrest ought to be a Cocoon subproject, with the consensus being it
> "makes sense".
>
> AFAICT the only practical difference would be that Cocoon committers
> would automatically become Forrest com
Gianugo Rabellino wrote:
>
>
> ...Anyway, given that you are the only one showing some
> interest, I'm starting to think that I'm just being paranoid...
No, you are definitely not. All the issues that you and Christopher
are attending to are extremely important. I, for one, do not think that
i c
Stefano Mazzocchi wrote:
> David Crossley wrote:
> > David Crossley wrote:
> >
> >>I propose Reinhard Pötz to be a Cocoon committer.
> >
> >
> > The summary so far is 21 positive votes and no negative votes.
> >
> > Is there an official
Gianugo Rabellino wrote:
> Joerg Heinicke wrote:
>
> >> Hmmm, if this is the case, that even Forrest committers has to have this
> >> kind of right.
> >
> > [RT] Why Forrest is not/does not become a subproject of Cocoon while
> > it's so heavily based on it?
>
> Definitely something to consider
Carsten Ziegeler wrote:
> David Crossley wrote:
> >
> > Geoff and i both asked that question the last time this issue arose,
> > Asking Pier if he was sure that there were no side effects. Pier
> > answered with a flat "Yes" :-)
> > http://marc.theaimsgr
Carsten Ziegeler wrote:
> Bertrand Delacretaz wrote:
> > Do you plan a document explaining the move and how to find the old and
> > new archives?
> >
> No :( - to be honest, I haven't thought about the archives. I thought
> that the archives would be somehow moved as well. Hmm, does anyone
> know
David Crossley wrote:
> I propose Reinhard Pötz to be a Cocoon committer.
The summary so far is 21 positive votes and no negative votes.
Is there an official duration that i have to wait before asking
root to set up the account? It has been about 2.5 days so far.
I want to do it ASAP, but do
Gururaja H wrote:
>
> I am having problem installing cocoon 2.0.4 on Tomcat 4.1.18
> on Windows 2000(on Sun J2SDK 1.3.1_08. I have down loaded the
> prebuilt library and
> copied the cocoon.war to %CATALINA%\webapps directory.
> When I start the Tomcat I get the following message:
>
Please ask s
Thanks Joerg for the excellent work with the Directory generator.
I notice that you tidied up the documentation, but only in the
2.0 branch. Should i add that same stuff to the 2.1 docs?
--David
I think that we need a document that clearly explains what it
means to be a "Cocoon sub-project under incubation".
This would go at the top-level of the cocoon website and help to
explain the mysterious statements on the Cocoon and Lenya home pages.
--David
I propose Reinhard Pötz to be a Cocoon committer.
Reinhard has been active on cocoon-dev since mid-2001, helping
with many useful things, such as: defining the Flow Object Model,
conceptualising and testing the Web3 (SAP) connectivity framework,
defining issues with forms frameworks, excellent Wik
Stefano Mazzocchi wrote:
> It is with real pleasure that I announce that three cocoon committers
> were elected members of the ASF in the last round of votation that ended
> today.
>
> Vadim, Sylvain and Carsten (in alphabetical order by their last names)
>
> Hoping that they will accept the inv
[EMAIL PROTECTED] wrote:
> stevenn 2003/06/19 02:28:17
>
> Modified:src/blocks/linotype/samples flow.js
> Log:
> Did I woke up today? Re-adding bugfix that I nuked by reverting.
Oh damn, you lost your toothbrush (or it became worn out).
Come back to Forrest and we will give you anot
[EMAIL PROTECTED] wrote:
> joerg 2003/05/30 19:06:10
>
> Modified:src/documentation/xdocs/userdocs/generators book.xml
>src/documentation/xdocs/userdocs/transformers book.xml
> Log:
> hmm, the menu must be maintained by hand ...
Yes, one day we will get around to u
Jeff Turner wrote:
> David Crossley wrote:
> > With current head cvs of both Cocoon-2.1 and Forrest
> > i cannot build Cocoon docs.
>
> Seems that sitemap compatibility was broken when Forrest
> upgraded to M2. I've updated src/documentation/sitemap.xmap
> an
With current head cvs of both Cocoon-2.1 and Forrest
i cannot build Cocoon docs. Does anyone else have these
troubles or know what they mean?
I also tried the "stable" tagged Forrest, but different error.
* [0]
-> [broken page] index.htmlnull <-
Thanks Tony, for all the excellent contributions that you
have made while you have been with us. Hope to see you back
again sometime. You are not alone with the "burn-out" issue.
Wishing you all the best.
--David
Tony Collen wrote:
> Hi everybody,
>
> I've decided to unplug for a while. I'm in t
The announcement.xml file was including the file changes.xml
So now the announcement is busted. We could get it to use
the new status.xml instead. However ...
Do we really want to dump the whole release notes out with
an announcement? There may be too many when 2.1 is announced.
There are about 21
One more microstep for Forrest ...
Please use status.xml for the changes and todo items.
--David
ivelin wrote:
> Steven Noels wrote:
>
> > Exactly. Then again, Ivelin is looking into making XMLForm
> > independent from Cocoon IIUC from the freebuilder CVS.
> > I don't know whether a branch
> > would liberate him sufficiently enough (which is if course
> > not our concern).
>
> The goal is to
ivelin wrote:
>
(And why did he not make any attempt to attribute who said what?)
>
> Someone said:
> > I am sure goodwill is a main reason but some question come to my mind
> >
> > *) why don't you wanna share your thoughts with us and let us
> >(or at least some of us) together steer the dir
Upayavira wrote:
> I am working on the CLI. I currently get an error when running
> it in Idea (which worked fine before): 'no protocol: characters.ent'.
> It would appear to be something
> wrong with entity resolving. However, it works when I run it from
> the docs target.
> Can anyone tell me h
Geoff Howard wrote:
> Vadim wrote:
> >Geoff Howard wrote:
> >>Vadim wrote:
> >>>Geoff Howard wrote:
> ### wrote:
> >Unfortunately, when validate-jars was put back in, an override mechanism
> >wasn't added so you're stuck manually editing the build file for now.
> >
> >I'll be
Steven Noels wrote:
> David Crossley wrote:
> >
> > I think that the murkiness is a result of not having
> > a proposal and subsequent discussion before calling
> > a vote.
>
> Hm. Could be, although this particular subject has been discussed,
> semi-proposed
Many thanks for setting those up so quickly.
Andrew and Geoff, please see the following URLs for
some background info for new committers:
http://www.apache.org/dev/committers.html
http://incubator.apache.org/drafts/
There are also various "cvs over ssh" guidelines on
those pages and here is anothe
Hello root, please add accounts for these two new
Cocoon committers.
They need availability for all Cocoon CVSs. In the
past, Cocoon committers also had access to xml-site
and xml-commons - not sure what the situation is now
that Cocoon is a top-level project.
Stefano Mazzocchi wrote:
> Stephan Michels wrote:
> > Stefano Mazzocchi wrote:
>
> So, at the end, here is what I propose:
>
> 1) we remove all the old docs targets from the build
To remove the "build docs" target, i agree.
To remove the webapp docs generation, i do not agree.
> 2) documentatio
Steven Noels wrote:
>
> Yep, this is quite some murky vote, and some tallying indeed does help.
I think that the murkiness is a result of not having
a proposal and subsequent discussion before calling
a vote.
--David
Jeremy Quinn wrote:
> David Crossley wrote:
>
> > Jeremy Quinn wrote:
> >
> >> OK
> >>
> >> This still fails:
> >>
> >>http://localhost:/samples/catalog/sdocbook-demo
> >>
> >> org.apache.cocoon.Pro
Stefano Mazzocchi wrote:
> [EMAIL PROTECTED] wrote:
> >
> > Modified: src/documentation/xdocs/userdocs/flow
> > invalidContinuation.xml
> > Log:
> > * Fixing build (file fails validation)
> -
> +
>
> ok, damn, forgot to remove that sorry.
>
> Stefano.
Are you guys saying
Stefano Mazzocchi wrote:
> Pier Fumagalli wrote:
> >
> > Folks, do you know that there's the possibility to alias certain subparts of
> > a particular CVS repository from another repository?
> >
> > Like "cocoon-2.1/src/docs" can be stored in the "cocoon-docs" repository.
> >
> > Apache does i
Stefano Mazzocchi wrote:
> This said, here are the actions you should vote:
>
> 1) cocoon moves to forrest for its documentation production
+1
> 2) if so, cocoon does it before releasing 2.1
+1
> 3) if so, I'd like a 'fast-yet-potentially-disruptive' move rather
> than a 'slow-yet-car
his commitment to Cocoon.
Becoming a committer will allow him to contribute
more effectively to Cocoon.
Here is my +1
--David Crossley
Jeremy Quinn wrote:
> OK
>
> This still fails:
>
> http://localhost:/samples/catalog/sdocbook-demo
>
> org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
> java.io.FileNotFoundException:
> /Users/jermq/Checkouts/Secure/cocoon-2.1/build/webapp/samples/catalog/
> s
and has
already contributed in various ways.
Becoming a committer will allow him to contribute more effectively
to Cocoon.
Here is my obvious +1
--David Crossley
oon-dev&m=104619931816392&w=2
> "never commit code that depends on non-released stuff"
> and I'm just pointing out that we are doing that here.
Ah, i understand you now.
Dianna Shannon wrote:
> > Stefano Mazzocchi wrote:
> David Crossley wrote:
> >
Stefano Mazzocchi wrote:
> Diana Shannon wrote:
> > Stefano Mazzocchi wrote:
> >> Diana Shannon wrote:
> >>
> >>> Perhaps it's just the nature of open source software, that a
> >>> tremendous amount of energy is unleashed right before a release date.
Actually i do not think that there is a "relea
Jeff Turner wrote:
> Stephan Michels wrote:
> ...
> > No, I mean not ignoring for the validation, I mean ignoring for the
> > documentation generation process.
>
> Yes, should be possible by defining 'project.sitemap-dir' to point to
> somewhere without any *.xmap files, and simultaneously definin
Stefano Mazzocchi wrote:
> I usually don't read weblogs. But today I found this
> I'm going to tell you what I think and what are my feelings.
>
> Hopefully this is going to be the tornado that will clear the skies
> again. If not, well, at least I tried.
Thanks for doing this. The air does ne
I have resurrected the lost Lucene sample
and put it into its block.
It does still need some attention. I cannot get
the view-file links at the top to work.
--David
Torsten Curdt wrote:
> Hurray!
>
> By using composition rather than inherritance I removed the
> the dependency to the jvm. No split code anymore :)
>
> Thanks for pointing me on that Berin.
>
> Everything *should* work as before. And at least on
> my machine the samples are working.
>
> Please
Bertrand Delacretaz wrote:
> David Crossley a écrit :
>
> > ...There are two samples at
> > http://localhost:/samples/catalog/welcome
> >
>
> Hi David,
>
> catalog-demo works fine here (mac osx 10.2.3, JDK 1.4.1_01) as far as I
> can tell: all five en
We have had the conversation buried under an obscure thread name.
Re: Finishing Deprecation Package
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104763803628330
Would people please report whether the Catalog Entity Resolver
samples work for them. There are two samples at
http://localhost:888
Hi Vadim, many thanks to you for fixing the "build test".
--David
I went to try to resurrect the Lucene search sample today.
However, i cannot find it anywhere in CVS. Was it deliberately
removed or this is an accidental victim of the refactoring?
--David
Carsten Ziegeler wrote:
>
> For 2.1 we have some additional points in our todo list in cvs
> that have to be solved before a final release.
There is also the document at:
http://xml.apache.org/cocoon/plan/release.html
Version 2.1 Beta 1
* apply patches
* test flowmap + do
Stefano Mazzocchi wrote:
> David Crossley wrote:
> > Found it - there is extra whitespace at the end of these
> > three lines in block.properties, i.e. after the =true
> >
> > Thank the lord, i am not going mad. Sounds like we
> > need normalize-space() whenever
David Crossley wrote:
> David Crossley wrote:
> > Stefano Mazzocchi wrote:
> >
> > > try to do a clean checkout, maybe there is something wrong in
> > > your local CVS metadata.
> > >
> > > ah, no, wait, what settings are you using for cvs
David Crossley wrote:
> Stefano Mazzocchi wrote:
>
> > try to do a clean checkout, maybe there is something wrong in
> > your local CVS metadata.
> >
> > ah, no, wait, what settings are you using for cvs update?
>
> cvs -q -z3 update -d -P cocoon-2.1
Stefano Mazzocchi wrote:
> I would like to see Cocoon released as soon as possible, but not sooner.
>
> Anything else I've missed?
*) Ensure that the new entity resolver works on all platforms.
We need people to test this on all platforms.
http://marc.theaimsgroup.com/?t=10473692462
*) Fix
Stefano Mazzocchi wrote:
> try to do a clean checkout, maybe there is something wrong in
> your local CVS metadata.
>
> ah, no, wait, what settings are you using for cvs update?
cvs -q -z3 update -d -P cocoon-2.1
Okay, i will try the full clean checkout.
--David
Bernhard Huber wrote:
> David Crossley wrote:
> >Today one of the blocks is broken. I tried to get around
> >it as usual by un-commenting the line in local.blocks.properties
> >to no avail.
>
> i made a CVS update, and had no problem running "build we
Diana Shannon wrote:
> David Crossley wrote:
>
> > However, this raises an issue. I presume that considering
> > Cocoon is now a top-level project, that all reference to
> > the Cocoon project should be removed from xml.apache.org
> >
> > That will be tr
About 4 days ago the build was changed to differently
handle the way blocks are excluded. Now it looks like
those properties are ignored.
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
Would people please test
Andrew Savory wrote:
>
> Not sure quite where to send this, but I'm sure someone on
> this list can deal with it ;-)
>
> http://xml.apache.org/cvs.html is referring to the old
> xml-cocoon and xml-cocoon2 repositories.
Thanks for spotting this Andrew, and yes cocoon-dev is
the right place. I have
David Crossley wrote:
> Carsten Ziegeler wrote:
> >
>
> > Ok, done (I hope) - I changed the implementation and the cocoon.xconf.
> > How can we test it to ensure that it works correctly?
>
> The main way is via the samples/catalog/
> (top Samples page => C
Carsten Ziegeler wrote:
>
> Ok, done (I hope) - I changed the implementation and the cocoon.xconf.
> How can we test it to ensure that it works correctly?
The main way is via the samples/catalog/
(top Samples page => Catalog Entity Resolver)
Try the first sample to ensure that default config
is
Carsten Ziegeler wrote:
> David Crossley wrote:
> > Carsten Ziegeler wrote:
> > > I just fixed some bugs in the catalog resolving code; as far
> > > as I can tell everything is working fine. If you experience
> > > problems, just let me know.
> >
> &g
Carsten Ziegeler wrote:
> I just fixed some bugs in the catalog resolving code; as far
> as I can tell everything is working fine. If you experience
> problems, just let me know.
Most bits seem to be working again, e.g. main Cocoon documentation.
I also resurrected the 'catalog-demo' sample and th
Carsten Ziegeler wrote:
> Hi David,
>
> I just fixed some bugs in the catalog resolving code; as far
> as I can tell everything is working fine. If you experience
> problems, just let me know.
Thanks, our emails crossed in mid-air :-)
I will look into it tomorrow.
--David
Carsten Ziegeler wrote:
> David Crossley wrote:
> > Carsten Ziegeler wrote:
> > >
> > >
> > > org.apache.cocoon.components.resolver.ResolverImpl has
> > > to be changed to use the new Resolver from the excalibur
> > > xmlutil package.
&
On Tue, 2003-03-11 Carsten Ziegeler wrote:
> As I will not do it this week, here is a list of
> things that have to be done to get the deprecation
> package working. If someone wants to do it, I will
> be very happy - otherwise I will perhaps do it
> next week.
>
> The XScriptObject must be change
Carsten Ziegeler wrote:
> David Crossley wrote:
> >
> > Why in the "init"? ... because it should fail straight away
> > if there are problems with the main config. Should that be
> > moved to another early build target?
> >
> The problem with "
[EMAIL PROTECTED] wrote:
> cziegeler2003/03/04 08:34:35
>
> Modified:.build.xml
> Log:
> Making cocoon at least buildable;
Thanks. Actually, validation did work when i committed it.
Erk, i see what the problem was - i forgot to commit
the "any.rng" grammar ... sloppy, sorry.
Steven Noels wrote:
> David Crossley wrote:
>
> > The used to have children like
> > etc. but these have been recently
> > changed to etc. However,
> > the sitemap.rng still has the former. Also, the code in
> > o.a.c.transformation.TraxTransformer still
I started to bring back some of the stuff from the
old build.xml that conducted validation of the
important configuration files.
However, i needed to comment-out the sitemap validation
because some recent changes to webapp/sitemap.xmap
cause errors.
The used to have children like
etc. but these
Morrison, John wrote:
> [EMAIL PROTECTED] seems to be doing an awful lot of
> coding atm, his patches look good and I can't see why he
> shouldn't be allowed to commit them himself!
>
> Votes...?
+1
--David
Nicola Ken Barozzi wrote:
>
> I'm asking the Cocoon PMC to vote for the inclusion of the below
> proposed project named Lenya (ex wyona.org) as a Cocoon subproject.
>
> This vote will take place on cocoon-dev where the Cocoon PMC lives.
> I'm CCing the incubator list just to notify that we're st
Antonio Gallardo wrote:
> David Crossley dijo:
> > Antonio Gallardo wrote:
> >
> >> Sorry, but I have another problem (see below).
> >
> > Thanks Antonio, i just fixed the broken xml comments
> > in cocoon.xconf ... so now you can proceed with
> >
Antonio Gallardo wrote:
> Sorry, but I have another problem (see below).
Thanks Antonio, i just fixed the broken xml comments
in cocoon.xconf ... so now you can proceed with
testing the new build system.
It finally compiles the webapp, so i am off to do
'build run'.
--David
Stephan Michels wrote:
> David Crossley wrote:
> > On a related issue ... you will notice in the
> > chaperon/samples/sitemap.xmap that i needed to use
> > the previously generated quote.xlex and quote.xgrm
> > I tried to instead use the "cocoon:" protocol
Steven Noels wrote:
>
> Sure, David - fully aware of that. My 'big hidden agenda' (duh) was to
> add a first step to the main cocoon build, so that others could jump in
> and expand. ...
Moving this part of the discussion over to cocoon-docs:
Re: [PROPOSAL] Use Forrest to build Cocoon docs
htt
Changing thread name for this new subject. Was:
Re: closing cocoon-docs? (was: Cocoon Project Report)
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104557472909525
Diana Shannon wrote:
> Steven Noels wrote:
> >
> > On the subject of a separate CVS repository & getting rid
> > of branches for
Martin Holz wrote:
> David Crossley writes:
>
> > Thanks Stephan for fixing my attempt to develop a basic
> > Chaperon sample. That is much better.
> >
> > I noticed that you also changed the pipeline for
> > generating the *.xlex and *.xgrm to be "
Steven Noels wrote:
> Sylvain Wallez wrote:
> >David Crossley wrote:
> >> Actually, the cocoon-docs list has had pathetic uptake.
> >> Is that because people are leaving documentation to be done
> >> by the mysterious "other people"?
> >>
Nicola Ken Barozzi wrote:
> Bertrand Delacretaz wrote:
> > Sylvain Wallez a écrit :
> >
> >> ...
> >> So what about closing cocoon-docs ? This would avoid believing some
> >> mysterious entities are writing the docs for us...
> >
> > I'd give a reluctant +1 to this proposal.
>
> I'd give a sure
Thanks Stephan for fixing my attempt to develop a basic
Chaperon sample. That is much better.
I noticed that you also changed the pipeline for
generating the *.xlex and *.xgrm to be "internal-only".
As i said in the Sourceforge posting, this was actually
a useful tool for helping to develop the g
Stefano Mazzocchi wrote:
> We are also planning to start using Forrest to build our own
> documentation, even if this will make it a circular dependency (cocoon
> depends on forrest and forrest depends on cocoon). But this is something
> the cocoon documentation team will decide with the forres
Niclas Hedhman wrote:
>
> I am probably an idiot, so bare with me
>
> If I check out
> cvs co xml-cocoon2
>
> I THINK I get ver 2.1, since there is cocoon_2_0_3 branch.
>
> Is that so? The head is the latest stuff and older revisions are branched?
That is correct.
By default you will get H
Nicola Ken Barozzi wrote:
> Niclas Hedhman wrote:
> > Just wondering about the Apache Forrest project NAME.
>
> http://xml.apache.org/forrest
> http://jakarta.apache.org/gump
Do you need more clues yet Niclas?
This could become an FAQ.
--David
-
Pier Fumagalli wrote:
> As I've just done it for axis-dev, should we move the cocoon mailing lists
> from cocoon-(dev|user)@xml.apache.org to (dev|user)@cocoon.apache.org ???
>
> It can be done transparently, so, without loosing the archive, the
> subscribers and stuff, but as we got the top level
Thanks, i added your changes to CVS. Please be aware that
there has not been much activity with that W3C Schema for
Cocoon Sitemap. The last changes were about 7 months ago.
In the meantime there has been various work with the
RELAX NG grammar at WEB_INF/entities/sitemap-v06.rng
The two grammars ma
Torsten Curdt wrote:
> Sylvain Wallez wrote:
> > Pier Fumagalli wrote:
> >
> >> Folks, cocoon.apache.org LIVES! :-)
>
> Cool! I am excited! :))
>
> What about setting up cocoon.apache.org with forrest?
Then please bring your excitement and energy to the
cocoon-docs mail list and
http://wiki.coc
[EMAIL PROTECTED] wrote:
> Pier Fumagalli wrote:
> > Sylvain Wallez wrote:
> >...
> >> Cool ! But why does this legal speech have be so hard to understand ?
> >
> > Unfortunately, the Apache Software Foundation is a legal corporation,
> > and therefore, for all its official proceedings, we need to
Bernhard Huber wrote:
> SAXESS - Hussayn Dabbous wrote:
> > I wonder, why the Catalog.properties must reside
> > in the classes directory. For me it would be
> > more natural to put it either into WEB-INF, or
> > WEB-INF/conf instead.
> >
> com.sun.resolver.CatalogManager reads this property file
Bernhard Huber wrote:
> hi, thanks for the response,
> for me hello.jpg is working, too.
> perhaps i have not explained it correctly, but the samples/welcom-svg
> page does not work for me,
> more exactly all svg images using not
> http://www.w3.org/2000/svg";
> are working fine.
>
> so does
1 - 100 of 482 matches
Mail list logo
