Hi, I will take a look at the pull, though if you can automate everything, I tend to say that it's the good solution whatever the time the build takes. Regarding Javadocs, yes, we can push them online, but I wouldn't bother too much on this. Generally, I want to browse sources in my IDE for external libraries or I use grepcode.com which is a lot easier than static Javadocs. Best regards, Jérôme
2014-02-11 10:04 GMT+01:00 Misagh Moayyed <[email protected]>: > Here's the pull: > https://github.com/Jasig/cas/pull/399 > > > > -----Original Message----- > > From: Misagh Moayyed [mailto:[email protected]] > > Sent: Monday, February 10, 2014 8:33 AM > > To: [email protected] > > Subject: RE: [cas-dev] CAS 4.0 Documentation > > > > I may have not-so-slightly miscalculated the site size. It appears to be > well > > below 100MB in total but still it's quite a bit. That aside, I have been > > running a few tests in the cloud and the entire generation of the site > takes > > about 30 to 40 minutes. Doing continuous manual pulls and pushes and > keeping > > the "current" javadoc and site updated, given the size and the time > seems > > like a major haul. > > > > I do take your point however that viewing apidocs online is infinitely > > easier. I did experiment with the "readthedocs" cloud service a bit, but > it > > turned out a bit more involved than I had hoped for. Nonetheless, the > good > > news is that I may found a way to automate everything via travis. I am > still > > running some experiments on my own local fork, but the idea is for > travis to > > build the site and auto-push the generated docs over to the gh-pages > branch. > > If I could get the last bit to work, then I don't think we'd have to > worry > > about anything as it will all be fully automated, on all commits on > master. > > It would then just be a matter of moving "current" > > to "x.y.z" upon release time. > > > > Sound fair? > > > > Misagh > > > > > -----Original Message----- > > > From: Marvin Addison [mailto:[email protected]] > > > Sent: Thursday, February 6, 2014 2:38 PM > > > To: [email protected] > > > Subject: Re: [cas-dev] CAS 4.0 Documentation > > > > > > I'm sorry I'm responding so late but I did want to voice an opinion on > > the javadocs, > > > which is something I feel strongly about. > > > > > > > Now onto Javadocs and having looked at the current build and size of > > > > the generated docs > > > > > > At first glance I'm surprised that size is an issue; it's just text > > after all. I'll take your > > > word for it in any case. > > > > > > > I'd propose that instead of actually maintaining the docs we'd just > > > > add links to sonatype where docs can be downloaded as jars. > > > > > > I can compromise on agreeing to externalize the javadocs, but I feel > > strongly that > > > they should be available as HTML to support online browsing. I'm sure > > there are > > > myriads of other devs that are lazy like me and bristle at the extra > > step to > > > download and browse a local file URL. > > > > > > M > > > > > > -- > > > You are currently subscribed to [email protected] as: > > [email protected] > > > To unsubscribe, change settings or access archives, see http://www.ja- > > > sig.org/wiki/display/JSG/cas-dev > > > > -- > > You are currently subscribed to [email protected] as: > > [email protected] To unsubscribe, change settings or access archives, > see > > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
