Just as a reminder the mail threads in which I suggest such a refactoring: http://apache-flex-development.2333347.n4.nabble.com/BlazeDS-Continuing-work-on-blazeds-td45427.html http://apache-flex-development.2333347.n4.nabble.com/BlazeDS-not-compiling-for-clean-copy-of-SDK-source-td43391.html http://apache-flex-development.2333347.n4.nabble.com/Has-anyone-been-able-to-build-BlazeDS-td37343.html#a37361
... I'll stop for now as I think 3 is enough to prove my point. So it's not something hat hasn't been discussed in the past and I didn't get any objections from those threads. Back to the topic: - I totally dislike a parallel build with Ant and Maven unless it's Justin's suggestion to use the Ant Maven Tasks. The reason for this is that I am 1000% certain that the build will be similar but not identical. If they are not identical, problems with Ant might occur, that don't for Maven and the other way around. I'm no longer willing to waste my time this way. - I doubt that there are people actually compiling BlazeDS on their own (Except eventually the guys at Adobe) ... what would they need to do that anyway? Most people also don't compile the Flex SDK, they just use it (I have never prior to starting to work on the Flex project) If we decide to do the dual thing I would like us to vote on ONE reference build and the other being the convenience build. If the reference is not Maven, we also need someone to maintain BlazeDS in the future, as I'm not going to do it. If we decide the reference to be Maven, we would need someone to create/move/migrate the Ant build to the modules-directory and adjust the readme. As soon as the modules directory is a nicely self-contained thing, I'd do the moving and removing of stuff. Chris ________________________________________ Von: Alex Harui <[email protected]> Gesendet: Mittwoch, 16. Dezember 2015 00:01 An: [email protected] Betreff: Re: AW: [VOTE] Remove the Ant scripts from BlazeDS? IMO, it doesn't so much matter that the Ant scripts can work, it matters what our customers want. Folks still seem to be using Ant and so we should try to provide that, but there is no requirement for Chris to work on it. I don't remember a past discussion that concluded we could remove Ant scripts, but my takeaway of recent Maven discussion is that we are going to reconfigure some of the repos so that Maven-generated releases work the way they should and other folks can get the Ant scripts to work with that new configuration. So, I'm totally fine with Chris making major changes to the BlazeDS repo like getting rid of a lot of the stuff that isn't used or critical, I just don't want the Ant scripts removed from modules or the root so parts of them can be leveraged to fix up the Ant scripts when Chris is done. -Alex On 12/15/15, 1:58 PM, "Christofer Dutz" <[email protected]> wrote: >I couldn't get them to work and the user on the users list couldn't >either ... So let's settle on: they work just as good as the other ant >builds ... For me that's reason enough to get rid of them. > >Chris > > > >Von meinem Samsung Galaxy Smartphone gesendet. > > >-------- Ursprüngliche Nachricht -------- >Von: OmPrakash Muppirala <[email protected]> >Datum: 15.12.2015 22:54 (GMT+01:00) >An: [email protected] >Betreff: Re: [VOTE] Remove the Ant scripts from BlazeDS? > >Alex responded saying that the Ant builds are working fine. Isn't that a >good reason not to delete them? > >Thanks, >Om > >On Tue, Dec 15, 2015 at 1:49 PM, Christofer Dutz ><[email protected]> >wrote: > >> Cause I had mentioned this not only once but even more than twice and >>none >> was objecting so I thought there was a general consensus on this. >>Discuss >> as long as you want ... I won't do anything till that discussion is >>over. >> >> Chris >> >> >> >> Von meinem Samsung Galaxy Smartphone gesendet. >> >> >> -------- Ursprüngliche Nachricht -------- >> Von: OmPrakash Muppirala <[email protected]> >> Datum: 15.12.2015 22:28 (GMT+01:00) >> An: [email protected] >> Betreff: Re: [VOTE] Remove the Ant scripts from BlazeDS? >> >> Chris, >> >> Can we have a discussion on this topic first? I would like to know what >> are the consequences of removing Ant scripts from BlazeDS. >> Alex had mentioned that they are indeed working on the CI server. Why >> would we want to delete things that are working? I am confused. >> >> Can we (not you, someone else) update the README to clarify how to make >>the >> Ant script work? That way those who want it can continue to use it. >> >> Not everyone uses Maven. There are still lots of people using Ant. I >> don't think removing Ant support is a good idea. >> >> Thanks, >> Om >> >> On Tue, Dec 15, 2015 at 1:21 PM, Christofer Dutz < >> [email protected]> >> wrote: >> >> > +1 (binding) >> > >> > ________________________________________ >> > Von: Christofer Dutz <[email protected]> >> > Gesendet: Dienstag, 15. Dezember 2015 22:21 >> > An: '[email protected]' >> > Betreff: [VOTE] Remove the Ant scripts from BlazeDS? >> > >> > Hi, >> > >> > >> > to start this discussion again (I think I mentioned this several times >> > before ... this time will be final though). >> > >> > >> > BlazeDS is currently Built by Maven ... all needed for this is >>contained >> > inside the "modules" directory. Additionally there is an Ant build >>around >> > that, which I have never gotten to work (Probably I had only set 4 or >>5 >> of >> > the 20 Environment Variables ;-) ). Whenever I work on BlazeDS, I use >> just >> > Maven and nothing but Maven. Just recently some of our users had been >> > confused about how to build BlazeDS. >> > >> > >> > I would like to remove everything outside the "modules" directory and >> make >> > the content of the "modules" directory the new root ... is this Ok for >> you? >> > >> > >> > Chris >> > >>
