No - Adobe has not released the jars in manner that would allow people 
to "host" the jars, which is what a maven repository is.

We have installed the jars into a local "internal" repository not 
accessible to the outside.  We used a "com.adobe.flex" groupId, and the 
artifactId identical to the jar names, and version 2.0.0.

Unfortunately we're still having some trouble deploying in WebLogic, 
because we have some limits around how we can deploy, and there are some 
limitations in FDS we are running into.  Specifically that the .swf sets 
the location of the data services at compile time.  This means that we 
cannot create a single .swf that can be deployed locally, in a share dev 
environment, in a QA/Testing environment, then in staging and/or 
production.  Our clients are large fortune 500 companies that require 
that only tested binary packages be deployed to production, so we have 
had to do all sorts of exceptions to allow for deployment of .mxml 
files.  Usually corporate policies oppose deploying source files to 
production environments.  Note that Maven makes many of the same 
assumptions around binary packaging.

This then has been problematic in turn, because of how WebLogic fails to 
explode the war in a consistent way that would allow the FDS and other 
flex stuff to write to the filesystem. The assumptions made in such file 
access do not match the weird organization of WebLogic's cached, 
exploded .war and .ear structures.  So we have to deploy exploded and 
get all sorts of exceptions to our client's deployment policies.

So I encourage you to put the flex jars in a maven repo, and I hope 
you're not using WebLogic too. :)  If you start getting craziness upon 
attempts to deploy, remember the above, and see if you can build per 
environment, or if you can deploy exploded with .mxml jars.  there are 
some bugs still and the next version of Flex is supposed to eliiminate 
this hard-coding in the .swf of the fds location.  It's crazy in the 
mean-time.

Incidentally, if you are deploying .mxml and therefore have to deploy 
the compiler servlet and mxmlc.jar etc., the maven folks suggested that 
you use the "dependency" plugin to copy certain appropriate jars (mxmlc, 
swfkit, etc.) into a temporary "resource" directory, then use the .war 
resource filtering to pack those resources into WEB-INF/flex/jars at 
package time.

Christian.

-- 

*christian** gruber + process coach and architect*

*Israfil Consulting Services Corporation*

*email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*




Aldo Bucchi wrote:
>
> Hi all,
>
> Just wondering if anyone has found / installed the fds2 libraries in a
> maven repo
> otherwise, any official naming to perform a manual install?
>
> thx,
> Aldo
>
> -- 
> ::::: Aldo Bucchi :::::
> mobile (56) 8 429 8300
>
>  



Reply via email to