Issue with pom.xml file when building EOP

[William Ferreira]

Hello

I'm trying to install EOP 1.2.3 on Mac OS X. At the EOP Code Building stage, the install breaks due to an issue with the pom.xml file. It appears that the pom.xml file has been truncated to 0 at some earlier point in the install, but a .bkg file has been created (see output below). Can anyone suggest a fix? I don't have any experience with maven.

Kind regards

Will

EOP Code Building. This process could take several minutes, please wait ...  

[INFO] Scanning for projects...

[ERROR] [ERROR] Some problems were encountered while processing the POMs:

[FATAL] Non-readable POM /Users/williamferreira/EOP/Excitement-Open-Platform-1.2.3/lap/pom.xml: input contained no data @ 

 @ 

[ERROR] The build could not read 1 project -> [Help 1]

[ERROR]   

[ERROR]   The project  (/Users/williamferreira/EOP/Excitement-Open-Platform-1.2.3/lap/pom.xml) has 1 error

[ERROR]     Non-readable POM /Users/williamferreira/EOP/Excitement-Open-Platform-1.2.3/lap/pom.xml: input contained no data

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

Error!

$ ls -la Excitement-Open-Platform-1.2.3/lap/

total 24

drwxr-xr-x@  7 williamferreira  staff    238  4 Sep 14:14 .

drwxr-xr-x@ 21 williamferreira  staff    714  4 Sep 14:13 ..

-rw-r--r--@  1 williamferreira  staff      0  4 Sep 14:14 pom.xml

-rw-r--r--@  1 williamferreira  staff  11410  4 Sep 14:14 pom.xml.bkg

-rw-r--r--   1 williamferreira  staff      0  4 Sep 14:14 pom.xml.tmp

drwxr-xr-x@  6 williamferreira  staff    204  4 Sep 14:14 src

drwxr-xr-x  14 williamferreira  staff    476  4 Sep 10:05 target

[Roberto Ferrari]

In the 'lap' directory where the .bkg file is create a copy of that file and name it as pom.xml (so that you restore the original pom file)

rerun the install script

--
You received this message because you are subscribed to the Google Groups "eop-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eop-users+...@googlegroups.com.
To post to this group, send email to eop-...@googlegroups.com.
Visit this group at http://groups.google.com/group/eop-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/eop-users/278ce4c4-1cbc-4d10-94ae-e6121204b487%40googlegroups.com.

[William Ferreira]

I tried that, and the problem just re-occurs.

[William Ferreira]

Could the output of the previous step in the build be significant?

Updating the pom.xml file of the EOP so that it can use TreeTagger ... 

awk: illegal field $(<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">), name "line"

 input record number 1, file ./Excitement-Open-Platform-1.2.3/lap/pom.xml

 source line number 1

OK

It seems to suggest that the pom.xml file is being updated - perhaps this step does not terminate correctly?

[William Ferreira]

I commented out the call to awk in the install.sh file:

echo ""

  echo "The TreeTagger has been installed correctly, [ENTER] to continue ... "

  read input_variable

  cd -

  echo ""

  echo "Updating the pom.xml file of the EOP so that it can use TreeTagger ... "

  #cp ./Excitement-Open-Platform-$VERSION/lap/pom.xml ./Excitement-Open-Platform-$VERSION/lap/pom.xml.bkg

  #awk 'BEGIN {remove_tag = "false";} {line = $0; if ($line ~ /if you want to use TreeTagger/) remove_tag = "true"; else if ($line ~ /end of TreeTagger related dependencies/) remove_tag = "false"; if (remove_tag == "true" && ($line ~ /<\!--/ || $line ~ /-->/) && $line !~ /[a-z0-9]/) line = ""; printf("%s\n", line);}' ./Excitement-Open-Platform-$VERSION/lap/pom.xml > ./Excitement-Open-Platform-$VERSION/lap/pom.xml.tmp

  #cp ./Excitement-Open-Platform-$VERSION/lap/pom.xml.tmp ./Excitement-Open-Platform-$VERSION/lap/pom.xml

  #check

and things seemed to work - at least I successfully built EOP. If you run that awk script on the cmd line it produces an error (sorry, I don't have the output any more, but it's a syntax error related to the line variable). Perhaps it's a problem with awk on the Mac, but since the lines the awk script is trying to remove are commented out anyway perhaps the awk call is redundant?

[Roberto Ferrari]

it seems that the awk command you use works differently from the one we use in Ubuntu. Commenting those rows it runs but TreeTagger can not be used.

In order to enable treetagger you could apply this semi-automatic procedure:

1) Open the original pom.xml (the file you downloaded with the EOP and not the one updated by running the install.sh script) file in Excitement-Open-Platform-1.2.3/lap/pom.xml

2) In the pom file there is a section about TreeTagger (i.e.  <!-- TreeTagger related dependencies -->)
Remove the tags for documentation (i.e. <!--) that are just after the line <!-- TreeTagger related dependencies --> and before <!-- end of TreeTagger related dependencies -->. That is what such an awk command does.

3) comment the following row of the install script that is not necessary any more:
#echo ""
 #echo "Updating the pom.xml file of the EOP so that it can use TreeTagger ... "
 #cp ./Excitement-Open-Platform-$VERSION/lap/pom.xml ./Excitement-Open-Platform-$VERSION/lap/pom.xml.bkg
 #awk 'BEGIN {remove_tag = "false";} {line = $0; if ($line ~ /if you want to use TreeTagger/) remove_tag = "true"; else if ($line ~ /end of TreeTagger related dependencies/) remove_tag = "false"; #if (remove_tag == "true" && ($line ~ /<\!--/ || $line ~ /-->/) && $line !~ /[a-z0-9]/) line = ""; printf("%s\n", line);}' ./Excitement-Open-Platform-$VERSION/lap/pom.xml > ./Excitement-Open-Platform-$VERSION/lap/pom.xml.tmp
  #cp ./Excitement-Open-Platform-$VERSION/lap/pom.xml.tmp ./Excitement-Open-Platform-$VERSION/lap/pom.xml
 #check

4) rerun the install script

To view this discussion on the web visit https://groups.google.com/d/msgid/eop-users/1787ee6c-5a20-4ebd-b277-c65e6b492c60%40googlegroups.com.

[William Ferreira]

Hi Roberto

Thanks for that. I figured out a similar solution over the weekend and I now have EOP built and running with the tree tagger. I have some more questions, but they are unrelated to this thread so I will post them to the forum.

Kind regards

Will