git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lang3] Problem with the OSGi metadata: Bundle-SymbolicName / breaking change between 3.7 and 3.8


Do we have a JIRA for this?

> On Sep 19, 2018, at 7:59 AM, Benedikt Ritter <britter@xxxxxxxxxx> wrote:
> 
> Hi,
> 
> Am Mi., 19. Sep. 2018 um 13:44 Uhr schrieb Rob Tompkins <chtompki@xxxxxxxxx <mailto:chtompki@xxxxxxxxx>
>> :
> 
>> 
>> 
>>> On Sep 19, 2018, at 4:25 AM, Benedikt Ritter <britter@xxxxxxxxxx <mailto:britter@xxxxxxxxxx>> wrote:
>>> 
>>> ... bringing this to the developers list...
>>> 
>>> I think this issue has been caused by this change:
>>> 
>> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=1833874&r2=1833926 <http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=1833874&r2=1833926>
>> 
>> Do we roll a 3.8.1?
>> 
> 
> I plan to do so once I've released commons-csv 1.6. We probably need to
> create 3.8.1 based on the 3.8 release tag because we already introduced the
> Java 8 changes on the master branch and I don't think those changes should
> be included in a patch release.
> 
> Regards,
> Benedikt
> 
> 
>> 
>> -Rob
>>> 
>>> I don't understand why an update of the commons build plugin had to
>> change
>>> the OSGi meta data being generated. Maybe the change
>>> to commons.osgi.symbolicName was by accident? Can it be reverted?
>>> 
>>> Regards,
>>> Benedikt
>>> 
>>> Am Do., 6. Sep. 2018 um 21:35 Uhr schrieb P. Ottlinger <
>>> pottlinger@xxxxxxxxxx>:
>>> 
>>>> Hi,
>>>> 
>>>> thanks for quick response ...
>>>> 
>>>>> Am 06.09.2018 um 21:24 schrieb Oliver Heger:
>>>>> So opening a ticket in Jira would be the correct action to take.
>>>> 
>>>> https://issues.apache.org/jira/browse/LANG-1419
>>>> 
>>>> Done :-) Hopefully I didn't miss any important stuff in Jira.
>>>> 
>>>> Cheers,
>>>> Phil
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxx
>>>> For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxx
>>>> 
>>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx <mailto:dev-unsubscribe@xxxxxxxxxxxxxxxxxx>
>> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx <mailto:dev-help@xxxxxxxxxxxxxxxxxx>