: (was: Nightly Build)
Assign To: (was: Struts Developer Mailing List)
[Shale] Struts Website Features
---
Key: SHALE-129
URL: http://issues.apache.org/struts/browse/SHALE-129
Project: Shale
Type: Improvement
Environment
On Apr 26, 2006, at 10:35 AM, Roy T. Fielding wrote:
The struts.apache.org website is being published by someone
doing an scp without the proper group permissions. The publication
caused the download.cgi permission to become 644 (instead of 775),
thus breaking the mirror process. I have fixed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35332.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35332.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On the topic of anchors, I changed my mind. Again. I had originally
planned to preserve as many URLs as possible, including the anchor names.
But then I decided to just go with whatever Maven came up with, which is the
text of the section name with spaces and special characters replaced by
On 8/12/05, Wendy Smoak [EMAIL PROTECTED] wrote:
From: Martin Cooper [EMAIL PROTECTED]
Are there any objections to having 'site' or 'website' as a new
sub-project?
None at all. As Ted mentioned, that was the original plan. :-)
NOW you tell me. ;)
Sorry about that. The bit about
On 8/12/05, Wendy Smoak [EMAIL PROTECTED] wrote:
Are there any objections to having 'site' or 'website' as a new sub-project?
I believe we may have contemplated that from the beginning. Site was
to be our seventh dwarf, along with Apps, Core, EL, Plugins,
Taglibs, and Tiles. :)
We left the
Quick related question about the website. Are the xdocs used by
forrest compatible with the xdocs used by Maven? If not, do you know
what portion of them can be salvaged if any?
TIA,
sean
ps. I'm not trying to reopen the maven discussion here, just looking
for some info on how the website is
From: Sean Schofield [EMAIL PROTECTED]
Quick related question about the website. Are the xdocs used by
forrest compatible with the xdocs used by Maven? If not, do you know
what portion of them can be salvaged if any?
Maven's 'multiproject:site' goal uses the Jakarta xdocs format:
On 8/12/05, Wendy Smoak [EMAIL PROTECTED] wrote:
From: Sean Schofield [EMAIL PROTECTED]
I'm trying to avoid having
to maintain a custom stylesheet, and looking at options such as DocBook to
generate some of the docs. (The User Guide in particular already has
chapter tags in it-- I think it
From: Ted Husted [EMAIL PROTECTED]
I've done some work in DocBook, and it's not so bad, expecially since
there are some editors out there, like XML Mind.
I don't suppose just plain-old XHTML is an option?
You want to maintain the actual HTML with the h1 h2 and div
class=indent tags rather
On 8/11/05, Wendy Smoak [EMAIL PROTECTED] wrote:
From: Wendy Smoak [EMAIL PROTECTED]
One remaining concern about the website conversion: If I copy the files
into build/xdocs, what happens when someone checks out struts/current and
gets the 'build' directory within every subproject? I have
On 8/12/05, Sean Schofield [EMAIL PROTECTED] wrote:
Quick related question about the website. Are the xdocs used by
forrest compatible with the xdocs used by Maven? If not, do you know
what portion of them can be salvaged if any?
I have no idea how the two xdocs formats relate to each other,
On 8/12/05, Wendy Smoak [EMAIL PROTECTED] wrote:
From: Ted Husted [EMAIL PROTECTED]
I've done some work in DocBook, and it's not so bad, expecially since
there are some editors out there, like XML Mind.
I don't suppose just plain-old XHTML is an option?
You want to maintain the
On 8/12/05, Martin Cooper [EMAIL PROTECTED] wrote:
I would say just remove the chapter tags. When I was messing around
with this a few months ago, that's what I did, and everything else
seemed to work out just fine. I have no concerns about any limitations
of the Maven format if we're going
Thanks for all the feedback and suggestions for the new site. Here's a
second draft, incorporating as many of the suggestions as I could get to:
http://svn.apache.org/builds/struts/maven/trunk/site-test/index.html
- Navigation to subprojects is now consolidated near the top of the menu.
- If
Very nice! The only thing I noticed is could the author, see also, etc.
metadata for a document be placed at the bottom instead of the top? Now
that we are rendering that, I'll need to go clean it up :)
Thanks again!
Don
Wendy Smoak wrote:
Thanks for all the feedback and suggestions for
Excellent work, Wendy. I know you've done a great deal of work
on this and we all appreciate it. Even if you are using Maven.
david
Le 05-08-11 à 07:25, Wendy Smoak a écrit :
Thanks for all the feedback and suggestions for the new site.
Here's a
second draft, incorporating as many of the
One remaining concern about the website conversion: If I copy the files
into build/xdocs, what happens when someone checks out struts/current and
gets the 'build' directory within every subproject? I have a feeling it's
going to retrieve all that documentation a dozen times, once for each
From: Wendy Smoak [EMAIL PROTECTED]
One remaining concern about the website conversion: If I copy the files
into build/xdocs, what happens when someone checks out struts/current and
gets the 'build' directory within every subproject? I have a feeling it's
going to retrieve all that
In keeping with the Maven-or-Ant thread, it's time to think about switching
to the Maven-generated multi-project website. James has had the basic
Maven-generated site available for a while now with the nightly builds.
I made a start on integrating the existing site with Maven's, and posted the
Developers List dev@struts.apache.org
Sent: Tuesday, August 09, 2005 3:28 AM
Subject: Struts website
In keeping with the Maven-or-Ant thread, it's time to think about
switching
to the Maven-generated multi-project website. James has had the basic
Maven-generated site available for a while now
Sent: Tuesday, August 09, 2005 3:28 AM
Subject: Struts website
In keeping with the Maven-or-Ant thread, it's time to think about
switching
to the Maven-generated multi-project website. James has had the basic
Maven-generated site available for a while now with the nightly builds
Good stuff! I was fiddling around with trying to generate the site
with Maven a while ago, but I think I was trying to kill too many
birds with the same stone, so to speak. Tackling it as you have seems
like a more expedient approach.
I do have the same question as James, though: Can we still
I do have the same question as James, though: Can we still generate
the TLDs from the same XML as the taglib docs? This is one place that
I got bogged down, since it seemed that Maven wouldn't take the extra
XML elements, and I would absolutely hate to lose the guaranteed
synchronisation we get
On 8/9/05, Joe Germuska [EMAIL PROTECTED] wrote:
I do have the same question as James, though: Can we still generate
the TLDs from the same XML as the taglib docs? This is one place that
I got bogged down, since it seemed that Maven wouldn't take the extra
XML elements, and I would absolutely
From: Martin Cooper [EMAIL PROTECTED]
Another thing I was trying to tackle - which, in retrospect, was much
too big to do in one chunk, let alone with everything else too - was
creating a completely generic main site that hands off to the
sub-project sites, where the main site doesn't get into
From: James Mitchell [EMAIL PROTECTED]
Do you know how that affects the generation of the tld files? Or is it a
non-issue (meaning that hasn't changed)
I don't know yet. I noticed that the html taglib docs are missing from the
test site, and it's on the list to check out. (The tlds have
+1 for me to.
A few notes might be:
* The Download links could point to anchors on the Acquiring page, to
provide a single gateway.
* In the end, I expect we would have a single Subprojects or Projects
section, instead of two. For subproject labels, I would suggest
dropping Struts as
/show_bug.cgi?id=35332
Summary: [Shale] Struts Website Features
Product: Struts
Version: Nightly Build
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Documentation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35332.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Summary|[Shale] Struts Website |[Shale] Struts Website
|Features|Features
--- Additional Comments From [EMAIL PROTECTED] 2005-06-12 06:49 ---
Added in nightly build 20050612.
--
Configure bugmail: http://issues.apache.org/bugzilla
On Wed, 16 Feb 2005 16:30:09 -0800, Martin Cooper wrote:
My thinking was that we'd have 'site' + all subprojects, where
'core' would play in the same way as other subprojects. Since that
will involve separating 'site' files from 'core' files, I'd prefer,
in the interim, to build the site from
OK, I'm still having trouble committing from this machine, so I added the
stopgap build file through bugzilla.
* http://issues.apache.org/bugzilla/show_bug.cgi?id=33617
If anyone want's to jump in and help setup the Struts subprojects as Maven
builds, I'm sure Martin, James, et al, will
Thanks, and done. Let me know if there is anything I missed.
Don
Ted Husted wrote:
Never mind. I ran svnpasswd on the new machine, and now everything works :)
So, Don, you can make the changes, use core/build-site.xml to rebuild the site, and scp it up to /www/struts.apache.org.
-T.
On Thu,
2005 17:55:53 -0800, Don Brown wrote:
Ok, I give up - how do you build the Struts website? Last I
remember, I used ant which pulled the content from /docs but I
can't seem to find any site building task in build.xml. Are we now
only using maven and /xdocs?
Don
the Struts website? Last I
remember, I used ant which pulled the content from /docs but I
can't seem to find any site building task in build.xml. Are we now
only using maven and /xdocs?
Don
- To unsubscribe, e-mail: [EMAIL PROTECTED
?
Don
-Ted.
On Tue, 15 Feb 2005 17:55:53 -0800, Don Brown wrote:
Ok, I give up - how do you build the Struts website? Last I
remember, I used ant which pulled the content from /docs but I
can't seem to find any site building task in build.xml. Are we
now only using maven and /xdocs
imagine
we don't want to have part of the build require Ant, and the other
require Maven. Are there any examples of this being done that use
Ant?
Don
-Ted.
On Tue, 15 Feb 2005 17:55:53 -0800, Don Brown wrote:
Ok, I give up - how do you build the Struts website? Last I
remember, I used ant which
On Wed, 16 Feb 2005 10:42:36 -0800, Don Brown wrote:
I know I haven't been keeping up on this as I should have, but
wasn't Martin reworking all the Ant scripts? Perhaps website
building was included?
Don
Not that I can see. The HTML pages are built using stylesheets, and the only
place the
that use
Ant?
Don
-Ted.
On Tue, 15 Feb 2005 17:55:53 -0800, Don Brown wrote:
Ok, I give up - how do you build the Struts website? Last I
remember, I used ant which pulled the content from /docs but I
can't seem to find any site building task in build.xml. Are we
now
On Wed, 16 Feb 2005 14:17:24 -0500, Ted Husted [EMAIL PROTECTED] wrote:
On Wed, 16 Feb 2005 10:42:36 -0800, Don Brown wrote:
I know I haven't been keeping up on this as I should have, but
wasn't Martin reworking all the Ant scripts? Perhaps website
building was included?
Don
Not
Ok, I give up - how do you build the Struts website? Last I remember, I
used ant which pulled the content from /docs but I can't seem to find
any site building task in build.xml. Are we now only using maven and
/xdocs?
Don
Historically, the Struts website has just been a copy of the
struts-documentation.war webapp, uploaded to the server and then
unpacked into /www/struts.apache.org/. The only semi tricky part is
you have to make sure the permissions are set correctly (set your
umask to 0002 before unpacking
44 matches
Mail list logo
