Ok that was my fault - I had wrong settings.xml file. I forgot to add
repositories. Settings file should look like that and everything builds
without the problem! [1]
We are ready !!
[1] https://paste.apache.org/5xD0
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message i
I just did simple test whether I'm able to build basic project by Maven
staged artifacts in RC2. I removed all my dependencies 0.8.0 from
".m2\repository\org\apache\flex\flexjs\" folder.
Add profile [1] in settings.xml.
Run simple build of test app [2]. It failed [3]. As you can see Maven was
abl
Looks like the Ant run didn't clean up some Maven output first. Something
for the next RM to be wary of.
-Alex
On 6/20/17, 10:56 PM, "piotrz" wrote:
>Hi Alex,
>
>During examination I noticed that in folder
>"apache-flex-falconjx-0.8.0-bin"
>rat complains about this files
>
>155 Unknown License
Hi,
It looks like the encoding of the help files [1] for the command line tools has
changed between RC1 and RC2.
I’m not sure if it was incorrect before or incorrect now or if it even matters.
Could someone who's first language isn't English please double check it’s not
broken.
Thanks,
Justi
Hi,
> During examination I noticed that in folder "apache-flex-falconjx-0.8.0-bin"
> rat complains about this files
That’s fine rat tends to complain a bit when run over binary releases.
> D:/flex_sdk/empty_folder/apache-flex-falconjx-0.8.0-bin/flex-typedefs/GCL/target/rat.txt
I’ve not looked
Hi Alex,
During examination I noticed that in folder "apache-flex-falconjx-0.8.0-bin"
rat complains about this files
155 Unknown Licenses
***
Unapproved licenses:
D:/flex_sdk/empty_folder/apache-flex-falconjx-0.8.0-bin/flex-typedefs/GCL/target/classes/META-INF/DE
This is the discussion thread.
Changes in this RC include:
Maven artifacts are available at
https://repository.apache.org/content/repositories/orgapacheflex-1020
Thanks,
Alex Harui
