You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Carsten Ziegeler <cz...@apache.org> on 2014/03/12 17:24:48 UTC
Versioning of oak-jcr?
Hi,
I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
(trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
between the 0.16 release and trunk.
Unfortunately that's not true, as my code does not compile with 0.16, so I
guess the export version needs to be updated
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Versioning of oak-jcr?
Posted by Julian Sedding <js...@gmail.com>.
... to the Felix *project*. (sorry for the typo)
On Thu, Mar 13, 2014 at 3:11 PM, Julian Sedding <js...@gmail.com> wrote:
> Hi Felix
>
> We can certainly look into donating the plugin to the Felix plugin.
>
> Regards
> Julian
>
>
> On Thu, Mar 13, 2014 at 11:05 AM, Felix Meschberger <fm...@adobe.com> wrote:
>> Hi Julian
>>
>> Cool !
>>
>> With my Apache Felix hat on: I am pretty sure this project would be interested in a contribution ;-)
>>
>> Regards
>> Felix
>>
>> Am 13.03.2014 um 10:51 schrieb Julian Sedding <js...@gmail.com>:
>>
>>> To mitigate such issues, I have developed a
>>> baselining-maven-plugin[0], which leverages the baselining feature of
>>> bnd in order to check that package exports are correctly versioned
>>> according to semantic versioning guidelines.
>>>
>>> If there is interest, I'd be happy to provide a patch for the Oak project.
>>>
>>> Regards
>>> Julian
>>>
>>> [0] https://github.com/code-distillery/baselining-maven-plugin
>>>
>>>
>>> On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>>>> Hi,
>>>>
>>>> I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
>>>> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
>>>> between the 0.16 release and trunk.
>>>> Unfortunately that's not true, as my code does not compile with 0.16, so I
>>>> guess the export version needs to be updated
>>>>
>>>> Carsten
>>>>
>>>> --
>>>> Carsten Ziegeler
>>>> cziegeler@apache.org
>>
Re: Versioning of oak-jcr?
Posted by Julian Sedding <js...@gmail.com>.
Hi Felix
We can certainly look into donating the plugin to the Felix plugin.
Regards
Julian
On Thu, Mar 13, 2014 at 11:05 AM, Felix Meschberger <fm...@adobe.com> wrote:
> Hi Julian
>
> Cool !
>
> With my Apache Felix hat on: I am pretty sure this project would be interested in a contribution ;-)
>
> Regards
> Felix
>
> Am 13.03.2014 um 10:51 schrieb Julian Sedding <js...@gmail.com>:
>
>> To mitigate such issues, I have developed a
>> baselining-maven-plugin[0], which leverages the baselining feature of
>> bnd in order to check that package exports are correctly versioned
>> according to semantic versioning guidelines.
>>
>> If there is interest, I'd be happy to provide a patch for the Oak project.
>>
>> Regards
>> Julian
>>
>> [0] https://github.com/code-distillery/baselining-maven-plugin
>>
>>
>> On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>>> Hi,
>>>
>>> I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
>>> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
>>> between the 0.16 release and trunk.
>>> Unfortunately that's not true, as my code does not compile with 0.16, so I
>>> guess the export version needs to be updated
>>>
>>> Carsten
>>>
>>> --
>>> Carsten Ziegeler
>>> cziegeler@apache.org
>
Re: Versioning of oak-jcr?
Posted by Felix Meschberger <fm...@adobe.com>.
Hi Julian
Cool !
With my Apache Felix hat on: I am pretty sure this project would be interested in a contribution ;-)
Regards
Felix
Am 13.03.2014 um 10:51 schrieb Julian Sedding <js...@gmail.com>:
> To mitigate such issues, I have developed a
> baselining-maven-plugin[0], which leverages the baselining feature of
> bnd in order to check that package exports are correctly versioned
> according to semantic versioning guidelines.
>
> If there is interest, I'd be happy to provide a patch for the Oak project.
>
> Regards
> Julian
>
> [0] https://github.com/code-distillery/baselining-maven-plugin
>
>
> On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>> Hi,
>>
>> I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
>> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
>> between the 0.16 release and trunk.
>> Unfortunately that's not true, as my code does not compile with 0.16, so I
>> guess the export version needs to be updated
>>
>> Carsten
>>
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
Re: Versioning of oak-jcr?
Posted by Julian Sedding <js...@gmail.com>.
I created https://issues.apache.org/jira/browse/OAK-1536 with a patch attached.
Regards
Julian
On Thu, Mar 13, 2014 at 11:03 AM, Michael Dürig <md...@apache.org> wrote:
>
> On 13.3.14 10:51 , Julian Sedding wrote:
>>
>> To mitigate such issues, I have developed a
>> baselining-maven-plugin[0], which leverages the baselining feature of
>> bnd in order to check that package exports are correctly versioned
>> according to semantic versioning guidelines.
>>
>> If there is interest, I'd be happy to provide a patch for the Oak project.
>
>
> Oh yes please!
>
> Michael
>
>
>>
>> Regards
>> Julian
>>
>> [0] https://github.com/code-distillery/baselining-maven-plugin
>>
>>
>> On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org>
>> wrote:
>>>
>>> Hi,
>>>
>>> I just noticed that the api exported by the oak-jcr bundle in trunk is
>>> 0.16
>>> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't
>>> changed
>>> between the 0.16 release and trunk.
>>> Unfortunately that's not true, as my code does not compile with 0.16, so
>>> I
>>> guess the export version needs to be updated
>>>
>>> Carsten
>>>
>>> --
>>> Carsten Ziegeler
>>> cziegeler@apache.org
Re: Versioning of oak-jcr?
Posted by Michael Dürig <md...@apache.org>.
On 13.3.14 10:51 , Julian Sedding wrote:
> To mitigate such issues, I have developed a
> baselining-maven-plugin[0], which leverages the baselining feature of
> bnd in order to check that package exports are correctly versioned
> according to semantic versioning guidelines.
>
> If there is interest, I'd be happy to provide a patch for the Oak project.
Oh yes please!
Michael
>
> Regards
> Julian
>
> [0] https://github.com/code-distillery/baselining-maven-plugin
>
>
> On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>> Hi,
>>
>> I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
>> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
>> between the 0.16 release and trunk.
>> Unfortunately that's not true, as my code does not compile with 0.16, so I
>> guess the export version needs to be updated
>>
>> Carsten
>>
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
Re: Versioning of oak-jcr?
Posted by Julian Sedding <js...@gmail.com>.
To mitigate such issues, I have developed a
baselining-maven-plugin[0], which leverages the baselining feature of
bnd in order to check that package exports are correctly versioned
according to semantic versioning guidelines.
If there is interest, I'd be happy to provide a patch for the Oak project.
Regards
Julian
[0] https://github.com/code-distillery/baselining-maven-plugin
On Wed, Mar 12, 2014 at 5:24 PM, Carsten Ziegeler <cz...@apache.org> wrote:
> Hi,
>
> I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
> (trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
> between the 0.16 release and trunk.
> Unfortunately that's not true, as my code does not compile with 0.16, so I
> guess the export version needs to be updated
>
> Carsten
>
> --
> Carsten Ziegeler
> cziegeler@apache.org