openmeetings-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Solodovnik <solomax...@gmail.com>
Subject Re: Current usage of the pom.xml
Date Sat, 03 May 2014 05:44:04 GMT
build uses java6 :)
I hope we will move to latest Flex (commented right now)
http://apache-flex-users.2333346.n4.nabble.com/flexmojos-maven-plugin-building-flex-project-without-mavenizing-Flex-binaries-td6313.html


On Sat, May 3, 2014 at 12:12 PM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:

> I have come to some kind of solution :)
>
> The version of Flex that is bundled with OpenLaszlo 4.9.5 has a file:
>
> /Openmeetings/openmeetings-flash/target/openlaszlo/openlaszlo46/WEB-INF/flexsdk/4.6.0/bin/mxml
>
> This file is the shell script that triggers the flex compiler and contains
> this a command like:
>
> java $VMARGS *$D32* $SETUP_SH_VMARGS -jar "$FLEX_HOME/lib/mxmlc.jar" +
> flexlib="$FLEX_HOME/frameworks" "$@"
>
> On my machine $D32 will filled with -d32. Which starts the JVM in 32 Bit
> mode.
>
> In Java7 the -d32 option is no more available. At least for the Java7 Mac
> OSx version.
>
> When I remove the $D32 option the flash compilation runs fine.
>
> Maybe useful to share. Hopefully this does not happen on our build server.
>
> Sebastian
>
>
>
>
>
> 2014-05-03 16:44 GMT+12:00 Maxim Solodovnik <solomax666@gmail.com>:
>
> This is my current java:
>>
>> java -version
>> java version "1.7.0_51"
>> Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
>> Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
>>
>> never saw error like this :(
>>
>>
>> On Sat, May 3, 2014 at 11:14 AM, seba.wagner@gmail.com <
>> seba.wagner@gmail.com> wrote:
>>
>>> No worries
>>>
>>> Java7, hm with Java7 I get this issue:
>>> -compile.flash:
>>>      [java] Compiling: main.as3.lzx to maindebug.as3.swf11.swf
>>>      [java] Compilation errors occurred:
>>>      [java] org.openlaszlo.sc.CompilerError: tunit/line unknown: , in
>>> line: Error: This Java instance does not support a 32-bit JVM.
>>>      [java] Please install the desired version.
>>>      [java]
>>>
>>>
>>> 2014-05-03 15:55 GMT+12:00 Maxim Solodovnik <solomax666@gmail.com>:
>>>
>>> I'm using java7 in everyday work
>>>> java6 for releases only
>>>>
>>>> tests works for me :)
>>>> packaging is not ready, we have lots of holidays in Russia these days
>>>> :) and I'm trying to fix Joomla plugin to work with joomla 3.3
>>>> hopefully will fix the build later :)
>>>>
>>>>
>>>> On Sat, May 3, 2014 at 10:38 AM, seba.wagner@gmail.com <
>>>> seba.wagner@gmail.com> wrote:
>>>>
>>>>> 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 <solomax666@gmail.com>:
>>>>>
>>>>> 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, seba.wagner@gmail.com <
>>>>>> seba.wagner@gmail.com> 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 seba.wagner@gmail.com <
>>>>>>> seba.wagner@gmail.com>:
>>>>>>>
>>>>>>> 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 seba.wagner@gmail.com <
>>>>>>>> seba.wagner@gmail.com>:
>>>>>>>>
>>>>>>>> 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 <solomax666@gmail.com>:
>>>>>>>>>
>>>>>>>>> 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, seba.wagner@gmail.com
<
>>>>>>>>>> seba.wagner@gmail.com> 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 <solomax666@gmail.com
>>>>>>>>>>> >:
>>>>>>>>>>>
>>>>>>>>>>> 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
<
>>>>>>>>>>>> solomax666@gmail.com> 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, "seba.wagner@gmail.com"
<
>>>>>>>>>>>>> seba.wagner@gmail.com> 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
>>>>>>>>>>>>>> seba.wagner@gmail.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> WBR
>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sebastian Wagner
>>>>>>>>>>> https://twitter.com/#!/dead_lock
>>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>>> seba.wagner@gmail.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> WBR
>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sebastian Wagner
>>>>>>>>> https://twitter.com/#!/dead_lock
>>>>>>>>> http://www.webbase-design.de
>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>> seba.wagner@gmail.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sebastian Wagner
>>>>>>>> https://twitter.com/#!/dead_lock
>>>>>>>> http://www.webbase-design.de
>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>> seba.wagner@gmail.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sebastian Wagner
>>>>>>> https://twitter.com/#!/dead_lock
>>>>>>> http://www.webbase-design.de
>>>>>>> http://www.wagner-sebastian.com
>>>>>>> seba.wagner@gmail.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sebastian Wagner
>>>>> https://twitter.com/#!/dead_lock
>>>>> http://www.webbase-design.de
>>>>> http://www.wagner-sebastian.com
>>>>> seba.wagner@gmail.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> https://twitter.com/#!/dead_lock
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>



-- 
WBR
Maxim aka solomax

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message