> |No worries, nothing is dependent on cygwin. But I don't have the patience > |to deal with maintaining a batch script. > > I have agreed to this experiment with the understanding that it would not > break portability. If it does because you don't maintain it and you put the > windows developers (80% of our developers) through pain then this is a > failed experiment. I do not wish to break portability, I just need some help to make the batch stuff as good as the /bin/sh bits. That is all I meant. > you work up that fucking patience or it is me that is going to run out of it > with you Chill. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
- RE: [JBoss-dev] requirements for build Dan - Blue Lotus Software
- RE: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build Dan - Blue Lotus Software
- RE: [JBoss-dev] requirements for build Jason Dillon
- Re: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build Dan - Blue Lotus Software
- RE: [JBoss-dev] requirements for build marc fleury
- RE: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build marc fleury
- RE: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build Dan - Blue Lotus Software
- RE: [JBoss-dev] requirements for build Jason Dillon
- RE: [JBoss-dev] requirements for build Vincent Harcq
- RE: [JBoss-dev] requirements for build Jason Dillon
- Re: [JBoss-dev] requirements for build Fred Loney
- Re: [JBoss-dev] requirements for build Jason Dillon