On Jun 24, 2012, at 12:05 AM, Mike Percy wrote: > On Friday, June 22, 2012 at 6:04 AM, Ralph Goers wrote: >> As it stands I have to vote -1 on any release since I can't validate it >> because I can't build it. I've spent hours investigating solutions to this >> but really feel like I am wasting my time as I just feel like whatever I >> propose is going to get shot down and you really don't care that I can't >> build the project. > > > > I just saw the last comment over on FLUME-1256, So I'm pasting it in here for > context: >> Ralph Goers edited comment on FLUME-1256 at 6/24/12 12:12 AM: >> -------------------------------------------------------------- >> >> I am now more confused than ever. >> >> I have two MacBook Pro's. >> >> The first is my personal machine that I use for all my open source work. It >> has a 2.5 GHz Intel Core i7 with 8GB of memory and is running Mac OS X Lion >> 10.7.4. I have never gotten the build to work on this machine even with a >> MaxPermSize of 512M. >> >> My second machine is provided by my employer and has a 2.4 GHz Intel Core i7 >> with 8GB of memory and is running Mac OS X Lion 10.7.3. The build succeeds >> on this machine with MaxPermSize of 512M. >> >> Both machines have Java 1.6.0_33 and Maven 3.0.3. So I have no idea why it >> succeeds on one and fails on the other. Obviously Mike has also gotten it to >> work on a similar machine. >> >> Although we really shouldn't have to change the default Maven settings to >> run a build I'm OK with removing this as a blocker to a release since I >> should be able to run the build and verify the release on one of my >> machines. However, I don't think this issue should be closed until either >> the issue with the plugin is resolved or the build is changed to not be >> impacted by the bug in the plugin. >> >> FWIW, I've opened https://github.com/tomdz/sphinx-maven/issues/7 since, as >> far as I can tell, the issue here is really with that plugin, not what the >> Flume build is attempting to do. > This is good to hear. In that case I'll assume this discussion is resolved.
From the perspective of the OutOfMemoryError yes, I think we should ignore the document format discussion. I have absolutely no problem with using RST although I certainly wish the plugin didn't cause problems. From the perspective of the web site though, I still think some discussion is warranted. I've gotten the impression that the plan is to simply clone something like what Sqoop has. As I said previously I think that site leaves much to be desired. I see no reason that the main site can't just be created and edited in the CMS as it is much easier and frankly provides many more options than using Maven to generate a site that doesn't really take advantage of what mvn site does in the way of generating reports. With the CMS you simply have two options - check out the site from subversion yourself and edit it as you would anything else or use the CMS editing tools. Where and how to house the user's guide and developers guides depends on how you want them to be delivered. Seeing how Sqoop is doing it and based on Arvind's prior comments I am getting the sense that there is a motivation to have the documentation packaged with each product release rather than be continually updated on the web site. Examples of doing it both ways would include http://sqoop.apche.org for individual releases and http://logback.qos.ch/documentation.html for the latter. Although I personally prefer having the online documentation up to date if it is preferred to have the documentation for each release on the site I would much prefer it if the RST could be converted to PDF instead of HTML. This will feel much more natural when browsing online and will allow the files to be downloaded for offline viewing. I'm sure there are other possibilities as well. I would really like to see some discussion in what people would like to see in a web site (both from an author's and a viewer's point of view) before we just clone what some other project is doing. > > I have assigned FLUME-1262 to myself to move the doc generation to another > Maven profile. OK - but to be honest I'm really confused as to how this project is currently using Maven. I have never seen anyone configure maven site to be forced to run on the package goal before. I'm sure whoever did it had a good reason but I'm not sure why it is being done. Having RAT and the javadoc plugin run all the time is also unusual. I'm also noticing that the distribution binary tar file contains a whole bunch of stuff that seems like it doesn't belong, such as all the source code and everything from the flume-ng-tests/target directory. So before disabling stuff with a profile I'd like to know why it is the default behavior and then possibly add comments to the pom to say why it is there. Ralph
