Hi Justin,
when doing my tests with an empty local maven repo I did encounter this message you were talking about. It's log output of the mavenizer. I remember having problems of the mavenizer kicking in, but I had no Idea what dependency actually triggered it getting active, so I added some info-level output containing the maven coordinates causing the activity. So this is actually just a normal information the mavenizer outputs when working correctly. :-) Chris ________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Freitag, 8. Juli 2016 10:44:56 An: dev@flex.apache.org Betreff: Re: [FlexJS] Developer Setup Hi, > Ok, I didn't put in the entire command ... as soon as we have released the > Mavenizer, the command I posted would work, but till then, you need the "-s > settings-template.xml" ;-) Much better, it's running along nicely now. Although I did notice this in the output: [INFO] Couldn't find artifact: org.apache.flex.compiler:4.15.0:swfutils:pom Thanks, Justin
