Hi Alex, I had a look and the plugin doesn't offer this ... the paths seem to be invalid ones anyway ... it seems that you copied the originals to a directory "a" and the patched ones to one called "b" and created the patch from that. After fixing this path-problem, I was able to apply most of the patch. The only files that weren't able to be patched were: - createjs/events/EventDispatcher.js - easeljs/display/Container.js - easeljs/display/DisplayObject.js - easeljs/utils/SpriteSheetUtils.js
When applying this manually IntelliJ complained about part of the patch already being applied. Any ideas? Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Donnerstag, 26. Mai 2016 15:27:16 An: dev@flex.apache.org Betreff: Re: AW: [FalconJX] Extern builds use patch files instead of replace tasks On 5/26/16, 3:08 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi Alex, > >so I finally had some time to look at the patch files. I do have a small >problem with them. Currently the patch path starts from the flexjs >projects root directory. This will probably work for the Ant build, but >in order to use this in the maven build, I would prefer them to be >relative to the src directory in the downloaded archive. I did a short >replace and was able to work with the patches, even if I did get some >errors ... will investigate them now. > Thanks for looking. Before I make those changes, are you sure there isn't an option in Maven's patch plugin to strip off leading directories? -Alex
