You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Costin Manolache <cm...@yahoo.com> on 2003/04/12 04:05:15 UTC
Re: [VOTE] distribute the compiled .jar binaries as part of the /dist
dion@multitask.com.au wrote:
> As Jason just remembered, Maven already includes the license in the jar if
> the project defines one.
Again - this proposal has nothing to do with "jar repositories", and it
does not distribute anything but Apache software.
There is no potential risk for ASF - it is not a redistribution of
some third party software.
If maven ( or any other redistributor ) wants to get the .jars or
preffer to take the .tgz and extract the .jars manually - that's
a different story.
So far I counted 3 +1 votes and one -1. I hope to see more votes on this,
and if it passes I volunteer to make some of the jars available ( at least
for the packages that I'm a committer )
Costin
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> Jason van Zyl <ja...@zenplex.com> wrote on 12/04/2003 12:13:42 PM:
>
>> On Tue, 2003-04-08 at 18:47, Martin Cooper wrote:
>>
>> >
>> > I believe this issue was raised with respect to Maven repositories,
> such as
>> > the one at ibiblio, but has not yet been clearly resolved.
>>
>> It has. There is a license/ directory for each product in the
>> repository. Dion went to great lengths to audit every last package on
>> ibiblio and there are licenses are present there. A license file is also
>> required for a maven project so if was deemed necessary can start
>> packaging up the lics in the generated JARs with one small change to the
>> Maven JAR plugin.
>>
>>
>> > I would not want
>> > to see us make such a change in Commons until we know the official ASF
>> > position. (If the issue has been resolved, and I missed the
> resolution, feel
>> > free to give me a pointer.)
>> >
>> > --
>> > Martin Cooper
>> >
>> >
>> > >
>> > > The .jars will be used the same as the .tar.gz or .zip - if someone
>> > > wants only the .jar ( for whatever reasons ) they should be able to
> get
>> > > an official version from apache or its mirrors.
>> > > In addition, the locatin can be used in manifests - as you know the
>> > > standard manifest allows someone to specify declarative
> dependencies,
>> > > and that includes a
>> > > <extension>-Implementation-URL:
>> > > header. The value of this header should point to the release .jar.
>> > >
>> > > Note: The mirrors.html defines the naming of the released files, as
> well
>> > > as symbolic links. I would like to propose that in addition to the
>> > required
>> > > -current symlink we should also create a symlink with the normal
> name.
>> > >
>> > >
>> > > Ex:
>> > > /www/www.apache.org/dist/jakarta/commons/logging/
>> > > commons-logging-current.jar ->
>> > binaries/commons-logging-1.0.3.jar
>> > > commons-logging.jar -> binaries/commons-logging-1.0.3.jar
>> > >
>> > >
>> > > /www/www.apache.org/dist/jakarta/commons/logging/binaries
>> > > commons-logging-1.0.3.jar
>> > >
>> > >
>> > > Costin
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>> --
>> jvz.
>>
>> Jason van Zyl
>> jason@zenplex.com
>> http://tambora.zenplex.org
>>
>> In short, man creates for himself a new religion of a rational
>> and technical order to justify his work and to be justified in it.
>>
>> -- Jacques Ellul, The Technological Society
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org