Hmm, so the name in the pom.xml needs to be the same as the prefix used
for the jira version?
In any case here is the stacktrace:
java.lang.IllegalArgumentException: No version found with name Default
POST Servlets 2.3.34
at
org.apache.sling.cli.impl.jira.VersionClient.lambda$find$1(VersionClient.java:84)
at java.base/java.util.Optional.orElseThrow(Unknown Source)
at
org.apache.sling.cli.impl.jira.VersionClient.find(VersionClient.java:84)
at
org.apache.sling.cli.impl.release.PrepareVoteEmailCommand.lambda$run$0(PrepareVoteEmailCommand.java:116)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
at java.base/java.util.Iterator.forEachRemaining(Unknown Source)
at
java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown
Source)
at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown
Source)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
at
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown
Source)
at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown
Source)
at java.base/java.util.stream.ReferencePipeline.collect(Unknown
Source)
at
org.apache.sling.cli.impl.release.PrepareVoteEmailCommand.run(PrepareVoteEmailCommand.java:117)
at picocli.CommandLine.executeUserObject(CommandLine.java:1687)
at picocli.CommandLine.access$900(CommandLine.java:146)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2059)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2026)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1893)
at picocli.CommandLine.execute(CommandLine.java:1822)
at
org.apache.sling.cli.impl.CommandProcessor.runCommand(CommandProcessor.java:110)
at
org.apache.sling.cli.impl.ExecutionTrigger.lambda$activate$0(ExecutionTrigger.java:33)
at java.base/java.lang.Thread.run(Unknown Source)
Carsten
Am 02.10.2019 um 11:57 schrieb Robert Munteanu:
Hi Carsten,
On Wed, 2019-10-02 at 07:52 +0200, Carsten Ziegeler wrote:
Hi
I tried the new docker based committer tools for the servlets post
release, but didn't get very far.
The error I got is :
java.lang.IllegalArgumentException: No version found with name
Default
POST Servlets 2.3.34
I'm unsure how to fix this - the comment in the staging repository
contains the correct jira release version; however this seems to be
taken from the pom?
Yes, I think this is due to a recent change that tries to map artifacts
to Jira versions using the pom.xml name.
I think at least we should make the error message more straightforward.
Since you can't change the name in the staged pom.xml the committer
tools will only be usable for the next release, after we align the
pom.xml name and the Jira version.
Can you reply with a stack trace or file a Jira issue with it? I'd like
to make the error message self-explanatory.
Thanks,
Robert
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
