Daniel Mayer

Originally posted by Arijit Ghosh:
But it keeps a local history whenever Save is pressed...

Pressing Save is generally very frequent and it will soon eat up all the Entries.

It should typically suffice for the history of a day of development. For
anything beyond that time span, you really should use a VCS!

Originally posted by Mike Clark:
Have you ever had a situation where you thought you checked in a file to version control, but when the other programmer tried to build the system it failed because the contents of the version control repository weren't what you expected? Or has the other programmer checked in code that didn't compile or pass all the tests?

Or worse, it worked fine in all the developers IDEs, but once you tried to produce a production release, the build scripts failed - and the last known working version is from weeks or even months ago...

When I started work in my current team three years ago, building a distribution could take up to three days because of integration problems (with a team of four developers). Today we are typically able to just use the CC build from last night.

Originally posted by somkiat puisungnoen:


What is CruiseControl ?

So you aren't reading the Journal?
http://www.javaranch.com/journal/200409/Journal200409.jsp#a2

Ant does only compile "dirty" files - if your class files are uptodate, nothing will happen.

Run ant with -verbose to see what's happening.

Eclipse has a local history - a kind of limited auto backup: it remebers some part of the history of every file. It is used via the "compare with" and "replace width" commands. How much it will remember can be configured in the workbench preferences.

Originally posted by Praful Thakare:
This application is yet to go live,but as per my knowledge it will be called
atleas once per second in working hours

OK - until it becomes likely that it will be called several hundred times a second, I wouldn't waste another thought on it...

You don't. It's a framework that is to be used by other plugins. It doesn't provide any functionality directly to the user, as far as I know.

Originally posted by Arijit Ghosh:
Why do I need to Check Out files as Java Project ? I can simply check out the project from the CVS and work on it without any problems.

Does the project icon have a "J" in the upper right corner whem you do this?

In fact, checking out as Java Project adds some dfault package and some JARs.

Does it? That's strange - what jars are added?

It also adds some classpath and project property files.

Actually the .project file should also be created for non-Java projects. The .classpath file is needed by eclipses java compiler. They shouldn't be shown in the package explorer, though.

Originally posted by Paul Sturrock:

ant-commons-net.jar (which contains the taskdefs)

Which in prior versions could be found in optional.jar.

What exactly do you mean with "AutoBackup"? Are you using a VCS?

Originally posted by Praful Thakare:
Daniel This method is called heavily from an BANKING application

Please define "heavily" - how often in a second?

I suspect it might have something to do with the number and nature of optimizations the hotspot engine already has done. That is, if you run in pure interpreted mode, ou should always see the line numbers (provided you used the right compile time switch).

We are using a combination of Ant, Cruise Control and shell scripts to

- have a continuous build running,
- have nightly distribution builds, and
- have a webstart distribution deployed to our intranet every night.

We also make heavy use of Eclipses Ant Builder to automatically recreate generated sources when the definition files change - for example when using JAXB to generate code from XML Schema.

Recently I started to automatically update the screenshots for the online handbook of one of our projects, using the Ant tasks of http://www.jdemo.de/

I have read of a team that uses a real traffic light.

The ambient orb looks cool, too: http://blogs.codehaus.org/people/vmassol/archives/000597_enlightening_build.html

Originally posted by Lasse Koskela:
${ant.project.name} is what you're looking for.
And if you find yourself needing to know the path of the build script itself, ${ant.file} to rescue

BTW, these properties and some more are documented in the manual: http://ant.apache.org/manual/using.html#built-in-props