Bug 241122 - [PATCH] java/jakarta-bcel move to Apache and update to version 6.4.1
Summary: [PATCH] java/jakarta-bcel move to Apache and update to version 6.4.1
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-java mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-07 22:23 UTC by Pedro F. Giffuni
Modified: 2019-10-08 17:57 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (java)


Attachments
update diff (without moving yet the directory) (2.11 KB, patch)
2019-10-07 22:23 UTC, Pedro F. Giffuni
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro F. Giffuni freebsd_committer 2019-10-07 22:23:24 UTC
Created attachment 208159 [details]
update diff (without moving yet the directory)

The ASF retired Jakarta on 2011 and now bcel is part of Apache Commons.

- Update to the latest version.
- Change the prefix from jakarta- to apache-.
  This should involve renaming also the directory.
Comment 1 Michael Osipov 2019-10-08 07:58:33 UTC
What is the purpose of maintaining this port at all? 99% of all users will request it from Maven Central anyway.
Comment 2 Pedro F. Giffuni freebsd_committer 2019-10-08 15:35:04 UTC
(In reply to Michael Osipov from comment #1)

Maven causes problems when building things in the cluster and packaging them.
OTOH, nothing depends on this ports so there is little interest in maintaining it.

In any case since we carry it, I'd rather prefer we carry a recent version rather than the old one.
Comment 3 Michael Osipov 2019-10-08 17:49:57 UTC
(In reply to Pedro F. Giffuni from comment #2)

I did not mean to build it with Maven, but other consumers will reference BCEL through MAven Central. No one will manually handle the JAR.

If no other port depends on it, don't put anymore effort into it, deprecate and remove by the end of the year.
Comment 4 Pedro F. Giffuni freebsd_committer 2019-10-08 17:57:13 UTC
(In reply to Michael Osipov from comment #3)

The decision to deprecate it is not mine to make: java@ is the maintainer. If the maintainer wants to deprecate it, I do request it is updated first to have an updated record in case it needs to be resurrected at a later time.