Re: [jira] (FLEX-33155)

That would be great. Thank you. On Sat, Mar 28, 2015 at 1:54 AM, Darrell Loverin wrote: > I used to be familiar with that code. I'll take a look at the patch this > weekend. > > -Darrell > > On Friday, March 27, 2015, Héctor A wrote: > > > It would be nice if somebody could check if the submitt

Re: [jira] (FLEX-33155)

I used to be familiar with that code. I'll take a look at the patch this weekend. -Darrell On Friday, March 27, 2015, Héctor A wrote: > It would be nice if somebody could check if the submitted patch is valid. > It's a longtime issue affecting many users, and it's a shame that the > contributor

[jira] (FLEX-33155)

It would be nice if somebody could check if the submitted patch is valid. It's a longtime issue affecting many users, and it's a shame that the contributor of the patch has been ignored. >From what I read here , this block of code

[Installer 3.2] # Apache Flex SDK Installer 3.2 nightly build 20: Successful

flex-utilities_installer_release-candidate - Build #20 - Successful Changes since last build: No changes For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_installer_release-candidate/20/.

AW: Apache BlazeDS default configuration files [License]

Hi, well actually none are in the release ... the two last ones are in the source package, but they belong to the test resources and are not contained in the actual jars that make up blazeds. I don't think it's a good idea to have default config files in there. Web applications are all differe

Re: Apache BlazeDS default configuration files [License]

The four files you mentioned: - messaging-config.xml - proxy-config.xml - remoting-config.xml - services-config.xml Were donated by Adobe, so there are now Apache 2.0 licensed versions of them in the repos. I didn’t notice until just now that the first two are not in the official Apache release.

Re: Apache BlazeDS default configuration files [License]

Default configuration files was not donated by Adobe? I want to use Apache BlazeDS. Could I create custom configuration for Apache BlazeDS without license restrictions? Thanks. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Apache-BlazeDS-default-configu

Re: Apache BlazeDS default configuration files [License]

Apache BlazeDS is licensed under Apache License 2.0. Many consider that less restrictive than LGPL. We cannot give legal advice, so you may need to consult a lawyer. -Alex On 3/27/15, 7:39 AM, "Victor Turansky" wrote: >Adobe BlazeDS default configuration files was licensed under LGPL v.3. >-

Apache BlazeDS default configuration files [License]

Adobe BlazeDS default configuration files was licensed under LGPL v.3. - messaging-config.xml - proxy-config.xml - remoting-config.xml - services-config.xml Is Apache BlazeDS default configuration published or described anywhere? Could I create and distribute custom configuration without license r

AW: ERROR Build BlazeDS - Could not find artifact com.sun:tools:jar:jdk-version

Are you eventually building from BlazeDS root using Ant? The actual build is a Maven build in the Modules directory. All these "../Some/Path" errors are usually results of an Ant build ;-) There is one todo on my list to move the modules directory to the root and the old stuff around in some "

AW: Maven and Apache Flex 4.1x

Hi, just as Frederic said. We could start publishing the Apache Flex parts, but you still couldn't use them out of the box as the flashplayer, playerglobal, fontkit, air-runtime, airglobal are not available. I have implemented a feature in FlexMojos to auto-download flash and air resources (aft

RE: ERROR Build BlazeDS - Could not find artifact com.sun:tools:jar:jdk-version

To be more precised, your path should point to , not /jre Frédéric THOMAS > From: webdoubl...@hotmail.com > To: dev@flex.apache.org > Subject: RE: ERROR Build BlazeDS - Could not find artifact > com.sun:tools:jar:jdk-version > Date: Fri, 27 Mar 2015 08:08:48 + > > Hi Edgar, > > > /System/

RE: Maven and Apache Flex 4.1x

> Hi all, I wonder if there is a guide on how to mavenize Apache Flex SDK 4.1x Yes, see [1] > Why Apache Flex SDK is not available on any apache maven repository? Because of some Adobe distribution policies, so, using the link provided above you should be able to install the Mavenized SDK int

RE: ERROR Build BlazeDS - Could not find artifact com.sun:tools:jar:jdk-version

Hi Edgar, > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar This error seems to indicate you are using the JRE instead of the JDK. Frédéric THOMAS > Date: Thu, 26 Mar 2015 11:42:58 -0700 > From: edgarmarioriv...@gmail.com > To: dev@flex.apache.org > Subject: ER