[
https://issues.apache.org/jira/browse/JEXL-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257477#comment-17257477
]
Garret Wilson commented on JEXL-338:
------------------------------------
I'm still waiting to hear back on what the release process is and what the next
steps are to get a release out.
I've found this [Apache Commons – Preparations for a
Release|https://commons.apache.org/releases/prepare.html] page. Is that the
most up-to-date documentation? It seems still to refer to Subversion. Surely
you're releasing from a Git repository now (I would hope)?
And who managed the last release? It would be nice to at least touch base with
them to see what the major pain points are.
> 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)
