Famous last words I posted on twitter today, “been (surprisingly?) productive today. I’m going to finish ahead of schedule ” No sooner did I say that when Jetbrain’s IDEA started to flake on me (see above). At first I thought it was a disk issue (logs pointed to the vfs) , so I wasted an hour or 2 going down that path. Disk is fine OSX disc permissions are fine…etc. I’m looking at other possibilities but I do know that I don’t have to stop development since this a maven project that lives in our subversion repositoriy. This is the point where all the whining and b**tching about doing things The Maven Way is silenced in favor of the pure joy of using a “standard” project structure . Both IDEA (as of 8.x) and NetBeans can open Maven Projects as IDE projects with all the classpath info intact. So as I wait for the Netbeans 6.5.1 to download I know that I should be ok to pick up where I left off. If this had been in some IDE specific project structure, this would have been a real pain in my@$$.
Peace,
GJ
im also sick of people whinging about “the maven way”. atleast it’s creating a standard, rather than every project structure being different.
So … why not just increase the memory settings shown there, restart, and get back to work? I use IDEA with glassfish, grizzly, and one of several other projects all open at once. All using maven. Working like a champ. Netbeans is ok but it’s no IDEA.
Before it was ‘the Maven way’, it was already an accepted directory layout, because it Just Makes Sense. I even use it for projects that do not use Maven.
@Justin Lee. Increasing the memory size didn’t after 2G of ram, the damn thing refused to start at all. Looking back, there most have been something in pom that was choking IDEA.