[
https://issues.apache.org/jira/browse/JEXL-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255128#comment-17255128
]
Garret Wilson commented on JEXL-338:
------------------------------------
{quote}Not sure what new features you want to see integrated that need
functionality/code changes …{quote}
I'm not sure, either; I was just making a guess from experience. (For example,
[Thymeleaf still doesn't support
{{Optional<>}}|https://github.com/thymeleaf/thymeleaf/issues/672] in a natural
way.)
{quote}… describing them as JIRA enhancements would be the (kinda) standard
way.{quote}
For sure! I mentioned this as another reason why I'd be interested in helping
make sure JEXL is kept current.
{quote}If you havent participated in releasing Apache (Commons?) projects
before though, it might be a longer and windier road than you think it
is.{quote}
I have not participated in releasing any Apache projects before, no. Is there
documentation on what I can expect so I can research what I might be getting
into?
> 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)
