I don't think this will be so easily figured out in a general case. I think this is something we will need to tell the plugin. I mean in my use case, the plugin could create a module for the 'src/main' source-set (including the 'src/test' source-set if there) and then simply create modules for each other source-set it encounters (with an inter-module dep on the "main" module). But again, I do'nt know if that fits the "general pattern" here or not.
For example, I'd like to have: src/main src/test src/intg-test src/jdbc3-test src/jdbc4-test (jdbc3/jdbc4 may still need to be separate projects though to properly isolate jdk selection). And create one intellij module for 'src/main' + 'src/test', another for 'src/intg-test', another for 'src/jdbc3-test' and yet another for 'src/jdbc4-test' On Thu, 2010-08-05 at 12:18 -0400, John Murph wrote: > I don't think it is possible. I just emailed Hans some issues this > morning, and this one was on the list. If I learn a different answer > from him, I'll let you know (assuming Hans doesn't pop over here and > tell you directly). My reason for wanting more than one module per > project is almost exactly the same as your. I wonder if that points > toward a solution. Maybe the plugin should associate IDEA modules > with a "main" and "test" sourceset (with the "test" sourceset > optional) instead of associating it with a project. That's how my own > custom IDEA project generation is doing things these days. > > > -- > John Murph > Automated Logic Research Team -- Steve Ebersole <[email protected]> http://hibernate.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
