[jboss-dev] Continuing Maven migration

[Paul Gier]

The surefire plugin is automatically part of the maven build, but it's not doing 
anything in the AS build at this point.  It just prints something like "no tests 
to run".

The jmx and profile service modules right are displaying a slightly different 
output than the other modules.  It looks like this is because these two have 
some test files that are picked up by maven, but these modules also are not 
running any tests.

Brian Stansberry wrote:
> When I watch the build console output now, I see some surefire stuff 
> flying by. For the mavenized modules is the build now executing tests in 
> src/tests ?
> 
> Paul Gier wrote:
>> This is an update on the progress of mavenizing the app server build.
>>
>> I have now migrated approximately half of the app server modules in 
>> trunk (AS 6) to maven, and I will be finishing the rest in the next 
>> couple of weeks.
>>
>> As I described previously, the build now works by calling the maven 
>> modules from the ant build (build/build.xml) and then continuing with 
>> the ant build of the distribution.  Soon I will be removing the 
>> build.xml files in the modules where they are no longer needed and I 
>> will change the sh and bat scripts to point to the maven build instead 
>> of ant.
>>
>> Once all of the individual modules are converted, the next step will 
>> be to simplify the distribution build (JBBUILD-513).
>>
>> After that, my goal is to gradually phase out use of the thirdparty 
>> directory. The dependencies that are currently downloaded into 
>> thirdparty will be split up into several places.  Each module will 
>> define it's own dependencies in its pom.  Dependencies that are needed 
>> for the distribution, but not for any module build will be added to 
>> build/pom.xml.  And dependencies that are only needed by the testsuite 
>> will be listed in a new pom in the testsuite directory.
>>
>> The modules that have already been migrated are:
>> bootstrap, main, j2se, mbeans, jmx, system, system-jmx, security, 
>> server, deployment, jbossas/remoting, jmx-remoting, jbossas/jmx-remoting
>>
>> The remaining modules will be migrated in this order:
>> messaging, cluster, varia, iiop, aspects, profileservice, connector, 
>> management, ejb3, tomcat, webservices, hibernate-int, console, spring-int
>>
>> As always, please let me know if you have any questions or concerns!
>>
>> Paul Gier wrote:
>>> I'd like to continue with the Maven migration of the app server 
>>> build.  So starting next week, I will be switching over one or two 
>>> modules at a time in the order that they are currently built.
>>>
>>> So for example, the first to switch will be the "bootstrap" module 
>>> followed by the "main" module.  The build/build.sh file will call 
>>> maven to run the mavenized modules first, and then continue with the 
>>> non-mavenized modules.  That way the later modules can depend on the 
>>> output of the earlier mavenized modules.
>>>
>>> Once a module has been mavenized and is working without any issues, I 
>>> will remove the build.xml file from the directory, and you will have 
>>> to build using maven.
>>>
>>> Please let me know of questions or concerns.
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
>