Jane,
'build' was reported as a wrong target, but when I tried 'install' it failed
with the same error.
It seems like mvn doesn't even reach any goals for execution - the error happens
during the list of the modules:
[INFO] GlassFish JPA Support (rfc #143) for OSGi Bundles
[INFO] Build aggregator for various OSGi/JavaEE modules
WAGON_VERSION: 1.0-beta-2
[WARNING] POM for
'org.glassfish.build:maven-glassfishbuild-extension:pom:3.0-SNAPSHOT:runtime' is
invalid. It will be ignored for artifact resolution. Reason: Failed to validate
POM for project org.glassfish.build:maven-glassfishbuild-extension at Artifact
[org.glassfish.build:maven-glassfishbuild-extension:pom:3.0-SNAPSHOT:runtime]
And then FATAL ERROR and the stack trace.
thanks,
-marina
Jane Young wrote:
> Can you do "mvn -Prelease-phase-1 clean build" before the "mvn clean
> install"?
>
>
>
>
> Marina Vatkina wrote:
>
>> [WARNING] POM for
>> 'org.glassfish.build:maven-glassfishbuild-extension:pom:3.0-SNAPSHOT:runtime'
>> is invalid. It will be ignored for artifact resolution. Reason: Failed
>> to validate POM for project
>> org.glassfish.build:maven-glassfishbuild-extension at Artifact
>> [org.glassfish.build:maven-glassfishbuild-extension:pom:3.0-SNAPSHOT:runtime]
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.UnsupportedOperationException
>> at java.util.AbstractCollection.add(AbstractCollection.java:221)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.checkPlexusUtils(DefaultPluginManager.java:878)
>>
>> at
>> org.apache.maven.extension.DefaultExtensionManager.addExtension(DefaultExtensionManager.java:122)
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:157)
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>
>>
>> I'm using mvn version 2.0.9 (and this didn't change since last week).
>>
>> thanks,
>> -marina
>>
>>
>> ---------------------------------------------------------------------
>> 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
>