>I'm not sure that many-to-many is needed, but one-to-many is certainly needed.
@John, thanks a lot for feedback. Did you happen to create a jira ticket for your request? Cheers! On Mon, Jul 11, 2011 at 6:20 PM, John Murph <[email protected]> wrote: > On Mon, Jul 11, 2011 at 11:59 AM, Szczepan Faber <[email protected]> wrote: >> >> My personal preference would to steer the model towards what Adam >> suggests but not let the scope creep. I don't think many-to-many >> project mapping is a requirement for a good IntelliJ integration (or >> eclipse integration). I think whatever engineering path we take we >> should make sure we are able to work on important items first, >> potentially leaving some less important feats for later. >> > > I'm not sure that many-to-many is needed, but one-to-many is certainly > needed. Gradle has great flexibility in allowing multiple source sets, > however, IDEA does not support this in the module concept. In order to map > this, we need to be able to create multiple IML files for one Gradle > project. I've posted about this need several times, and I know we cannot be > the only ones to need this. > > -- > John Murph > Automated Logic Research Team > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
