Dear Daniels,
I am new to ant Scripting. My requirement is like this. We are using
Weblogic.
I receive an .EAR file and before deployment my BUILD should do the
following.
a. My Script should locate the weblogic-ejb-jar.xml inside the
.EAR and
<trans-time-out></trans-time-out>
Element should be modified per EJB basis.
What do you suggest?
Regards,
Srini.
-----Original Message-----
From: Daniels, Doug [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 04, 2005 12:55 AM
To: Ant Developers List
Subject: RE: Google Summer of Code, Apache ANT project ideas?
Yeah I was way off on Velocity I thought it was part of XDocs but really its
that servlet engine. What's wrong with XDocs it seems like a good way to
parse through the Ant Tasks meta-data javadoc comments and extract the
information we need for documentation. What other types of capability were
you looking for?
The project deliverable would most likely be an Ant Task that could perform
this document auto-generation right?
Where can I find the previous XDoc stuff that was developed?
Doug Daniels
-----Original Message-----
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 2:09 PM
To: Ant Developers List
Subject: Re: Google Summer of Code, Apache ANT project ideas?
Doug - I've added it as project ID ant-xdocs to that wiki page. As
for technologies - I'm not sure if Velocity and XDoclet are the best
technologies to use right now. Let's solicit input from others here
on their architecture ideas.
Erik
On Jun 3, 2005, at 1:46 PM, Daniels, Doug wrote:
> Erik,
>
> Sounds great, maybe you can submit it on the Apache SoC proposal
> page(http://wiki.apache.org/general/SummerOfCode2005), and I'll
> submit my application to google with Apache as my selected
> organization.
>
> I guess I'd propose it something like:
> The Apache Ant project needs a way to auto-generate task/type
> documentation. The proposed solution would use Velocity and xdocs
> to create a standard way to document the old and new Ant tasks to
> keep the documentation up to date and easily updatable in the
> future automatically.
>
> By the way I have your book and it was a great help with what I've
> been working on at my job. I was thinking of writing up an Ant
> tutorial describing an interesting build system we came up with
> utilizing Ant's import task to create a common build hierarchy
> infrastructure, that can be extended to new products very easily.
> It really helps when we have to add a new product in and all we do
> is define some properties and throw a build.xml stub in and it is
> then included into our software package.
>
> Doug Daniels
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
*********************************************************
Disclaimer:
The contents of this E-mail (including the contents of the enclosure(s) or
attachment(s) if any) are privileged and confidential material of MBT and
should not be disclosed to, used by or copied in any manner by anyone other
than the intended addressee(s). In case you are not the desired addressee,
you should delete this message and/or re-direct it to the sender. The views
expressed in this E-mail message (including the enclosure(s) or attachment(s)
if any) are those of the individual sender, except where the sender expressly,
and with authority, states them to be the views of MBT.
This e-mail message including attachment/(s), if any, is believed to be free of
any virus. However, it is the responsibility of the recipient to ensure that
it is virus free and MBT is not responsible for any loss or damage arising in
any way from its use
*********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
