tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: [VOTE] Apache Tomcat Maven plugin 2.0-beta-1
Date Wed, 01 Feb 2012 13:33:11 GMT
2012/2/1 Mark Thomas <markt@apache.org>:
> On 01/02/2012 13:01, sebb wrote:
>> On 1 February 2012 11:56, Olivier Lamy <olamy@apache.org> wrote:
>>> 2012/2/1 sebb <sebbaz@gmail.com>:
>>>> On 1 February 2012 10:14, Olivier Lamy <olamy@apache.org> wrote:
>>>>> Hello,
>>>>> As the others currently provided tomcat maven artifacts, adding those
>>>>> in the download section doesn't have (IMHO) sense.
>>>>> Because to be able to consume it within a maven build, users will have
>>>>> to install it locally respecting the maven repository format layout.
>>>>> So when the vote passed the files available in the staging repository
>>>>> https://repository.apache.org/content/repositories/orgapachetomcat-142/
>>>>> will be sync to http://repo.maven.apache.org/maven2/org/apache/tomcat/
>>>>> .
>>>>>
>>>>> What we can do at least is to add in the ASF download system the
>>>>> source archive. See files *-source-release.zip* in
>>>>> https://repository.apache.org/content/repositories/orgapachetomcat-142/org/apache/tomcat/maven/tomcat-maven-plugin/2.0-beta-1/
>>>>>
>>>>> At least with the file named
>>>>> tomcat-maven-plugin-2.0-beta-1-source-release.zip you can rebuild the
>>>>> plugins.
>>>>>
>>>>> Makes sense ?
>>>>
>>>> Apache Commons also releases code which is mainly consumed by Maven users.
>>>> All the components are released to the Apache mirrors (as source and
>>>> binary archives) as well as to Maven Central (as jars, with additional
>>>> src and javadoc jars).
>>>> Same as Tomcat itself, really.
>>>
>>> For commons it's artifacts/jars which can be consume "manually" but
>>> AFAIK consuming "manually" maven plugins jars doesn't have sense IMHO.
>>
>> The ASF releases source - from which it must be possible to build the plugin.
>> That's not generally easy or even possible from the jars that are
>> released to Maven Central.
>>
>>> If the case of a Maven plugin, I can put the jars in something like
>>> http://apache.multidist.com/tomcat/maven-plugin/ but so how will you
>>> use it ? installing manually using mvn install:.... ?
>>
>> You don't; you use the copies in Maven Central.
>>
>>> And If I go here : http://apache.multidist.com/tomcat/tomcat-7/v7.0.25/bin/
>>> I don't see maven artifacts which are available here:
>>> http://repo.maven.apache.org/maven2/org/apache/tomcat/tomcat-api/7.0.25/
>>
>> Exactly.
>>
>> Tomcat (as Commons) releases are made to *both* the mirrors *and* Maven Central.
>>
>> The ASF mirrors are for source and binary archives.
>> The Maven Central repo is used for the binary jars, along with pom and
>> accompanying source/javadoc jars.
>
> +1
>
> The primary/master/whatever Tomcat release is the source that we voted
> on. It comes in two formats .zip and .tar.gz. Everything else (the
> binaries, the Maven artefacts, the docs) is (and can be by anyone who
> cares to) derived from that source release.
>
> Every Apache release *must* have a source form from which everything
> else may be derived. Without that, the release is invalid.

Yup I proposed to add
https://repository.apache.org/content/repositories/orgapachetomcat-142/org/apache/tomcat/maven/tomcat-maven-plugin/2.0-beta-1/tomcat-maven-plugin-2.0-beta-1-source-release.zip

In http://www.apache.org/dist/tomcat/maven-plugin/ ?

>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message