Henri Gomez wrote:
>> First define 'mavenizing' please :-)
>>
>
> Yes
>
>
>> If you mean exporting tomcat components in maven repository - fine with me.
>>
>
> It's allready done (by hand) ?
>
>
>> If you mean building tomcat with maven instead of ant - the opposite,
>> absolutely not fine.
>>
>
> it was the idea.
>
This subject has been beaten do death, with the same outcome, I don't
think it does anyone any good going there again
Filip
>
>> Maintaining a separate maven build file - unofficial, i.e. the default
>> build instructions still point to ant - maybe.
>>
>
> To modularise we should use modules layout ie :
>
> pom.xml
>
> -- catalina
> pom.xml
>
> -- catalina-ant
> pom.xml
>
> -- catalina-ha
> pom.xml
>
> -- jasper
> pom.xml
>
> -- jasper-jdt
> pom.xml
>
> ....
>
> So some changes in the actual source layout.
>
> we could also provide ant scripts to build also from this new layout.
>
> Could you comment why maven is not the welcome here, ASF JackRabbit or
> ApacheDS are pretty large projects and allready use it.
>
> I don't want to start a pros/cons maven, but it will ease :
>
> - build TC from scratch
>
> - upload artifact to maven repos
>
> - fit finelly with IC tools, like Hudson or TeamCity
>
> - maven tools like maven-bundle-plugin will ease the OSGI bundle stuff
>
> Cheers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
|