[ http://issues.apache.org/jira/browse/TAPESTRY-793?page=all ]
     
Jesse Kuhnert resolved TAPESTRY-793:
------------------------------------

    Fix Version: 4.0
     Resolution: Invalid

> Error in UsersGuide/hivemind.xml
> --------------------------------
>
>          Key: TAPESTRY-793
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-793
>      Project: Tapestry
>         Type: Bug
>   Components: Documentation
>     Versions: 4.0
>     Reporter: Jan Normann Nielsen
>     Priority: Minor
>      Fix For: 4.0

>
> I can't figure out how to reopen the issue TAPESTRY-780 som I'm raising a new 
> issue instead. The original message was: "[email protected] 
> said that I should raise this issue: "I tried opening the 
> UsersGuide/hivemind.xml file included in the tapestry-4.0-beta13 docs but is 
> seems that the file is not valid XML. In four places, <link> start tags are 
> missing.""
> I just downloaded Tapestry 4.0-rc1 and the file UsersGuide/hivemind.xml still 
> does not validate. Please don't rely on your build system validating the file 
> correctly because obviously it doesn't, or it's another file that it actually 
> validates.
> Please open the file UsersGuide/hivemind.xml and look at the contents. Here 
> is a snippet:
>       <p> But how to get access to those services? Tapestry allows you to 
> <em>inject</em> your pages and components 
>         with HiveMind services (or other objects accessible from within a 
> HiveMind registry). This is accomplished via 
>         the &lt;inject&gt;</link> specification element: </p>
> The </link> closing tag has not been opened and there are four places in 
> which this problem occurs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to