Personally, I'd rather see
http://youtrack.jetbrains.net/issue/IDEA-56332


On Wed, 2010-08-18 at 15:30 -0500, Dan Tanner wrote:
> I'm struggling with this too.  Any decent workarounds in the meantime?
>  e.g. I'm seeing an odd issue where my idea task fails with the
> following error if it's in a sub-project...if it's in a standalone
> directory, it works fine.
> Cause: Could not find method ideaProject() for arguments
> [build_gradle_2e9682f88ae35360a55e43d5a3c1aca4$_run_closu...@1104da7]
> on project ':shared-test'.
> 
> 
> Also, since we're actually paying JetBrains, it'd be great to see them
> continue to enhance support of gradle integration.  I don't see
> anything more on the EAP 10 release for it yet, and now's a good time
> to encourage them to put it on the list.  I *think* this is the
> closest issue to what you guys are talking about.?
> http://youtrack.jetbrains.net/issue/IDEA-53476
> 
> 
> 
> 
> On Wed, Aug 18, 2010 at 1:17 PM, Steve Ebersole <[email protected]> wrote:
> > Still have not seen a definitive answer to this.  Is it possible?  If
> > not, is such a thing planned?
> >
> > On Thu, 2010-08-05 at 13:23 -0400, John Murph wrote:
> >> I agree with you, I just wasn't being clear enough.  I meant that the
> >> plugin could assume that the main and test sourcesets go into the
> >> "normal" IDEA module.  Then allow some way for the script to tell it
> >> that other sourcesets go into other IDEA modules.  These other modules
> >> then need to be configurable.  Your jdbc3/jdbc4 needing to be separate
> >> projects also illustrates that there needs to be some way to add other
> >> Project objects and associate modules with them.
> >>
> >>
> >> On Thu, Aug 5, 2010 at 12:31 PM, Steve Ebersole <[email protected]>
> >> wrote:
> >>         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
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> 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
> >
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 

-- 
Steve Ebersole <[email protected]>
http://hibernate.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to