Re: Oops, groovy-3.0.0-beta-3.jar has a non OSGi valid version number!

[Paul King <pa...@asert.com.au>]

Yes oops. I didn't realise we hadn't done the TODO mentioned here yet:
https://github.com/apache/groovy-release/blob/master/gradle/phase1.gradle#L126


 So to confirm, if it was 3.0.0.beta-3 that would have been fine. Correct?

Cheers, Paul.


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Sep 1, 2019 at 2:49 AM Tommy Svensson <to...@natusoft.se> wrote:

> Hmm, got the following from apache karaf log:
>
> 2019-08-31 18:32:54 ERROR F​a​i​l​e​d​ ​t​o​ ​i​n​s​t​a​l​l​
> ​a​r​t​i​f​a​c​t​:​
> ​/​v​a​g​r​a​n​t​/​v​a​g​r​a​n​t​/​d​e​p​l​o​y​/​g​r​o​o​v​y​-​3​.​0​.​0​-​b​e​t​a​-​3​.​j​a​r Apache
> Felix File Install <http://192.168.72.60:8181/system/console/bundles/10> java.lang.IllegalArgumentException:
> invalid version "3.0.0-beta-3": non-numeric "0-beta-3"
>
> It correctly complains that 3.0.0-beta-3 is an invalid version number due
> to not being 100% numeric. Otherwise the jar is an OSGi bundle, but it will
> not deploy due to version number.
>
> Could you consider using OSGi valid version numbers for betas ?
>
> Yes, it is possible to unpack the jar, edit the version in MANIFEST.MF,
> and repackage to jar again.
>
> Best Regards,
> Tommy Svensson
>
>
>

Fwd: Oops, groovy-3.0.0-beta-3.jar has a non OSGi valid version number!

[Paul King <pa...@asert.com.au>]

Forwarding to list ...

---------- Forwarded message ---------
From: Tommy Svensson <to...@natusoft.se>
Date: Sun, Sep 1, 2019 at 7:34 PM
Subject: Re: Oops, groovy-3.0.0-beta-3.jar has a non OSGi valid version
number!
To: <pa...@asert.com.au>


Hi Paul,

Currently the micro part of the version number is "0-beta-3" and there is
no qualifier. Doing that change would make the "micro" part of the version
"0" and the "beta-3" would become a qualifier. Looking at
https://www.osgi.org/wp-content/uploads/SemanticVersioning.pdf that change
looks correct.

Best Regards,
Tommy

Från: Paul King <pa...@asert.com.au> <pa...@asert.com.au>
Svara: paulk@asert.com.au <pa...@asert.com.au> <pa...@asert.com.au>
Datum: 1 september 2019 at 03:09:50
Till: users@groovy.apache.org <us...@groovy.apache.org>
<us...@groovy.apache.org>
Ämne:  Re: Oops, groovy-3.0.0-beta-3.jar has a non OSGi valid version
number!

Yes oops. I didn't realise we hadn't done the TODO mentioned here yet:
https://github.com/apache/groovy-release/blob/master/gradle/phase1.gradle#L126


 So to confirm, if it was 3.0.0.beta-3 that would have been fine. Correct?

Cheers, Paul.


<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#m_4829187668084820927_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Sep 1, 2019 at 2:49 AM Tommy Svensson <to...@natusoft.se> wrote:

> Hmm, got the following from apache karaf log:
>
> 2019-08-31 18:32:54 ERROR Failed to install artifact:
> /vagrant/vagrant/deploy/groovy-3.0.0-beta-3.jar Apache Felix File Install
> <http://192.168.72.60:8181/system/console/bundles/10> java.lang.IllegalArgumentException:
> invalid version "3.0.0-beta-3": non-numeric "0-beta-3"
>
> It correctly complains that 3.0.0-beta-3 is an invalid version number due
> to not being 100% numeric. Otherwise the jar is an OSGi bundle, but it will
> not deploy due to version number.
>
> Could you consider using OSGi valid version numbers for betas ?
>
> Yes, it is possible to unpack the jar, edit the version in MANIFEST.MF,
> and repackage to jar again.
>
> Best Regards,
> Tommy Svensson
>
>
>