Bug 8080 - New <jythonc> task to compile Python code in java bytecode
Summary: New <jythonc> task to compile Python code in java bytecode
Alias: None
Product: Ant
Classification: Unclassified
Component: Optional Tasks (show other bugs)
Version: 1.5
Hardware: Other other
: P3 enhancement with 1 vote (vote)
Target Milestone: ---
Assignee: Ant Notifications List
: 18363 (view as bug list)
Depends on:
Reported: 2002-04-15 00:56 UTC by Cyrille Morvan
Modified: 2008-02-22 12:18 UTC (History)
1 user (show)

WHATSNEW, optionaltasklist.html, defaults.properties (2.33 KB, patch)
2002-04-15 00:58 UTC, Cyrille Morvan
Details | Diff
jakarta-ant\src\main\org\apache\tools\ant\taskdefs\optional\python\Jythonc.java (14.12 KB, text/plain)
2002-04-15 00:59 UTC, Cyrille Morvan
jakarta-ant\docs\manual\OptionalTasks\python.html (8.38 KB, text/html)
2002-04-15 01:00 UTC, Cyrille Morvan

Note You need to log in before you can comment on or make changes to this bug.
Description Cyrille Morvan 2002-04-15 00:56:20 UTC
I think this new task should be part of Ant, because it difficult with Ant 1 to
install a new task (no dynamic load), I hope the problem will be resolve with
Ant 2, and I'm sure there are more Python developers than dotNet developers !

Example : <jythonc home="/usr/jython-2.1/" srcdir="${src}"  > 
   <include name="*.py" /> 
   <exclude name="Test.py" />

Sorry no unit-test, but I can't run unit-test without a correct Jython installation.
Comment 1 Cyrille Morvan 2002-04-15 00:58:06 UTC
Created attachment 1565 [details]
WHATSNEW, optionaltasklist.html, defaults.properties
Comment 2 Cyrille Morvan 2002-04-15 00:59:46 UTC
Created attachment 1566 [details]
Comment 3 Cyrille Morvan 2002-04-15 01:00:32 UTC
Created attachment 1567 [details]
Comment 4 Erik Hatcher 2002-04-15 01:10:56 UTC
Just to clarify: what is so difficult about using <taskdef> in Ant 1.x?  Why is 
having this part of Ant much different than having this task available with 
Jython with an example <taskdef>?
Comment 5 Conor MacNeill 2002-04-15 01:18:02 UTC
A few points.

1. "No dynamic load" - have you looked at the taskdef task? Perhaps you 
mean "No auto load".

2. I would suggest not extending MatchingTask. Instead it would be preferable 
to provide support for filesets with an addFileset() method.

3. I'm not sure I understand the issue with unit tests?

Comment 6 Cyrille Morvan 2002-04-19 02:11:53 UTC
<taskdef> is not cool because you have to download a JAR file, 
put in a directory, and add <taskdef> in your build file
without syntax error. If you want to distribute your build file, 
you must not forget to give the JAR file. 
Yes I would mean "auto load".

Ant is a great tool, but a lot of junior developers prefer to use the one button
click of JBuilder (or worst VStudio).
Ant must progress in its installation and configuration process.

> I would suggest not extending MatchingTask.
I don't understand why. You don't like it ?

Comment 7 Steve Loughran 2002-04-19 04:52:51 UTC
Hmm, two lines of code per build file, versus the support and maintenance we'd 
have to add

but wait a minute, you need jython anyway right? So stick the JAR in your own 
SCM system (like in lib)

<taskdef resource="org.someone.jythontask.properties

And all is well.

FYI we are trying to move away from putting everything in optional.jar and 
move to a world where we can load stuff from jars more easily; once that is 
done we can break up optional jar into pieces anyway. Adding more tasks to ant 
just adds diversionary work.

In particular, for other open source projects we like the tasks to go with the 
projects themselves, if at all possible. Can you get the jython people to take 
this task on board? Then all you need is jython.s own jar. 
Comment 8 Stephane Bailliez 2002-06-23 22:08:14 UTC
I support Steve arguments, this task is in a better place in Jython ...would 
it be for a simple maintenance and support reason.
Comment 9 Stefan Bodewig 2003-03-26 15:40:13 UTC
*** Bug 18363 has been marked as a duplicate of this bug. ***