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 unit tests are failing (so use -DskipTests). I will try to fix that too. 2011/10/14 Olivier Lamy <ol...@apache.org>: > 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 > plus a module to package the distro. > > in each module, compiler plugin will be configured to use only a set > of java files. > This won't change the current sources layout > > As an example, this solution is used by the selenium project: > http://selenium.googlecode.com/svn/trunk/maven/ > > I can maybe try to work on that and provide a patch. > Or at least commit in trunk (if I have no layout changes to do). > > But not before end of next week or early week after. > > 2011/10/14 Konstantin Kolinko <knst.koli...@gmail.com>: >> 2011/10/14 Henri Gomez <henri.go...@gmail.com>: >>>> >>>> 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 all those related to Maven? Do they publish only zips, or the full >> set of tgz and zips (~80Mb) ? >> >> Keeping an in-house copy of 3rd party library is a different story, >> and it is needed regardless of whether somebody uses Maven Central to >> publish their work. >> >> I personally am using Apache Ivy [1] to manage my repository of >> dependencies, and AFAIK it can download not only from maven, but from >> any other structured repository as well. >> >> [1] http://ant.apache.org/ivy/ >> >>> >>> BTW, did there is a strong -1 to have an alternative build system using >>> Maven if this build keep the current Tomcat structure ? >>> >> >> There are not may people here to support it here if it breaks, and on >> RTC branches that would require 3+ committers that understand what >> happens. >> >> >> There was some discussion here on dev@ about 2 years ago, and some >> person proposed to create a maven build, but he disappeared never >> showing anything working. >> >> Best regards, >> Konstantin Kolinko >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >> > > > > -- > Olivier Lamy > Talend : http://talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
