Hi,
Yes, this works. Thank you. :)
A followup question... running whole build like this is a bit clunky.
Basically I have to execute:
mvn clean install
cz.fiisch.maven.plugin.deploy.askpass:askpass-deploy-plugin:1.0-SNAPSHOT:askpass
deploy
to do the whole build. This should be ok as long
Hi,
Thanks for the hint.
The wiki page you mentioned was the first thing I read when I started.
It's worth to say that it states only one explicit requirement: "Do not
name your plugin maven-SOMETHING-plugin."
The phrase You will typically name your
plugin|-maven-plugin|. does not sound as a
Hi Peter
Your plugin name doesn't meet maven plugin name requirements.
Maybe some maven plugin name patterns are hardcoded in maven code.
Please try rename your plugin to something as askpass-maven-plugin.
https://maven.apache.org/guides/plugin/guide-java-plugin-development.html
śr., 20 maj
Hi Petr,
If you want to specifically invoke your plugin, you would need
mvn
cz.fiisch.maven.plugin.deploy.askpass:askpass-deploy-plugin:1.0-SNAPSHOT:askpass
(so not mvn deploy:askpass - this looks for the askpass goal in the
maven-deploy-plugin which doesn't exist)
That said, I would expect
Hi,
Sure thing. :)
I have set of private Maven repos which are readable (writeable) only to
logged-in users.
We need to use login:password credentials because it is a community
version of Nexus and AFAIK it does not allow use of API keys. Accounts
are centralized so this is not the only place
Hi,
This sound interesting. I gave it a try but it didn't work for me. It
even seems that my plugin does not get picked up during "deploy" at all.
I added maven-deploy-plugin to the build config like this:
cz.fiisch.maven.plugin.deploy.askpass
askpass-deploy-plugin
Hi,
On 19.05.20 14:24, Petr Fišer wrote:
Hello,
I am trying to create custom maven plugin. Problem is I need to hook it
up into the "deploy" phase before the default maven-deploy-plugin gets
executed.
The plugin itself seems to be ok - I hooked it up to "package" phase to
verify its working.
Hi Petr,
As far as I know, when two plugins are bound to the same phase, the
order of execution is the same as the order in which you define them in
pom.xml.
So if you want your plugin to be executed before the
maven-deploy-plugin, I guess you'll need to explicitly list the
Hello,
I am trying to create custom maven plugin. Problem is I need to hook it
up into the "deploy" phase before the default maven-deploy-plugin gets
executed.
The plugin itself seems to be ok - I hooked it up to "package" phase to
verify its working. But when trying to get it into "deploy"