[VOTE] Where to put the Clover license? (was RE: Maven-Clover-Plugin: License is not downloaded from local Maven repo)

[Vincent Massol <vm...@pivolis.com>]

Actually this thread made me think about the Clover license. ATM, I had
stored it in the Maven repository under a "license" type. I now think this
is wrong...

The problems that I can see:
- A license is not tied to a version of a project (it is tied to a time span
only). Currently all the artifacts are tied to such a version.
- A license expires and thus it is unnecessary (and even counter-productive)
to store different versions of the license in the repository

The solution:
- I think the best solution is simply to bundle the license as a plugin
resource in the Clover plugin jar. In any case, the Clover plugin's
project.xml is already tied to a license version (except if you use a
special property for specifying your own license).

Here's my +1.

Thanks
-Vincent

> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: mardi 15 février 2005 18:01
> To: 'Maven Users List'
> Subject: RE: Maven-Clover-Plugin: License is not downloaded from local
> Maven repo
> 
> 
> 
> > -----Original Message-----
> > From: Gisbert Amm [mailto:gia@webde-ag.de]
> > Sent: mardi 15 février 2005 17:55
> > To: Maven Users List
> > Subject: Re: Maven-Clover-Plugin: License is not downloaded from local
> > Maven repo
> >
> > Vincent Massol wrote:
> > >>When I then read the documentation I found out
> > >>about the maven.clover.license.path parameter or the classpath (I use
> > >>the param now) but still wonder why my tacit understanding to put the
> > >>licence in a license folder of the local Maven http repo shall not
> work.
> > >
> > > If you wish to use the remote repository it is still possible (I could
> a
> > FAQ
> > > for this) by doing the following:
> > > - add the license as a dependency in your project.xml
> > > - use maven.clover.license.path =
> > > ${pom.getDependencyPath('clover:yourlicensename')
> >
> > Thanx, it worked.
> >
> > However, there's the disadvantage that I have to repeat this (global
> > configuration, at least for us) for every project. OTOH it's not a big
> > problem since I'm about to create templates for new projects.
> 
> Yes, you could use a master project and have all projects inherit from it.
> 
> >
> >   >>I think it should not be a dependency in the project.xml of the
> > >>maven-clover plugin but rather the default entry for
> > >>maven.clover.license.path in the plugin.properties. Probably the
> license
> > >>  had to be distributed with the plugin then what I'd consider an
> > >>advantage.
> > >
> > > Yeah but then who performs the download of the license? ATM this done
> by
> > the
> > > Maven dependency manager. If we do this (and this may be possible but
> > I'm
> > > not sure it's worth it) we'll need to hook in the Maven API (like
> using
> > > HttpUtils but I'm not sure it's a public API).
> >
> > If it was possible and not too much work it would be nice. It's
> > certainly not necessary for survival ;-)
> 
> To be honest that's not on my priority list. I plan to add lots of other
> features in the coming weeks (like history reports, etc).
> 
> -Vincent
> 
> _________________________________________________________________
> 
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> 
> Yahoo! Mail : http://fr.mail.yahoo.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org