Guys -
The new version sounds good. I'll tell you step by step how I interpreted the
instructions, but I feel I have such a disconnect I don't want to waste your
time.
Pre-README: Installed Flash Builder 4.7.0. Added "4.9.0" directory underneath
Flash Builder sdks.
1. Unzip the source distribution. You should see the 'installer' directory
and the
'common' directory in the root.
No problem - I'm not a linux admin type, but know command line and have done
sudo installs.
2. In the installer directory run:
ant get-as3commons.swc
This step downloads the required as3commons library and saves it in the
libs
directory.
In running this, I get a message, but the build is successful. Only later do I
figure out from Justin that this is something that needs to be dealt with. The
reason I blow this message off is because it isn't indicated as an error, and
during a typical make/make install there are a lot of messages that I usually
ignore.
$ ant get-as3commons.swc
Buildfile:
/Users/jk/Downloads/apache-flex-sdk-installer-2.0.2-src/installer/build.xml
[taskdef] Could not load definitions from resource flexTasks.tasks. It could
not be found. check-as3commons.swc: get-as3commons.swc:
[mkdir] Created dir:
/Users/jk/Downloads/apache-flex-sdk-installer-2.0.2-src/installer/libs
[get] Getting:
http://projects.yoolab.org/maven/content/repositories/releases/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc
[get] To:
/Users/jk/Downloads/apache-flex-sdk-installer-2.0.2-src/installer/libs/as3commons-zip-1.0.0-alpha.1.swc
[get] ..........
[get] Getting:
http://projects.yoolab.org/maven/content/repositories/releases/org/as3commons/as3commons-zip/1.0.0-alpha.1/as3commons-zip-1.0.0-alpha.1.swc.md5
[get] To:
/Users/jk/Downloads/apache-flex-sdk-installer-2.0.2-src/installer/libs/as3commons-zip-1.0.0-alpha.1.swc.md5
[get] .
[delete] Deleting:
/Users/jk/Downloads/apache-flex-sdk-installer-2.0.2-src/installer/libs/as3commons-zip-1.0.0-alpha.1.swc.md5
BUILD SUCCESSFUL Total time: 2 seconds
At first, I moved on, but later when nothing worked I went back to this step
and asked users@ what the message meant.
As a fix for this, Justin suggests:
Ant can't find flexTasks, add flexTask.jar to your ANT lib directory or pass it
to ant via -lib. You can find it in the Flex SDK modules/antTasks.
I really have no idea what this means, so I start searching for 'flexTask.jar'
and the directory 'modules' from the source directory, both turn up nothing:
$ find . -name "modules"
$ find . -name "flexTask.jar"
$
So I go to Google, and I see:
the flexTasks.jar file is located at flash_builder_install/sdks/4.6.0/ant/lib
There is no flash_builder_install, and the previous search of the installer
directory turned up null, so I assume flash_builder_install is the installed
directory. 4.9.0 is still empty, so I go back to my old 4.6.0, which does have
the flexTasks.jar, but is this correct to use an older version? Assuming that's
correct, which I don't think it is, I'm really not sure where the SDK is at
this point - I only have the installer. Or does the installer contain the SDK?
A search didn't show any module directories. So I try and look for a tarball
within the installer source:
$ find . -name "*tar*"
$
Which returns nothing. I realize at this point that I have no idea what's going
on, but unfortunately I don't have the time to clear the confusion on my own.
In my original effort (before writing Justin), I had ignored the original
message and went onto step 3.
3. If using Adobe Flash Builder, add a linked resource called:
APACHE_FLEX_UTILITIES_ROOT
and point it to the directory path where the 'installer' and 'common'
directories are
located.
I am using FB 4.7, so I go into FB and figure out how to add the linked
resource. I believe I did that correctly, I move onto step 4.
4. In the installer project, add ${APACHE_FLEX_UTILITIES_ROOT}/common/src as a
source path.
At this point, I have no idea what "installer project" refers to. I was purely
working command line, up until step 3. I believe the inference is that somehow
there is a project in FB which is managing the installation of the SDK, but I
have really no concept how the focus changed from command line to FB, except in
step 3, which only indicated to set a variable. So I speculate, and I wonder if
the variable sets up some sort of installer project, so I exit and come back
in, no difference.
Giving up on FB, I go back to the command line. There is a xml file called
build.xml which contains a <project> item, and one of the attributes is
'installer', so I figure I found the installer project that I was supposed to
be adding the source path to. In looking through the XML, there is no child
elements that have source path definitions of any kind, so I'm assuming I am
back in the weeds. I write this to users@:
I'm assuming the installer project it's referring to is in the build.xml, but
what is the mechanism to add it? Or am I misunderstanding something?
Justin writes back:
This refers to if you building the installer in Flash Builder, the installer
uses code form the common project (/flex/untilities/trunk/common). It's in
properties under Flex Build Path in the Source Path tab, click add folder to
add it.
I'm entirely sure this makes sense to you guys, and the thousands of people who
have installed it before. As a basic user, I view the SDK 4.9.0 as an overlay
on top of FB 4.7. I view the install source that I downloaded as a mechanism to
bind that overlay. It would never occur to me that I could 'build the installer
in Flash Builder', I would assume the build process would take place on the
command line, similar to make/make install. At this point I'm guessing I should
see an installer project in Flash Builder? This is a foreign idea to me, and
I'm sort of giving up at this point, because my fundamental assumptions about
the build process are totally flawed. I'll leave it up to you guys to determine
if you think I'm close and can provide guidance, or if I should just wait for
Lee's single click installer which specifies FP.
Thanks for the support though.
On Feb 22, 2013, at 9:21 AM, Om wrote:
On Feb 22, 2013 12:56 AM, "Joe Kryzak" <[email protected]> wrote:
>
> Yes, I was attempting to build 4.9 with flash player 11.5.
>
> Is there a plan to have the binary installer select the flash player
version? I'm not locating the artifacts you are referencing, I might be
better off waiting.
>
> Thanks for the response.
>
Joe, the README in the installer directory has directions on how to do
this. Basically, you grab a copy of the insataller config xml, modify the
urls and version number and inject the xml into the installer as a command
line parameter.
Let me know if you run into problems.
As Lee mentioned, he is planning to make this doable via the UI. Hopefully
that would make things easier.
Thanks,
Om
> Joe
>
> On Feb 22, 2013, at 12:10 AM, Justin Mclean wrote:
>
> Hi,
>
> I assume you trying the build the installer project?
>
>> 4. In the installer project, add
${APACHE_FLEX_UTILITIES_ROOT}/common/src as a source path.
> This refers to if you building the installer in Flash Builder, the
installer uses code form the common project
(/flex/untilities/trunk/common). It's in properties under Flex Build Path
in the Source Path tab, click add folder to add it.
>
>> 2. Also, In the ant command in step 2 I see the message below.
> Ant can't find flexTasks, add flexTask.jar to your ANT lib directory or
pass it to ant via -lib. You can find it in the Flex SDK modules/antTasks.
>
> Thanks,
> Justin
>
