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.

I have assigned FLUME-1262 to myself to move the doc generation to another 
Maven profile.

Regards,
Mike




Reply via email to