Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4EF9EE91.1090500@nanthrax.net>
Date: Tue, 27 Dec 2011 17:13:05 +0100
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: dev@tomcat.apache.org
Subject: Re: Move to Maven? (WAS: Re: Publishing process for JARs for Maven
 Central)
References: 
 <CAHTRnewpqyWHQtYiOB-Vidzbq-yaaoxL1Q5VO9_y3cXx9ZVYvw@mail.gmail.com>
 <4EEDA65A.9040905@apache.org> <4EEF7067.7050609@pidster.com>
 <4EEF73A9.8040009@apache.org>
 <CALyUpY1PK29MKMSpLiTCOuNidWUfufFdHyXt1=uU_kWDt4oXTw@mail.gmail.com>
 <4EEF807B.2030709@apache.org>
 <CAHTRnewJguGrU7t_GpLuzbGWoOGTh26urFMJdwLTnfJmY+Y-qw@mail.gmail.com>
 <4EF07258.7050106@apache.org>
 <CAPoyBqQNUBZ6GNY_2J5CicKjy3_-ebaJn-KV=0GS64cqU+qJUA@mail.gmail.com>
 <CAPoyBqSLP4AuOZicKZazmczYNnX+f=7oFwksdMW27jRMA6S1NA@mail.gmail.com>
 <CAPoyBqQ7PeZ+s-62-V=DA0cCX23UiXiCFexcyuBvWzN7L+Ms0Q@mail.gmail.com>
In-Reply-To: 
 <CAPoyBqQ7PeZ+s-62-V=DA0cCX23UiXiCFexcyuBvWzN7L+Ms0Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi guys,

I switched to:

http://svn.apache.org/repos/asf/tomcat/sandbox/trunk-mvn-build/

and prepare a set of update for OSGi.

Unfortunately, it seems that the sandbox is not open to all committer:

git svn dcommit
Committing to=20
https://svn.apache.org/repos/asf/tomcat/sandbox/trunk-mvn-build ...
RA layer request failed: Server sent unexpected return value (403=20
Forbidden) in response to CHECKOUT request for=20
'/repos/asf/!svn/ver/1224904/tomcat/sandbox/trunk-mvn-build/tomcat-juli/p=
om.xml'=20
at /usr/lib/git-core/git-svn line 579


Is it a way to open sandbox (at leat the trunk-mvn-build to all ASF=20
committer ? It will allow me to commit my OSGi changes directly (without=20
submitting a patch to olamy each time).

Thanks,
Regards
JB

On 12/23/2011 09:51 AM, Olivier Lamy wrote:
> Hello,
>
> Distro is now ok (at least for unix platform) (common-daemon and
> tomcat-native now included).
> Some unit test has been fixed (was broken due to path changes), I'm
> now at 45 failures on 533 tests (some path changes to fix).
> Now I have some fixes to do:
> * version build date in docs included in distro
> * windauze packaging
>
>
>
>
> 2011/12/22 Olivier Lamy<olamy@apache.org>:
>> Hello,
>> I have added the distro packaging (commons-daemon* and
>> tomcat-native.tar.gz not yet done).
>>
>> I still have weird issues which I don't' yet understand:
>>
>> when runing unit test
>> from the top module
>>
>> mvn clean install -Dtest=3DTestCompositeELResolver
>> ....
>> GRAVE: Error loading
>> jar:file:/Users/olamy/dev/sources/tomcat/tomcat70/tomcat-catalina/targ=
et/tomcat-catalina-7.0.24-SNAPSHOT.jar!/org/apache/catalina/mbeans/mbeans=
-descriptors.xml
>> ....
>>
>> or using the generated distro
>> mvn clean install -DskipTests
>> I have added for testing convenience an exploded distro so:
>> cd apache-tomcat/target/apache-tomcat-7.0.24-SNAPSHOT-bin/apache-tomca=
t-7.0.24-SNAPSHOT/bin/
>>
>> same error in catalina.out
>>
>> 22 d<8E>c. 2011 14:21:04 org.apache.tomcat.util.modeler.Registry loadD=
escriptors
>> GRAVE: Error loading
>> jar:file:/Users/olamy/dev/sources/tomcat/tomcat70/apache-tomcat/target=
/apache-tomcat-7.0.24-SNAPSHOT-bin/apache-tomcat-7.0.24-SNAPSHOT/lib/cata=
lina.jar!/org/apache/catalina/mbeans/mbeans-descriptors.xml
>>
>> I will start debugging.
>> For enable debugging in your ide (after the first install of all
>> dependent modules), you can use: mvn clean install
>> -Dtest=3DTestCompositeELResolver -pl :tomcat-tests
>> -Dmaven.surefire.debug=3Dtrue
>> debug port will be 5005.
>>
>> Someone with ideas on the exact cause of this ?
>>
>> 2011/12/21 Olivier Lamy<olamy@apache.org>:
>>> Hello,
>>> I have started some stuff here: https://github.com/olamy/tomcat70.
>>>
>>> * sources have been to appropriate modules.
>>> * I'm now working on some test which fail (some tests need webapp exa=
mples)
>>> * distro not yet done.
>>> * repackaging of dbcp pool, commons-logging is done using shading tec=
hnology
>>> * I will work with jbonofre (who is karaf committer) to add necessary
>>> stuff to osgiing.
>>>
>>> NOTE: It's really work in progress not finish (so pull requests will
>>> be accepted :-) )
>>>
>>> 2011/12/20 Mark Thomas<markt@apache.org>:
>>>> On 20/12/2011 08:17, Antonio Petrelli wrote:
>>>>> 2011/12/19 Mladen Turk<mturk@apache.org>
>>>>>
>>>>>> On 12/19/2011 07:04 PM, Henri Gomez wrote:
>>>>>>
>>>>>>> Exactly. Since any change would require a learning curve
>>>>>>>> and it seems we don't have that many (read none) maven
>>>>>>>> experts in the house, Gradle could be equally considered,
>>>>>>>> given that it seems more advanced in customization.
>>>>>>>>
>>>>>>>
>>>>>>> I know well Maven but Olivier (Lamy) is a Maven expert, so there =
is
>>>>>>> friend in the business.
>>>>>>> And there is a full Maven PMC not too far ready to provide advice=
s and
>>>>>>> help.
>>>>>>> Not counting Tomcat consumers ASF projects like OpenEJB.
>>>>>>>
>>>>>>>
>>>>>> All I have seen so far is talk and talk and more talk.
>>>>>> There is trunk, branches, sandbox, so anyone is free to
>>>>>> make a proposal and if things work, I'll be the first
>>>>>> one supporting it.
>>>>>>
>>>>>
>>>>> I already forked my own repository from GitHub. I hope to start it =
after
>>>>> the holidays.
>>>>
>>>> I would be very interested in seeing what a Mavenised build of trunk
>>>> looks like.
>>>>
>>>> While I may come across as anti-Maven, that is not my position. I am
>>>> anti *any* disruptive change that causes more disruption then benefi=
t it
>>>> brings and right now I see more disruption than I do benefit.
>>>>
>>>> I am also wary (from my experience of infrastructure at the ASF) of
>>>> folks pushing strongly for a switch to something better, promising t=
o
>>>> help with the switch and promising to support things moving forwards=
 and
>>>> then melting away just as their support is really needed.
>>>>
>>>> A demonstration of a fully Mavenised build of Tomcat trunk (or 7.0.x=
,
>>>> 6.0.x or 5.5.x) at GitHub would help considerably:
>>>> - we would be able to see how all the potential wrinkles (down-loadi=
ng
>>>> JDT, building a packages renamed DBCP, building a package renamed
>>>> Commons logging, etc) were handled in Maven
>>>> - we'd be able to judge how much simpler the build process was
>>>> - Maven newbies like me could try building it, debugging with it and
>>>> developing with it to see how easy we found it
>>>> - the work required to create it would demonstrate a commitment to
>>>> supporting this change
>>>>
>>>> I should stress that a working Mavenised build of a version of Tomca=
t is
>>>> necessary but not sufficient to get my support for a switch from Ant=
 to
>>>> Maven for the build / release process.
>>>>
>>>> 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
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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