Hey Chris.

I took some time today to create a patch for the mavenizer, I've attached it
to this post.  I hope this helps and you don't have to change too much with
it.  I fixed two issues.

The first is the one mentioned a couple days ago.  The BaseConverter is not
using the proxy when checking with maven central for an artifact.

The second is the the CLI converter doesn't use any proxy information.  I
added support for using the information in the HTTP_PROXY env variable.  

Both of these fixes are for proxies that don't require authentication.  I'm
not sure if there was a better way to do it, and I didn't create any new
unit tests, but with this in place, I can use both the maven extension and
the CLI to mavenize the flex/flash/air/fontkit sdks.

Hopefully there are no apache licensing issues as I applied the apache
license header to the only class I added. proxyUpdates.patch
<http://apache-flex-development.2333347.n4.nabble.com/file/n48946/proxyUpdates.patch>
  



--
View this message in context: 
http://apache-flex-development.2333347.n4.nabble.com/Problems-Installing-Flash-SDK-according-to-documentation-tp48319p48946.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Reply via email to