Dear All, We are using Maven 2.1.0 with resource bundles with any issues. However, there was one issue with the Maven Integration for Eclipse (plugin)
-- the m2eclipse from codehaus. While running multi module builds we found that the dependencies were not getting properly resolved. Some dependencies were getting referred to the target/classes folder. This happens when you right the multi module project and say run as. --> Maven Build ... There are 6 check boxes in the Edit configuration and launch window. One of these check boxes is the Resolve workspace artifacts which is checked by default. We need to un check it to get rid of this issue. Otherwise maven 2.1.0 works great without any issues. Hope this helps. best regards sriraman. On Fri, Jun 5, 2009 at 3:54 AM, Logan Allred <[email protected]> wrote: > > On Thu, Jun 4, 2009 at 12:31 PM, Marvin Froeder<[email protected]> wrote: > > Same here... > > It works fine, but I don't build resource bundles, just consume. > > So far I kept flexmojos integration tests compatible with maven 2.0.9 > > The problem only seems to happen when you build the resource bundle > along with the project that dependends on them. > > So if appA needs libB and libB has resource bundles, then appA can't > find libB.rb.swc when they are both part of the same build. If you > build libB and appA independently, they both work. > > Logan > > > > --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
