The point I am making is that you should check the reactor list *FIRST* and if not there *ONLY THEN* do you go and build the project. The Maven build itself may have modified the pom files that are in the reactor during the course of the build (not encouraged but possible... I've heard of people doing crazy stuff with my versions-m-p) in which case the files on disk differ from the in-memory model that the build is working from and you will generate inconsistent results.
Trust me, if you want a stable build and to write a good plugin, resolve from the reactor if available first On 13 December 2012 13:13, Marcos Mendez <mar...@jitisoft.com> wrote: > reactor projects in the plugin are not all the projects and i'm not going > to force the user to run things from a top-level project. i'm interested in > simple properties not building or doing anything else with the project. my > plugin does just that with a little elbow grease. i could also just parsed > the pom files myself for what i need... > > On Dec 13, 2012, at 7:14, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > FYI: You should look for them in the list of reactor project first before > > resorting to building a new model. Otherwise subtle effects to do with > > order of installation into the maven repository can creep in > > > > > > On 13 December 2012 11:53, Marcos Mendez <mar...@jitisoft.com> wrote: > > > >> Well. figured it out. Thanks. > >> > >> Found a way to get the root module. Then figured out how to load the > >> modules by using the maven project builder. > >> > >> On Dec 13, 2012, at 6:47 AM, Anders Hammar wrote: > >> > >>> I don't know, but I would look in the source code of some open source > >> maven > >>> plugin that does similar things. Try the javadoc plugin as I believe it > >> has > >>> an aggregate goal. > >>> > >>> /Anders > >>> > >>> > >>> On Thu, Dec 13, 2012 at 11:55 AM, Marcos Mendez <mar...@jitisoft.com> > >> wrote: > >>> > >>>> > >>>> Does anyone know to get children modules as MavenProjects? > >>>> > >>>> I'm building a plugin. I've already created something to find the > parent > >>>> project from any child project. Now I want to find a specific project > by > >>>> group and artifact ids. So I need to traverse the hierarchy from any > >> child > >>>> module. I can go up, but I need to be able to get the child modules as > >>>> projects and repeat the process recursively. > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >>>> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
