Matthias, I can confirm it's a problem with Maven 3.6.3. According to the integration tests, Maven 3.6.0 should work fine. Fix is on its way.
I downgraded to Maven 3.5.4 and I could create a new recipe successfully
:-)
thanks
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
> On Jan 17, 2020, at 15:08, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
>
>> On Jan 17, 2020, at 11:05, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
>>
>> junit4 (master *)]$ mvn ebr:create-recipe -DgroupId=junit -DartifactId=junit -Dversion=4.13.0 -DbundleSymbolicName=org.junit
>
> So the code in question is passing a blank version string to Maven on purpose. We want to discover the latest version of an artifact. It seems that this is no longer correct. I'll investigate a fix. I think that we can also skip this in case a specific version is passed on the command line.
>
> -Gunnar
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orbit-dev
