[
https://issues.apache.org/jira/browse/JEXL-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255105#comment-17255105
]
Garret Wilson commented on JEXL-338:
------------------------------------
It works!! I was able to plug in my own resolver and access properties from my
own object type, which has specialized property access methods.
JEXL may work as-is for my _initial_ needs, but I'd hate to see the project go
stale, and eventually I'll probably need support for newer Java features (e.g.
streams and {{Optional}}) if they aren't supported already.
So if you still need a Release Manager, I would be willing to step forward. If
the project has some specialized, complicated build requirements (such as
installing a C++ build subsystem or something) I probably wouldn't have the
time, but if this is just a straightforward Maven Java project, I'd love to
help. I can make sure the POM is tidied up, make sure the dependencies are
up-to-date, go through the checklist, and get a new version up on Maven
Central. If everything goes well, I should be able to continue in the role for
the near future for other releases.
How would you like to proceed?
{quote}There one user's mailing list for all of Apache Commons and one
developer's mailing list for all of Apache Commons.{quote}
I just saw that there is a new [GitHub
Discussions|https://docs.github.com/en/free-pro-team@latest/discussions]
feature for the GitHub repository, and it seems ideal for discussions such as
these. Have you looked into turning on something like that?
If absolutely necessary I can subscribe to the Apache Commons mailing lists,
but being bombarded with irrelevant emails from unrelated projects is not ideal.
> Release 3.2 to Maven Central
> ----------------------------
>
> Key: JEXL-338
> URL: https://issues.apache.org/jira/browse/JEXL-338
> Project: Commons JEXL
> Issue Type: Wish
> Environment: Maven, Eclipse-GIT, Maven Central.
> Reporter: Sylke Soong
> Priority: Critical
> Labels: maven
>
> Similar to JEXL-220.
> JEXL github homepage [https://github.com/apache/commons-jexl] recommends
> {noformat}
> <dependency>
> <groupId>org.apache.commons</groupId>
> <artifactId>commons-jexl3</artifactId>
> <version>3.2</version>
> </dependency>{noformat}
> But Maven central does not have it.. EGIT croaks artefact jar not foundr,
> when jexl 3.2 dependency is in the pom.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
