So I figured this out by looking at the pmd report plugin, but essentially
you need to use a different classloader. so you will need to do something
like this:
ClassLoader origLoader =
Thread.currentThread().getContextClassLoader();
try {
Thread.currentThread().s
+1
--
Olivier
2008/3/10, Vincent Siveton <[EMAIL PROTECTED]>:
> Hi,
>
> It s again me :) I would like to release (again) the Maven Plugin
> Tools projects:
> * maven-plugin-plugin-2.4
> * maven-plugin-tools-beanshell-2.4
> * maven-plugin-tools-java-2.4
> * maven-plugin-tools-2.4
> * maven-p
The vote has passed:
+6 binding: Brian, Jason, Lukas, Olivier, Stephan, Vincent
I'll proceed with the release.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 08, 2008 5:17 PM
To: Maven Developers List
Subject: [Vote] Release maven-javadoc-plugin 2.
Benjamin Bentmann wrote:
I noticed that Maven is using junit:3.8.1 quite everywhere for its tests
although a later maintenance release of the 3.x line exists with junit:3.8.2.
Is there a known issue with 3.8.2 that makes one stick to 3.8.1?
I think it's just that JUnit 3.8.1 was released in 2
I am trying to run a maven report that I wrote that needs to create a spring
applicationcontext. but I seem to have a problem placing the spring context
files needed on the classpath for the site report to run properly.
I have this a report setting setup in my pom.xml :
I'm not aware of any issues, doxia is using 3.8.2 everywhere.
-Lukas
Benjamin Bentmann wrote:
Hi,
I noticed that Maven is using junit:3.8.1 quite everywhere for its tests
although a later maintenance release of the 3.x line exists with
junit:3.8.2. Is there a known issue with 3.8.2 that make
+1
Dennis Lundberg wrote:
Hi
To get the latest version of maven-source-plugin into our toolchain, I'd
like to release the shared components parent r635758 as version 9. A
site.xml has been added in this release.
Source:
https://svn.apache.org/viewvc/maven/shared/trunk/pom.xml?r1=587316&r2=63
You may want to use a profile for this, set in your settings.xml (or
rather a settings.xml of the user used to build your ultimate
releases). This profile would define a propertly, and you reference
the properly in your actual pom.xml. This way you either:
1. only execute the signing
Hi,
Don't know if this is the right place to post this, but here it is anyway:
Currently we have a requirement to sign JARS which will hold applets.
After reading the documentation, you can easily sign JARS using the sign
goal with the jar maven plugin. The plugin will eventually call the
jars
