Do you mean using "mvn install" or some flex-mojos install thing? We only use flex-mojos in the build fase. To build/compile the Flex sources.
On Thu, Nov 12, 2009 at 1:08 PM, Marvin Froeder <[email protected]> wrote: > Well, if you are using install-mojo I can't help you. > > It is banned, was deleted from the project and by definition his bad usage > causes problems like this one you have. > > > VELO > > On Thu, Nov 12, 2009 at 10:01 AM, Robbert de Vries < > [email protected]> wrote: > >> I might be too much of a newby in these matters (maven, flex-mojos) to >> know what you mean by that remark :) >> Do you mean that locally I don't install, and on the build server I do? >> And that this is the actual difference in environments? >> I use the install mojo locally too. Works perfectly. >> >> This morning I realised there are 2 ways to solve this; >> > find out where that unneeded dependency is defined; then get rid of the >> unneeded dependency (most preferable, and being the only path tried so far) >> > download and install the unneeded dependency manually (as maven >> suggests) >> >> The problem with the latter is that the dependency in the missing language >> is not available in any >> of the repositories. Which is also kind of strange as an isolated fact, >> isn't it? >> mvn install:install-file -DgroupId=com.adobe.flex.framework >> -DartifactId=automation -Dversion=3.2.0.3958 -Dclassifier=nl_NL >> -Dpackaging=rb.swc -Dfile=/path/to/file >> >> >> >> On Thu, Nov 12, 2009 at 11:07 AM, Marvin Froeder <[email protected]>wrote: >> >>> That smells like install mojo abuse >>> >>> >>> On Thu, Nov 12, 2009 at 7:46 AM, Robbert de Vries < >>> [email protected]> wrote: >>> >>>> Ok... done that... on the parent-pom level. >>>> I don't find any dependencies on automation. >>>> >>>> The strange thing is, and remains: it builds perfectly locally, but not >>>> on the build server. >>>> What could be different between these 2 environments? >>>> The actual project is exactly the same. >>>> There has to be something different in de environment that 'creates' the >>>> dependency. >>>> Well, at least that's my hunch. >>>> >>>> Any other thoughts? >>>> >>>> Robbert >>>> >>>> >>>> >>>> >>>> >>>> On Wed, Nov 11, 2009 at 6:09 PM, Marvin Froeder <[email protected]>wrote: >>>> >>>>> Review all your poms... one is dependending on automation.... >>>>> >>>>> mvn help:effective-pom that should bring some light into that matter. >>>>> >>>>> >>>>> VELO >>>>> >>>>> >>>>> On Wed, Nov 11, 2009 at 2:27 PM, Robbert de Vries < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi there! >>>>>> >>>>>> *Some history first; (see next section for the actual problem) * >>>>>> >>>>>> Recently, it was requested that our Flex application, which was >>>>>> single-language, should be bilingual. >>>>>> The languages I've implemented now are nl_NL and en_US. >>>>>> >>>>>> In the process, we've moved from flex-mojos version 2.0.3 to version >>>>>> 3.4.2. >>>>>> Which meant a change in repository URLs and naming of the >>>>>> groupId/artifactId of the flexmojos maven plugin. >>>>>> Also, we stopped using the flexmojos-super-poms. (And I can't remember >>>>>> what the reason for doing so was :)) >>>>>> >>>>>> For the i18n, we decided to put all languages in one SWF file. (it's >>>>>> only 2 languages and little texts) >>>>>> So I've added some parameters to the flexmojos maven plugin. >>>>>> Most importantly: >>>>>> >>>>>> <resourceBundlePath>${basedir}/locale/{locale}</resourceBundlePath> >>>>>> <compiledLocales> >>>>>> <locale>en_US</locale> >>>>>> <locale>nl_NL</locale> >>>>>> </compiledLocales> >>>>>> <mergeResourceBundle>false</mergeResourceBundle> >>>>>> >>>>>> And I've run copylocale with the appropriate parameters. >>>>>> Locally, everything builds (maven, obviously) and runs (jetty) >>>>>> perfectly. >>>>>> Both on a Windows machine and an Ubuntu Linux machine. >>>>>> >>>>>> >>>>>> *Now for the actual problem! * >>>>>> >>>>>> We use a continuous build server, Atlassian Bamboo, which runs on >>>>>> Unix. >>>>>> On this machine, I've had the 'copylocale' command run exactly as I >>>>>> did on my Ubuntu machine; >>>>>> "copylocale en_US nl_NL" >>>>>> That resulted in likewise logging indicating no problems. >>>>>> >>>>>> But the build server doesn't want to build the project, and this is >>>>>> what maven is complaining about: >>>>>> [INFO] Failed to resolve artifact. >>>>>> GroupId: com.adobe.flex.framework >>>>>> ArtifactId: automation >>>>>> Version: 3.2.0.3958 >>>>>> It's not finding the nl_NL version of the automation library files. >>>>>> I've looked manually and couldn't find them either. >>>>>> It seems that the new version of the maven flexmojos needs this file, >>>>>> according to the following log-extract: >>>>>> 11-Nov-2009 14:53:20 [INFO] [flexmojos:compile-swc] >>>>>> 11-Nov-2009 14:53:20 [INFO] Flexmojos 3.4.2 - Apache License (NO >>>>>> WARRANTY) - See COPYRIGHT file >>>>>> 11-Nov-2009 14:53:20 Downloading: >>>>>> http://10.20.4.36/repository/com/adobe/flex/framework/automation/3.2.0.3958/automation-3.2.0.3958-nl_NL.rb.swc >>>>>> >>>>>> But, as just stated, it's not able to find it in any of the repo's, >>>>>> resulting in the build error. >>>>>> The very strange thing is; >>>>>> we don't use or need automation. It seems that the flexmojos itself >>>>>> wants to have it. >>>>>> Although not locally, but only on the build server. >>>>>> >>>>>> Does anyone have a hunch.... as into which direction to try and solve >>>>>> this? >>>>>> >>>>>> Thanks in advance and kind regards, >>>>>> Robbert de Vries >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> --~--~---------~--~----~------------~-------~--~----~ >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Flex Mojos" group. >>>>> To post to this group, send email to [email protected] >>>>> To unsubscribe from this group, send email to >>>>> [email protected]<flex-mojos%[email protected]> >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/flex-mojos?hl=en?hl=en >>>>> >>>>> http://blog.flex-mojos.info/ >>>>> -~----------~----~----~----~------~----~------~--~--- >>>>> >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Flex Mojos" group. >>>> To post to this group, send email to [email protected] >>>> To unsubscribe from this group, send email to >>>> [email protected]<flex-mojos%[email protected]> >>>> For more options, visit this group at >>>> http://groups.google.com/group/flex-mojos?hl=en?hl=en >>>> >>>> http://blog.flex-mojos.info/ >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Flex Mojos" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected]<flex-mojos%[email protected]> >>> For more options, visit this group at >>> http://groups.google.com/group/flex-mojos?hl=en?hl=en >>> >>> http://blog.flex-mojos.info/ >>> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Flex Mojos" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected]<flex-mojos%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/flex-mojos?hl=en?hl=en >> >> http://blog.flex-mojos.info/ >> > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<flex-mojos%[email protected]> > For more options, visit this group at > http://groups.google.com/group/flex-mojos?hl=en?hl=en > > http://blog.flex-mojos.info/ > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/
