You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Niall Pemberton <ni...@blueyonder.co.uk> on 2006/03/14 01:15:56 UTC
[shale] Web Site - Issue Tracking
Over in Commons quite a few components have used custom "issue tracking" and
"source repository" pages. I notice that Shale currently has a section on
"issue tracking" in the main page. Is there any objections to me adding
these kind of custom pages for Shale?
The advantage of a custom "issue tracking" page is that it will
automagically be used in the "project info" menu and we can also replace the
current link at the top of the main menu. As with Commons we can provide
links so that new bugs are created with the right settings and provide some
useful links to search existing bugs. Heres an example from validator:
http://jakarta.apache.org/commons/validator/issue-tracking.html
The "source repository" is less of a win, but also useful IMO:
http://jakarta.apache.org/commons/validator/cvs-usage.html
Niall
P.S. I just found the PDF version of the Shale docs - very impressive
whoever was responsible for that! Need to find out how that was done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [shale] Web Site - Issue Tracking
Posted by Niall Pemberton <ni...@gmail.com>.
On 3/14/06, Wendy Smoak <ws...@gmail.com> wrote:
> On 3/13/06, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
>
> > Over in Commons quite a few components have used custom "issue tracking" and
> > "source repository" pages. I notice that Shale currently has a section on
> > "issue tracking" in the main page. Is there any objections to me adding
> > these kind of custom pages for Shale?
>
> Go right ahead. (You really don't have to ask...) I already added a
> custom team-list page, because we're not maintaining the list of
> committers in the Shale project.xml file. Feel free to add to that
> one as well.
OK, need to start build Shale first
> > P.S. I just found the PDF version of the Shale docs - very impressive
> > whoever was responsible for that! Need to find out how that was done.
>
> :) I'll give you one guess who it was. :) It takes a custom
> navigation.xml file, a couple of lines in project.properties, and a
> postGoal in maven.xml (or a <report> element in project.xml). FOP is
> *very* picky, though. One duplicate anchor and the entire thing
> breaks. More here: http://maven.apache.org/maven-1.x/plugins/pdf/
My memory said it was you, but I didn't want to assume in case it was
someone else. Good job and thanks for the info.
Niall
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [shale] Web Site - Issue Tracking
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/13/06, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> Over in Commons quite a few components have used custom "issue tracking" and
> "source repository" pages. I notice that Shale currently has a section on
> "issue tracking" in the main page. Is there any objections to me adding
> these kind of custom pages for Shale?
Go right ahead. (You really don't have to ask...) I already added a
custom team-list page, because we're not maintaining the list of
committers in the Shale project.xml file. Feel free to add to that
one as well.
> P.S. I just found the PDF version of the Shale docs - very impressive
> whoever was responsible for that! Need to find out how that was done.
:) I'll give you one guess who it was. :) It takes a custom
navigation.xml file, a couple of lines in project.properties, and a
postGoal in maven.xml (or a <report> element in project.xml). FOP is
*very* picky, though. One duplicate anchor and the entire thing
breaks. More here: http://maven.apache.org/maven-1.x/plugins/pdf/
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [shale] Web Site - Issue Tracking
Posted by Wendy Smoak <ws...@gmail.com>.
On 3/13/06, Craig McClanahan <cr...@apache.org> wrote:
> Isn't that part of the Maven goodness? (In other words, thank Wendy :-).
... and Lukas, and Arnaud, and the rest of the Maven 1 team. They've
repeatedly gone above and beyond the call of duty to get the xdoc and
PDF plugins to work with Shale's somewhat creative Maven build.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [shale] Web Site - Issue Tracking
Posted by Craig McClanahan <cr...@apache.org>.
On 3/13/06, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
>
> Over in Commons quite a few components have used custom "issue tracking"
> and
> "source repository" pages. I notice that Shale currently has a section on
> "issue tracking" in the main page. Is there any objections to me adding
> these kind of custom pages for Shale?
Definitely +1. I have my own private Bugzilla query for this, but it'd be
better for everyone to have a common starting point.
The advantage of a custom "issue tracking" page is that it will
> automagically be used in the "project info" menu and we can also replace
> the
> current link at the top of the main menu. As with Commons we can provide
> links so that new bugs are created with the right settings and provide
> some
> useful links to search existing bugs. Heres an example from validator:
>
> http://jakarta.apache.org/commons/validator/issue-tracking.html
>
> The "source repository" is less of a win, but also useful IMO:
>
> http://jakarta.apache.org/commons/validator/cvs-usage.html
>
> Niall
>
> P.S. I just found the PDF version of the Shale docs - very impressive
> whoever was responsible for that! Need to find out how that was done.
Isn't that part of the Maven goodness? (In other words, thank Wendy :-).
---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>