[BlazeDS] Continuing work on blazeds

[Christofer Dutz <ch...@c-ware.de>]

Hi,


I just created the develop branch. Whoever is planning on working on BlazeDS please use that branch as we have releases the Master is now reserved for released code.


So after having the first release out the door, I would like to clean up the project. I don't want to do this without your consensus. I know we have discussed some of this prior, but I would like to re-fresh it as the old discussion was pretty old:


I would like to:

- create an "attic" directory in the "modules" directory and move the root of the current project there (ok ... all except the modules directory ;-) )

- move the content of the "modules" directory to become the new root

- Create a maven replacement of the old turnkey war (This was waaaaay outdated anyway)


I don't want to delete the old stuff as it looses its visibility.

The current state only confuses users. Adobe seem to have switched to a Maven build, but didn't delete the Ant build. Even if the Ant build might still somehow work. I don't see the benefit of maintaining two builds.


What do you think?


Chris

Re: [BlazeDS] Continuing work on blazeds

[Justin Mclean <ju...@me.com>]

Hi,

> I would like to:
> 
> - create an "attic" directory in the "modules" directory and move the root of the current project there (ok ... all except the modules directory ;-) )

Perhaps "historical"? Apache has an attic [1] and probably best not  suggest the code is there.

> - move the content of the "modules" directory to become the new root

Seems fine to me.

> - Create a maven replacement of the old turnkey war (This was waaaaay outdated anyway)

Users want something that works out of the box so that useful.

>  Even if the Ant build might still somehow work. I don't see the benefit of maintaining two builds.

I'd ask if anyone is willing to maintain it and if not then remove it.

Thanks,
Justin

AW: [BlazeDS] Continuing work on blazeds

[Christofer Dutz <ch...@c-ware.de>]

BlazeDS supports nither Maven nor Ant ... it's just built with one or the other. So noone will probably complain about a release not supporting Ant ;-)

Chris

-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com] 
Gesendet: Freitag, 6. März 2015 22:32
An: dev@flex.apache.org
Betreff: Re: [BlazeDS] Continuing work on blazeds

IMO, before doing something like this, I would wait until a week or so after the announcement of the BlazeDS release to see if folks try Apache Flex BlazeDS and then complain about lack of Ant support.

-Alex

On 3/6/15, 12:53 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>
>I just created the develop branch. Whoever is planning on working on 
>BlazeDS please use that branch as we have releases the Master is now 
>reserved for released code.
>
>
>So after having the first release out the door, I would like to clean 
>up the project. I don't want to do this without your consensus. I know 
>we have discussed some of this prior, but I would like to re-fresh it 
>as the old discussion was pretty old:
>
>
>I would like to:
>
>- create an "attic" directory in the "modules" directory and move the 
>root of the current project there (ok ... all except the modules 
>directory ;-) )
>
>- move the content of the "modules" directory to become the new root
>
>- Create a maven replacement of the old turnkey war (This was waaaaay 
>outdated anyway)
>
>
>I don't want to delete the old stuff as it looses its visibility.
>
>The current state only confuses users. Adobe seem to have switched to a 
>Maven build, but didn't delete the Ant build. Even if the Ant build 
>might still somehow work. I don't see the benefit of maintaining two builds.
>
>
>What do you think?
>
>
>Chris
>

Re: [BlazeDS] Continuing work on blazeds

[Alex Harui <ah...@adobe.com>]

IMO, before doing something like this, I would wait until a week or so
after the announcement of the BlazeDS release to see if folks try Apache
Flex BlazeDS and then complain about lack of Ant support.

-Alex

On 3/6/15, 12:53 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>
>I just created the develop branch. Whoever is planning on working on
>BlazeDS please use that branch as we have releases the Master is now
>reserved for released code.
>
>
>So after having the first release out the door, I would like to clean up
>the project. I don't want to do this without your consensus. I know we
>have discussed some of this prior, but I would like to re-fresh it as the
>old discussion was pretty old:
>
>
>I would like to:
>
>- create an "attic" directory in the "modules" directory and move the
>root of the current project there (ok ... all except the modules
>directory ;-) )
>
>- move the content of the "modules" directory to become the new root
>
>- Create a maven replacement of the old turnkey war (This was waaaaay
>outdated anyway)
>
>
>I don't want to delete the old stuff as it looses its visibility.
>
>The current state only confuses users. Adobe seem to have switched to a
>Maven build, but didn't delete the Ant build. Even if the Ant build might
>still somehow work. I don't see the benefit of maintaining two builds.
>
>
>What do you think?
>
>
>Chris
>