HEADS UP: Source Tree Reorg
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
HEADS UP: Source Tree Reorg
by Jason Lee
::
Rate this Message:
Ryan and I have been discussing migrating the Mojarra 2 build system
to Maven for some time now, and we'd like to get that ball rolling. What we'd like to do is continue using the ant build while we get the Maven build ready, then, when we're comfortable with it, just start issuing different commands to build. To allow for this "parallel" migration, we'd like to reorganize the tree into the Maven standard format, and updating the ant build to reflect that. This will allow us to write simpler POMs as we test Maven-based versions of our various build tasks. If there are no complaints, I will likely begin sometime this evening (with Ryan's blessing) modifying the jsf-api sub-tree. In theory, this should be fairly transparent, with the possible exception of IDE project files (which we won't need once we're on Maven. :) Are there any complaints or concerns? I hope all that made sense. If not, you know where to find me. :) Jason Lee, SCJP President, Oklahoma City Java Users Group Senior Java Developer, Sun Microsystems http://blogs.steeplesoft.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
RE: HEADS UP: Source Tree Reorg
by Manfred Riem
::
Rate this Message:
Can you create a multi-module that includes all the projects?
Manfred > -----Original Message----- > From: Jason Lee [mailto:jason@...] > Sent: Thursday, August 27, 2009 6:42 PM > To: dev@... > Subject: HEADS UP: Source Tree Reorg > > Ryan and I have been discussing migrating the Mojarra 2 build system > to Maven for some time now, and we'd like to get that ball rolling. > What we'd like to do is continue using the ant build while we get the > Maven build ready, then, when we're comfortable with it, just start > issuing different commands to build. To allow for this "parallel" > migration, we'd like to reorganize the tree into the Maven standard > format, and updating the ant build to reflect that. This will allow > us to write simpler POMs as we test Maven-based versions of our > various build tasks. > > If there are no complaints, I will likely begin sometime this evening > (with Ryan's blessing) modifying the jsf-api sub-tree. In theory, > this should be fairly transparent, with the possible exception of IDE > project files (which we won't need once we're on Maven. :) > > Are there any complaints or concerns? I hope all that made sense. If > not, you know where to find me. :) > > Jason Lee, SCJP > President, Oklahoma City Java Users Group > Senior Java Developer, Sun Microsystems > http://blogs.steeplesoft.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: HEADS UP: Source Tree Reorg
by Jason Lee
::
Rate this Message:
On Aug 27, 2009, at 9:15 PM, Manfred Riem wrote:
> Can you create a multi-module that includes all the projects? That's the plan, yes. Jason Lee, SCJP President, Oklahoma City Java Users Group Senior Java Developer, Sun Microsystems http://blogs.steeplesoft.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
RE: HEADS UP: Source Tree Reorg
by Manfred Riem
::
Rate this Message:
Cool!
Thanks, Manfred > -----Original Message----- > From: Jason Lee [mailto:jason@...] > Sent: Thursday, August 27, 2009 8:34 PM > To: dev@... > Subject: Re: HEADS UP: Source Tree Reorg > > On Aug 27, 2009, at 9:15 PM, Manfred Riem wrote: > > > Can you create a multi-module that includes all the projects? > > > That's the plan, yes. > > Jason Lee, SCJP > President, Oklahoma City Java Users Group > Senior Java Developer, Sun Microsystems > http://blogs.steeplesoft.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: HEADS UP: Source Tree Reorg
by Kito Mann
::
Rate this Message:
Jason,
Why Maven? What about just using Ivy and Ant, or maybe even Gradle? I like the dependency management part of Maven, but the rest of it... --- Kito D. Mann -- Author, JavaServer Faces in Action http://twitter.com/kito99 http://twitter.com/jsfcentral JSF 2 Seminar Oct 6tth: http://www.regonline.com/jsf2seminar JSF Summit Conference Dec 1st-4th in Orlando: http://www.jsfsummit.com http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info +1 203-404-4848 x3 On Thu, Aug 27, 2009 at 8:41 PM, Jason Lee <jason@...> wrote: Ryan and I have been discussing migrating the Mojarra 2 build system to Maven for some time now, and we'd like to get that ball rolling. What we'd like to do is continue using the ant build while we get the Maven build ready, then, when we're comfortable with it, just start issuing different commands to build. To allow for this "parallel" migration, we'd like to reorganize the tree into the Maven standard format, and updating the ant build to reflect that. This will allow us to write simpler POMs as we test Maven-based versions of our various build tasks. |
|
|
Re: HEADS UP: Source Tree Reorg
by Adnan Durrani
::
Rate this Message:
http://in.relation.to/Bloggers/Maven2YearsAfter
Adnan Kito Mann wrote: Jason, --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: HEADS UP: Source Tree Reorg
by Jason Lee
::
Rate this Message:
On Aug 28, 2009, at 1:16 PM, Kito Mann wrote:
> Jason, > > Why Maven? What about just using Ivy and Ant, or maybe even Gradle? > > I like the dependency management part of Maven, but the rest of it... Ryan and I have talked about his a LONG time. At one point, we thought we'd try ant+ivy, but it just made the build uglier. It's been too long, so I don't recall the specifics, but it didn't come close to helping. TBH, I have only a passing knowledge of Gradle, but, from scanning the docs, it has the same problem ant does (IMO) in that there's no standard. Having said that, here's why we want to move to Maven: * Standard project layout. When I move from one ant project to another, I have to take time to read the build file (ant -p doesn't always list the interesting targets, as the developer has to give it a description. Dumb). I have to scan the source tree or build.xml to figure out where the source files are, the resources, the web files, the tests. Where are the build artifacts put? Where is the final deployable archive put? Yes, there are some common locations for all of these, but ant doesn't enforce it, so you can't just assume. With Maven, in every project I've looked at, I *know* where those are. * Convention over configuration. Along those same lines, maven assumes a lot (much to the Hibernate team's dismay), but that makes the build files much simpler in the common case. Until I start doing "strange" things (cobertura, YUI compressor, e.g., from a couple of my projects), the build files are typically very simple, and always look familiar. * IDE Integration. With NetBeans, at least, and I'm pretty sure Eclipse and IDEA at least have plugins for this, I can point my IDE at a POM file and I have an instant project in my IDE. * Built-in dependency management * Built-in repository deployment And I'm sure there are some others. Personally, there are some things I'd like to see changed: * The POM file is too verbose. It seems no one on the Maven team has ever heard of XML attributes. Not everything needs to be a child element. * It's a bit rigid. For those times when you *have* to jump of the rails, Maven can make that difficult. I've done OK with the antrun plugin, but a cleaner, scripted approach (say, anything JSR-223 compliant) would be awesome. * It can be slow. Reading and parsing all those XML documents can take a bit longer than an equivalent ant build (I'm guessing. I've not actually tried, because...) but the effort it would take to build an ant-based build system for a multi-module project is worse than a slightly slower build. And I'm sure there are more. :) Since no one has raised any show-stopping complaints, we'll probably press on with Mavenization. At this point, we're just rearranging the source tree to the Maven standard layout. In the interim, should someone propose a compelling alternative build tool, this directory layout can still be used more likely than not. Jason Lee, SCJP President, Oklahoma City Java Users Group Senior Java Developer, Sun Microsystems http://blogs.steeplesoft.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: HEADS UP: Source Tree Reorg
by Jason Lee
::
Rate this Message:
With Ryan's permission, I just committed the changes to the jsf-api tree that I made over the weekend. There shouldn't be any changes required to build. IDEs may need updating, and I have some fixes to verify WRT to the maven ant tasks in common/, but everything else should be fine. Please reply here if you have any issues.
Probably let that rest a bit before we try another, just to make sure we don't confuse the environment should issues be found. On Aug 28, 2009, at 1:43 PM, Adnan Durrani wrote:
Jason Lee, SCJP President, Oklahoma City Java Users Group Senior Java Developer, Sun Microsystems |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
