If we were to publish all themes equally as swcs though, I wouldn't need to
compile them in the mavenization process and we could get rid of the additional
playerglobal 10.2 download, which has to be confirmed.
I would love to allow setting an environment variable ... something like:
-DI_ACCEPT_
> but Alex strictly objected that when I started working on the
Mavneizer. Even if the SDK build does have such an environment variable
to allow CI builds. If anything here has changed, I would love to allow
that.
Same here !
Btw, if the mavenized sdk was public, I would need to accept the lic
The Problem with Everything thats not a core extension is that it will not get
executed if maven can't resolve a plugin dependency or a normal dependency. So
if you update the maven version to a new version. The build will fall before
your extension/plugin had a chance to do anything. With the
On 4/21/15, 12:44 AM, "Christofer Dutz" wrote:
>If we were to publish all themes equally as swcs though, I wouldn't need
>to compile them in the mavenization process and we could get rid of the
>additional playerglobal 10.2 download, which has to be confirmed.
>
>I would love to allow setting a
This finally got officially recorded and reviewed by Apache. I’m ready to
commit it to a repo, but which one? I was going to use flex-utilities,
but maybe it should go in a folder on our web site SVN?
BTW, Justin found in the IP review that there are a few other trademark
names used in lists of
