Thanks Brett, On 10/13/05, Brett Porter <[EMAIL PROTECTED]> wrote: > This is fixed in the next Maven release (see it0013 for an example). > After traversing some hairy classloading issues, plugins can now be > reloaded during an execution which should pave the way for a console > and easier to use scripting.
Would that also support more streamlined memory usage? I sometimes see an OutOfMemoryError for complex reactor builds, but if plugins could be executed and then unloaded, the steady-state memory usage should be much more constant, right? Kind Regards, John Fallows. > On 10/13/05, John Fallows <[EMAIL PROTECTED]> wrote: > > Folks, > > > > I developing a "non-aggregator" plugin that is manually executed on > > the command line using the goal name, in much the same way as "m2 > > idea:idea" is executed. > > > > However, this "custom:custom" plugin is still under development and so > > it has a n.m-SNAPSHOT version and has never been deployed to any > > central repository. Instead, it has been installed locally, so that > > it can be tested before the first official "release". > > > > When trying to run the plugin after a local install, I get the > > following exception. > > > > [INFO] Cannot find mojo descriptor for: 'custom:custom' - Treating as > > non-aggregator. > > [INFO] > > ---------------------------------------------------------------------------- > > [INFO] Building Maven Plugin Parent > > [INFO] task-segment: [custom:custom] > > [INFO] > > ---------------------------------------------------------------------------- > > [INFO] > > ---------------------------------------------------------------------------- > > [ERROR] FATAL ERROR > > [INFO] > > ---------------------------------------------------------------------------- > > [INFO] Diagnosis: Error resolving plugin version > > [INFO] > > ---------------------------------------------------------------------------- > > [INFO] > > ---------------------------------------------------------------------------- > > [ERROR] FATAL ERROR > > [INFO] > > ---------------------------------------------------------------------------- > > FATAL ERROR: Error executing Maven for a project > > Error stacktrace: > > org.apache.maven.reactor.ReactorException: Error executing project > > within the reactor > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:282) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:247) > > 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:324) > > 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) > > Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: > > Error resolving plugin version > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycl > > eExecutor.java:1286) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLife > > cycleExecutor.java:516) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecu > > tor.java:498) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecy > > cleExecutor.java:307) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor. > > java:149) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) > > ... 9 more > > Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: > > Error resolving version for > > 'org.custom.maven.plugins:maven-custom-plugin': Failed to resolve a > > valid version for this plugin > > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(Defa > > ultPluginVersionManager.java:202) > > at > > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(Defa > > ultPluginVersionManager.java:79) > > at > > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:1 > > 56) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycl > > eExecutor.java:1277) > > ... 14 more > > > > Note that the "org.custom.maven.plugins" groupId is already in the > > pluginGroups section of ~/.m2/settings.xml, allowing that groupId to > > be searched for the "custom" plugin. > > > > Do I need to do something special so that the SNAPSHOT version can be > > picked up after only a local install? > > > > Kind Regards, > > John Fallows. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
