It would be nice to have all these features :) BUT :) I was unable to build our project using 1 command :( "mvn clean install" in parent project just don't work :( Too much forking then fail I tried to ask for the help http://markmail.org/thread/jin5y6vbnsb456yc no luck according to Maven source code "Forking" is started when there is "ExecuteGoal" or "ExecutePhase", so I believe we need to remove all calls to ant and get this issue https://jira.codehaus.org/browse/MWEBSTART-176resolved.
According to publishing the "publish the assembled Tomcat server including red5 as a build artifact" I'm afraid we need to create another one subproject But I would like to take a brake with maven tuning :) 3.1.0 need to be developed :) On Thu, May 8, 2014 at 4:56 AM, [email protected] <[email protected] > wrote: > And :) > > The build has a dependency (see "upstream projects") into > https://builds.apache.org/job/maven-surefire/ which means whenever there > is a change to the Maven surefire build tools our build is automatically > triggered as we are depending on it. So kind of we are integrated into the > Apache Maven infrastructure :) > > Sebastian > > > 2014-05-08 9:51 GMT+12:00 [email protected] <[email protected]>: > > Each module will automatically publish its own module artifacts, for >> example: >> >> https://builds.apache.org/job/OpenMeetingsMaven/3/org.apache.openmeetings$openmeetings-core/ >> >> We only might need to add something to also publish the assembled Tomcat >> server including red5 as a build artifact. >> >> Sebastian >> >> >> 2014-05-08 9:48 GMT+12:00 [email protected] <[email protected]>: >> >> Hi Maxim, >>> >>> our current build is using some hand build Jenkins configuration. >>> Jenkins does actually provide its own Maven template. When you create a >>> new Job you can see that option. >>> >>> By using that it results in having this kind of build overview: >>> https://builds.apache.org/job/OpenMeetingsMaven/ >>> >>> With a graph of the test results. >>> >>> Also it shows details of the module builds: >>> https://builds.apache.org/job/OpenMeetingsMaven/3/ >>> >>> and generates automatically the Test Result overview: >>> https://builds.apache.org/job/OpenMeetingsMaven/3/testReport/ >>> >>> All of that stuff is kind of available in our current build but we all >>> did that by manually scripting and configuring Jenkins. >>> I think we should use the Maven template of Jenkins and get rid of our >>> custom config. We might benefit from improvements that are done to it in >>> the future with zero effort. And it also looks a bit more cleaner. >>> >>> What do you think ? >>> >>> Sebastian >>> >>> >>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> [email protected] >>> >> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax
