You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by kamcknig <ka...@gmail.com> on 2019/04/21 20:07:40 UTC
Error with flex-tool-api-jar in modules/downloads.xml
Hello,
So building 4.15.0 gives me errors with the flex-tool-api-jar target in
modules/downloads.xml with the following error
https://pastebin.com/Kcs0SwX5
I looked at the latest 4.16.1 tag and the URLs themselves look like they
don't changed, just the way in which errors are handled. I'm not sure how to
fix this in this case.
Kyle
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I think the README says to use environment variables. I think env.properties is only for integration tests.
HTH,
-Alex
On 4/24/19, 5:24 AM, "kamcknig" <ka...@gmail.com> wrote:
It looks like I got it working, at least it compiled, I haven't yet tried to
use the resultant libraries.
Though I still had problems and this is what I had to do:
1. I reset the branch so that my local repo matches tag 4.15.0 as it is in
the remote repo.
2. Updated env.properties in the base Flex SDK source folder to point to the
Java 8 64-bit JDK
3. I compiled and ran into this issue https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2FdKnF08Ti&data=02%7C01%7Caharui%40adobe.com%7C38a20a1b3fed4b768dbe08d6c8afbfbf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636917054537724147&sdata=fN4WBF%2Bcy9Vv%2Fd6d%2FxaLGVwgvJo1WRFMWmRu%2Fo3naHM%3D&reserved=0 which I
solved by removing the 'target' and 'source' attributes from the compile
target of modules/xerces-patch/build.xml file.
4. I compiled again and ran into a problem with the velocity jars. I noticed
in the output that the velocity build wasn't using the right JDK (it was
still pointed at the Amazon Corretto one). I couldn't figure out why that
was so I just had to set the actual environment variable JAVA_HOME to the
right JDK rather than being able to use the env.properties file in the base
Flex SDK folder.
After that the build was reported successful
Thanks for all your help. If you have any insight into #4 as to why ti
wouldn't pick up the right JDK it'd be appreciated. I built with verbose on
as well just to see but when it got to that build step it just said that it
was ignoring the java.home override. So I'm not quite sure why it was using
the environment variable and not inheriting from the env.properties file.
Kyle
--
Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C38a20a1b3fed4b768dbe08d6c8afbfbf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636917054537724147&sdata=DnERX89Libvb0CqqSHnJUJYLZCjq3EmcgtpKewFz8Oc%3D&reserved=0
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by kamcknig <ka...@gmail.com>.
It looks like I got it working, at least it compiled, I haven't yet tried to
use the resultant libraries.
Though I still had problems and this is what I had to do:
1. I reset the branch so that my local repo matches tag 4.15.0 as it is in
the remote repo.
2. Updated env.properties in the base Flex SDK source folder to point to the
Java 8 64-bit JDK
3. I compiled and ran into this issue https://pastebin.com/dKnF08Ti which I
solved by removing the 'target' and 'source' attributes from the compile
target of modules/xerces-patch/build.xml file.
4. I compiled again and ran into a problem with the velocity jars. I noticed
in the output that the velocity build wasn't using the right JDK (it was
still pointed at the Amazon Corretto one). I couldn't figure out why that
was so I just had to set the actual environment variable JAVA_HOME to the
right JDK rather than being able to use the env.properties file in the base
Flex SDK folder.
After that the build was reported successful
Thanks for all your help. If you have any insight into #4 as to why ti
wouldn't pick up the right JDK it'd be appreciated. I built with verbose on
as well just to see but when it got to that build step it just said that it
was ignoring the java.home override. So I'm not quite sure why it was using
the environment variable and not inheriting from the env.properties file.
Kyle
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Please use Java 8 64-bit. What problems do you run into with that version?
-Alex
On 4/23/19, 6:44 PM, "kamcknig" <ka...@gmail.com> wrote:
I downloaded the oracle 32 and 64 bit versions of 8 and the 64 bit version of
12. But none of them seem to work as well. Looks like 6 and 7 are harder to
get now
KYle
--
Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C5b07d99efe4e4e2225db08d6c85654f2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636916670452656888&sdata=jbRztT7QxX%2Fmt25TvM%2FDgY0QV7n%2Bjh%2BQbDJEqYTBvGw%3D&reserved=0
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by kamcknig <ka...@gmail.com>.
I downloaded the oracle 32 and 64 bit versions of 8 and the 64 bit version of
12. But none of them seem to work as well. Looks like 6 and 7 are harder to
get now
KYle
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi,
You seem to be using a version of Java that Flex does not support. Is there some reason you have to use the version you are using?
Thanks,
-Alex
On 4/21/19, 1:45 PM, "kamcknig" <ka...@gmail.com> wrote:
I should wait a few before posting :)
So after paying closer attention to the difference between 4.15.0 and
4.16.1, a "/" was as well in the target to download the jars. I removed that
"/" from 4.15.0 modules/downloads.xml and was able to download the jars from
the maven repository.
However, I then ran into a problem compiling the thirdparty xerces library
(and then subsequently many others) that had the following error:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2Fj3eLTR6c&data=02%7C01%7Caharui%40adobe.com%7C2837f03d9a3f44b88f0e08d6c69a46ee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636914763302790455&sdata=bi%2BURDQpyaDmojA2vPlsnnu0KRSJENOlokBdcmb52EI%3D&reserved=0
I tried changing the javac.src property to 1.6 but that didn't work, so I
just tried removing the 'source' and 'target' attributes from each of the
javac tasks for those targets that failed. Not sure if that was the best
solution, but it seemed to have worked.
Lastly... I'm stuck again and this time I haven't found the answer yet. I'm
getting an error with compiling the debugger it looks like and I don't know
enough about java compilation and these files to determine what is going on
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2FDFFvERRb&data=02%7C01%7Caharui%40adobe.com%7C2837f03d9a3f44b88f0e08d6c69a46ee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636914763302790455&sdata=2ldfGV72Rjff%2BO47smXNwPuOXsQ%2BLukDtWhysf9dlxQ%3D&reserved=0
Thanks,
Kyle
--
Sent from: https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C2837f03d9a3f44b88f0e08d6c69a46ee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636914763302790455&sdata=OuKuLgsSFWWNjP3tte%2F%2FPCm%2FttRWYlc4sXaDYVd2kgQ%3D&reserved=0
Re: Error with flex-tool-api-jar in modules/downloads.xml
Posted by kamcknig <ka...@gmail.com>.
I should wait a few before posting :)
So after paying closer attention to the difference between 4.15.0 and
4.16.1, a "/" was as well in the target to download the jars. I removed that
"/" from 4.15.0 modules/downloads.xml and was able to download the jars from
the maven repository.
However, I then ran into a problem compiling the thirdparty xerces library
(and then subsequently many others) that had the following error:
https://pastebin.com/j3eLTR6c
I tried changing the javac.src property to 1.6 but that didn't work, so I
just tried removing the 'source' and 'target' attributes from each of the
javac tasks for those targets that failed. Not sure if that was the best
solution, but it seemed to have worked.
Lastly... I'm stuck again and this time I haven't found the answer yet. I'm
getting an error with compiling the debugger it looks like and I don't know
enough about java compilation and these files to determine what is going on
https://pastebin.com/DFFvERRb
Thanks,
Kyle
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/