You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Mark Slater (JIRA)" <ji...@apache.org> on 2006/03/20 03:00:03 UTC

[jira] Created: (JCR-358) Add new top-level projects to the building documentation

Add new top-level projects to the building documentation
--------------------------------------------------------

         Key: JCR-358
         URL: http://issues.apache.org/jira/browse/JCR-358
     Project: Jackrabbit
        Type: Improvement
  Components: docs  
    Reporter: Mark Slater


The current building.xml file only mentions jackrabbit and contrib as being top level Jackrabbit projects. With the push towards 1.0, there are now several additional projects at the same level as jackrabbit and contrib. The building.xml page should be updated to mention and link to them. It should also provide a link into the subversion repository that is labeled as something like "Current Jackrabbit project list"; even though the link location is the same as the link to the repository, the label will help readers know that's where to look for the most up-to-date list of Jackrabbit projects.

-- 
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


[jira] Assigned: (JCR-358) Add new top-level projects to the building documentation

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-358?page=all ]

Jukka Zitting reassigned JCR-358:
---------------------------------

    Assign To: Jukka Zitting

> Add new top-level projects to the building documentation
> --------------------------------------------------------
>
>          Key: JCR-358
>          URL: http://issues.apache.org/jira/browse/JCR-358
>      Project: Jackrabbit
>         Type: Improvement
>   Components: docs
>     Reporter: Mark Slater
>     Assignee: Jukka Zitting
>  Attachments: building.xml.patch
>
> The current building.xml file only mentions jackrabbit and contrib as being top level Jackrabbit projects. With the push towards 1.0, there are now several additional projects at the same level as jackrabbit and contrib. The building.xml page should be updated to mention and link to them. It should also provide a link into the subversion repository that is labeled as something like "Current Jackrabbit project list"; even though the link location is the same as the link to the repository, the label will help readers know that's where to look for the most up-to-date list of Jackrabbit projects.

-- 
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


[jira] Resolved: (JCR-358) Add new top-level projects to the building documentation

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-358?page=all ]
     
Jukka Zitting resolved JCR-358:
-------------------------------

    Resolution: Fixed

Excellent, thanks Mark! Committed in revision 387153.

> Add new top-level projects to the building documentation
> --------------------------------------------------------
>
>          Key: JCR-358
>          URL: http://issues.apache.org/jira/browse/JCR-358
>      Project: Jackrabbit
>         Type: Improvement
>   Components: docs
>     Reporter: Mark Slater
>     Assignee: Jukka Zitting
>  Attachments: building.xml.patch
>
> The current building.xml file only mentions jackrabbit and contrib as being top level Jackrabbit projects. With the push towards 1.0, there are now several additional projects at the same level as jackrabbit and contrib. The building.xml page should be updated to mention and link to them. It should also provide a link into the subversion repository that is labeled as something like "Current Jackrabbit project list"; even though the link location is the same as the link to the repository, the label will help readers know that's where to look for the most up-to-date list of Jackrabbit projects.

-- 
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


[jira] Updated: (JCR-358) Add new top-level projects to the building documentation

Posted by "Mark Slater (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-358?page=all ]

Mark Slater updated JCR-358:
----------------------------

    Attachment: building.xml.patch

I've uploaded a patch for the building.xml file that uses text from the individual project README.txt files to describe them. I've also fixed the text of the link to the main jackrabbit repository (".../af/..." should have been ".../asf/..."); the link itself was correct.

> Add new top-level projects to the building documentation
> --------------------------------------------------------
>
>          Key: JCR-358
>          URL: http://issues.apache.org/jira/browse/JCR-358
>      Project: Jackrabbit
>         Type: Improvement
>   Components: docs
>     Reporter: Mark Slater
>  Attachments: building.xml.patch
>
> The current building.xml file only mentions jackrabbit and contrib as being top level Jackrabbit projects. With the push towards 1.0, there are now several additional projects at the same level as jackrabbit and contrib. The building.xml page should be updated to mention and link to them. It should also provide a link into the subversion repository that is labeled as something like "Current Jackrabbit project list"; even though the link location is the same as the link to the repository, the label will help readers know that's where to look for the most up-to-date list of Jackrabbit projects.

-- 
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