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 wi
I changed the dependency on flexunit to
org.apache.flex.flexunit
flexunit-flex
4.3.0-SNAPSHOT
swc
test
since I saw that in the repo and nothing for org.flexunit. With this
version of flexunit, and my hacked maven exte
Hey Chris.
Ok, so attempts to build with a full pom continue to fail, though I think I
know why. I added more logging to my custom maven extension to help me
understand better what was happening and it seems i'm failing on the first
artifact in the flex sdk:
[INFO] In order to convert some of th
Perfect. Both the playerglobal and fontkit only poms build correctly now
that I'm pointed to the correct artifact :). I didn't realize the
artifactId had changed so was still using the old one.
Now on to a full blown pom. Thanks!
--
View this message in context:
http://apache-flex-developme
Ok, seems the maven extension artifactId changed. I'll try with
"flex-sdk-converter-maven-extension".
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Problems-Installing-Flash-SDK-according-to-documentation-tp48319p48937.html
Sent from the Apache Flex Deve
Hey Chris.
I tried to build this morning with the 1.0.0-SNAPSHOT, but it doesn't look
like it's picking up a new jar. This is what is being resolved for the
extension dependency:
Downloading:
http://repository.apache.org/content/groups/snapshots/org/apache/flex/utilities/converter/maven-extensio
Betreff: Re: AW: AW: AW: AW: AW: AW: Problems Installing Flash SDK according to
documentation
Ok made more progress today.
It seems the reason my Fontkit only pom was failing was a side effect of
previous attempts to download the fontkit libraries with the 1.0.0-SNAPSHOT
version of the maven extensi
Ok made more progress today.
It seems the reason my Fontkit only pom was failing was a side effect of
previous attempts to download the fontkit libraries with the 1.0.0-SNAPSHOT
version of the maven extension. Because it doesn't utilize the proxies, it
wrote out _remote.repositories and .lastUpda
Sorry about the previous message... Here it is formatted correctly
(hopefully).
Ok. That makes sense about the ProxyTest. It's interesting because that
test will always fail for anyone building the maven extension that IS behind
a proxy... You'd almost have to check if the environment the test
Ok. That makes sense about the ProxyTest. It's interesting because that
test will always fail for anyone building the maven extension that IS behind
a proxy... You'd almost have to check if the environment the test is
running on is behind a proxy, and if so then try to use those proxy
settings.
Hi,
the proxy test was intended to run on a machine without actually needing a
proxy. I could immagine, that if you run it on a machine with proxy-settings in
place, that the "run without" test will definitely fail, cause your maven
settings enables them ... this could be a strange szenario ...
11 matches
Mail list logo