On 05/01/17 09:49, Rob Vesse wrote:
As others have already noted in this thread you will need to do a mvn install
rather than a package.
Yes - it is looking for "jena-core/3.1.1-myfork-SNAPSHOT" as specificed
in the jena-arq POM.
Rob
On 05/01/2017 07:45, "Samur Araujo" <[email protected]> wrote:
Hi Rob, I tried your approach but I got this error when packing:
It still cannot solve the dependencies. Am I missing any parameter?
~/tools/jena-master-forked/jena-arq$ mvn package
Why not run mvn at the top level?
mvn clean install
or (quicker but not all of Jena):
mvn clean
mvn install -Pbootstrap
mvn install -Pdev
these profiles are documented in the POM - you seem to have changed
the version everywhere so you may need -Pbootstrap
otherwise -Pdev is a fast build(and test!) of modules up to Fuseki2
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Jena - ARQ (SPARQL 1.1 Query Engine)
3.1.1-myfork-SNAPSHOT
[INFO]
------------------------------------------------------------------------
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.pom
[WARNING] The POM for
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT is missing, no
dependency information available
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-core/3.1.1-myfork-SNAPSHOT/jena-core-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-base/3.1.1-myfork-SNAPSHOT/jena-base-3.1.1-myfork-SNAPSHOT-tests.jar
Downloading:
http://repository.apache.org/snapshots/org/apache/jena/jena-shaded-guava/3.1.1-myfork-SNAPSHOT/jena-shaded-guava-3.1.1-myfork-SNAPSHOT.jar
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3.449 s
[INFO] Finished at: 2017-01-05T08:42:05+01:00
[INFO] Final Memory: 19M/480M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jena-arq: Could not resolve
dependencies for project
org.apache.jena:jena-arq:jar:3.1.1-myfork-SNAPSHOT: The following artifacts
could not be resolved: org.apache.jena:jena-core:jar:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-core:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-base:jar:tests:3.1.1-myfork-SNAPSHOT,
org.apache.jena:jena-shaded-guava:jar:3.1.1-myfork-SNAPSHOT: Could not find
artifact org.apache.jena:jena
On 4 January 2017 at 17:58, Rob Vesse <[email protected]> wrote:
> Probably the easiest thing to do is to change the versions in all the
> pom.xml files to a custom version so it can only use locally installed
> artefacts because the version won’t exist anywhere else i.e. Even if it
> looks for it on the Internet it won’t find it.
>
> You can do this automatically like so:
>
> mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT
>
> Rob
>
> On 04/01/2017 16:23, "Andy Seaborne" <[email protected]> wrote:
>
> The other modules will look for jena-core. If you want a different
> one,
> then change the pom.xml files to name a different artifact.
>
> Andy
>
> On 04/01/17 15:41, Lorenz Buehmann wrote:
> > You can specify the modules that you want to install or ignore
> >
> >
> > mvn clean install -pl !jena-core
> >
> >
> > should do the trick and omit jena-core
> >
> >
> > On 04.01.2017 15:53, Samur Araujo wrote:
> >> My forked version overwrite the dependencies. I do not want it to
> get the
> >> jena-core from repository but look for it locally, in the
> jena-master local
> >> folder structure.
> >>
> >> Is there any way to easily configure this?
> >>
> >> On 4 January 2017 at 15:03, Andy Seaborne <[email protected]> wrote:
> >>
> >>> "mvn clean install"
> >>>
> >>>
> >>> On 04/01/17 13:17, Samur Araujo wrote:
> >>>
> >>>> Hi all, how do I compile a forked version of Jena?
> >>>>
> >>>> What are the parameters I need to be passed to maven?
> >>>>
> >>>> I used "mvn package -o"
> >>>>
> >>>> But I got the error:
> >>>>
> >>>> Could not resolve dependencies.
> >>>>
> >>> You will need to let it down dependencies at least once.
> >>>
> >>> See "mvn dependency:tree" (when online).
> >>>
> >>>
> >>>>
> >>
> >
>
>
>
>
>
>
--
Senior Data Scientist
Geophy
www.geophy.com
Nieuwe Plantage 54-55
2611XK Delft
+31 (0)70 7640725
1 Fore Street
EC2Y 9DT London
+44 (0)20 37690760
