-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 try the following:
m2 deploy -DupdateReleaseInfo=true This will prompt maven to update the release metadata for that artifact, ~ and *should* result in the plugin being found. You might need to remove the plugin from the plugin-registry.xml...but in general, this should help you. HTH, john Andrius Karpavicius wrote: | Hi, | | Maybe this was touched before, but can not find it in the mailing list. | | | Made a plugin and specified version 1.0. Then simply it deployed m2 | deploy | | When I try to use it, maven keeps looking for a RELEASE version. | | How do I tell that version 1.0 is a RELEASE version. Something to specify | during deploy? | | Last time, I simply modified plugin-registry.xml file and specified a | version I needed, but that does not seem right | | Any documentation on versioning?? | |>From plugin pom.xml file | | <groupId>lt.sintagma.maven.plugins</groupId> | <artifactId>my-plugin</artifactId> | <packaging>maven-plugin</packaging> | <version>1.0</version> | |>From plugin-registry.xml | <plugin> | <groupId>lt.sintagma.maven.plugins</groupId> | <artifactId>maven-jar-plugin</artifactId> | <useVersion>RELEASE</useVersion> | </plugin> | | Thank you, | Andrius Karpavicius -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDNA3pK3h2CZwO/4URAj/8AKCGLrdjYoHM5bvzlB9LgqRLzVyMSQCfdqWP dTeaamM7DcMAdQFYa3BQkVc= =yzdt -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
