Issue2182

classification
Title: Build Jython with Gradle
Type: rfe Severity: normal
Components: Core Versions: Jython 2.7
Milestone: Jython 2.7.2
process
Status: open Resolution: accepted
Dependencies: Superseder:
Assigned To: jeff.allen Nosy List: darjus, hjacobs, jeff.allen, mbooth, pdina, zyasoft
Priority: urgent Keywords:

Created on 2014-07-26.10:58:29 by hjacobs, last changed 2018-05-29.10:50:38 by jeff.allen.

Messages
msg8894 (view) Author: Henning Jacobs (hjacobs) Date: 2014-07-26.10:58:29
Jython relies on "ant" for the build process and developers have to configure their IDEs individually to import/use the project.
I would like to migrate Jython to the standard Maven structure, this would make it much easier to get started (pom.xml can easily be opened out-of-the-box in Eclipse, Netbeans, IntelliJ). We can still use the ant build.xml for the more complicated or "special" parts (it's easy to call ant from Maven).
msg8895 (view) Author: Jim Baker (zyasoft) Date: 2014-07-27.21:11:00
This is a good idea!
msg10557 (view) Author: Jim Baker (zyasoft) Date: 2015-12-28.18:35:06
I believe the general consensus is that we will use Gradle instead, especially since it's also easy to use Ant tasks (such as our expose processor for Python types) from Gradle.

Maybe we can do this as the first task for 2.7.2?
msg10580 (view) Author: Jim Baker (zyasoft) Date: 2016-01-03.16:46:25
Given the recent switch of the repo from hg.python.org to GitHub, we need to get this build change done sooner (2.7.2) than later. See http://sourceforge.net/p/jython/mailman/message/34736089/
msg10652 (view) Author: Jim Baker (zyasoft) Date: 2016-01-15.15:22:34
Top priority for 2.7.2, so marking accordingly
msg10825 (view) Author: Jim Baker (zyasoft) Date: 2016-03-18.20:11:03
Also discussed here: https://github.com/jythontools/jython/issues/11
msg12005 (view) Author: Jeff Allen (jeff.allen) Date: 2018-05-29.10:50:37
Users will continue to depend on the JARs we currently build using Ant, and the installer, which takes the approach that all dependencies are bundled in javalib (or the standalone JAR). So it is clear that we need to continue to deliver that. Call this the "bundled" product.

I take this issue to be a request that we build (using Gradle) an artifact that can be cited as a dependency by other projects, and cites its dependencies in turn. And this is an enhancement that stands alongside the established, bundled product. I imagine it would be referenced by the co-ordinates "org.python:jython:2.7.2". Is this a reasonable interpretation?

It seems feasible for me to try this, leaving the Ant build exactly as it is and starting from scratch with Gradle. If it fails we haven't broken anything. One would run both builds to release Jython.

There will be a problem keeping the versions of JARs in sync between the two builds, that we will want to solve eventually (I predict), by moving production of both to Gradle: not for 2.7.2, though.
History
Date User Action Args
2018-05-29 10:50:38jeff.allensetassignee: jeff.allen
type: behaviour -> rfe
messages: + msg12005
nosy: + jeff.allen
2016-03-18 20:11:03zyasoftsetmessages: + msg10825
2016-01-15 15:22:34zyasoftsetpriority: high -> urgent
messages: + msg10652
2016-01-07 03:02:11zyasoftsettitle: Build Jython using Gradle -> Build Jython with Gradle
2016-01-03 16:46:25zyasoftsetmessages: + msg10580
2015-12-28 18:35:06zyasoftsetnosy: + darjus
title: Jython should support Maven build with pom.xml -> Build Jython using Gradle
messages: + msg10557
milestone: Jython 2.7.1 -> Jython 2.7.2
2015-04-20 21:02:55zyasoftsetresolution: accepted
milestone: Jython 2.7.1
2015-02-13 17:50:27zyasoftsetpriority: high
2014-11-09 12:49:58mboothsetnosy: + mbooth
2014-08-18 11:19:49pdinasetnosy: + pdina
2014-07-27 21:11:00zyasoftsetnosy: + zyasoft
messages: + msg8895
2014-07-26 10:58:29hjacobscreate