Oops, just realised I'm on the users list asking stupid dev
questions! Will join the dev list and hop on over.
However in the meantime, I managed to get it to work by putting the
plugin section into my target pom. Then running the plugin in the
same directory somehow picked up all of the configuration info. Yet
at the same time running the pom itself didn't cause the plugin to be
run - guess that must be due to the @execute annotation.
Cheers
AW
On 5 Sep 2005, at 12:16, Yann Le Du wrote:
--- Ashley Williams <[EMAIL PROTECTED]> a écrit :
Not quite sure what this achieves, but I did try it to no avail. I
ended up with a rather nasty looking error:
Edge between 'Vertex{label='com.williams1000.maven.plugin:maven-
eclipseproject-plugin'}' and 'Vertex
{label='com.williams1000.maven.plugin:maven-eclipseproject-plugin'}'
introduces to cycle in the graph com.williams1000.maven.plugin:maven-
eclipseproject-plugin --> com.williams1000.maven.plugin:maven-
eclipseproject-plugin
Does Maven really operate on the basis of some text file being
present for user plugins?
Seems like. I had the same kind of failure as you, and copying the
LATEST file
to a RELEASE file solved the problem. The <updateReleaseInfo> does
this
automatically, but if it results in a failure, that's an issue...
Will the -DarchetypeArtifactId=maven-archetype-mojo code be fixed to
add this automatically into your plugin start pom if it's needed?
This mechanism seems to be on purpose, so I really don't know...
Maybe the dev
can shed some light on this ? I don't know how come I got the
problem and you
didn't... :)
Thanks
-AW
On 5 Sep 2005, at 10:10, Yann Le Du wrote:
Ashley,
Check in your repository if there is a
maven-myplugin-plugin-RELEASE.version.txt in your plugin dir (along
the LATEST
file). If not, add these lines to your plugin POM then re-launch m2
install :
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-myplugin-plugin</artifactId>
<configuration>
<updateReleaseInfo>true</updateReleaseInfo>
</configuration>
</plugin>
</plugins>
</build>
HTH,
Yann
--- "Johnny R. Ruiz " <[EMAIL PROTECTED]> a écrit :
Ashley Williams wrote:
I've written a simple plugin that I wish to call from the command
line rather than as part of the project, just like m2
clean:clean, so
as such I've used the 'execute' goal annotation.
However no matter what I try maven seems to look for a RELEASE
plugin
somewhere in the org.apache package structure. For example
specifying
-Dpackage -Dversion settings didn't work. Additionally there
will be
additional configuration settings I'd need to specify depending on
the project.
Any ideas?
------------------------------------------------------------------
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
have you tried "m2 groupId:artifactId:goal"?
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
____________________________________________________________________
__
_____
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo!
Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
--------------------------------------------------------------------
-
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]
______________________________________________________________________
_____
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo!
Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
---------------------------------------------------------------------
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]
