Cool, thanks... I just want to make sure there wasn't another part I would
end up missing. If that's all I need to do to finish it, then I can deal
with it. :)
I notice that when I do a deploy on the subproject, rather than the whole
thing, it uses about 950 MB of memory.. so it just barely
Sure, I already did that a couple of times. The more important and complex
part actually resides in the release:prepare goal.
Release:perform is basically just a svn checkout from the freshly created
tag (during the prepare) followed by a mvn deploy run from the checkouted
directory.
Cheers.
I'm trying to figure out why maven 2.1 is running out of heap space when I
do a release:perform on my project. The project builds fine until I do a
release:perform in which case it runs out of memory. The stack trace seems
to indicate that there was enough memory. Do I need to give more memory
Interesting. The artifact you're trying to deploy is 350MB+ large.
Could you please try and just mvn deploy your project?
I don't remember is the release plugin forks or not.
My 2 cents,
Cheers
2009/6/8 Ryan Moquin fragility...@gmail.com
I'm trying to figure out why maven 2.1 is running out
Well, after some research, it seems like this is due to the fact that
PosterOutputStream/ByteArrayOutputStream class is quite space-greedy,
according to:
https://issues.alfresco.com/jira/browse/ETHREEOH-974
Looking at the code shows that PosterOutputStream can't be the culprit, as
it's not doing
It looks like it does fork since if I use jconsole, I will get a second JVM
that has identical properties as the first. Part of the issue with this is
I notice that both JVMs will have the amount of memory I specify for
MAVEN_OPTS. In the above case, 1GB. If I run release:perform, the forked
Ok, if I do just a mvn:deploy with 1024MB of memory, it fails at the same
spot with what I think is the same stack trace:
[INFO]
[ERROR] FATAL ERROR
[INFO]
