well I am also changing the version control system we use (it's cuurently CVS) so any moves done before the conversion will loose the history of the files). Any moves done after the conversion will mean a few more hours of down time as I move the files afterwards (got scripts to do it but it still takes time to check all the effected source code repositories out, run the scripts, and check the result back in (on multiple supported versions). (8 source code repositories (versioned differently) and at the current count 78 sub projects spread amoung them)
But in general the two bits of code are in different namespaces but are very closely linked. I have to deliver both to my consumers but they should only deliver one to their customers. (I think that was the reason they were in the same project) I was hoping for a way not to have to use filters on the jar creation as this makes the build.gradle files a bit more complex I have an awfull lot to write (Although at the moment most of my time is spent trying to figure out the dependencies between all that lot :( cheers Matt --- On Fri, 6/2/09, Adam Murdoch <[email protected]> wrote: > From: Adam Murdoch <[email protected]> > Subject: Re: [gradle-user] Multiple source directories to multiple jar files. > To: [email protected] > Date: Friday, 6 February, 2009, 7:34 PM > [email protected] wrote: > > Hi all, > > > > I'm currently porting and old build system to > gradle and have encountered a > > bit of a problem. > > > > > > One of the projects contains two source directories > and produces two jar > > files (one for each source > > directory). I can compile both source directories to a > single ouput > > location. But is it possible to use the Java Plugin to > compile > > each source directory to its own location and jar it > up (without having to > > drop down to the ant compiler or fiddle around with > filters > > and manual jaring). I know that ideally these would be > two projects (or > > subprojects) but I would like to avoid that option at > the moment. > > > > > > > > Does each source directory contain a separate package > hierarchy? If so, > you can compile them together, and jar them up separately > using an > include pattern. If not, you're going to have to > manually add a compile > task. You could use Gradle's compile task instead of > the Ant one. > > Can I ask, is there a reason why you don't want to use > separate projects > for these 2 source directories? > > > Adam > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
