No way to configure generate env-entry elements in generated application.xml

yes it should.

Jim Brownfield provided a patch for this one which I am currently reviewing and adapting.

I just reverted this commit in r129166 since it was breaking the IT's on 32 bit linux.

It has nothing to do with linux. It's failing with maven 2.x

Instead of reverting, can't you reopen this issue and ignore the test instead. It's working fine with Maven 3, we just need to figure out what is going wrong in plexus with 2.x

From the mailing list discussion there seemed to be some confusion as to the source of the problem.

I am not particularly opposed to the patch itself as long as the tests pass, and I wanted to fix the build.

If you're using a less brain-dead client than subversion it's just two keystrokes to revert the revert.

There was some confusion at the beginning but the issue is coming from Maven 2, not linux (probably some plexus dependency chain nightmare).

I checked out MEAR version 1239783 (prior to the revert)
This works for me with Maven 2.2.1 on Linux (ubuntu 11.10)

BUT you must specify the env-entry like this:
<envEntries>
<env-entry>...
</envEntries>

and NOT as in the examples

<env-entries>
<env-entry>...
</env-entries>

ah, excellent. I understand the difference now. Thanks !

Somebody have plans to restore functionality provided by 1235631? Feature still doesn't work.

It does not work because the code was reverted. But now that I understand the differences, we should document this and re-apply the patch indeed.

It was just what I mean - it was reverted, everybody agreed that it was almost nothing to do with test failure and nobody have applied that patch back for half of a year... I was thinking that may be there was something else preventing from doing this?

Time. And now it's done. I also changed the tests so that they use envEntries to make sure ITs will pass on Maven2