Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

Use maven-metadata.xml tag for version polling #13

Merged
merged 5 commits into from
Apr 27, 2017

Conversation

piotr-kaczmarczyk
Copy link
Contributor

Implement additional parameter for polling latest version from specified tag inside maven-metadata.xml

The name of the tag can be configured in the GoCD UI.
If there none tag specified or the specified tag can not be found in maven-metadata.xm, the poller behaves as before: look for all available versions and take the greatest one
If one enters a tag name (e.g. release) the version inside this xml tag of maven-metadata.xml is taken.

…ied tag inside maven-metadata.xml

The name of the tag can be configured in the GoCD UI.
If there none tag specified or the specified tag can not be found in maven-metadata.xm, the poller behaves as before: look for all available versions and take the greatest one
If one enters a tag name (e.g. release) the version inside this xml tag of maven-metadata.xml is taken.
…ied tag inside maven-metadata.xml

The name of the tag can be configured in the GoCD UI.
If there none tag specified or the specified tag can not be found in maven-metadata.xm, the poller behaves as before: look for all available versions and take the greatest one
If one enters a tag name (e.g. release) the version inside this xml tag of maven-metadata.xml is taken.
@iatanasov
Copy link

Hi ,
Any chance getting this merged ?

@bitionaire
Copy link
Contributor

@netdevfighter can you have a look? I don't have the permissions :)

@netdevfighter netdevfighter merged commit 379b0ec into master Apr 27, 2017
@netdevfighter netdevfighter deleted the use-tag-for-version-polling branch April 27, 2017 05:40
@netdevfighter
Copy link
Contributor

Thanks for contributed go-maven-poller. The new release 1.2.0 is ready for download.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants