SV: Making Struts Build Easier (Re: coming out for JSF + Struts , was: Struts JSR?)
Hi I think that the move to Maven is a giant leap forward. Now at least we can build with requisite jars that are already build. Earlier it ment that you would have to buil a bunch of projects before you could actually do the real build. Also you can have local repositories for when you are offline. Hermod -Opprinnelig melding- Fra: Joe Germuska [mailto:[EMAIL PROTECTED] Sendt: 22. mars 2004 15:28 Til: Struts Developers List Emne: Making Struts Build Easier (Re: coming out for JSF + Struts, was: Struts JSR?) For me, the main discouraging thing about contributing to the development of Struts has been the build process. In the past, you had to download all of jakarta-commons and spend a day or two figuring out how to get that to build. Recently, I tried to build Struts and was successful using the Maven stuff. Personally, I don't mind using Maven, but I don't know that it should be *required* to build a project from scratch. I'd love to be able to cvs co Struts, navigate to jakarta-struts and type ant jar. I realize this is no easy thing to accomplish with a build file - but it has been the most discouraging factor for me. ;-) The only way we could accomplish something like that with a build file would be by including JARs in CVS, and if you ask me, there are enough reasons why that's a bad idea that I prefer the way it is, even though I'd very much like to see people feel more comfortable getting in and working on Struts source code. When you say I don't know that [Maven] should be *required*... is your point that Ant is a widely accepted Java tool, while Maven has yet to cut a 1.0 release? That's fair -- just want to make sure I understand you. The build.xml file generated by 'maven ant' uses the ant 'get' task and the Maven iBiblio repository to download dependencies; we could perhaps look at copying some of that into our ant script to reduce build.properties to being more about configuration stuff and less about dependency stuff. Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that DnB NOR cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SV: Making Struts Build Easier (Re: coming out for JSF + Struts , was: Struts JSR?)
On Mon, 22 Mar 2004 [EMAIL PROTECTED] wrote: Hi I think that the move to Maven is a giant leap forward. Now at least we can build with requisite jars that are already build. Earlier it ment that you would have to buil a bunch of projects before you could actually do the real build. Also you can have local repositories for when you are offline. Building the dependencies yourself has *never* been required for Struts. You can build against released versions of Commons components, or, when those are in flux and we've been depending on unreleased features, on the nightly builds of them. Note that with Maven, you actually have a stronger requirement than with the Ant build - that the versions of the Commons dependencies you need have been made available in a Maven repository. (Yes, that can be worked around, but we're talking here about the ease with which you can just type 'maven' and have everything happen.) -- Martin Cooper Hermod -Opprinnelig melding- Fra: Joe Germuska [mailto:[EMAIL PROTECTED] Sendt: 22. mars 2004 15:28 Til: Struts Developers List Emne: Making Struts Build Easier (Re: coming out for JSF + Struts, was: Struts JSR?) For me, the main discouraging thing about contributing to the development of Struts has been the build process. In the past, you had to download all of jakarta-commons and spend a day or two figuring out how to get that to build. Recently, I tried to build Struts and was successful using the Maven stuff. Personally, I don't mind using Maven, but I don't know that it should be *required* to build a project from scratch. I'd love to be able to cvs co Struts, navigate to jakarta-struts and type ant jar. I realize this is no easy thing to accomplish with a build file - but it has been the most discouraging factor for me. ;-) The only way we could accomplish something like that with a build file would be by including JARs in CVS, and if you ask me, there are enough reasons why that's a bad idea that I prefer the way it is, even though I'd very much like to see people feel more comfortable getting in and working on Struts source code. When you say I don't know that [Maven] should be *required*... is your point that Ant is a widely accepted Java tool, while Maven has yet to cut a 1.0 release? That's fair -- just want to make sure I understand you. The build.xml file generated by 'maven ant' uses the ant 'get' task and the Maven iBiblio repository to download dependencies; we could perhaps look at copying some of that into our ant script to reduce build.properties to being more about configuration stuff and less about dependency stuff. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
