I only generated eclipse files with buildr so it is not in a weird state. I figured out that buildr uses the parent project id as "PARENT-CHILD" and that is used as the eclipse project name.
I had to add: eclipse.options.short_names = true to the parent project to use the project names that correspond to the directory. I believe that is missing in the documentation, but somewhat crucial. Thanks! Anthony Bargnesi On Fri, Aug 10, 2012 at 11:37 AM, Alex Boisvert <alex.boisv...@gmail.com>wrote: > My best guess is that you have an inconsistent set of Eclipse .project / > .classpath files. > > I would recommend trying to delete all your .project / .classpath files for > all projects/sub-projects, re-running "buildr eclipse", removing all > projects from your eclipse workspace and re-importing them. > > alex > > > On Fri, Aug 10, 2012 at 4:12 AM, Anthony Bargnesi <abargn...@gmail.com > >wrote: > > > Hello, > > > > I have a project defined with a parent project and a number of > subprojects. > > > > The structure looks something like: > > > > define 'Parent', :layout => layout do > > project.group = 'com.acme.parent' > > project.version = '1.0.0' > > > > define 'base' do > > compile.with ... > > package(...) > > end > > > > define 'core' do > > compile.with ... > > package(...) > > end > > end > > > > When I run the "eclipse" task to generate project files I receive > classpath > > errors in 'core'. > > The core module depends on base as a project dependency in eclipse. > > > > The subprojects appear as base/core projects, but core refers to > > "Parent-base" as its > > project dependency. This refers to the parent project "Parent", but > causes > > invalid eclipse > > metadata to be generated. > > > > Is this intentional and can this behavior be overridden? > > > > Thanks! > > Anthony Bargnesi > > >
