tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1478) Outdated tutorial version is online concurrently with updated tutorial
Date Thu, 31 Mar 2011 23:46:05 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-1478.
--------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

The tutorial you linked to was valid for 5.1, and every page in it includes "Release 5.1.0.5"
in the upper left corner.  We have since decoupled documentation from the release process
(which brings with it its own problems as the code evolves), but http://tapestry.apache.org/
is now the expected starting point.

> Outdated tutorial version is online concurrently with updated tutorial
> ----------------------------------------------------------------------
>
>                 Key: TAP5-1478
>                 URL: https://issues.apache.org/jira/browse/TAP5-1478
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 5.0.19
>            Reporter: Rael G.C.
>            Assignee: Howard M. Lewis Ship
>            Priority: Blocker
>
> I entered the site at http://tapestry.apache.org/tapestry5/ and open the tutorial link
by there, it give me this tutorial URL: http://tapestry.apache.org/tapestry5/tutorial1/
> This tutorial is really outdated, without enough information about how to import project
to eclipse, other minor issues, and most important: it uses old software versions, like maven2,
jetty5, jettylauncher (which is even discontinued).
> After read the tutorial, I gone to home and found a updated version: http://tapestry.apache.org/tapestry-tutorial.html
> So, why keep the old version so accessible (should be archived), or at least not labeled
as outdated?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message