I recently ran into the problem. It seems like telling NetBeans to
index the .m2 repo helped, though it might have been coincidence. The
problem went away after that, though.
On Aug 11, 2009, at 10:04 AM, Tim Quinn wrote:
> Hi, Kumar.
>
> In NB try View->IDE Log.
> I used to have this problem using NB 6.7 with modules that were
> distribution fragments. NB 6.7.1 which I've been using lately seems
> to be better with those.
>
> I remember seeing advice somewhere to look in the IDE log and see
> why it objects to the pom.xml file.
>
> - Tim
>
> Kumar Jayanti wrote:
>> Hi,
>>
>> Lately i am seeing that many of the V3 modules do not open properly
>> in NetBeans, it shows up as <Badly formed Maven Project>. This was
>> not the case 2 weeks ago. Does anyone know how to correct this.
>>
>> A full mvn clean install does not seem to help either.
>>
>> regards,
>> kumar
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
Jason Lee
Senior Java Developer
GlassFish Administration Console
Sun Microsystems, Inc.
Phone x31197/+1 405-343-1964
Email jasondlee_at_sun.com
Blog
http://blogs.sun.com/jasondlee
Blog
http://blogs.steeplesoft.com