Not sure I understand the issue, but I am just now testing the Ant build for BlazeDS on the apacheflexbuilds CI server. I spent time over the past several days getting it to work in the develop branch. I'd prefer not to have to start over, although I would imagine that most of what I did would still apply or only need minor tweaking.
-Alex On 12/28/15, 7:15 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Öhm ... just noticed who actually wrote that last message :-) Sorry for >the over-detailled email. > >Just started comparing the develop and the 4.8.0 branch and there were >quite I lot of changes I did. Especially in bringing the directory >structure to a default maven structure. I actually didn't quite notice >this as my IDE hid the details of the structure. > >What do you think ... 4.8.0 is a full blown maven default structure ... >re-doing all of that is quite some effort. Especially cleaning up the >tomcat projects. > >Would it be another option to add the Ant build to 4.8.0 and to merge >that to develop as soon as it's done? > >Chris > >________________________________________ >Von: Christofer Dutz >Gesendet: Montag, 28. Dezember 2015 16:07 >An: dev@flex.apache.org >Betreff: AW: [VOTE] Remove the Ant scripts from BlazeDS? > >Well actually I was thinking about dropping that branch, as I re-did the >cleanup in the develop branch. I still kept it there in order to find out >if I did any changes that I missed. But I just checked and I could easily >build 4.8.0. Having a deeper look at the code however I did notice that >in the parent chain one level was skipped. This can cause problems when >building the first time. I fixed this and now these problems shouldn't >occur any more, but I would strongly suggest not to work on the 4.8.0 >branch ... I have to clean this up first. > >The main reason for this was that I did some changes in the structure >that were not backed by the majority of the Flex project, so I started >from develop again and re did only the changed that have public backing. > >Thinking about it, It should actually be the ideal time to do that right >away ... I'll keep you posted on my progress. > >Chris > >________________________________________ >Von: Justin Mclean <justinmcl...@me.com> >Gesendet: Montag, 28. Dezember 2015 03:04 >An: dev@flex.apache.org >Betreff: Re: [VOTE] Remove the Ant scripts from BlazeDS? > >Hi, > >> So anyone else following this ... in order to build develop now all you >>should need is: "mvn install" > >Tried it out on the 4.8.0 branch and got these errors: > >[ERROR] The build could not read 3 projects -> [Help 1] >[ERROR] >[ERROR] The project >org.apache.flex.blazeds:flex-messaging-opt-tomcat-4:[unknown-version] >(/Users/justinmclean/Documents/flex-blazeds/opt/tomcat/tomcat-4/pom.xml) >has 1 error >[ERROR] Non-resolvable parent POM: Could not find artifact >org.apache.flex.blazeds:flex-messaging-opt:pom:4.8.0-SNAPSHOT and >'parent.relativePath' points at wrong local POM @ line 22, column 10 -> >[Help 2] >[ERROR] >[ERROR] The project >org.apache.flex.blazeds:flex-messaging-opt-tomcat-6:[unknown-version] >(/Users/justinmclean/Documents/flex-blazeds/opt/tomcat/tomcat-6/pom.xml) >has 1 error >[ERROR] Non-resolvable parent POM: Could not find artifact >org.apache.flex.blazeds:flex-messaging-opt:pom:4.8.0-SNAPSHOT and >'parent.relativePath' points at wrong local POM @ line 22, column 10 -> >[Help 2] >[ERROR] >[ERROR] The project >org.apache.flex.blazeds:flex-messaging-opt-tomcat-7:[unknown-version] >(/Users/justinmclean/Documents/flex-blazeds/opt/tomcat/tomcat-7/pom.xml) >has 1 error >[ERROR] Non-resolvable parent POM: Could not find artifact >org.apache.flex.blazeds:flex-messaging-opt:pom:4.8.0-SNAPSHOT and >'parent.relativePath' points at wrong local POM @ line 22, column 10 -> >[Help 2] > >Running on OS X and tried java 1.7 and 1.8 > >Thanks, >Justin >
