maven-site-plugin

[Rod Widdowson]

Resurrecting this thread (which is to do with "mvn site -P release",
failing).

This annoyed me enough today that I chased the bug down.  I try to avoid
doing tool-smithing, so I do not understand exactly what is going on, but
the failure is because of this error:

> "java.lang.VerifyError: Expecting a stackmap frame at branch target ....."

Which appears to be something to do with TestNG and a new opcode
('InvokeDynamic') introduced in V7 which it doesn't understand[1][2]. 

It turns out that if I add 

                      <argLine>-XX:-UseSplitVerifier</argLine>

As per Daniel's note below then 'mvn site' starts working again.  But it
raises a few questions:

- Could it really be that TestNG doesn't understand V7 opcodes? I did a
quick scan for articles or documentation, but came up with nothing.
- I have not proven it, but my impression is that if one runs the "site" on
the jars in our repository they work OK.  Does this mean that our repository
is compiled for V6?

Either way I do not feel qualified to just change the V3 parent pom, so I
wanted to give the issue some airtime.

Rod


[1]
http://stackoverflow.com/questions/8958267/java-lang-verifyerror-expecting-a
-stackmap-frame
[2]
http://stackoverflow.com/questions/7010665/testng-emma-cobertura-coverage-an
d-jdk-7-result-in-classformaterror-and-verif


> -----Original Message-----
> From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net]
> On Behalf Of Rod Widdowson
> Sent: 06 March 2013 13:43
> To: 'Shib Dev'
> Subject: RE: maven-site-plugin
> 
> > I haven't seen this specifically, but most of my strange surefire
problems
> > have been cured by increasing JVM heap size.
> > Since surefire tests typically fork a new JVM, you have to set the heap
> size in
> > the configuration block:
> >
> >         <groupId>org.apache.maven.plugins</groupId>
> >         <artifactId>maven-surefire-plugin</artifactId>
> >         <version>2.11</version>
> >         <configuration>
> >           <argLine>-Xms1g -Xmx2g -XX:PermSize=256m -
> > XX:MaxPermSize=256m</argLine>
> 
> Thanks for this.  I played around with it last night and didn't get any
> further.  Then this morning I cleaned up some old cruft (2 weeks old) from
> my maven repository, did a rebuild and it is working (even with an
> unchanged
> configuration).  I have no real idea of what might have cleared it but
that
> is something to watch.
> 
> Is this something we should be adding to our parent pom anyway?
> 
> Rod
> 
> 
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net