-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build lastest version #29
Comments
Same problem here. Which is sad because the project looks promising. |
Same errors. I guess I will have to fix it myself. I hope the code isn't buggy. |
hey @nasagfunaro did you fix the bug? Not looking forward to digging in the Java hole :( |
I only spent about an hour on it. It is not a high priority for me. Though I would like to find a solution for keeping pdf paragraphs together. It looks like a maven dependency issue. If I have time this week and the inclination I may try again to work out the dependency.
If I find a solution, I will post.
On Jun 11, 2017, at 3:07 PM, Alexander Whillas <[email protected]<mailto:[email protected]>> wrote:
hey @nasagfunaro<https://github.com/nasagfunaro> did you fix the bug? Not looking forward to digging in the Java hole :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#29 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIt_EwvexZmo8vINH1kTjJ6AhPD7XofIks5sDEkOgaJpZM4J3BQa>.
|
Well, the repos here are indeed confusing . . . I guess a build would look like this (did not get it to build successful :( )
git clone https://github.com/BMKEG/bmkeg-as-parent.git
cd bmkeg-as-parent
mvn install
https://github.com/BMKEG/vpdmfCore.git
diff --git a/pom.xml b/pom.xml
index 3e7eca9..144cf73 100644
--- a/pom.xml
+++ b/pom.xml
@@ -9,9 +9,9 @@
<parent>
<groupId>edu.isi.bmkeg</groupId>
- <artifactId>bmkeg-parent</artifactId>
- <version>1.2.0-SNAPSHOT</version>
- <relativePath>../bmkeg-parent</relativePath>
+ <artifactId>bmkeg-as-parent</artifactId>
+ <version>1.1.5-SNAPSHOT</version>
+ <relativePath>../bmkeg-as-parent</relativePath>
</parent>
<name>VPDMf</name>
https://github.com/BMKEG/vpdmfGenerator.git
diff --git a/pom.xml b/pom.xml
index eea1148..a801495 100644
--- a/pom.xml
+++ b/pom.xml
@@ -8,9 +8,9 @@
<packaging>jar</packaging>
<parent>
<groupId>edu.isi.bmkeg</groupId>
- <artifactId>bmkeg-parent</artifactId>
- <version>1.2.0-SNAPSHOT</version>
- <relativePath>../bmkeg-parent</relativePath>
+ <artifactId>bmkeg-as-parent</artifactId>
+ <version>1.1.5-SNAPSHOT</version>
+ <relativePath>../bmkeg-as-parent</relativePath>
</parent>
<name>VPDMf Generator System</name>
git clone https://github.com/BMKEG/vpdmf-parent.git
cd vpdmf-parent
diff --git a/pom.xml b/pom.xml
index 5d61835..4ff01e4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -9,7 +9,7 @@
<parent>
<groupId>edu.isi.bmkeg</groupId>
- <artifactId>bmkeg-parent</artifactId>
+ <artifactId>bmkeg-as-parent</artifactId>
<version>1.1.5-SNAPSHOT</version>
<relativePath>../bmkeg-parent</relativePath>
</parent>
This is where I gave up. Don't know why the repo owner do not mention how to build anywhere :( |
This article mentiones install builds as well as an installation instructions, but both are not working :( The installers are dead links |
I was able to fix this issue by adding a second pom.xml as the parent POM and providing its relative path in the actual pom.xml which is throwing the mentioned error. The reference in the POM.xml I added the parent pom.xml under src , hence the relative path in the above mentioned pom.xml Here's the path to the parent POM.xml https://github.com/BMKEG/bmkeg-parent/blob/d6a5649d5214e3c43b86ee9bd372ecba4c2ac1d3/pom.xml |
If you're still pursuing this, I got the build to work without changing any pom files. Starting with: Then, in bmkeg-parent, run mvn install It ran to completion with no errors. FYI, the build took 2 hrs and 42 minutes on a macbook air. |
In my case this pom.xml worked! |
Got this error message after executing the
mvn -DskipTests assembly:assembly
command I'm not familiar with Maven so I couldn't dig any further.The text was updated successfully, but these errors were encountered: