Martin, This is the ANT list... and you suggest a Maven solution...
I am not sure that that is what the OP is after... In moving from Makefile to a more modern build process I usually find that jumping as far as Maven is a "step too far" for most people... don't get me wrong, I am a Maven fan, but I given the issues the OP is having with getting "how ant works" I'd rather keep them on the ANT list rather than have similar questions posted to the Maven list ;-) -Stephen 2009/9/18 Martin Gainty <[email protected]> > > you can implement *the majority* of what you're trying to accomplish using > maven Native Archive Plugin > http://java.freehep.org/freehep-nar-plugin/intro.html > > be aware this is a brand new plugin is attempting to emulate every > make,compile and link tool > available for every OS and library set so as with all things which are > brand new > *caveat emptor* > > i presume you already downloaded php? > http://www.php.net/downloads.php > > a fairly active and supportive user community is available at > http://maven.apache.org/mail-lists.html > > bedankt, > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > > > From: [email protected] > > To: [email protected] > > Subject: Re: converting ant from a make file > > Date: Fri, 18 Sep 2009 19:22:23 +0200 > > CC: [email protected] > > > > I think by now you should read up on Ant and understand the basic > > concepts before proceeding... > > > > Met een vriendelijke groet, > > > > > > Ernst de Haan > > PensioenPage B.V. > > www.pensioenpage.com > > > > tel. (026) 364 56 34 > > > > Op 18 sep 2009 om 18:53 heeft veena pandit <[email protected]> het > > volgende geschreven:\ > > > > > So how would I write it in the build.xml > > > > > > for c in A B C D E; do > > > perl -ibak process.pl abc.txt > > > perl -ibak process.pl def.txt > > > perl -ibak proces.pl xyz.txt > > > - mkdir Backup > > > mv *bak Backup > > > > > > Not clear what this is doing; but it is executing the same pl file > > > against > > > different input files. > > > > > > Sorry, but I don't quite get it yet. > > > > > > Thanks, > > > > > > Veena > > > > > > On Fri, Sep 18, 2009 at 12:41 PM, Ernst de Haan < > [email protected] > > > >wrote: > > > > > >> The Ant way to process multiple Perl files would be: > > >> > > >> <perl dir="src/perl" todir="build" includes="*.pl" /> > > >> > > >> See? It's a different way of thinking... > > >> > > >> Met een vriendelijke groet, > > >> > > >> > > >> Ernst de Haan > > >> PensioenPage B.V. > > >> www.pensioenpage.com > > >> > > >> tel. (026) 364 56 34 > > >> > > >> Op 18 sep 2009 om 17:12 heeft veena pandit <[email protected]> het > > >> volgende geschreven:\ > > >> > > >> > > >> Do you mind posting a small example of the exec command with the > > >> script: > > >>> for c in A B C D E; do? > > >>> > > >>> Thanks, > > >>> > > >>> Veena > > >>> > > >>> On Fri, Sep 18, 2009 at 10:38 AM, John Shott <[email protected]> > > >>> wrote: > > >>> > > >>> Veena: > > >>>> > > >>>> for c in A B C D E; do > > >>>> > > >>>>> perl ... > > >>>>> perl ... > > >>>>> perl... > > >>>>> - mkdir Backup > > >>>>> mv *bak Backup > > >>>>> > > >>>>> How do I move this script over to ant build.xml. > > >>>>> > > >>>>> > > >>>>> This is probably a bit hard to answer. In principle, you can > > >>>>> simply > > >>>> call > > >>>> the existing script using something like the exec task along with > > >>>> appropriate arg values. Or, you can consider breaking the script > > >>>> apart > > >>>> and > > >>>> call individual perl scripts with appropriate arguments. In > > >>>> general, > > >>>> however, I think that you'll be happier if you are able to use the > > >>>> built-in > > >>>> ant tasks wherever possible and resort to things like the exec > > >>>> task only > > >>>> when you absolutely need to. > > >>>> > > >>>> While I'm not a great authority on either make or ant, I did > > >>>> spend a > > >>>> great > > >>>> deal of time converting a good sized project with a bunch of > > >>>> Makefiles to > > >>>> an > > >>>> ant-based build. My experience is that if you try to simply do a > > >>>> line-by-line conversion of your Makefiles into the ant > > >>>> equivalent, that > > >>>> you > > >>>> will not be terribly happy with the result. Why? Ant is not > > >>>> make and > > >>>> they > > >>>> approach things differently. > > >>>> > > >>>> I suspect that you'll be a lot happier with the result if you look > > >>>> carefully at what Make is doing, make sure that you understand that > > >>>> fully, > > >>>> and then look at ant to see how some of it's tasks can be > > >>>> harnessed to do > > >>>> the same thing. For example, make tends to do things on a > > >>>> directory by > > >>>> directory basis whereas ant has a much more sophisticated (to me at > > >>>> least) > > >>>> means of specifying filesets that become the target of a task. > > >>>> Also, ant > > >>>> now has a wide range of tasks that perform interesting and often > > >>>> complex > > >>>> elements of a build in a single step. You may even find it > > >>>> desirable (if > > >>>> you have that flexibility) to restructure your source tree in a > > >>>> more "ant > > >>>> friendly" structure. You may also find that some of the things > > >>>> that your > > >>>> Perl scripts are doing are conveniently doable by ant tasks so > > >>>> that when > > >>>> everything is done, instead of having a handful of Makefiles plus > > >>>> Perl > > >>>> scripts that you may have a single build.xml file. Of course, not > > >>>> knowing > > >>>> what your Perl scripts are doing .... they may be doing things > > >>>> that would > > >>>> be > > >>>> hard to do in ant. > > >>>> > > >>>> I hope that helps, > > >>>> > > >>>> John > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> --- > > >>>> ------------------------------------------------------------------ > > >>>> 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] > > > > _________________________________________________________________ > Hotmail: Powerful Free email with security by Microsoft. > http://clk.atdmt.com/GBL/go/171222986/direct/01/ >
