Note that there are some explanatory texts on larger screens.

plurals
  1. POBuild system that allows sharing modules amongst different binaries
    primarykey
    data
    text
    <p>I'm trying to choose the most appropriate build system to work in enterprise with a common source repository, emphasizing sharing of common code. I'd like the source hierarchy to look something like this:</p> <pre> - src - java - common - net - database - team1 - team2 - team3 - lib - tests - java - common - net - database - team1 - team2 - team3 - lib </pre> <p>The goal is to have a build system where team[1-3] can have independent builds that explicitly specify their dependencies. Dependencies might look like:</p> <pre> - team1 - common/net - team3/lib - team2 - common/database - team3 </pre> <p>So, for example, the build for team1 would include everything within the team1, common/net, and team3/lib; but nothing else. Ideally, tests would be integrated in the same fashion (testing team1 would run tests for team1, common/net, and team3/lib).</p> <p>I'm currently using Ant, but haven't found a sane way to manage a hierarchy like this. I started to look at Maven 2 for its ability to manage a dependency hierarchy, but it seems to want full-fledged projects for each module. That wouldn't be a problem, but it seems to force me into a directory structure that does not map well to the traditional java package hierarchy. It seems like I might be able to do what I want with buildr using an <a href="http://buildr.apache.org/extending.html#layouts" rel="nofollow noreferrer">alternative layout</a>, but I'm worried that might prove to be brittle.</p> <p>Can someone recommend something that might work for me?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload