I agree. Option 2 is the better choice.
Changesets on trunk can be Java5 specific. It would be problematic to
have to also include tested Java 1.4 versions on a 1.8 branch that may
never see the light of day. If there are bug fixes that need to go into
a future 1.8.4 release we can deal with t
On Thu, Mar 15, 2012 at 11:58 PM, Stefan Bodewig wrote:
> Hi,
>
> WRT merging to the branch we basically have two options: (1) merge when
> we commit to trunk or (2) merge when we know we want to create another
> 1.8.x release.
>
> I'm leaning towards (2) since I personally don't expect a 1.8.4
>
Le 16 mars 2012 à 06:02, Stefan Bodewig a écrit :
> On 2012-03-09, Nicolas Lalevée wrote:
>
>> As a quick fix I guess we can add in the command line launched by
>> Jenkins a -Djava.io.tmpdir=$WORKSPACE/tmpdir
>
> Have you changed the configuration to contain that? If so, it doesn't
> look to h
