Hello Daniel, You can get nightly build (both binary and source) from our build server: https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/ Not sure why tests are failing for you (works OK both locally and on build server) After successful build you can get artifacts from openmeetings-server/target folder
to update you can 0) backup everything (just in case) 1) use import/export 2) just change the binaries (if you absolutely sure what you are doing) :)) On Tue, Mar 14, 2017 at 9:41 AM, Daniel Baker <[email protected]> wrote: > Yes its builds now. > > The question I have now is how do I use the results to replace my existing > OM install ? > > > I have these results from the build : > > # ls > CHANGELOG NOTICE openmeetings-db > openmeetings-install openmeetings-server openmeetings-util > openmeetings-webservice README target > LICENSE openmeetings-core openmeetings-flash > openmeetings-screenshare openmeetings-service openmeetings-web > pom.xml src > > Thanks, > > > Dan > > > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Openmeetings ....................................... SUCCESS [ > 46.428 s] > [INFO] Openmeetings Util .................................. SUCCESS [ > 37.478 s] > [INFO] Openmeetings DB .................................... SUCCESS [ > 41.338 s] > [INFO] Openmeetings Core .................................. SUCCESS [ > 49.204 s] > [INFO] Openmeetings Install ............................... SUCCESS [ > 38.220 s] > [INFO] Openmeetings Service ............................... SUCCESS [ > 37.993 s] > [INFO] Openmeetings Webservices ........................... SUCCESS [03:01 > min] > [INFO] Openmeetings Web ................................... SUCCESS > [01:52 min] > [INFO] Openmeetings Flash ................................. SUCCESS > [05:06 min] > [INFO] Openmeetings Screen Sharing applet ................. SUCCESS [06:08 > min] > [INFO] Openmeetings Server ................................ SUCCESS > [02:52 min] > [INFO] ------------------------------------------------------------ > ------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Total time: 23:17 min > [INFO] Finished at: 2017-03-14T09:25:32+07:00 > [INFO] Final Memory: 81M/529M > [INFO] ------------------------------------------------------------ > ------------ > > > > > On 03/14/2017 08:58 AM, Coscend@OM wrote: > > Hello Dan, > > > > For nightly build, you might want to add the following to your maven > install command. This builds all modules without running tests. > > -P allModules -DskipTests=true > > > > You might want to avoid a similar command -Dmaven.test.skip=true, which > will skip test compilation, thereby giving compilation errors. > > > > Thank you. > > > > Sincerely, > > > > Hemant K. Sabat > > > > Coscend Communications Solutions > > Web site: www.Coscend.com <http://www.coscend.com/> > > ------------------------------------------------------------------ > > *Real-time, Interactive Video Collaboration, Tele-healthcare, > Tele-education, Telepresence Services, on the fly…* > > ------------------------------------------------------------------ > > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > <http://www.coscend.com/Terms_and_Conditions.html> > > > > > > > > > > *From:* Daniel Baker [mailto:[email protected] > <[email protected]>] > *Sent:* Monday, March 13, 2017 7:45 PM > *To:* [email protected] > *Subject:* Re: Apache Maven build failure when issuing mvn clean install > -P allModules > > > > After trying to build I get an error. > > > Maybe this is because it is the nightly build? What I would really like > is branch 3.2.2 as that fixes 2 issues am I am most concerned about. > > How can I build 3.2.2 ? > > Thanks, > > Dan > > > Results : > > Tests in error: > TestUserContact>AbstractWicketTester.setUp:43 » NullPointer > TestUserContact>AbstractWicketTester.setUp:43 » NullPointer > TestUserContact>AbstractWicketTester.setUp:43 » NullPointer > TestUserContact>AbstractWicketTester.setUp:43 » NullPointer > > Tests run: 54, Failures: 0, Errors: 4, Skipped: 0 > > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Openmeetings ....................................... SUCCESS > [25:01 min] > [INFO] Openmeetings Util .................................. SUCCESS > [03:34 min] > [INFO] Openmeetings DB .................................... SUCCESS > [02:22 min] > [INFO] Openmeetings Core .................................. SUCCESS > [01:21 min] > [INFO] Openmeetings Install ............................... SUCCESS [ > 43.018 s] > [INFO] Openmeetings Service ............................... SUCCESS [ > 38.830 s] > [INFO] Openmeetings Webservices ........................... SUCCESS [06:04 > min] > [INFO] Openmeetings Web ................................... FAILURE > [25:44 min] > [INFO] Openmeetings Flash ................................. SKIPPED > [INFO] Openmeetings Screen Sharing applet ................. SKIPPED > [INFO] Openmeetings Server ................................ SKIPPED > [INFO] ------------------------------------------------------------ > ------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------ > ------------ > [INFO] Total time: 01:10 h > [INFO] Finished at: 2017-03-14T07:09:38+07:00 > [INFO] Final Memory: 75M/524M > [INFO] ------------------------------------------------------------ > ------------ > [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-surefire-plugin:2.19.1:test (default-test) on project > openmeetings-web: There are test failures. > [ERROR] > [ERROR] Please refer to /opt/trunk/openmeetings-web/target/surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ > MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :openmeetings-web > > > > > > > > > > > > > > > > > On 03/14/2017 06:26 AM, Daniel Baker wrote: > > There's another step . You have to cd into /trunk. > > Get the source: > > svn checkout https://svn.apache.org/repos/asf/openmeetings/application/trunk/ > > > > *Change into correct directory :* > > *cd /trunk* > > > > Run the command: > > mvn clean install -P allModules > > > > http://openmeetings.apache.org/BuildInstructions.html > > > > Thanks, > > > > Dan > > > > > > On 03/13/2017 07:56 PM, Maxim Solodovnik wrote: > > Just have tested > > Everything works as expected > > Profile definitely exists: > > https://github.com/apache/openmeetings/blob/trunk/pom.xml#L62 > > > > On Mon, Mar 13, 2017 at 4:00 PM, Daniel Baker > > <[email protected]> <[email protected]> wrote: > > The nightly build. So far i've issued two commands : > > > > > > Get the source: > > > > svn checkout > > https://svn.apache.org/repos/asf/openmeetings/application/trunk/ > > > > Run the command: > > > > mvn clean install -P allModules > > > > > > On 03/13/2017 03:30 PM, Maxim Solodovnik wrote: > > > > What branch are you building? > > > > On Mon, Mar 13, 2017 at 1:55 PM, Daniel Baker > > <[email protected]> <[email protected]> wrote: > > > > Hi, > > > > Following your tutorial here > > http://openmeetings.apache.org/BuildInstructions.html > > > > > > apache-maven-3.3.9 # mvn clean install -P allModules > > > > > > I get this error : > > > > > > [INFO] Scanning for projects... > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 0.260 s > > [INFO] Finished at: 2017-03-13T13:29:00+07:00 > > [INFO] Final Memory: 5M/106M > > [INFO] > > ------------------------------------------------------------------------ > > [WARNING] The requested profile "allModules" could not be activated because > > it does not exist. > > [ERROR] The goal you specified requires a project to execute but there is no > > POM in this directory (/opt/apache-maven-3.3.9). Please verify you invoked > > Maven from the correct directory. -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, please > > read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > > > > > > > > I have also tried the command in the parent directory > > /opt/apache-maven-3.3.9 > > > > > > > > I followed the link > > http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException > > from the error message and it says this usually occurs because the command > > is issued from the wrong directory. > > > > > > Anybody else experienced this and how can I resolve this problem ? > > > > > > Thanks, > > > > Dan > > > > > > > > > > > > > > > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com <http://www.avg.com/email-signature> > Version: 2016.0.8007 / Virus Database: 4756/14112 - Release Date: 03/13/17 > > No virus found in this message. > Checked by AVG - www.avg.com <http://www.avg.com/email-signature> > Version: 2016.0.8007 / Virus Database: 4756/14112 - Release Date: 03/13/17 > > > -- WBR Maxim aka solomax
