I'm running into this too. I don't understand the solution below.
I've got hk2 checked out. Do I need to load it as a project in
NetBeans? I tried that and it doesn't seem to work. If I build
it outside of NetBeans, what do I do with the result? Does it have
to end up in the .m2 repo that NetBeans is using?
Has anyone figured out why this problem occurs to begin with?
Ludovic Champenois wrote on 8/11/09 6:05 PM:
> On 8/11/09 1:41 PM, Lloyd Chambers wrote:
>> Maybe this is the problem? But I don't know the fix.
>>
>>
>> org.apache.maven.plugin.version.PluginVersionNotFoundException: The
>> plugin 'com.sun.enterprise:hk2-maven-plugin' does not exist or no
>> valid version could be
>>
>>
> Yes, the solution is to check out the hk2 code and build it. Then
> NetBeans maven support is happy for GlassFish v3.
>
> So it seems to indicate something missing in our global pom.xml
> describing the hk2 plugin...Or something in the IDE side...
>
> INFO [org.netbeans.modules.maven.NbMavenProjectImpl]: Error on loading
> project /v3/code/pom.xml
> org.apache.maven.plugin.version.PluginVersionNotFoundException: The
> plugin 'com.sun.enterprise:hk2-maven-plugin' does not exist or no valid
> version could be found
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:128)
>
> at
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:65)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:178)
>
> at
> org.apache.maven.extension.DefaultExtensionManager.addPluginAsExtension(DefaultExtensionManager.java:218)
>
> Caused: org.apache.maven.extension.ExtensionManagerException: Failed to
> resolve extension plugin:
> com.sun.enterprise:hk2-maven-plugin:maven-plugin:RELEASE
> at
> org.apache.maven.extension.DefaultExtensionManager.addPluginAsExtension(DefaultExtensionManager.java:247)
>
> at
> org.netbeans.modules.maven.embedder.NbExtensionManager.addPluginAsExtension(NbExtensionManager.java:111)
>
> at
> org.apache.maven.extension.DefaultBuildExtensionScanner.checkModelBuildForExtensions(DefaultBuildExtensionScanner.java:401)
>
> Caused: org.apache.maven.extension.ExtensionScanningException: Cannot
> resolve pre-scanned plugin artifact (for use as an extension):
> com.sun.enterprise:hk2-maven-plugin: Failed to resolve extension plugin:
> com.sun.enterprise:hk2-maven-plugin:maven-plugin:RELEASE
> at
> org.apache.maven.extension.DefaultBuildExtensionScanner.checkModelBuildForExtensions(DefaultBuildExtensionScanner.java:405)
>
> at
> org.apache.maven.extension.DefaultBuildExtensionScanner.scanInternal(DefaultBuildExtensionScanner.java:196)
>
> at
> org.apache.maven.extension.DefaultBuildExtensionScanner.scanForBuildExtensions(DefaultBuildExtensionScanner.java:120)
>
> at
> org.apache.maven.embedder.MavenEmbedder.readProject(MavenEmbedder.java:377)
> at
> org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody0(MavenEmbedder.java:416)
>
> at
> org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody1$advice(MavenEmbedder.java:304)
>
> at
> org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:1)
>
>
> Ludo
>> On Aug 11, 2009, at 1:29 PM, Lloyd Chambers wrote:
>>
>>> Odd that today I should open NetBeans 6.7 and get this mess:
>>>
>>>
>>> <pastedGraphic.png>
>>>
>>>
>>> On Aug 11, 2009, at 8:50 AM, Lloyd Chambers wrote:
>>>
>>>> I see the same problem with the QuickLook code, I have never been
>>>> able to get NB to work right on it.
>>>>
>>>> Lloyd
>>>>
>>>> On Aug 11, 2009, at 8:13 AM, Jason Lee wrote:
>>>>
>>>>> 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
>>>>>>> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>> <mailto:dev-help_at_glassfish.dev.java.net>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>> <mailto:dev-unsubscribe_at_glassfish.dev.java.net>
>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>> <mailto:dev-help_at_glassfish.dev.java.net>
>>>>>>
>>>>>
>>>>> <http://www.java.com> * Jason Lee *
>>>>> Senior Java Developer
>>>>> GlassFish Administration Console
>>>>>
>>>>> *Sun Microsystems, Inc.*
>>>>> Phone x31197/+1 405-343-1964
>>>>> Email jasondlee_at_sun.com <mailto:jasondlee_at_sun.com>
>>>>> Blog http://blogs.sun.com/jasondlee
>>>>> Blog http://blogs.steeplesoft.com
>>>>>
>>>>>
>>>>
>>>> Lloyd Chambers
>>>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>>>> GlassFish Team
>>>>
>>>>
>>>>
>>>
>>> Lloyd Chambers
>>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>>> GlassFish Team
>>>
>>>
>>>
>>
>> Lloyd Chambers
>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>> GlassFish Team
>>
>>
>>
>