2008/9/17 Brad Cox <[EMAIL PROTECTED]> > The reason I didn't notice this is, now that the root pom won't open in > eclipse, refreshing the root no longer refreshes all sub-modules. Eclipse > won't even open them now; you can see that in my screenshot. Why should > pax-clean delete files it doesn't own and not replace them with something > better? They were created by eclipse:eclipse, not pax. >
as I mentioned before, the current default is to not create hierarchical Eclipse projects because this doesn't work with earlier releases of Eclipse - and even the latest version doesn't appear to handle deep hierarchies that well because of this, no-one has ever noticed that pax:clean would remove such files - it just goes through each project removing the same set of generated files, and just happens to treat pom packaging projects like any other btw, the pax-plugin eclipse mojos are derived from the standard eclipse plugin, so when we eventually upgrade to the latest plugin level it should start creating those .project files as per eclipse:eclipse (feel free to raise a ticket for any bugs at http://issues.ops4j.org/) > Its working again now. To get to that state I had to manually refresh every > subdirectory and run the manifests thru the eclipse wizard. Very labor > intensive. > ouch, yep that's a pain - I usually do a select all across the projects and hit F5, not sure why you had to run the manifests through the wizard though, as I never need to do that > Brad Cox wrote: > >> Belay that previous. Refresh cleared the errors. Argggh!! This is so >> confusing. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Cheers, Stuart
