Kristof, can you open an enhancement request so that people can override Eclipse project names ?
In general, I am also in favor of avoiding long names with dashes, but they are the only way to avoid collisions of namespaces. Something like eclipse.project_name should be made available if you want to override the name of the project name. On Tue, Jul 6, 2010 at 02:12, Kristof Jozsa <[email protected]> wrote: > examining the buildr gem source, it seems that eclipse.rb:334 adds the > classpath entries using the project ids which use the fully qualified > name of subprojects in the Parent:Subproject form. I made it fix for > my needs changing this short method to: > > def src_projects project_libs > project_libs.map(&:id).sort.uniq.each do |project_id| > stripped = project_id.gsub(/.*-/, '') > @xml.classpathentry :kind=>'src', :combineaccessrules=>'false', > :path=>"/#{stripped}" > end > end > > so if anyone else bumps into this problem, something like this might > help. I just wonder if anyone names it's Eclipse projects using the > naming schema suggested by this Buildr behaviour at all.. :) > > cheers, > K > > On Mon, Jul 5, 2010 at 10:06 AM, Kristof Jozsa <[email protected]> > wrote: > > Hi, > > > > assume I have a buildfile with the following projects structure: > > > > Parent > > |- Sub1 > > |- Sub2 > > > > where Sub2 also depends on Sub1. As this is an older project where I'm > > trying to introduce Buildr, the directories are named like 'parent', > > 'sub1' and 'sub2' (all lowercase). > > > > Once I execute the eclipse task of buildr, it generates an eclipse > > classpath which makes Sub2 module depend on the Sub1 module > > (correctly) but using the name "Parent-Sub1". Is there any way to > > override this naming with our own somehow easily? > > > > thanks, > > K > > >
