[me]
Now that ant.jar has been removed, the project is slightly less
friendly to eclipse since ant.jar is required by the files in
org.apache.fop.tools.anttasks.
It is easily solved locally, I just wanted to point it out.
[Peter B. West]
Finn,
I've been trying to find an Eclipse-clean way to
Finn Bock wrote:
[me]
Now that ant.jar has been removed, the project is slightly less
friendly to eclipse since ant.jar is required by the files in
org.apache.fop.tools.anttasks.
It is easily solved locally, I just wanted to point it out.
[Peter B. West]
Finn,
I've been trying to find an
Finn Bock wrote:
The same way that I locally solved the Jimi and JAI dependency:
copy d:\java\ant-1.5.1\lib\ant.jar lib
and adding the .jar to the Java Build Path/Libraries.
You don't need the copy, you can add external jars as
well.
J.Pietschmann
[Jeremias Maerki]
I've removed the embedded Ant in HEAD. I rewrote build.bat and build.sh
to call a separately installed Ant. Instructions will be given on the
command-line if Ant cannot be found.
Now that ant.jar has been removed, the project is slightly less friendly
to eclipse since ant.jar
Finn Bock wrote:
Now that ant.jar has been removed, the project is slightly less friendly
to eclipse since ant.jar is required by the files in
org.apache.fop.tools.anttasks.
It is easily solved locally, I just wanted to point it out.
Finn,
I've been trying to find an Eclipse-clean way to solve
Jeremias Maerki wrote:
I've removed the embedded Ant in HEAD. I rewrote build.bat and build.sh
to call a separately installed Ant. Instructions will be given on the
command-line if Ant cannot be found.
Peter, please test build.sh on Unix. I hope I got the whole thing right.
Jeremias,
It compiles
No, I guess that's what was needed. Thanks.
On 14.12.2003 09:57:50 Peter B. West wrote:
Jeremias Maerki wrote:
I've removed the embedded Ant in HEAD. I rewrote build.bat and build.sh
to call a separately installed Ant. Instructions will be given on the
command-line if Ant cannot be found.
I've removed the embedded Ant in HEAD. I rewrote build.bat and build.sh
to call a separately installed Ant. Instructions will be given on the
command-line if Ant cannot be found.
Peter, please test build.sh on Unix. I hope I got the whole thing right.
Jeremias Maerki
Well done--I particularly liked the Ant instructions
you added.
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I've removed the embedded Ant in HEAD. I rewrote
build.bat and build.sh
to call a separately installed Ant. Instructions
will be given on the
command-line if Ant cannot be
Peter B. West wrote:
In the medium term, I think some sort of protocol for provides/requires
and versioning will have to be established for matching jars. It has
always galled me that everyone bundles everything to ensure that a
particular application runs.
Short: use Maven.
What does
I don't think so, as potential fop-dev have to learn about other things,
too, especially CVS and how to build patches. I think that's a lot more
complicated than having to install Ant.
fop-devs can be expected to know about Ant because almost every Open
Source project written in Java I've
Jeremias,
On Dec 12, 2003, at 7:13 AM, Jeremias Maerki wrote:
I don't think so, as potential fop-dev have to learn about other
things,
too, especially CVS and how to build patches. I think that's a lot more
complicated than having to install Ant.
fop-devs can be expected to know about Ant
Jeremias Maerki wrote:
Following a problem on fop-user I'd like to propose the removal of
ant.jar and the build.bar/sh pair. I've heard that best practice is not
to bundle Ant with a project, though I can't point you to a web page.
It's reasonable to expect that everybody who wants to compile a
I can do that but someone will have to test the unix script for me.
On 11.12.2003 10:33:34 Peter B. West wrote:
Removing ant, fair enough, but why the build scripts? Shouldn't they be
extended a little to check for the presence of an ant installation and
make appropriate noises if one isn't
Jeremias Maerki wrote:
I can do that but someone will have to test the unix script for me.
On 11.12.2003 10:33:34 Peter B. West wrote:
Removing ant, fair enough, but why the build scripts? Shouldn't they be
extended a little to check for the presence of an ant installation and
make
I disagree on this point, if we're removing ant.jar, I
don't see a need for continuing to maintain a build.sh
and build.bat.
Given that they must install Ant, it isn't too
traumatic to next navigate to the fop working
directory and type ant to make the build. (I'm not
being sarcastic--the way
Glen Mazza wrote:
I disagree on this point, if we're removing ant.jar, I
don't see a need for continuing to maintain a build.sh
and build.bat.
Given that they must install Ant, it isn't too
traumatic to next navigate to the fop working
directory and type ant to make the build. (I'm not
being
I don't think ant should be removed from the maintenance branch.
Granted, users of HEAD should be adept enough to install and configure
ANT, but I think it is more important to make at least the
maintenance branch of FOP easy to use, than it is to encourage them
to install and configure ant.
Peter B. West wrote:
Removing ant, fair enough, but why the build scripts? Shouldn't they be
extended a little to check for the presence of an ant installation and
make appropriate noises if one isn't found?
I agree.
Victor Mote
On tor, 2003-12-11 at 16:42, Clay Leeds wrote:
I don't think ant should be removed from the maintenance branch.
Granted, users of HEAD should be adept enough to install and configure
ANT, but I think it is more important to make at least the
maintenance branch of FOP easy to use, than it is
--- Clay Leeds [EMAIL PROTECTED] wrote:
Web Maestro Clay
p.s. I guess this means I get to add ant to my list
of tools in my
toolbox... :-)
Yes, highly transportable skills in CVS and Ant may be
the two biggest up-front goodies you get by working on
FOP.
Instructions:
1.) Download ant
J.Pietschmann wrote:
Hmhm. The unix version (build.sh) added *all* jars in the
lib directory to the classpath, which made the drop into
lib and call build.dh much easier. If this has to be done
in build.xml, there's trouble ahead with jars containing
release identifiers and such ugly stuff.
Well,
Following a problem on fop-user I'd like to propose the removal of
ant.jar and the build.bar/sh pair. I've heard that best practice is not
to bundle Ant with a project, though I can't point you to a web page.
It's reasonable to expect that everybody who wants to compile a Java
program to install
Great idea! Like CVS, Ant is highly beneficial to
learn, and it opens doors to many other open source
projects as well. So I think this a tool we should be
encouraging others to at least load on their machine.
+1 for HEAD, and I think it would be fine to remove it
from maintenance as well.
24 matches
Mail list logo
