Hi Nick,
actually it doesn't matter if we use Ant or Maven to build it, in both cases a
source distribution and the binaries will be released. As someone intending on
using BlazeDS you wouldn't know the difference (Ok ... when looking into the
jar files you will have one pom.xml in the
On 12/13/14, 4:31 AM, Christofer Dutz christofer.d...@c-ware.de wrote:
So if you guys haven't got any objections, I would try starting the
release process.
But I would initiate the Maven release and not use the Ant stuff.
No objections from me, and I don’t think it matters to me whether you
Shouldn't we make it as easy as possible for folks get BlazeDS, if we want
them to use it? If so, then it would sure help to have everything in one
zip, along with examples.
On Sat, Dec 13, 2014 at 11:31 AM, Alex Harui aha...@adobe.com wrote:
On 12/13/14, 4:31 AM, Christofer Dutz
Maybe we offer it via a Mavel release for those that want to build from
source, and offer a binary download. That should take care of both major
use cases, I think.
-Nick
On Sat, Dec 13, 2014 at 10:31 AM, Alex Harui aha...@adobe.com wrote:
On 12/13/14, 4:31 AM, Christofer Dutz
