> I have to search what it's done exactly with that. (BTW version is
> defined in poms with maven).
> I will try to work on that later this week.
Thanks
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional c
2011/10/24 Henri Gomez :
>>> So I have just commit some stuff in r 1187561.
>>> Note: Sources layout not touched.
>>> Currently only maven artifacts are build (I will work later on distrib).
>>>
>>> to test it on the top of
>>> https://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk.
>>> Just use:
>> So I have just commit some stuff in r 1187561.
>> Note: Sources layout not touched.
>> Currently only maven artifacts are build (I will work later on distrib).
>>
>> to test it on the top of
>> https://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk.
>> Just use: mvn -f maven/pom.xml clean insta
Wonderfull
Thanks Olivier !
Le 21 oct. 2011 à 23:46, Olivier Lamy a écrit :
> So I have just commit some stuff in r 1187561.
> Note: Sources layout not touched.
> Currently only maven artifacts are build (I will work later on distrib).
>
> to test it on the top of
> https://svn.apache.org/re
So I have just commit some stuff in r 1187561.
Note: Sources layout not touched.
Currently only maven artifacts are build (I will work later on distrib).
to test it on the top of https://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk.
Just use: mvn -f maven/pom.xml clean install.
Currently some un
On 14/10/2011 17:26, Mark Thomas wrote:
> On 14/10/2011 17:09, David Jencks wrote:
>> I really hope that just because the main tomcat developers don't see
>> the benefits of the maven ecosystem
[sigh] If that were true, I doubt I'd have observed the acceptance of
the Maven Tomcat plugin by this
On Oct 14, 2011, at 6:05 AM, Olivier Lamy wrote:
> 2011/10/14 Mark Thomas :
>> On 14/10/2011 09:15, Konstantin Kolinko wrote:
>>> 2011/10/14 David Blevins :
We've been using plain Tomcat zips for creating TomEE in the
OpenEJB maven build for a while now. So far that has been done by
>>
Great Olivier
Impatient to see it in action, best of both worlds
Le 14 oct. 2011 à 19:37, Olivier Lamy a écrit :
> Hello,
> I can maybe help here.
> A solution I have in mind to not change sources layout.
> http://svn.apache.org/repos/asf/tomcat/trunk/
> /maven/pom.xml (root pom.xml
Hello,
I can maybe help here.
A solution I have in mind to not change sources layout.
http://svn.apache.org/repos/asf/tomcat/trunk/
/maven/pom.xml (root pom.xml here)
/tomcat-coyote/pom.xml
etc.. one module for each artifact to produce
p
2011/10/14 Henri Gomez :
>>
>> This is the first time that I can recall that anyone has stated that
>> there is a requirement for this.
>>
>
> I should say many companies, including mine are injecting full Tomcat (as
> zip) in their enterprise repositories (Archiva/Nexus/Artifactory powered)
Are a
On 14/10/2011 17:53, Henri Gomez wrote:
>> Granted, the Tomcat project currently has no interest in using Maven as
>> a build system but that doesn't mean Maven is ignored. A lot of work
>> went into improving the Maven artefacts for Tomcat 7.
>
>
> Use of Maven was allready discussed many times
>
>
> Binary dependencies for any build process do not belong in svn. The
> infra team doesn't go looking for them but where a project is found
> using them then they will be encouraged to use a more appropriate
> approach. The more excessive the usage, the stronger the encouragement.
> The odd ja
On 14/10/2011 17:40, David Jencks wrote:
>
> On Oct 14, 2011, at 9:18 AM, Mark Thomas wrote:
>
>> On 14/10/2011 17:09, David Jencks wrote:
>>> If using a non-tomcat groupId is the only choice I'd keep the
>>> openejb copy in apache svn.
>>
>> That is not an option that is acceptable to the ASF i
>
> This is the first time that I can recall that anyone has stated that
> there is a requirement for this.
>
I should say many companies, including mine are injecting full Tomcat (as
zip) in their enterprise repositories (Archiva/Nexus/Artifactory powered)
> Granted, the Tomcat project currentl
On Oct 14, 2011, at 9:18 AM, Mark Thomas wrote:
> On 14/10/2011 17:09, David Jencks wrote:
>> If using a non-tomcat groupId is the
>> only choice I'd keep the openejb copy in apache svn.
>
> That is not an option that is acceptable to the ASF infrastructure team.
In this context, it's pretty mu
On 14/10/2011 17:09, David Jencks wrote:
>
> On Oct 14, 2011, at 4:06 AM, Mark Thomas wrote:
>> Since the requirements for this are driven by the OpenEJB project
>> and - as far as I am aware - they are the only folks with this
>> requirement, I suggest that OpenEJB runs with this and publishes
>
On 14/10/2011 17:09, David Jencks wrote:
> If using a non-tomcat groupId is the
> only choice I'd keep the openejb copy in apache svn.
That is not an option that is acceptable to the ASF infrastructure team.
Mark
-
To unsubscrib
On Oct 14, 2011, at 4:06 AM, Mark Thomas wrote:
> On 14/10/2011 09:15, Konstantin Kolinko wrote:
>> 2011/10/14 David Blevins :
>>> We've been using plain Tomcat zips for creating TomEE in the
>>> OpenEJB maven build for a while now. So far that has been done by
>>> publishing the Tomcat zips to
2011/10/14 Mark Thomas :
> On 14/10/2011 09:15, Konstantin Kolinko wrote:
>> 2011/10/14 David Blevins :
>>> We've been using plain Tomcat zips for creating TomEE in the
>>> OpenEJB maven build for a while now. So far that has been done by
>>> publishing the Tomcat zips to a maven repo in svn. Not
On 14/10/2011 09:15, Konstantin Kolinko wrote:
> 2011/10/14 David Blevins :
>> We've been using plain Tomcat zips for creating TomEE in the
>> OpenEJB maven build for a while now. So far that has been done by
>> publishing the Tomcat zips to a maven repo in svn. Not the best
>> idea to have them
2011/10/14 David Blevins :
> We've been using plain Tomcat zips for creating TomEE in the OpenEJB maven
> build for a while now. So far that has been done by publishing the Tomcat
> zips to a maven repo in svn. Not the best idea to have them in svn, so we're
> trying to get them in the actual
except some webapps included in distrib are not in central repo:
* manager
* host-manager
* examples
* docs
* ROOT
2011/10/14 Henri Gomez :
>>> The goal is to have this as a maven artifact:
>>>
>>>
>>> http://www.apache.org/dist/tomcat/tomcat-7/v7.0.22/bin/apache-tomcat-7.0.22.zip
>>
>> You
>> The goal is to have this as a maven artifact:
>>
>>
>> http://www.apache.org/dist/tomcat/tomcat-7/v7.0.22/bin/apache-tomcat-7.0.22.zip
>
> You really need this file? I think you just use the jars in the file,
> correct?
David, why do you want to use a complete distro instead of
independants art
On 10/14/2011 09:17 AM, David Blevins wrote:
On Oct 14, 2011, at 12:07 AM, jean-frederic clere wrote:
On 10/14/2011 02:01 AM, David Blevins wrote:
We've been using plain Tomcat zips for creating TomEE in the OpenEJB maven
build for a while now. So far that has been done by publishing the To
On Oct 14, 2011, at 12:07 AM, jean-frederic clere wrote:
> On 10/14/2011 02:01 AM, David Blevins wrote:
>> We've been using plain Tomcat zips for creating TomEE in the OpenEJB maven
>> build for a while now. So far that has been done by publishing the Tomcat
>> zips to a maven repo in svn. No
On 10/14/2011 02:01 AM, David Blevins wrote:
We've been using plain Tomcat zips for creating TomEE in the OpenEJB maven
build for a while now. So far that has been done by publishing the Tomcat zips
to a maven repo in svn. Not the best idea to have them in svn, so we're trying
to get them in
We've been using plain Tomcat zips for creating TomEE in the OpenEJB maven
build for a while now. So far that has been done by publishing the Tomcat zips
to a maven repo in svn. Not the best idea to have them in svn, so we're trying
to get them in the actual maven repo.
It's pretty slick to b
27 matches
Mail list logo
