thanks for the quick reply.

first of all it sounds great. about the api changes i think we can't and won't 
avoid them, although some of them seem arbitrary.
sometimes i think "wouldn't it be a better approach if flexmojos would just 
reference to an preinstalled flexsdk? no more redundancy. flashbuilder, fdt and 
maven all could use the same flex SDK." but otherwise "in a better world adobe 
would maintain their own maven repository and we both could talk about more 
human topics."

currently i don't use application Domains, so those current problems does not 
really concern me. except for the delay it affects on the release. does it mean 
i can use the snapshot version on any flexmojos snapshot repository?

depending on the costs you have in mind and if the tool helps solving the 
problem it will definitely fix my problem.

mace

Am 15.03.2011 um 00:41 schrieb Marvin Froeder:

> Well, I have the flex SDK almost ready, but guess, what, guess what, adobe 
> did it again....
> there is some API changes that I need to resolve before I can publish a new 
> flex SDK + new flexmojos 4 release.  You may or may not be affect (it is 
> related to applicationDomains, if you don't use that you should be fine, but 
> still breaks build/ITs/backward compatibility).
> 
> 
> If I release my SDK installer tool as a paid + closed source tool, would that 
> fix your problem?
> 
> 
> VELO
> 
> On Mon, Mar 14, 2011 at 8:13 PM, mace <[email protected]> wrote:
> hi velo,
> 
> i know this topic is quite annoying. but after few weeks of
> researching we decided to go with the following setup:
> 
> * flexmojos 4 beta 5
> * maven 3.0.2
> * flex sdk 4.5.0.19786
> * flashbuilder burrito
> 
> everything went fine but unfortunately we haven't tried to reference
> to image resources in a swc project. the flexsdk version has a bug:
> https://bugs.adobe.com/jira/browse/SDK-29135
> 
> i was happy to see it fixed, but it only helps us in the ide and not
> in our continous integration setup.
> 
> after few hours of reading mail threads and trying out 3rd party
> solutions on installing a new flexsdk into the maven repository i'm
> worried. instead of spending hours using and modifying your descriptor
> file i spent them on some dirty shell scripts without any satisfying
> result.
> 
> I really appreciate your work on flexmojos and dont want to go back to
> the ant way of compiling projects. but honestly what would you do?
> pausing the continous build system till flexmojos is updated? working
> on a new solution to install flex sdk? switching back to ant?
> 
> best regards
> 
> mace
> 
> --
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
> 
> http://flexmojos.sonatype.org/
> 
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>  
> http://flexmojos.sonatype.org/

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to