Hi,
Yes for me it did work, but not with the hpi:run. Just in live usage (mvn
clean install -> .hpi manually added). The thing is that the hpi:run is
executed in the compile phase, so with mvn install (when creating a .hpi)
the plugin configuration works, but for some reason hpi:run does not. I did
not investigate further. It should be just a different setting phase+goal.
I'll try it soon and if I succeed I'll also update the wiki. If you find a
solution for this please post a comment.
Currently this is the pom.xml configuration:
<plugins>
...
<plugin>
<groupId>org.jenkins-ci.tools</groupId>
<artifactId>
maven-hpi-plugin
</artifactId>
<executions>
<execution>
<phase>compile</phase>
<goals>
<goal>hpi</goal>
</goals>
</execution>
</executions>
<configuration>
<pluginFirstClassLoader>true</pluginFirstClassLoader>
<maskClasses>org.objectweb.asm.</maskClasses>
</configuration>
</plugin>
...
</plugins>
I had the problem with the org.objectweb.asm package.
Ref: https://jenkins-ci.org/maven-hpi-plugin/run-mojo.html
Cheers,
Ogi
On Tuesday, October 23, 2012 11:38:28 PM UTC+2, Stephen Connolly wrote:
>
> 'tis a fair cop
>
> On 23 October 2012 20:18, Jesse Glick <[email protected]
> <javascript:>>wrote:
>
>> On 10/23/2012 02:44 PM, Stephen Connolly wrote:
>>
>>> You seriously suggesting I have time to update wikis?
>>>
>>
>> Nope! Was actually addressing Ognjen, who claims to have had success
>> combining pluginFirstClassLoader with maskClasses.
>>
>
>
