Jason van Zyl wrote:
>
>> Wishlist:
>> 1) maven generated build.xml files didn't hard code the version suffix
>>
>
> That's easy enough to fix. You just want to be able to define the final
> name of the jar?
>
> If we made ${maven.final.name} a parameter that you could use to set the
> name of the assembled JAR would that suit?
On the assumption that some projects will ultimately have more than one
jar, I would presume that having a way to specify the ${version} would
be more than sufficient. As it stands now the /project/currentVersion
(in this case "1.2-dev") gets folded into the name.
> 2) GPL'ed code is removed from jakarta.apache.org:
>> /www/jakarta.apache.org/turbine/jars2/fesi/jars/fesi-1.1.5.jar
>
> There is a mirror now @ ibiblio
>
> http://www.ibiblio.org/maven/
>
> And we will move the main distribution repository off the jakarta
> machines fairly soon because not being able to distribute (L)GPL code
> will be a problem for a lot of projects.
Actually, the root problem is an Apache project (xml-rpc) having a
dependency on an LGPL'ed code base (FESI). This is very puzzling as
there is a very capable alternative available (Rhino).
Jason, as you were the original sponsor for xml-rpc, can you take a look
into correcting this?
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
