Franz: This is excellent discussion. This was what I was looking for. I had seen the intro to the lifecycle link before but that seems out there somewhat for most folks. I'm looking to put together more documentation that is neutral to maven or any specific plugin and try to focus on e.g. J2EE packaging. If I wanted to put together a project for a web service and package that service for JBoss, the information for using Maven or the corresponding plugin is scarce. I want to define my project and package it and I don't want to spend all my time trying to figure out how to use Maven2 even though I might have used Maven1 a little years past.
Does that make sense? There is a lot of information, but it has very little organization. Most of it's complicated and seems to run me away instead of convincing me to give it a try. I know better so I want to figure things out more and document it for others. Thanks, David Whitehurst On 11/5/06, franz see <[EMAIL PROTECTED]> wrote:
Good day to you, David, The generate-sources, phase is used for auto code generation. An example for this would be the maven-modello-plugin (see [1]) which allows the creation of Xpp3 Readers, Writers and the corresponding models. Running an XDoclet maven goal would most probably be bound here if that goal produces source codes. For the process-sources, its the phase used when what you're processing (prior to compilation) is the sources themselves. hhmm..can't think of a good example though... The generate-resources phase on the other hand, is like the generate-sources phase, except that this auto generates resources (i.e. xmls, property files) instead of codes. An example which uses that is the maven-eclipse-plugin. the eclipse:eclipse goal which generates the .classpath and .project resources is bound to that phase (see [2] for the released documentation and for [3] for the staged unreleased documentation). And if you have an XDoclet goal which produces resources such as schemas, that goal would most likely be bound to this goal. And as for the process-resources phase, this phase handles the resources-related processes prior to compilation. An example of this is the maven-resources-plugin, which filters and copies resources (see [4] for the released documentation and for [5] for the staged unreleased documentation). And example of a resource would be a property file. For more information about the lifecycle, kindly see [6]. And if you want to suggest somethings or have some feebdacks or something, you might want to create a jira issue in [7] under the "Documentation: Introduction" component. In relation to the eclipse plugin, only one goal (that i know of that works) is bound to a lifecycle phase, and that's the eclipse:eclipse goal which is bound to the generate-resources phase. And with regards to the goals, the current plugin documentations now have their goals documented. However, not all of these new plugin documentations have been released yet (plugin documentations released after Oct 16, 2006 are probably the latest ones..since it was the last time [8] was updated). But nonetheless, if you have any comments about the plugin documentation, you can create a jira issue under that plugin ([9] for maven-eclipse-plugin, [10] for maven-resources-pluign, etc). And lastly, goals are plugin-specific (a plugin consists of 1 or more goals). Phases are were a goal can bind to so that you can use a lifecycle (sequence of phases) to execute your goals in a specific manner. At least, these are my notes. :-) Did I answer your question? Cheers, Franz [1] http://modello.codehaus.org/ [2] http://maven.apache.org/plugins/maven-eclipse-plugin/ [3] http://people.apache.org/~epunzalan/maven-eclipse-plugin/ [4] http://maven.apache.org/plugins/maven-resources-plugin/ [5] http://people.apache.org/~aramirez/maven-resources-plugin/ [6] http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html [7] http://jira.codehaus.org/browse/mng [8] http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation [9] http://jira.codehaus.org/browse/MECLIPSE [10] http://jira.codehaus.org/browse/MRESOURCES David Whitehurst wrote: > > After the message about the documentation, I kind of felt the same way. I > like ANT because I can look at my build.xml file and see what each target > will do exactly. Maven2 is much different but it's more standard. That's > good because we all can begin to learn each goal and then know as we issue > the keystroke what's going to happen and what to expect. > > I started moving around some of the texts on the Maven User WIKI at > http://docs.codehaus.org/display/MAVENUSER/Home > > As long as my interest holds, I plan to keep working on the basic > documentation for using Maven. I'm interested in Appfuse now and they've > moved to Maven2 and away from my old friend ANT. This message is a > request > to get some answers on some goals that I'm not exactly familiar with yet. > I'm using the Maven plugin for Eclipse and I figured that I would start > with > explanation of the lifecycle phases. > > Let's document through mvn compile. > > - Initialize > -Generate sources > -Process sources > -Generate resources > -Process resources > -compile > > I understand initialize and compile. Can someone relate the ones in > between > for me in relation to doing things e.g. running xdoclet, moving properties > files, building schema, etc.? The official documentation discusses > validate, compile, and test. I understand these, but the eclipse plugin > has > more. We should document goals that are used the most for various types > of > projects. > > If this was ANT, I'd know what these goals did exactly. Can someone tell > me > what the above goals will do when I run them in eclipse? Also, I imagine > some of them may or may not be there. That would be worth documenting for > folks on the WIKI. > > Thanks, > > David Whitehurst > > -- View this message in context: http://www.nabble.com/We-need-some-explanation-...-tf2579501s177.html#a7192212 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
