I had this problem also, but upgrading to Maven 1.1beta2 solved it.
2005/9/30, Hal Arnold <[EMAIL PROTECTED]>: > > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 29, 2005 6:55 PM > To: Hal Arnold > Subject: Re: weird idea plugin issue > > please email [email protected] > > A few people have reported it, but I haven't yet seen something > reproducible. There is an open JIRA itcket. > > = Brett > > Hal Arnold wrote: > > > Brett, > > > > I just upgraded to 5.01 intellij. When I run the maven idea plugin, it > > produces a java module that doesn't work. When I looked into the *.iml > > file that the plugin produces, it appears to be the same as all the > > old *.imls produced, except that it doesn't put in the type variable: > > > > <module version="4" relativePaths="true" type="(this is empty)"> . The > > only thing I've changed is the update. Since I don't think the Maven > > module has any idea that I've updated, I'm mystified. Any thoughts? > > I've run the plugin against fairly stable *.project files, with the > > same errant results, that is, the *.iml configuration file is crippled > > vs. what it was only a month ago. > > > > /hba > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
