As a developer I want to have as many modules within as possible - because when I start 'mvn install' on the super project I want all tests run! Only by this process I can be assured that my modifications are valid for all of Castor... I think we should have another way to suppress things from being deployed... Have fun
Joachim On 08/02/2008, Werner Guttmann <[EMAIL PROTECTED]> wrote: > > Tanks, Joachim. It might be that we have to exclude some of those > modules again, as by default they would be included in a deployment as > well, something we don't want to happen. > > But for the time being, this looks alright. > > Werner > > Joachim Grüneis wrote: > > Hello, > > > > I continued a bit on the work of Werner... > > my progress is documented in the pom.xml of the super project: > > <modules> > > <module>xml</module> > > <module>schema</module> > > <module>codegen</module> > > <module>ddlgen</module> > > <module>anttask</module> > > <module>xmlctf-framework</module> > > <!-- Joachim: the tests are not yet running when started using > > mvn install in super project > > <module>xmlctf</module> > > --> > > <module>cpa</module> > > <!-- Joachim: cpactf is not yet successfully executeable.. > > <module>cpactf</module> > > --> > > <!-- Joachim: cpaptf are performance tests - nothing for every > > time execution > > <module>cpaptf</module> > > --> > > <!-- Joachim: examples not yet successfully executeable.. > > <module>cpaptf</module> > > --> > > <module>maven-plugins</module> > > </modules> > > > > I will stop for now - other tasks to do ;-) . > > > > Have fun > > > > Joachim > > > > On Feb 8, 2008, at 12:58 AM, Werner Guttmann wrote: > > > >> Alright, just committed the copied classes in the XML module. Please > >> note that I have not deleted the old files in the project root > >> directory yet. > >> > >> Here's what I have done in addition: > >> > >> - Cleaned up the parent POM. > >> - Changed packaging of the parent POM to 'pom'. > >> - Added a <modules> section to the parent POM, with the XML module > >> only being active. > >> - Stream-lined plugin configuration in the parent POM. > >> - Introduced a <dependencyManagement> section in the parent POM. > >> - Changed the artifact name for the XML module to castor-xml, so that > >> there's no conflict with the parent POM. > >> > >> - Added a <parent> element in the XML POM. > >> - Removed version numbers from <dependencies> in the XML POM, as they > >> are maintained in the parent POM. > >> - Removed all plugin configuration, as this is sourced from the parent > >> POM. > >> > >> As a result of this, the Maven build works just fine .. ;-), > >> > >> Please note that I have *not* touched the Ant build yet, something I > >> plan to do over the weekend. > >> > >> As I haven not deleted in the files in the root directory yet, the Ant > >> build will (most likely) fail. And for those of you using Eclipse, > >> please set exclusion filters accordingly. > >> > >> Regards > >> Werner > >> > >> Werner Guttmann wrote: > >>> Okay, just to let everybody know that I am about to start this move. > >>> As a result of this, a project build with both Maven and/or Ant might > >>> not work for a few days. I'll try to keep things minimal, but I am > >>> not in a position to move this in one go. > >>> Werner > >>> Werner Guttmann wrote: > >>>> Hi, > >>>> > >>>> I just created http://jira.codehaus.org/browse/CASTOR-2287 to signal > >>>> that I would like to move all classes from > >>>> > >>>> src/main/java > >>>> src/main/resources > >>>> src/test/java > >>>> src/test/resources+ > >>>> > >>>> to the already existing 'xml' module. Are there any objections > >>>> currently, due to e.g. outstanding patches that should make it into > >>>> the codebase before I go ahead and svn copy the code. > >>>> > >>>> One thing might be note-worthy: I will be SVN copying the files > >>>> across, excluding the old files from the Maven build only for the > >>>> time being. In other words, I will be looking at the Ant build at a > >>>> later time. > >>>> > >>>> Regards > >>>> Werner > >>>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list, please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
