Website

Hi, I have just read about possibility to automatically publish our website so I requested INFRA to prepare everything :) https://blogs.apache.org/infra/entry/git_based_websites_available Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl

Migrate website to Git

Hi, It just occurred to me that we can move the whole source of the website to Git - we don't use any fancy features of Apache CMS nor SvnPubSub - basically to release a new version of site I must copy all the generated htmls into a folder and commit changes to https://svn.apache.org/repos/

Re: Call another website when we click Link

, 2009 at 1:03 PM, S.Szenthilkumar wrote: > > Hi, > > I have one link in my JSP. When i click that link i have to call aanother > website(for example: call www.google.com). Please anyone help me to proceed > further. > > Thanks > S Senthilkumar > -- > View

Call another website when we click Link

Hi, I have one link in my JSP. When i click that link i have to call aanother website(for example: call www.google.com). Please anyone help me to proceed further. Thanks S Senthilkumar -- View this message in context: http://www.nabble.com/Call-another-website-when-we-click-Link

Re: xwork website

never mind, it seems like FF was caching a broken version or something. musachy On Wed, Jan 7, 2009 at 2:05 PM, Musachy Barroso wrote: > something went wrong on the xwork website: > > http://www.opensymphony.com/xwork/ > > musachy > > -- > "Hey you! Would you help

xwork website

something went wrong on the xwork website: http://www.opensymphony.com/xwork/ musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For

Re: Problems with apache website?

On 2/12/07, Michael Jouravlev <[EMAIL PROTECTED]> wrote: About an hour ago I could not access http://struts.apache.org/1.3.5, now I cannot access http://wiki.apache.org/struts/, returns 500 Internal Server Error. Is this a know issue, someone is working on this? It seems to be okay now. If so

Problems with apache website?

About an hour ago I could not access http://struts.apache.org/1.3.5, now I cannot access http://wiki.apache.org/struts/, returns 500 Internal Server Error. Is this a know issue, someone is working on this? Michael. - To unsubscr

Re: 1.3.5 on website?

Ok, I've made the changes. And I'll move the nightlies once the manual run is complete. -- James Mitchell 678.910.8017 On Aug 7, 2006, at 12:19 PM, Wendy Smoak wrote: On 8/7/06, James Mitchell <[EMAIL PROTECTED]> wrote: Are we still going to use the nightly build location [0] for host

Re: 1.3.5 on website?

On 8/7/06, James Mitchell <[EMAIL PROTECTED]> wrote: Are we still going to use the nightly build location [0] for hosting the test builds? I'm wondering because I think the current layout is confusing with '1.3.x' and '1.3.5' listed in the same directory. ... If we want to keep these here, ca

Re: 1.3.5 on website?

Are we still going to use the nightly build location [0] for hosting the test builds? I'm wondering because I think the current layout is confusing with '1.3.x' and '1.3.5' listed in the same directory. If we want to keep these here, can we inject another directory? Besides making my cron

Re: 1.3.5 on website?

On 8/2/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 8/2/06, Ted Husted <[EMAIL PROTECTED]> wrote: > That's true, but looking over my schedule, I have no discretionary > time left until the 20th. If someone wants to rebuild the release from > the 1.3.5 tag and move it out, that would be great.

Re: 1.3.5 on website?

On 8/2/06, Ted Husted <[EMAIL PROTECTED]> wrote: That's true, but looking over my schedule, I have no discretionary time left until the 20th. If someone wants to rebuild the release from the 1.3.5 tag and move it out, that would be great. I'll try to do it Thursday night, but most likely it wi

Re: 1.3.5 on website?

\On 8/2/06, Paul Benedict <[EMAIL PROTECTED]> wrote: You got me there, Martin :-) It didn't make sense. hehe I do believe the remaining issues can be solved. No time like the present. The 1.3.5 build is tagged, and the repository is open to commits. But that will be a 1.3.6, right? Well,

Re: 1.3.5 on website?

On 8/1/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: It isn't on the mirrors yet, and hasn't been announced, so the website hasn't been updated. I think only the signatures remain to be done, then everything can be deployed to the mirrored directories. That's true, bu

Re: 1.3.5 on website?

getting a production version out that more complex. I'd like to work on a production branch though before delivering. Martin Cooper <[EMAIL PROTECTED]> wrote: On 8/1/06, Paul Benedict wrote: > > If 1.3.5 is officialy beta and uploaded to mirrors, doesn't it make sense >

Re: 1.3.5 on website?

On 8/1/06, Paul Benedict <[EMAIL PROTECTED]> wrote: If 1.3.5 is officialy beta and uploaded to mirrors, doesn't it make sense to then publish it on the website sidebar simply with a "(beta)" postfix? It isn't on the mirrors yet, and hasn't been announced, so

Re: 1.3.5 on website?

On 8/1/06, Paul Benedict <[EMAIL PROTECTED]> wrote: If 1.3.5 is officialy beta and uploaded to mirrors, doesn't it make sense to then publish it on the website sidebar simply with a "(beta)" postfix? Also if 1.3.5 does not go production, I don't think 1.3 ever will.

1.3.5 on website?

If 1.3.5 is officialy beta and uploaded to mirrors, doesn't it make sense to then publish it on the website sidebar simply with a "(beta)" postfix? Also if 1.3.5 does not go production, I don't think 1.3 ever will. I am going to deliver my localization stuff soon, and so th

Re: Website version handling (was [jira] Created: (STR-2898) Rename Struts Action 1 to Struts 1)

See * http://issues.apache.org/struts/browse/SITE-8 -T. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Website version handling (was [jira] Created: (STR-2898) Rename Struts Action 1 to Struts 1)

", but later they may equate to "1.4" and "2.1" To be clear, the primary Struts site isn't and shouldn't be versioned. This is the code in struts/site. The versioning discussion is regarding the generated site docs from each Struts version. Yes, not "v

Website version handling (was [jira] Created: (STR-2898) Rename Struts Action 1 to Struts 1)

Well, that raises an interesting problem. When a user goes to the Struts site, they expect to see documentation covering the latest released version, but when developers maintain the site, they are documenting the latest code in development. I like the idea of automatically versioned sites as

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On 6/21/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: Unfortunately doesn't look like I'm going to find time to do this, I can make time in the first week of July, and it doesn't sound like anyone else will have time before then. So if anyone wants to drum up some checkstyle patches, it looks

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On 6/15/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: On 6/15/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > On Thu, June 15, 2006 6:35 am, Ted Husted wrote: > > > In the meantime, that would give Frank time to work on those patches. > > So you don't want to wait for GA now? That's fine wit

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

You might at least want to start those discussions about the checkstyle settings, so that we can develop a strategy about how they would be fixed the next time there is a window of opportunity. When I did a a time study in February, curing the the current errors with the current settings would ta

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

Ok, my head is spinning :) I like simple, so, I'll say the same thing I remember saying months ago... just ping me when the time is right to deal with Checkstyle complaints, and so long as I still have some free time then, I'll do it. You have someone willing to do the work, I'll let you worry ab

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

The problem is patches. People will tend to write patches against whatever version they are using. If we make a lot of changes right after a popular release, then a lot of the patches people submit back won't work. The ideal time for broad refactorings is at the beginning of a minor series (pre #.

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

Ok, cool Niall... I guess we maybe need to decide what the "wait point" really is here... do we want to wait for GA before I generate these patches, or just the next release? At first I thought Ted was saying let's wait for GA, but then it sounded like maybe just wait for 1.3.5 (which may or may n

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On 6/15/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: On Thu, June 15, 2006 6:35 am, Ted Husted wrote: > In the meantime, that would give Frank time to work on those patches. So you don't want to wait for GA now? That's fine with me... I'm not sure I can take care of all the complaints by J

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On Thu, June 15, 2006 6:35 am, Ted Husted wrote: > In the meantime, that would give Frank time to work on those patches. So you don't want to wait for GA now? That's fine with me... I'm not sure I can take care of all the complaints by July, but I should be able to get rid of enough of them to m

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

If no one else wants to step up, then I can do it first thing come July, but not before. In the meantime, that would give Frank time to work on those patches. -Ted. On 6/14/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 6/13/06, Ted Husted <[EMAIL PROTECTED]> wrote: > Right now, Wendy has been

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On 6/13/06, Ted Husted <[EMAIL PROTECTED]> wrote: Right now, Wendy has been publishing 1.3.5 snapshots, and she may be ready for another try at a release. I don't know if we want to get into this again now or after we have a GA 1.3. The 1.3 distribution is in good shape, I think, (but I've tho

Re: SAF1 Checkstyle (was: Maven 2 website documentation editing)

On 6/13/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: Hi Ted... I wouldn't say there's no one interested in fixing the errors :) I offered to do it some time ago, and I'm still willing (and my time has freed up again, so able as well!) Unforutnately, it seems to be a timing issue. If the pa

SAF1 Checkstyle (was: Maven 2 website documentation editing)

Hi Ted... I wouldn't say there's no one interested in fixing the errors :) I offered to do it some time ago, and I'm still willing (and my time has freed up again, so able as well!) I just started going through them... my plan was to do one package in Core and see if anyone was willing to com

Re: Maven 2 website documentation editing

Yes, as to Action1, the vast majority of the style errors are a fair cop and reflect things we shouldn't be doing. Of course, as far as Action 1 is concerned, it's a fair question of whether the checkstyle report adds any value. No one appears interested in fixing the errors, and so there are sti

Re: Maven 2 website documentation editing

ork. The assembly descriptor format is different, it's ignoring the element, and it seems to only want to work if it's in the top-level shale-parent pom. I gave up and used v2.0.1 which is working fine for Struts Action. The assembly includes the website, so you have to build that

Re: Maven 2 website documentation editing

I was looking into how to provide better aggregation. It's been a while since I looked at that code, so please don't wait for me to provide a fix in the short term. Between the day job and the kids (since school is out), I hardly have time to just keep up with mailing list traffic. Go a

Re: Maven 2 website documentation editing

On 6/11/06, James Mitchell <[EMAIL PROTECTED]> wrote: > I thought you were still building nightlies from the trunk, but yes, > the assembly is next. We can't do much about the aggregation anyway > (unless James wants to go work on Maven plugins... ;) ) > Already looking at it, albeit with what

Re: Maven 2 website documentation editing

On Jun 11, 2006, at 2:14 AM, Wendy Smoak wrote: On 6/10/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: On 6/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Old site plugin? Try -U on the command line to make it update, or >rm -rf $M2_REPO/org/apache/maven/plugins/maven-site-plugin > so

Re: Maven 2 website documentation editing

;s like changing the law just because people keep breaking it. -- Martin Cooper * The JxrReport plugin seemed to fail on every module, looking for a pom.xml in the directory above the "mvn_reorg" root. Shouldn't it be obeying the parent declarations in the POMs? * Even though I used

Re: Maven 2 website documentation editing

On 6/10/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: On 6/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Old site plugin? Try -U on the command line to make it update, or >rm -rf $M2_REPO/org/apache/maven/plugins/maven-site-plugin > so it will download again. The -U switch worked. H

Re: Maven 2 website documentation editing

PO/org/apache/maven/plugins/maven-site-plugin so it will download again. The -U switch worked. Hmm, does that mean Maven treats snapshot plugins different from snapshot dependencies? * Even though I used the -DstagingDirectory approach, the javadocs > for the modules aren't correctly

Re: Maven 2 website documentation editing

used the -DstagingDirectory approach, the javadocs for the modules aren't correctly linked from the website home page. That's probably because those links are done manually. I don't think it will automatically add links to sub-project Javadoc, but see below. * On the Project Summa

Re: Maven 2 website documentation editing

port plugin seemed to fail on every module, looking for a pom.xml in the directory above the "mvn_reorg" root. Shouldn't it be obeying the parent declarations in the POMs? * Even though I used the -DstagingDirectory approach, the javadocs for the modules aren't correc

Re: Maven 2 website documentation editing

On 6/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: You can also "stage" the entire site locally with: 'mvn site:stage' It defaults to target/staging, or you can specify -DstagingDirectory=/path/to/tempdir Strange. The default is to put target/staging under each module, which isn't any mo

Maven 2 website documentation editing

I updated the wiki page [1] but I want to call attention to a couple of features of the Maven 2 site plugin. First is the ability to start Jetty and regenerate pages on the fly as you're editing them. This works for a single module at a time. 'mvn site:run' then browse to http://localhost:80

Re: struts website issues

ding 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 both issues for now, but they will break

Re: struts website issues

Sorry for "shoot first and ask questions later". Does anyone care to comment? -- James Mitchell On Apr 26, 2006, at 11:01 AM, James Mitchell wrote: On Apr 26, 2006, at 10:35 AM, Roy T. Fielding wrote: The struts.apache.org website is being published by someone doing an s

Re: struts website issues

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

struts website issues

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 both issues for now, but they will break again the

[jira] Moved: (SHALE-129) [Shale] Struts Website Features

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

DO NOT REPLY [Bug 33617] - Add build-website to core

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35332] - [Shale] Struts Website Features

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 6384] - Add website to "Powered by Struts" page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 35332] - [Shale] Struts Website Features

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33617] - Add build-website to core

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 6384] - Add website to "Powered by Struts" page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug

Re: Website redirect

be working... let me know if that's not the right answer. It's working, but perhaps we should add another link to faqs from the website root, for consistency. -Ted. On 11/10/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > James fixed most of the issues with moved content by linkin

Website redirect

James fixed most of the issues with moved content by linking (for example) flow -> struts-flow in /www/struts.apache.org. (Thanks!) Most of the links are working fine, except for the User Guide in Core. Because the content moved down one level, userGuide -> struts-core/userGuide is breaking the

Nice job on the new website

Nice job to everyone who worked on the new Mavenized website. Just checked it out today. Looks good. sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: FYI on website

Does this mean that expiration headers for struts.apache.org/index.html are not set correctly? On 10/24/05, James Mitchell <[EMAIL PROTECTED]> wrote: > I thought I was seeing this last week too. Turns out it was just my > browser caching the page. > > On Oct 24, 2005, at 9:34 AM, [EMAIL PROTECTED

RE: FYI on website

So it is. Sorry for the bother. > -Original Message- > From: James Mitchell [mailto:[EMAIL PROTECTED] > Sent: Monday, October 24, 2005 9:40 AM > To: Struts Developers List > Subject: Re: FYI on website > > > I thought I was seeing this last week too.

Re: FYI on website

I thought I was seeing this last week too. Turns out it was just my browser caching the page. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMA

FYI on website

I get different pages for http://struts.apache.org/ and http://struts.apache.org/index.html and on the former, a number of the navigation links on the left-hand side are broken. -- George Dinwiddie 410-884-6473 [EMAIL PROTECTED] [EMAIL PROTECTED] If you want to build a ship, don't drum up peo

Re: Publishing the new website

On 10/20/05, James Mitchell <[EMAIL PROTECTED]> wrote: > > I believe the permissions issue can be resolved with a simple setting > in everyone's .bashrc file. Here's mine... > > > cat .bashrc > umask 002 <- this should do the trick This should no longer be necessary, at least on minotaur, sin

Re: Publishing the new website

Wendy Smoak wrote: Laurie, it would be great if you could update your sidebar to use the new URLs. Also I don't think Struts EL was done when you created it: http://struts.apache.org/struts-el/tlddoc/index.html Done. I haven't added the EL tagref yet, though; I'm in two minds about including

Re: Publishing the new website

I believe the permissions issue can be resolved with a simple setting in everyone's .bashrc file. Here's mine... > cat .bashrc umask 002 <- this should do the trick alias ll="ls -l" export PS1='\h:\w \u\$ ' I'm not sure why a struts-1.2.x dir is there. Stick a backup of

RE: Publishing the new website

> -Original Message- > From: Wendy Smoak [snip] > The permissions on the 'old' docs that came from the .war > files are wrong-- everything is executable. (Except a couple > of them that I started to fix, but I was doing it directory > by directory. There must be a better way, b

Re: Publishing the new website

I wrote: I'm working on the site now... Done. Thanks to James for getting this all started and Ted for rewriting large portions of the site. :) I ended up with a 'struts-1.2.x' directory that I'm not quite sure about. It's owned by James, so it must have been there before tonight. I think it

Re: Publishing the new website

From: "Martin Cooper" <[EMAIL PROTECTED]> Can we add the ApacheCon logo first, per the request from Lars? Done in r326399. I'm working on the site now... -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additi

Re: Publishing the new website

Can we add the ApacheCon logo first, per the request from Lars? -- Martin Cooper On 10/16/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > One more (last) time... > > http://svn.apache.org/builds/struts/maven/trunk/site-test/ > > (I only uploaded the 1.2.7 docs, so the other links to old docs won'

Re: Publishing the new website

Can we add the ApacheCon logo first, per the request from Lars? -- Martin Cooper On 10/16/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > One more (last) time... > > http://svn.apache.org/builds/struts/maven/trunk/site-test/ > > (I only uploaded the 1.2.7 docs, so the other links to old docs won'

Re: Publishing the new website

That seems fine to me, Wendy. I think it will be helpful to have it out there. -Ted. On 10/16/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > One more (last) time... > > http://svn.apache.org/builds/struts/maven/trunk/site-test/ > > (I only uploaded the 1.2.7 docs, so the other links to old docs won

Re: Publishing the new website

Sorry, I haven't had time to finish this. Go ahead and publish what you've got. I've got a few more things on my plate before I can get back to this. Thanks. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechse

Publishing the new website

One more (last) time... http://svn.apache.org/builds/struts/maven/trunk/site-test/ (I only uploaded the 1.2.7 docs, so the other links to old docs won't work.) I'm ready to publish it. Briefly, I plan to create struts-doc-1.2.x under /www/struts.apache.org/ and move the current site content do

Re: DTDs on the website

From: "Joe Germuska" <[EMAIL PROTECTED]> I bet they're coming from people using XML editing tools which do validation. Exactly. That's why I was working on the Shale DTDs last weekend-- JEdit had been complaining about every single tag in any dialog or clay config file I opened. While I can

Re: DTDs on the website

On 9/21/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > > >(On the other hand, infra@ has been griping about the number of requests > for > >DTDs that hit the ASF servers. I don't know how we can debug where those > are > >coming from, though.) > > I bet they're coming from people using XML editing t

Re: DTDs on the website

(On the other hand, infra@ has been griping about the number of requests for DTDs that hit the ASF servers. I don't know how we can debug where those are coming from, though.) I bet they're coming from people using XML editing tools which do validation. I wonder what they leave in the logs as

Re: DTDs on the website

On 9/21/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > On 9/21/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > > [snip] > > (On the other hand, infra@ has been griping about the number of requests > > for > > DTDs that hit the ASF servers. I don't know how we can debug where those > > are >

Re: DTDs on the website

On 9/21/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > > [snip] > (On the other hand, infra@ has been griping about the number of requests > for > DTDs that hit the ASF servers. I don't know how we can debug where those > are > coming from, though.) I'm wondering if some portion of those are comi

Re: DTDs on the website

x27;ll remove those files in a day or so (unless someone objects). The > question I have is whether to check in the current set of DTDs and > maintain > them as part of the website, or just leave it as-is. IIRC, when Struts was in Jakarta-land, the DTD location wasn't underneath the St

Re: DTDs on the website

On 9/20/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > Craig, can the dialog and clay DTDs be put on the website? Done. -- > Wendy Craig

DTDs on the website

://svn.apache.org/viewcvs.cgi/struts/site/trunk/xdocs/dtds/?rev=290621 I'll remove those files in a day or so (unless someone objects). The question I have is whether to check in the current set of DTDs and maintain them as part of the website, or just leave it as-is. Craig, can the dialog and

Re: Website Updates

From: "Ted Husted" <[EMAIL PROTECTED]> Do we expect to have PDF versions of the documentation? It's listed on the Website conversion, * http://wiki.apache.org/struts/StrutsWebsiteConversion and I wondered if anyone was working on it, or had reason to be optimistic :)

Re: Website Updates

des Core: > > > Originally, the Apache Struts software was distributed as one > > monolithic bundle. Today, the Struts project is comprised of several > > subprojects. Each subproject has its own website, documentation, and > > release cycle, and may be downloaded separate

Re: Website Updates

Do we expect to have PDF versions of the documentation? It's listed on the Website conversion, * http://wiki.apache.org/struts/StrutsWebsiteConversion and I wondered if anyone was working on it, or had reason to be optimistic :)

Re: Website Updates

bundle. Today, the Struts project is comprised of several > subprojects. Each subproject has its own website, documentation, and > release cycle, and may be downloaded separately. The six original > Apache Struts subprojects -- Core, Taglibs, Tiles, Extras, > Applications, and EL -- are als

Re: Website Updates

in the same situation as Faces, Maven is really only building the website (and only incidentally compiling the source code in order to produce some reports.) It's somewhere on the list, but below things like updating the remaining t

Re: Website Updates

On Mon, 2005-09-05 at 17:10 -0400, Ted Husted wrote: > Here's an odd idea: What if we called Struts "Core", Struts "Config" instead? > > After all, the purpose of the codebase is to realize the struts-config > XML file. What goes into Struts "Core" might be ambiguous, but what > goes inot Struts C

Re: Website Updates

On 9/5/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > What needs to be done with Taglibs? You added it to the Wiki, but there's > nothing under site/xdocs for it. I'm fairly sure that the files under > taglib/doc can be deleted-- I used them to create the JSP 1.2 TLDs that now > live in taglib/src/

Re: Website Updates

On 9/5/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > > Ted: > > I hear what you're saying, but I think that "struts-core" is the most > accurate label for the things included in that artifact. > Conceptually, it is "Struts 1.x core", but that's too verbose. > > I'm for sticking with "core". I'

Re: Website Updates

From: "Ted Husted" <[EMAIL PROTECTED]> I really must commend Wendy and James for the excellent work on the new Struts build. It's working well, and I'm having fun with it. :) Thanks for taking on the rewrites and the final reorganization... it's been fun seeing it all come together this weeke

Re: Website Updates

Standalone Tiles has a good Maven build, Shale is under construction, (the website won out this weekend,) and Faces has only enough to compile the core library and build its site. (I have uncommitted changes for Faces, IIRC we were negotiating on dependencies, but not a full Maven build.) IMO, a

Re: Website Updates

Ted: I hear what you're saying, but I think that "struts-core" is the most accurate label for the things included in that artifact. Conceptually, it is "Struts 1.x core", but that's too verbose. I'm for sticking with "core". Joe The moniker "Core" did make a lot of sense when we were thin

Re: Website Updates

From: "Ted Husted" <[EMAIL PROTECTED]> And, we do have to call it something. We're having great success with Maven, and Maven expects artifacts to have names. The closest we could come to a no-name artifact would be struts-struts-1.3.0 -- which is too odd, even for me :) Maven doesn't care wha

Re: Website Updates

Ted Husted wrote: The moniker "Core" did make a lot of sense when we were thinking that the other Struts subprojects would depend on Core. But, we dismissed that idea when we decided to host Shale. Now, should we decide to host Struts Ti one day, we would have two Java subprojects not dependant o

Re: Website Updates

On 9/5/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > I agree, config is a little too left-field (even though it does make > sense as Ted describes). > > I'm not actually too thrilled with even saying "core" frankly... I would > be more in favor of simply calling core "Struts" and all the > su

Re: Website Updates

Where do we stand on moving the rest of the nightly builds to Maven? Can we assume that Shale, Struts Faces, and Standalone Tiles (currently in the Sandbox) will all be built by Maven, and remove the dichotomy on the Acquiring page? -T. --

Re: Website Updates

I agree, config is a little too left-field (even though it does make sense as Ted describes). I'm not actually too thrilled with even saying "core" frankly... I would be more in favor of simply calling core "Struts" and all the sub-projects "Struts-xxx". I understand the reasoning of adding c

Re: Website Updates

You are right, that seems odd. I really like 'core' since it seems (to me anyway) to encapsulate the 'core' of the framework, but I'm not married to it, and I know how (sometimes) being too close to something makes it harder to see the 'forrest' ;) Your thoughts? -- James Mitchell Softw

  1   2   >