All, Let's start a new thread focused on planning out what a possible move to maven would look like. I know it's easy to dive in to the code and just start playing around, but if not done right, we are going to get a lot of push back from others on moving to maven. We need to plan this out and identify exactly what we intend to do, who is going to do it, how were are going to do it, and when it will be done. The discussion of this should happen on the mailling list, and the results of the discussion should be captured in the development wiki (which I can set up).
The following questionnaire should help us get going. I realize that some of this discussion has already taken place. I would suggest simply answering the questions for yourself in this thread. If we need to discuss a particular question lets start a separate thread for each question. I don't want to distract people from filling out the "survey". Thanks. ~Michael Questions: 1) What is the objective (just provide maven jars to a repo? fully mavenize the project? etc)? 2) What are the benefits of what we are proposing? Why should we move to maven? 3) Who is really committed to work on this? 4) hat is the general approach for adding maven support (just writing poms? moving source around? etc)? 5) How will the development cycle of the developers who are not working on this be impacted? 6) What are our deliverables? Other than the mavenized project, do we need to provide documentation or tutorials to show others how to work with the new system? 7) What are the various modules we would propose having and what is the purpose of each (simply stating that we stick with the current jars is not enough info)? 8) What group ids / artifact ids should we use? 9) What are the timelines and milestones?
