Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The HPI version in use incorrectly sets the metadata for Hudson-Version to null, which causes the plugin manager to pull in SVN, Maven and CVS as dependencies. If I want Maven plugin to use token-macro-plugin, then this generates a nasty circular dependency. Can be removed when HPI is released and parent pom has been updated. Signed-off-by: Nigel Magnay <nigel.magnay@gmail.com>
- Loading branch information
cfe107d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't you set the parent version above to 1.399 instead of this change?
cfe107d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think so - the required fix is in hpi plugin 1.65-SNAPSHOT.
Once that is released properly as 1.65, it will need to be added into the plugin master pom. Then it can be set to that and removed.
In the interim, without it there's potential nasty circular dependencies as the metadata gets incorrectly set as
Hudson-Version: null
which jenkins interprets as v < 1.286 ish.
cfe107d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you point to the commit with the fix? afaik, Hudson-Version: null was fixed in maven-hpi-plugin 1.64 which is already used by parent/plugin pom 1.399
jenkinsci/maven-hpi-plugin@maven-hpi-plugin-1.63...maven-hpi-plugin-1.64
jenkinsci/maven-hpi-plugin@c3a3a98
cfe107d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agh; you're right, I tried building against 1.399 and it's fine.
IntelliJ incorrectly pointed me at 255348b, which is the direct ancestor, not the last place it changed.
Can you apply a change to update to 1.399 (it seems peverse to me to issue a pull request ;-) )