That's right. mvn compile and test should work fine. The benign test failed error from junit tests is coming from install/package; it's been there since the beginning of time [1]. It would be a nice to have and remove the benign warning messages. If a proposed critical patch release passes the regression tests, doesn't break any existing behavior, enhances the project, and we have volunteers for RM, I do not see these superious reasons as valid to block releases and keep things moving along. Sean: it would great if you can open a Jira and apply the patch; we can always cut another release next time- I'll be happy to be RM for that one whenever you feel it's' ready.
[1] http://markmail.org/search/?q=ctakes%20mvn%20package%20-DskipTests#query:ctakes%20mvn%20package%20-DskipTests+page:1+mid:oxgrkslhhjimpv4k+state:results On Tue, Dec 13, 2016 at 9:19 AM, Andrey Kurdumov <kant2...@googlemail.com> wrote: > NP for broken build. Finally I manage to run it, so I just report issue so > other don't have have to go through hoops like me. > > I just want to made small correction - mvn compile works. mvn test works > too, but mvn package require -DskipTests. > The problem with build is somehow related to how Maven package stuff, I > suspect. > > Packaging failed for me at "Apache cTAKES Dependency Parser > .................... FAILURE", I also attach report from Surefire with > error. > > I will try to figure out why is that error happens, but it could take a > while until I understand how Maven works. > Thanks for prompt response! > > Also I start looking how cTakes working, and investigate dependencies > between packages, and found following comment: "Temporary workaround: Adding > in the system scoped libraries. Remove these once they are in Maven Central" > in the ctakes-distribution\src\main\assembly\bin.xml . These comment related > to dependencies which checked in in the source code, but for me seems to be > that they are now on MAven Central See > (https://mvnrepository.com/artifact/net.sf.mastif/mastif-zoner). > I saw issue > > CTAKES-185 > > which could be appropriate for that, and I could create patch for that > change. During the course of my next project, very likely I would be > involved in the activities similar to cTakes, so I potentially could > contribute something back, so I try to familiarize myself with the project. > > > > 2016-12-13 19:30 GMT+06:00 Finan, Sean <sean.fi...@childrens.harvard.edu>: >> >> Hi Andrey, >> >> The requirement of skipping tests for a successful build is something that >> all ctakes developers have stumbled across, but after initial setup we all >> forget about it and it has never been handled. Apologies. >> >> The github mirror is something that would be great to have, but getting it >> up has been a nightmare. The problem is that historically we have had >> binary files that are larger than the 100MB limit enforced by github. >> https://help.github.com/articles/working-with-large-files/ >> This causes github to reject the creation of the repository. >> >> I do think that, should somebody feel like putting in the effort, we could >> work with apache infra and get a working solution ... possibly starting with >> 3.2.4-SNAPSHOT and ignoring the rest of the history? Unfortunately I do not >> have the time to tackle the problem. >> >> Sean >> >> >> -----Original Message----- >> From: Andrey Kurdumov [mailto:kant2...@googlemail.com] >> Sent: Monday, December 12, 2016 10:01 PM >> To: dev@ctakes.apache.org >> Subject: Infrastructures questions. >> >> Hi, I very new to cTakes and interested to take a look at it, and maybe >> create custom pipeline on top of it. Right now I checkout source code and >> successfully build it, but have following question. >> >> Why mvn package does not run successfully for me until I exclude tests >> from build? I'm not very good at Java, so maybe I miss something obivious. >> >> Also, you seems to be have not only SVN repository, but Git also ( >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_ctakes_&d=DgIBaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao&m=v58bHfswf4lrCGRXVvbZcOuRlfxX4A2JFW3Y0a7wEy0&s=XzjL16KbCkVYgzwzcBN71XtHS-Bf5CtQ27hsmHKwizg&e= >> ) but it is very outdated. I even initially think that project is dead, >> since Git show activity only from >> 2013 year! If you could restore Git, that would be awesome. >> >> Best regards, >> Andrey Kurdyumov > >
