To clarify what I meant, here [1] is a quick mockup. It's far from complete just so that you get the
idea...
Uli
[1] http://uli.spielviel.de/~uli/tapestry_site_layout.png
On 25.03.2010 19:37, Ulrich Stärk wrote:
I agree with you Andreas. My idea was that we'd have some replacement
for tapestry-site backed up by some sort of content management system or
something that makes editing easy (e.g. a confluence wiki export) as a
staging site and link to the documentation from there, with the latest
release being the default and additional links for older documentation.
See for example the CXF website. I believe that decoupling the site from
the documentation is a good thing because that way we can easily ship
the documentation (and the documentation only, without the rest of the
site) with our builds.
Each version's documentation would still be generated by maven (or
whatever tool we will use for documentation in the future) and deployed
to the correct location under the main page. That way we'd also get rid
of the problem we'd get by simply merging tapestry-site with
tapestry-project with respect to new releases.
So no, I'm against simply merging tapestry-site with tapestry-project.
Uli
On 25.03.2010 18:51, Andreas Andreou wrote:
ok - my idea was that we'd be going for something like this:
- every version deploys to its own folder, i.e. /tapestry5.1
/tapestry5.0, e.t.c.
upon release + there's no separate 5.0.11 vs 5.0.12 folders
- snapshots deploy every now and then (from CI machines) to similar
folders, i.e. /tapestry5.2-dev
- the landing page along with news, e.t.c. is kept separate (and in
fact doesn't
even need to be created from maven + it'd be cool if it could have
some "social" features)... it doesn't have to mention older versions
right up front& it can link to content from the latest stable release
That's why i thought current structure (with tapestry-site separate)
is better...
Now, the proposed reorganization doesn't sound like it's improving on
anything -
perhaps the only thing that gets easier is linking pages since they're
all in the same
project but that hasn't been a problem before...
That being said, i will not object to the change - i just don't get it
- yet !
On Thu, Mar 25, 2010 at 18:55, Howard Lewis Ship<[email protected]> wrote:
On Thu, Mar 25, 2010 at 9:45 AM, Andreas Andreou<[email protected]>
wrote:
i dont really get it... what is the practical difference with what
exists now?
Also, wouldn't this cause problems when the current trunk becomes
an "older release"?
It's a bit of an issue, you need to move the necessary files and
directories to a new sub-folder. Further, if you do a follow-up
release, such as 5.1.0.6, you need to update the deployed site
directory as well.
On Thu, Mar 25, 2010 at 18:27, Thiago H. de Paula Figueiredo
<[email protected]> wrote:
On Thu, 25 Mar 2010 13:23:19 -0300, Howard Lewis
Ship<[email protected]>
wrote:
This has gone around before but I expect to take this up pretty soon.
Basically, we'll be getting rid of tapestry-site.
It's content will be merged into tapestry-project, and
tapestry-project's documentation will take over the landing page,
http://tapestry.apache.org.
Older releases will be under that: i.e.,
http://tapestry.apache.org/tapestry4 or
http://tapestry.apache.org/tapestry5.1
The site content be updated out-of-release cycle, to put up important
documentation or news.
Any objections?
Go ahead!
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer, and
instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
Coordenador e professor da Especialização em Engenharia de Software
com
Ênfase em Java da Faculdade Pitágoras
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
Sócio, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
