With the next release of Maven the current maven-gpg-plugin will become useless.
With the build//consumer pom, the local pom will be different compared to the
uploaded pom.
However, the maven-gpg-plugin now uses the pom.xml of the local project.
(btw, the plugin uses the gpg commandline with a
dadon-david commented on pull request #200:
URL: https://github.com/apache/maven-site/pull/200#issuecomment-695782987
Hi @elharo,
So IntelliJ fooled me :p
Thanks for your answer, I will open a ticket on their side,
Have a nice day,
elharo commented on pull request #200:
URL: https://github.com/apache/maven-site/pull/200#issuecomment-695782562
The problem is in IntelliJ. It's assuming things about the relationships
between namespaces and schemas that simply aren't true. The Maven code is
correct.
dadon-david commented on pull request #200:
URL: https://github.com/apache/maven-site/pull/200#issuecomment-695781151
Hi @michael-o :)
Thank you for your rapid response,
Maybe I didn't explained my PR enough, sorry if this is the case.
On the existing
michael-o closed pull request #200:
URL: https://github.com/apache/maven-site/pull/200
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
michael-o commented on pull request #200:
URL: https://github.com/apache/maven-site/pull/200#issuecomment-695752443
Learn namespace first.
This is an automated message from the Apache Git Service.
To respond to the message,
