Thank's a lot - the build is valid!
I did on Mac:
- Install the
https://developer.apple.com/certificationauthority/AppleWWDRCA.cer in
keychain
- Install my app *.cer (Distri) (not the p12!!) in the keychain
- During the package process I have to enter my Mac password twice
Clint Modien wrote
> I
Hi Alex,
the problem is that a Maven build of an Artifact goes through a fixed set of
phases ... one of these is "generate-sources" and one of them is "compile" ...
"compile" naturally comes after "generate-sources". In the case of Falcon,
there are some classes which the generators need to be
Another thing I just noticed:
We have even more tools that are needed during the build:
- AnnotateClass.java
- ProblemEnumGenerator.java
- ProblemLocalizer.java
So I guess it would be good if I just moved those 3 together with the
UnknownTreePatternInputOutput into a separate falcon-build-tools p
Hi,
while I see an actual chance to have Falcon built with maven and hereby
producing Maven artifacts, I think we should discuss the coordinates these
artifacts are created under.
Currently I was using "org.apache.flex.compiler:falcon-compiler" while the
normal compiler was "org.apache.flex.
On 2/20/16, 7:32 AM, "Christofer Dutz" wrote:
>Another thing I just noticed:
>We have even more tools that are needed during the build:
>- AnnotateClass.java
>- ProblemEnumGenerator.java
>- ProblemLocalizer.java
>
>So I guess it would be good if I just moved those 3 together with the
>UnknownTr
So in theory, the SWF compiler in flex-falcon/compiler, the Flash Builder
integration jar in flex-falcon/flex-oem-compiler, and the FDB debugger in
flex-falcon/debugger will some day replace MXMLC and its FDB for compiling
future Flex (as well as FlexJS) SWFs.
Then we have the cross-compiler or tr
Well the one is needed at compile & runtime, the rest are code that is only
needed at build time. You should never bundle build code with your product. In
the Maven world "yet another artifact" usually doesn't matter, cause the tool
takes care of managing this.
Chris
__
More thoughts:
Falcon was actually never intended to be the product name for the
compiler. Adobe teams often used code-names for the code. Adobe released
flex-falcon/compiler as ASC2.0.
We could call flex-falcon/compiler MXMLC2.0 since we completed the MXML
support (or at least, lots of it) onc
Hi Alex,
I agree with most of your thoughts, but my intention was to make it simpler for
people to get started, having to know all of the history just in order to know
which artifacts to get doesn't make things easier.
I guess the best thing would have been, if we didn't change the groupIds an
