Re: jansi 2.x and jline 3.x

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


On Tue, Dec 15, 2020 at 4:36 PM Jerry James <loganjerry@xxxxxxxxx> wrote:
> On Tue, Dec 15, 2020 at 6:57 AM Mikolaj Izdebski <mizdebsk@xxxxxxxxxx> wrote:
> > Duplicate osgi provides are generally not a problem. Duplicate mvn
> > provides are, but there is a solution to this problem: compat
> > packages, see
> > Compat packages have different mvn provides, eg.
> > mvn(org.fusesource.jansi:jansi:1) = 1.18
> Yes, Severin pointed that out, so I have updated the COPR accordingly.
> This means little changes and rebuilds for packages that consume jansi
> 1.x and jline 2.x, which I have also built in COPR:
> > My preference would be to update jansi/jline to latest upstream
> > versions and introduce compat packages jansi1/jline2 if necessary.
> Thanks for the input, Mikolaj.  Since that seems to be everybody's
> preference, I will go with that plan.  Regards,

Thanks for working on this! As main admin for jansi/-native, I approve
of this approach.
Do you plan to submit PRs for jansi and jline? At least creating the
compat packages is at least easy.

java-devel mailing list -- java-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to java-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:

[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux