I will rollback the emma version (scheduled to do that this afternoon), I did update to check if a bug was fixed.... but it isn't.
VELO On Thu, Jun 11, 2009 at 9:53 AM, John R. Fallows <[email protected]>wrote: > On Thu, Jun 11, 2009 at 1:48 PM, Marvin Froeder <[email protected]> wrote: > >> Ok, now I understudy what you meant... sorry my bad. > > > No problem. > > Would you mind staging the emma dependency on the flex-mojos repository > until it is available on the default Maven repository, just so we can get > the flex-mojos build fully automated again? > > Kind Regards, > John Fallows > > >> >> >> On Thu, Jun 11, 2009 at 9:46 AM, John R. Fallows < >> [email protected]> wrote: >> >>> On Wed, Jun 10, 2009 at 4:57 PM, Marvin Froeder <[email protected]>wrote: >>> >>>> Note: in order to fully test the build dependencies, it may be necessary >>>>> to remove (or rename) ~/.m2/repository directory before executing mvn -P >>>>> minimal clean install. >>>>> >>>> >>>> >>>> I never had to do that.... why do you need to remove local repo? >>>> >>> >>> Say you are building different independent projects using Maven, >>> Project-A and Project-B. >>> >>> Project-A has a dependency on something from a public but non-default >>> repository, like the java.net repository, so Project-A includes a >>> <repository> element allowing the java.net dependency to download and >>> populate the local ~/.m2/repository. >>> >>> Project-B also has a dependency on the same thing from a public but >>> non-default repository, like the java.net repository, but Project-B >>> omitted the <repository> element. >>> >>> Building Project-A first causes ~/.m2/repository to be populated with the >>> java.net dependency. Then Project-B can build successfully, because all >>> dependencies can be resolved from the local repository. >>> >>> However, Project-B's pom is still not correct, but this is difficult to >>> detect without first removing (or renaming) ~/.m2/repository and then >>> performing a clean build for Project-B. Without the dependency >>> pre-populated in the local repository, the Project-B build now breaks. >>> >>> In short, side effects of the Project-A build can cause the Project-B >>> build to be successful even though an independent build of Project-B would >>> fail. >>> >>> Kind Regards, >>> John Fallows >>> >>> >>>> >>>> >>>> VELO >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
