https://github.com/mbentoalves/jena
[minor]
You'll need to add
nb-configuration.xml
to .gitignore.
+ <dependency>
+ <groupId>com.hp.hpl.jena</groupId>
+ <artifactId>arq</artifactId>
+ <version>2.8.8</version>
+ <type>zip</type>
Couple of things:
1/ It's type "jar" isn't it?
2/ Version - should be the same as the rest of Jena: 2.12.0-SNAPSHOT if
you are working from the current source tree. 2.8.8is likely to give
you some kind of incompatibility error at some point.
It would be good to put in some tests of the work so far so that you
know when future changes affect code already written.
Andy
On 18/06/14 10:02, Andy Seaborne wrote:
On 18/06/14 09:01, Miguel Bento Alves wrote:
Andy,
I did that and builded well except for JDBC TDB Driver. For me is not a
problem, I can work.
Good.
The "mvn -Pdev" build does the part you care about - not SDB nor JDBC
which are the slower ones - so it's faster.
Andy
Miguel
On 17/06/14 20:08, "Andy Seaborne" <[email protected]> wrote:
Miguel,
You'll need to set JAVA_HOME to a java7 installation.
Not only is it doclint problems but ARQ does not build due to a plugin
problem with maven.
Andy
On 17/06/14 09:38, Andy Seaborne wrote:
On 16/06/14 23:55, Miguel Bento Alves wrote:
Hi all,
I tried to create a maven repository in my machine as recommended in
https://jena.apache.org/download/maven.html
svn co https://svn.apache.org/repos/asf/jena/trunk/ Jena
cd Jena
mvn clean install
(instead of Jena, my folder name is JenaMBA_JENA650)
I got several errors in third step. I list the errors below. My
machine
specifications are:
apache-maven-3.2.1
java version "1.8.0_05"
Mac OS X 10.9.3
I also tried build on netbeans in my machine (after created a
branch in
github and clone to my computer) but I have the same kind of errors.
Three weeks ago I created the same repository and everything worked
fine.
Now, I needed to create again and I can¹t create a repository.
I have managed to recreate the same situation (same versions of maven
and java) when I set JAVA_HOME to point to a java8 system (this is
independent of what "mvn -version" prints out!!). If that points to a
java7, it works.
http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-
8-when-javadoc-tags-are-incomplete
so adding one of those fixes should make it work for you in your local
environment.
We (also) need a general, multi-java-version, solution.
Setting JAVA_HOME to be Java7, even if maven is running with java8
works.
(Notes as JENA-716)
Cleaning the javadoc would be good but it seems failing due to just
warnings, not strict errors. One warning shouldn't break the build.
Andy
Miguel
