Stuart McCulloch wrote:
2008/4/25 Sahoo <[EMAIL PROTECTED]>:
Hi,
While using maven-bundle-plugin, fairly regularly I see an error (details
given below) emitted by bnd. The jar file it complains about is not fixed.
Upon subsequent attempt, the error either disappears or it complains about a
different jar file. I am not the only person in my team who is facing this
weired problem. Has anyone else experienced such a problem? Is there a work
around or a solution? It appears to be a problem in bnd. I will definitely
report to bnd folks, but I thought of checking with the large bnd user base
that exists in this community. Who knows, may be it is a problem that only
happens when bnd runs inside maven? I run maven with -Xmx=512m, so there is
sufficient memory for the program to execute.
Hi Sahoo,
I haven't seen this myself - looks more like a corrupted jarfile rather
than an OOM*, are the jars located on a local or remote filesystem?
Also could other people be updating these jars while you're doing
the build?
you might want to try the latest 1.4.1 snapshot which I just deployed,
as it contains a couple of fixes to make Bnd more memory efficient.
* actually it might be a native OOM as the inflaters/deflaters use
native memory - so you might want to monitor the process size
using an OS tool, just in case...
HTH
The jars located in local file system. Thy are not corrupted - I can use
jar tool to view them. No other process is updating the jars except the
mvn command that I run. I will try with 1.4.1 snapshot.
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
