remove o.a.l.cms.publishing?

["Gregor J. Rothfuss" <gr...@apache.org>]

it appears to me that the classes under o.a.l.cms.publishing are no 
longer needed with the usecase framework, and specifically the 
documentmanager.

we need to convert the blog to no longer use ant tasks for publishing, 
and we need to provide a static exporter replacement that uses the lenya 
api.

does that make sense?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org

Re: remove o.a.l.cms.publishing?

["Gregor J. Rothfuss" <gr...@apache.org>]

Andreas Hartmann wrote:

> Would someone like to collect the requirements for a static export service?

the simplest that could work would be to just export html / css to an 
export directory (while fixing the bugs reported against export)

the question how the static export arrives at the destination is 
related, but does not have to be solved at the same time (ie, shell 
scripts work fine)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org

Re: remove o.a.l.cms.publishing?

[Andreas Hartmann <an...@apache.org>]

Gregor J. Rothfuss wrote:
> it appears to me that the classes under o.a.l.cms.publishing are no 
> longer needed with the usecase framework, and specifically the 
> documentmanager.
> 
> we need to convert the blog to no longer use ant tasks for publishing, 
> and we need to provide a static exporter replacement that uses the lenya 
> api.
> 
> does that make sense?

+1

Would someone like to collect the requirements for a static export service?

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org