http://jira.codehaus.org/browse/MCLOVER-23
John Allen commented on MCLOVER-23:
-----------------------------------
I completely agree with the principal but think the approach adopted by
checkstyle and PMD for custom resource resolution should be adopted:-
A resource (in this case the license file) is specified by a URL which is
resolved in a fallback manner covering HTTP, file and classloaders
locations. This allows us to simply specify the license file as a file path
and include a JAR depdency which contains that file path to the plugin using
the standard maven dependency mechanism, the plugin will then locate the
resource in the dependency jar.
See checkstyle and PMD for details of this custom resource loader (if memory
serves me right its a very simple helper method)
----- Original Message -----
From: "Andreas Guther" <[EMAIL PROTECTED]>
To: "Maven Users List" <[email protected]>
Sent: Sunday, March 26, 2006 1:16 AM
Subject: RE: Clover Plugin
I think it would be better to have the location defined in the user's
settings.xml file. That would allow having a build machine with its own
license file etc. The absolute path is seldom a sufficient solution.
Andreas
-----Original Message-----
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, March 24, 2006 2:03 PM
To: Maven Users List
Subject: Re: Clover Plugin
You could perhaps try an absolute pathname to the file ie
/home/afreeman/clover/clover.license or c:/maven/clover/clover.license
etc but I'm not certain that this would work...
Wayne
On 3/24/06, Aaron Freeman <[EMAIL PROTECTED]> wrote:
That worked. I guess I was putting the license in the wrong place.
However, if you do it this way then you would have to put the
clover.license file in every project that you want a clover report on.
Is this the only way to do it. I was looking for some way to put it in
one location so all POM's could reference it, but not have to include
it in the project.
On 3/24/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I believe this is "correct"...
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-clover-plugin</artifactId>
> <configuration>
> <licenseFile>clover.license</licenseFile> <!-- this assumes license
> file is stored in $basedir with the name clover.license -->
> </configuration>
> </plugin>
>
> Wayne
>
>
> On 3/24/06, Boris Lenzinger <[EMAIL PROTECTED]> wrote:
> > Have a look here:
> > http://mavenbook.xwiki.com/xwiki/bin/view/Clover%20Plugin%20v1/9%20released
> > and search license in the page. They point out a property
> > maven.clover.license.path
> > (this is from 2005 so I hope it is not out of date)
> >
> > I don't know if it is working since I do not use Clover but it can be
> > a
> > track.
> >
> > Aaron Freeman a écrit :
> > > I was looking into using Clover at my company, so I got an
> > > evaluation
> > > license from there web site. I wanted to use it with the Maven
> > > Clover
> > > plugin, but I can't figure out how to specify the license file. How
> > > is
> > > this supposed to be done? I couldn't really find much on the net
> > > about
> > > it.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
