ingenieux/beanstalker

Could not find goal 'update-environment'

Closed this issue · 8 comments

hi.

I am trying to use

'update-environment'

and getting

[ERROR] Could not find goal 'update-environment' in plugin com.ingenieux:beanstalk-maven-plugin:0.2.0-SNAPSHOT among available goals list-stacks, describe-environments, upload-source-bundle, create-application, terminate-environment, delete-application, delete-application-version, create-application-version, create-storage-location, rebuild-environment, check-availability, restart-application-server, create-environment -> [Help 1]

probably wrong snapshot?

there is no release in ther central yet?
http://search.maven.org/#search|ga|1|beanstalk

can you please let me know where can I get current snapshot?

thank you.

This mojo is present in the 0.20 tag but not in master?
Has the been deleted?

this
http://search.maven.org/#artifactdetails|br.com.ingenieux|beanstalker|0.2.0|pom

has a goal
update-environment

but fails with

[INFO] --- beanstalk-maven-plugin:0.2.0:update-environment (beanstalk) @ barchart-session-war ---
[WARNING] FAILURE:
java.lang.NullPointerException
at java.util.Arrays$ArrayList.(Arrays.java:3357)
at java.util.Arrays.asList(Arrays.java:3343)
at br.com.ingenieux.mojo.beanstalk.UpdateEnvironmentMojo.executeInternal(UpdateEnvironmentMojo.java:40)
at br.com.ingenieux.mojo.beanstalk.AbstractBeanstalkMojo.execute(AbstractBeanstalkMojo.java:145)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

This issue is fixed in master (or 'default' as mercurial/bitbucket calls it). I've build 0.21.0 and put it in my private Maven repository. The update-environment goal now works as expected. @aldrinleal when do you expect to release 0.21.0 so people can benefit from this fix?

@richard: wow! thanks for the fix!

Sorry guys, I often take morre attention in Bitbucket than github and didn't noticed all those issues.

0.2.0 has been released into maven central, and snapshots (built from bamboo can be fetched from Sonatype OSS repository).

I'm looking forward to fix the mercurial / git pipeline.

I haven't noticed the update-environment was put AFTER I released 0.2.0.

Release 0.2.1 was done in Bitbucket, triggering updates to github.

Next, release was finished into Sonatype, and version 0.2.1. should be available from maven central shortly.

I expect version 0.2.2 to have more detailed docs on feature and 'stuff, specially CI deployments and Beanstalk Settings.

(ANY HELPERS OUT THERE? hehe)

Moved previous commit to seperate issue: see "Split UpdateEnvironment"

On Fri, Jul 15, 2011 at 1:52 AM, aldrinleal <
reply@reply.github.com>wrote:

I haven't noticed the update-environment was put AFTER I released 0.2.0.

Release 0.2.1 was done in Bitbucket, triggering updates to github.

Next, release was finished into Sonatype, and version 0.2.1. should be
available from maven central shortly. I expect versoin 2.2 to have more
detailed docs on feature and 'stuff

(ANY HELPERS OUT THERE? hehe)

Reply to this email directly or view it on GitHub:
#5 (comment)