We could use something like profiles in maven. That way you can easily configure which projects to compile and which not. That would include tests.
I will have a look at it and come up with a proposal. On Mon, Aug 16, 2010 at 2:49 PM, <karl.wri...@nokia.com> wrote: > Re maven: There is a wiki page describing the Maven dependencies; somebody > needs to tackle this. If you want to volunteer, we'd love to hear your > proposal. However, please remember that you really must be sure to retain > the connector conditional compilation structure as is currently in place, > for license reasons. > > Re unit tests: The Junit test code was actually placed carefully based on > the above considerations. In other words, you can't run a test that > requires connectors x,y,z unless those connectors have actually been built. > Similarly, you may think in terms of testing a specific connector by > including tests for that connector, but those tests cannot use any OTHER > connectors or you will break the build, which is why any tests that use > multiple connectors must be at the module level. > > Karl > > -----Original Message----- > From: jettro.coenra...@gmail.com [mailto:jettro.coenra...@gmail.com] On > Behalf Of ext Jettro Coenradie > Sent: Monday, August 16, 2010 8:21 AM > To: connectors-dev@incubator.apache.org > Subject: improving the build > > Hi, > I think the current download is pretty big. Is there is good reason that we > do not use something like maven. Or at least, if you do not like maven, ivy > to share dependencies between projects. Also enforces you to use libraries > that are generally available. > > I would also love to have the (unit)tests closer to the actual code, hard > to > locate the tests at the moment > > Would like to hear the thoughts of the developers > > regards > > -- > Jettro Coenradie > http://www.gridshore.nl > -- Jettro Coenradie http://www.gridshore.nl
