I resolved the problem like this : Add this ligne in the file .m2/settings.xml : <usePluginRegistry>true</usePluginRegistry>
Create the file .m2/plugin-registry.xml with : <?xml version="1.0" encoding="UTF-8"?> <pluginRegistry xsi:schemaLocation="http://maven.apache.org/PLUGIN_REGISTRY/1.0.0 [url]http://maven.apache.org/xsd/plugin-[/url] registry-1.0.0.xsd" xmlns="http://maven.apache.org/PLUGIN_REGISTRY/1.0.0"; xmlns: xsi="http://www.w3.org/2001/XMLSchema-instance";> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jspc-maven-plugin</artifactId> <useVersion>1.4.7-SNAPSHOT</useVersion> <rejectedVersions> <rejectedVersion>1.4.6</rejectedVersion> </rejectedVersions> </plugin> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <useVersion>1.0.1-alpha-1</useVersion> </plugin> </plugins> </pluginRegistry> I delete the version plugin in the pom.xml. Le goal release:prepare is ok. Is it the best way ? Rémy Rémy wrote: > > Hello, > > To compile the JSP I use the plugin > org.apache.maven.plugins:jspc-maven-plugin:1.4.7-SNAPSHOT. I use version > 1.4.7-SNAPSHOT and not 1.4.6 to exclude some JSP from compilation > http://jira.codehaus.org/browse/MJSPC-8 > http://jira.codehaus.org/browse/MJSPC-8 . To my knowledge there is no > release for v1.4.7. > > I can't make the release of my project. release:prepare detects that the > plugin is in SNAPSHOT (There are still some remaining snapshot > dependencies.: Do you want to resolve them now? (yes / no)), I answer yes > or no, the build fails. > > I don't know how to get out. The solution is it to put it in my enterprise > repository plugin version release (v1.4.6.1 for example). > > Thank you for your help. > > Remy > -- View this message in context: http://old.nabble.com/release%3Aprepare-and-plugin-in-snapshot-version-tp26954720p26955433.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
