Hi Maxim, thanks I figured it out. I could fix the build for me. I have added a minor change: http://svn.apache.org/viewvc?view=revision&revision=r1592141 That made the openmeetings-web and eclipse:eclipse work fine for all modules. It was a bit strange, I had to build module by module in the end.
The only thing remaining seems to fix the tests of the openmeetings-web module. During the tests of openmeetings-web I could see some exceptions, for example one was: Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.apache.openmeetings.db.dao.room.IInvitationManager org.apache.openmeetings.db.dao.calendar.AppointmentDao.invitationManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'invitationManagement': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.apache.openmeetings.core.mail.SMSHandler org.apache.openmeetings.service.room.InvitationManager.smsHandler; nested exception is java.lang.UnsupportedClassVersionError: org/smslib/AGateway : Unsupported major.minor version 51.0 Is the org/smslib/AGateway a Java 7 library ? What are you using the build, is it java6 or java7 ? Thanks, Sebastian 2014-05-03 15:34 GMT+12:00 Maxim Solodovnik <[email protected]>: > Hello Sebastian, > > mvn clean install -Dmaven.test.skip=true > > mvn clean install -pl openmeetings-web -am -Dmaven.test.skip=true > > > > On Sat, May 3, 2014 at 7:08 AM, [email protected] < > [email protected]> wrote: > >> I have added >> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetingsMaven/ >> to test. >> >> We can set up a new build with a different name and copy the >> configuration if we are happy with the results. >> >> And I played a little bit around using mvn eclipse:eclipse. >> I think we need to do some stuff to generate the Eclipse configuration >> files by Maven. >> It somehow creates a couple of files but the packages et cetera are not >> set up correctly. >> >> Sebastian >> >> >> 2014-05-03 11:12 GMT+12:00 [email protected] <[email protected]>: >> >> When I simply run mvn without specifiying a target I get this error: >>> [ERROR] Failed to execute goal on project openmeetings-web: Could not >>> resolve dependencies for project >>> org.apache.openmeetings:openmeetings-web:war:3.1.0-SNAPSHOT: The following >>> artifacts could not be resolved: >>> org.apache.openmeetings:openmeetings-service:jar:3.1.0-SNAPSHOT, >>> org.apache.openmeetings:openmeetings-webservice:jar:3.1.0-SNAPSHOT, >>> org.apache.openmeetings:openmeetings-core:jar:tests:3.1.0-SNAPSHOT: Failure >>> to find org.apache.openmeetings:openmeetings-service:jar:3.1.0-SNAPSHOT in >>> http://red5.googlecode.com/svn/repository was cached in the local >>> repository, resolution will not be reattempted until the update interval of >>> Red5 has elapsed or updates are forced -> [Help 1] >>> >>> >>> 2014-05-03 10:39 GMT+12:00 [email protected] <[email protected]> >>> : >>> >>> What are the Maven targets / commands that you use to build/develop >>>> OpenMeetings at the moment ? >>>> >>>> Thanks, >>>> Sebastian >>>> >>>> >>>> 2014-04-29 3:45 GMT+12:00 Maxim Solodovnik <[email protected]>: >>>> >>>> I believe we will use this guide next release :) >>>>> Here is the way to change version only >>>>> http://stackoverflow.com/questions/5726291/updating-version-numbers-of-modules-in-a-multi-module-maven-project >>>>> >>>>> >>>>> On Mon, Apr 28, 2014 at 3:54 AM, [email protected] < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Maxim, >>>>>> >>>>>> awesome news! I will test this in the next couple of days. >>>>>> >>>>>> One of the upcoming tasks would be to have Maven also create and >>>>>> manage our release process. >>>>>> >>>>>> Normally with Maven you can release a new package with one line of >>>>>> mvn. >>>>>> Something like mvn release:release -version 3.0.2 -nextVersion >>>>>> >>>>>> What normally happens when you use that command is that it: >>>>>> 1) Create the release artifacts with the correct Version name without >>>>>> "-SNAPSHOT" >>>>>> 2) Uploads the release artifacts to the Maven repository >>>>>> 3) Create a SVN-Tag for the release version >>>>>> 4) Update and increase the pom.xml with the version string of the >>>>>> next SNAPSHOT >>>>>> >>>>>> This is basically all described in the Maven release plugin: >>>>>> http://maven.apache.org/maven-release/maven-release-plugin/usage.html >>>>>> https://maven.apache.org/guides/mini/guide-releasing.html >>>>>> >>>>>> There is even a guide how to do this for Maven for the Apache >>>>>> Foundation: >>>>>> https://www.apache.org/dev/publishing-maven-artifacts.html >>>>>> >>>>>> The guide also shows how to configure Maven to automatically sign the >>>>>> code/packages: >>>>>> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env >>>>>> >>>>>> I think on the long run it would be really worthwhile considering >>>>>> applying this guide. Making a release is currently a multi-step process. >>>>>> With this guide we might be able to shrink it to one command. That >>>>>> makes it a lot more handy for the release manager (and also for anybody >>>>>> else that wants to step up into that role). >>>>>> >>>>>> Maybe we try to use this guide when we are ready for the next >>>>>> release. What do you think ? >>>>>> >>>>>> Sebastian >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> 2014-04-28 3:56 GMT+12:00 Maxim Solodovnik <[email protected]>: >>>>>> >>>>>> Hello Sebastian, >>>>>>> >>>>>>> here are the migration news: all modules seems to be converted :) >>>>>>> >>>>>>> Assembly and site building need to be added. Will try to add this in >>>>>>> the end of next week. >>>>>>> >>>>>>> Additional task is: developer "fast" build should be added >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sat, Apr 12, 2014 at 1:31 PM, Maxim Solodovnik < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hello Sebastian, >>>>>>>> >>>>>>>> I'm currently in the middle of my trip from ApacheCon Denver :) >>>>>>>> >>>>>>>> I really enjoy the conference this year. >>>>>>>> >>>>>>>> Maven build status is: the very first initial version is ready: >>>>>>>> artifacts are able to build with tests turned off. >>>>>>>> >>>>>>>> Next steps would be: >>>>>>>> 1) add build of flash component (with action script migration, to >>>>>>>> remove openlazlo dependency) >>>>>>>> 2) add red5 server retrieving >>>>>>>> 3) add step to create big package of everything currently being >>>>>>>> released >>>>>>>> 4) add steps for our webstart app. >>>>>>>> >>>>>>>> I believe it will require lots of work and refactoring. >>>>>>>> >>>>>>>> Hopefully I'll be able to finish this, maven community seems to be >>>>>>>> responcive enough and they already help me a lot. >>>>>>>> >>>>>>>> I currently would like to release 3.0.1, resolve couple of issues >>>>>>>> and then continue with the build. >>>>>>>> On Apr 12, 2014 6:31 AM, "[email protected]" < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Maxim, >>>>>>>>> >>>>>>>>> how are you doing? I have seen a number of changes in the project >>>>>>>>> structure. I think its exciting to see those changes. It gives us the >>>>>>>>> chance to get rid of quite a bit of custom build scripts in the >>>>>>>>> future. >>>>>>>>> >>>>>>>>> I was wondering if we need to update the Build Instructions yet? >>>>>>>>> >>>>>>>>> Is the there a dependency between the pom.xml and the build.xml or >>>>>>>>> are this two completely independent build files ? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Sebastian >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sebastian Wagner >>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>> http://www.webbase-design.de >>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>> [email protected] >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sebastian Wagner >>>>>> https://twitter.com/#!/dead_lock >>>>>> http://www.webbase-design.de >>>>>> http://www.wagner-sebastian.com >>>>>> [email protected] >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> WBR >>>>> Maxim aka solomax >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
