You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Julian Reschke <re...@apache.org> on 2026/07/31 12:28:16 UTC
Linking to changes in Commons components
Hi there,
what's the best way to link (as in JIRA) to changes in Commons
components, such as IO?
AFAICT, only *bugs* have a Jira ticket.
The Release Notes (as in
<https://commons.apache.org/proper/commons-io/changes.html#a2.22.0>)
list the changes, but the individual changes do not have a unique
identifier.
I'm currently using a link into Github - such as
<https://github.com/apache/commons-io/blob/274cd956de35dc664a2caca200c2d73b2b37efdc/RELEASE-NOTES.txt#L48>
- is there a better way to do this?
(Context: <https://issues.apache.org/jira/browse/SLING-13268>).
Best regards, Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Linking to changes in Commons components
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Aug 4, 2026, 12:05 Julian Reschke <re...@apache.org> wrote:
>
>
> Am 31.07.2026 um 14:33 schrieb Gary Gregory:
> > On Fri, Jul 31, 2026 at 8:28 AM Julian Reschke <re...@apache.org>
> wrote:
> >>
> >> Hi there,
> >>
> >> what's the best way to link (as in JIRA) to changes in Commons
> >> components, such as IO?
> >>
> >> AFAICT, only *bugs* have a Jira ticket.
> >>
> >> The Release Notes (as in
> >> <https://commons.apache.org/proper/commons-io/changes.html#a2.22.0>)
> >> list the changes, but the individual changes do not have a unique
> >> identifier.
> >
> > It all depends on what your definition of "individual changes" is. For
> > commits, you can ask git with "git log" or you can ask GitHub, for
> > example:
> >
> >
> https://github.com/apache/commons-io/compare/rel/commons-io-2.21.0...rel/commons-io-2.22.0
> > ...
>
> Yes, I'm aware of that :-)
>
> That said, the granularity of Git commits is not ideal.
>
> So, what about giving in each line a stable identifier (could be
> auto-generated), so one could link *into* the change log file? Such as
> "
> https://commons.apache.org/proper/commons-io/changes.html#a2.22.0-change-1
> "?
>
That's a cool and interesting idea! It could be done with HTML anchors, but
these must generated from the Maven changes plug-in we use. It sounds
simple enough ;) I guess you'll have to create a PR against the plugin.
Gary
>
> ...and - while I'm writing this - I realize that *something* like that
> only (sort of) works:
>
> <
> https://commons.apache.org/proper/commons-io/changes.html##:~:text=BoundedReader%20now%20extends%20ProxyReader
> <https://commons.apache.org/proper/commons-io/changes.html#%23:~:text=BoundedReader%20now%20extends%20ProxyReader>
> >
>
>
> Best regards, Julian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: Linking to changes in Commons components
Posted by Julian Reschke <re...@apache.org>.
Am 31.07.2026 um 14:33 schrieb Gary Gregory:
> On Fri, Jul 31, 2026 at 8:28 AM Julian Reschke <re...@apache.org> wrote:
>>
>> Hi there,
>>
>> what's the best way to link (as in JIRA) to changes in Commons
>> components, such as IO?
>>
>> AFAICT, only *bugs* have a Jira ticket.
>>
>> The Release Notes (as in
>> <https://commons.apache.org/proper/commons-io/changes.html#a2.22.0>)
>> list the changes, but the individual changes do not have a unique
>> identifier.
>
> It all depends on what your definition of "individual changes" is. For
> commits, you can ask git with "git log" or you can ask GitHub, for
> example:
>
> https://github.com/apache/commons-io/compare/rel/commons-io-2.21.0...rel/commons-io-2.22.0
> ...
Yes, I'm aware of that :-)
That said, the granularity of Git commits is not ideal.
So, what about giving in each line a stable identifier (could be
auto-generated), so one could link *into* the change log file? Such as
"https://commons.apache.org/proper/commons-io/changes.html#a2.22.0-change-1"?
...and - while I'm writing this - I realize that *something* like that
only (sort of) works:
<https://commons.apache.org/proper/commons-io/changes.html##:~:text=BoundedReader%20now%20extends%20ProxyReader>
Best regards, Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Linking to changes in Commons components
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, Jul 31, 2026 at 8:28 AM Julian Reschke <re...@apache.org> wrote:
>
> Hi there,
>
> what's the best way to link (as in JIRA) to changes in Commons
> components, such as IO?
>
> AFAICT, only *bugs* have a Jira ticket.
>
> The Release Notes (as in
> <https://commons.apache.org/proper/commons-io/changes.html#a2.22.0>)
> list the changes, but the individual changes do not have a unique
> identifier.
It all depends on what your definition of "individual changes" is. For
commits, you can ask git with "git log" or you can ask GitHub, for
example:
https://github.com/apache/commons-io/compare/rel/commons-io-2.21.0...rel/commons-io-2.22.0
Gary
>
> I'm currently using a link into Github - such as
> <https://github.com/apache/commons-io/blob/274cd956de35dc664a2caca200c2d73b2b37efdc/RELEASE-NOTES.txt#L48>
> - is there a better way to do this?
>
> (Context: <https://issues.apache.org/jira/browse/SLING-13268>).
>
> Best regards, Julian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org