Craeg Strong wrote:
> Although it will only interest a small number of developers, i would
happily contribute a "ecmascript/javascript with Ant" including JSdoc
(similar with javadoc) and JSLint (instead of checkstyle) integration,
unit test etc.
> Manos
Yes, Please!
I am involved with a l
Erik Hatcher wrote:
On Jul 26, 2005, at 5:30 AM, Steve Loughran wrote:
Actually, maybe we should put together some official ant team
presentations, for use in in-house or external talks, something like
the following set. This could be something to get the user community
involved in too...
> Although it will only interest a small number of developers, i would
happily contribute a "ecmascript/javascript with Ant" including JSdoc
(similar with javadoc) and JSLint (instead of checkstyle) integration,
unit test etc.
> Manos
Yes, Please!
I am involved with a large project that is
On Jul 26, 2005, at 5:30 AM, Steve Loughran wrote:
Actually, maybe we should put together some official ant team
presentations, for use in in-house or external talks, something
like the following set. This could be something to get the user
community involved in too...
-intro to ant
-why
Steve Loughran wrote:
Actually, maybe we should put together some official ant team
presentations, for use in in-house or external talks, something like
the following set. This could be something to get the user community
involved in too...
-intro to ant
-why testing matters more than you th
Kev Jackson wrote:
Hi all,
I'm preparing a talk for the developers here in Vietnam about how to use
Ant to build software (mainly Java, but you know there's the .net tasks
too). I have the main body of the presentation completed, but I wanted
to include some of the more esoteric things you c
They are at the leading edge then... I have been interviewing
candidates for a developer position not later than yesterday and it
left me with a bitter test about software process and tools used
within a team working...no source control within a team of 15 people
(10 dev), etc... all that wit
You may well have already included this sort of thing, but I'd cover
(not really esoteric):
* Immutability and overriding of properties (an often mis-
understood aspect)
* Conditional targets
* Usage of id/refid
* Multiple source tree support (e.g. for production an
Kev Jackson wrote:
Needless to say, the working practices are similar to what I'd expect
in the 80's (SourceSafe as version control, everyone locks files,
Waterfall as the process, massive investment in design up front,
testing is done by teams of bored people etc etc).
They are at the leadi
I work in a web agency, here are some of the more esoteric things I have done:
- strictly control access to deployment/live servers; only access to deploy
is via a series of Ant tasks; limit files that can go live by the use of
file filters
- promoting reference data from dev > staging databas
10 matches
Mail list logo
