Having a XPathChoiceListProvider would allow to grab certain entries from an XML file.
In our case we want to grab all Maven provile ids because those profile ids are the name of the environments where you can deploy an artifact to.
The selected entry could later be passed to the Maven build by something like that "-P${profileId}"...
As filename any file should be possible, relative to the job's workspace root - not only pom.xml.
Originally reported by mirumpf, imported from: Implement a XPathChoiceListProvider so that entries could be read from the pom.xml for example
- status: Open
- priority: Major
- component(s): extensible-choice-parameter-plugin
- resolution: Unresolved
- votes: 1
- watchers: 2
- imported: 20251216-182730
Raw content of original issue
Having a XPathChoiceListProvider would allow to grab certain entries from an XML file.
In our case we want to grab all Maven provile ids because those profile ids are the name of the environments where you can deploy an artifact to.
The selected entry could later be passed to the Maven build by something like that "-P${profileId}"...
As filename any file should be possible, relative to the job's workspace root - not only pom.xml.
Having a XPathChoiceListProvider would allow to grab certain entries from an XML file.
In our case we want to grab all Maven provile ids because those profile ids are the name of the environments where you can deploy an artifact to.
The selected entry could later be passed to the Maven build by something like that "-P${profileId}"...
As filename any file should be possible, relative to the job's workspace root - not only pom.xml.
Originally reported by mirumpf, imported from: Implement a XPathChoiceListProvider so that entries could be read from the pom.xml for example
Raw content of original issue