Hi All,
it’s even simpler. In general whatever you build, is stored in the maven local
repo.
So if you only change something in the compiler-jx, you only need to rebuild
that.
If you want to update the distribution, you run that build.
Also if you want, you can force Maven to update the SNAPSHOTs by providing the
„-U“ flag.
I think with maven it’s easier to build only the parts that have changed.
Chris
Am 08.11.16, 08:48 schrieb "Alex Harui" <aha...@adobe.com>:
On 11/7/16, 10:18 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>Josh, Alex,
>
>If maven distribution binaries won't be usable in IDE, it will increase
>time
>of fixing bugs in FlexJS.
>
>Let say that I know in FlexJS is some bug.
>
>1) I'm changing code in FlexJS
>2) I have to push this to repository - Jenkins build it for me - I have to
>wait for propagation of artifacts to maven repository yes ?
I don't think so. Whenever I make a change, I just run "mvn clean
install" and my local Maven repo seems to get the results of that build.
In development mode, we seem to be working with snapshots instead of
released artifacts. I can make a change in flex-falcon, run "mvn clean
install" and then go the the flex-asjs and run "mvn clean install" there
and it just works.
>3) I'm building my project in order to check fix
And to test the changes on an example, I just run "mvn clean install" in
that project folder. I add "-P release" if I need to test a js-release
build.
For Flash Builder, some changes require restarting Flash Builder, which is
no fun at all. I generally use FB for editing only and use Ant or Maven
to build things.
-Alex
