Building Falcon with Maven

[Christofer Dutz <ch...@c-ware.de>]

Hi (especially) Jose,



I was just informed that you are working on making falcon buildable with Maven. First of all that is great.

But we should coordinate how the artifacts are called.

I could see that your artifacts for the compiler are located in the groupId "org.apache.flex". You would make things a lot easier if you used "org.apache.flex.compiler" instead. Otherwise the structure would start getting a little messy. This way all compiler related artifacts are generated to "org.apache.flex.compiler", all framework related artifacts are generated to "org.apache.flex.framework". This is also somewhat the structure all maven forms of Flex have had and I strongly suggest to continue this. Secondly I would suggest to either generate the artifacts to "org.apache.flex.compiler.falcon" groupId or call the artifact "falcon-compiler" because the normal FDKs allready have an artifact called compiler.



If you need any help with this work, I'd rather help here than implement a Mavenizer for Falcon (Which I had allready started working on) ;-)

For example I remember a plugin for downloading and locally deploying a single jar file. This might be good for the jburg dependency.



Chris

AW: Building Falcon with Maven

[Christofer Dutz <ch...@c-ware.de>]

Hi Jose,

having such a thing would have the major benefit hof being able to publish SNAPSHOTS of the compiler automatically.
I think this would be a major breakthrough for bleeding edge developers ... simply referencing org.apache.flex.compiler:falcon-compiler:pom:4.13.0-SNAPSHOT would allow you to use the latest nightly build version with no need to manually update anything :-)

I also saw that you seem to be struggling with Antlr ... it's a real beast and I could see that you too gave 4.x a try and reverted to 3.x ... I use that in all of my projects too :-)
But why are you mixing both antlr versions? Seems you are using Antlr2 for some and Antlr3 for other grammar files.

Probably I could help with the grammar files as well as with the setup, if you are having any trouble. Just tell me what the problem is and I'll try to help sort that out as fast as possible.

Chris



________________________________________
Von: Jose Barragan <jo...@codeoscopic.com>
Gesendet: Dienstag, 15. Juli 2014 12:18
An: dev@flex.apache.org
Betreff: Re: Building Falcon with Maven

Hi Chris,

Good to chat to you again, finally.

I just continue the original initiative, started by Carlos Rovira in order to mavenized the falcon project from their build process.

Regarding the group id name you mentioned, I don't have any problem to adopt your proposal.
I'm open to get help from you and others like Frank Wienberg, whose self offered to participate it too, due to I'm pretty busy (with chaotic mind), at last times after my first son was born, this causes that my effort on this work will a really hard defiance, due I'm working on it at my little ocio time.

Well, after say this... I'll keep on working on it, taking in account your comments, and trying to maintain the efforts synchronized with all of you.

Thanks,
______________________
Jose Barragan
Senior Software Engineer

On 15 Jul 2014, at 09:09, Christofer Dutz <ch...@c-ware.de> wrote:

> Hi (especially) Jose,
>
>
>
> I was just informed that you are working on making falcon buildable with Maven. First of all that is great.
>
> But we should coordinate how the artifacts are called.
>
> I could see that your artifacts for the compiler are located in the groupId "org.apache.flex". You would make things a lot easier if you used "org.apache.flex.compiler" instead. Otherwise the structure would start getting a little messy. This way all compiler related artifacts are generated to "org.apache.flex.compiler", all framework related artifacts are generated to "org.apache.flex.framework". This is also somewhat the structure all maven forms of Flex have had and I strongly suggest to continue this. Secondly I would suggest to either generate the artifacts to "org.apache.flex.compiler.falcon" groupId or call the artifact "falcon-compiler" because the normal FDKs allready have an artifact called compiler.
>
>
>
> If you need any help with this work, I'd rather help here than implement a Mavenizer for Falcon (Which I had allready started working on) ;-)
>
> For example I remember a plugin for downloading and locally deploying a single jar file. This might be good for the jburg dependency.
>
>
>
> Chris

Re: Building Falcon with Maven

[Jose Barragan <jo...@codeoscopic.com>]

Hi Chris,

Good to chat to you again, finally.

I just continue the original initiative, started by Carlos Rovira in order to mavenized the falcon project from their build process.

Regarding the group id name you mentioned, I don't have any problem to adopt your proposal. 
I'm open to get help from you and others like Frank Wienberg, whose self offered to participate it too, due to I'm pretty busy (with chaotic mind), at last times after my first son was born, this causes that my effort on this work will a really hard defiance, due I'm working on it at my little ocio time.

Well, after say this... I'll keep on working on it, taking in account your comments, and trying to maintain the efforts synchronized with all of you.

Thanks,
______________________
Jose Barragan
Senior Software Engineer

On 15 Jul 2014, at 09:09, Christofer Dutz <ch...@c-ware.de> wrote:

> Hi (especially) Jose,
> 
> 
> 
> I was just informed that you are working on making falcon buildable with Maven. First of all that is great.
> 
> But we should coordinate how the artifacts are called.
> 
> I could see that your artifacts for the compiler are located in the groupId "org.apache.flex". You would make things a lot easier if you used "org.apache.flex.compiler" instead. Otherwise the structure would start getting a little messy. This way all compiler related artifacts are generated to "org.apache.flex.compiler", all framework related artifacts are generated to "org.apache.flex.framework". This is also somewhat the structure all maven forms of Flex have had and I strongly suggest to continue this. Secondly I would suggest to either generate the artifacts to "org.apache.flex.compiler.falcon" groupId or call the artifact "falcon-compiler" because the normal FDKs allready have an artifact called compiler.
> 
> 
> 
> If you need any help with this work, I'd rather help here than implement a Mavenizer for Falcon (Which I had allready started working on) ;-)
> 
> For example I remember a plugin for downloading and locally deploying a single jar file. This might be good for the jburg dependency.
> 
> 
> 
> Chris