Kenney, Thanks for you response. I understand that in the ideal case all meta data needed to perform a build is stored in the pom files. This sounds logic looking from a Maven persective. But I think this will not work for our team, as Maven has no native integration with the Visual Studio IDE.
We like to provide a build solution that is centered around the .csproj files instead of the pom files. This would allow our developers to create their C# software projects (including the definition of both external-dll-references and project-references) in their IDE without a need to bother about the pom files. From the developers perspective a very important requirement about the build infrastructure is that he/she can use the IDE to build and debug the project directly. In the ideal case we are able to let Maven adapt its build order automatically to the content c# projects through a plugin that is aware of the content of solution files and csproj-files. So again the question: Is there a way to perform my mojo prior to sorting the reactor? Or should I write some sort of event handler that listens to a build event to extend the project definition while the pom file is loaded and analyzed? Thanks in advance for any suggestions, Mark Koops GE Healthcare -----Original Message----- From: Kenney Westerhof [mailto:[EMAIL PROTECTED] Sent: maandag 7 augustus 2006 15:50 To: Maven Developers List Subject: Re: How to execute a plugin prior to the reactor sorting? Mark Koops wrote: > Hi all, > > I have been creating a plugin that extends the dependencies in the > Maven projects in the reactor programmatically based on the references > found is associated C# project files (.csproj files). This is all > working fine but I am wondering how I can get the references injected > as dependencies before the reactor is being sorted. I need this to get > the artifacts builds before they are resolved as build dependencies. > The idea is that the pom.xml is fully describing the needed dependencies, so if you're missing the .csproj files in the repository then you can't build. So I think you're going about this the wrong way. What you could do is write a plugin that updates the pom using the information in the .csproj files. Ideally the pom is the basis of all project metadata, so if you need other deps/refs in the .csproj, you should update the pom and then re-run the plugin that created the .csproj (if there is one out there..) -- Kenney > > Is there a way to force mojo executions to be done prior to the > reactor being sorted? I've tried the validate phase but found this to > be executed after reactor sorting. Does anyone know about another > plugin that deals with this or a similar problem? > > Or is there a mechanism to force resorting of the build reactor after > changing project definition within a plugin? > > Hope anyone can give me clue. > > Thanks in advance, > > Mark Koops > GE Healthcare > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.7/410 - Release Date: 5-8-2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.7/410 - Release Date: 5-8-2006 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
