Can you explain a little more about what you are trying to do? When you say "compile a forked version of Jena", if you have actually forked the entire codebase, you should be able to just compile the entire codebase to get SNAPSHOT version artifacts of your forked code. Why are you trying to compile a mix of modules? Are you trying to maintain both ordinary and forked forms of Jena in your local Maven repo? What do you intend to do with the forked artifacts? Are you going to integrate them into some other application? There may be an easier way to do all this.
--- A. Soroka The University of Virginia Library > On Jan 5, 2017, at 10:01 AM, Samur Araujo <s.ara...@geophy.com> wrote: > > I run the sequence of commands below but it still failures. > > mvn release:update-versions -DdevelopmentVersion=3.1.1-myfork-SNAPSHOT > mvn clean > mvn install -Pbootstrap > mvn install -Pdev -DskipTests=true > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Apache Jena - Fuseki Server Engine 3.1.1-myfork-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > [WARNING] The POM for org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT > is missing, no dependency information available > [WARNING] The POM for > org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT is missing, no > dependency information available > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Jena - Parent ............................... SUCCESS [ > 1.552 s] > [INFO] Apache Jena - Base Common Environment .............. SUCCESS [ > 8.325 s] > [INFO] Apache Jena - Core ................................. SUCCESS [ > 11.643 s] > [INFO] Apache Jena - ARQ (SPARQL 1.1 Query Engine) ........ SUCCESS [ > 19.718 s] > [INFO] Apache Jena - TDB (Native Triple Store) ............ SUCCESS [ > 2.547 s] > [INFO] Apache Jena - Libraries POM ........................ SUCCESS [ > 0.234 s] > [INFO] Apache Jena - Command line tools ................... SUCCESS [ > 5.790 s] > [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SUCCESS [ > 0.047 s] > [INFO] Apache Jena - Fuseki Server Engine ................. FAILURE [ > 0.045 s] > [INFO] Apache Jena - Fuseki Embedded Server ............... SKIPPED > [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED > [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED > [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED > [INFO] Apache Jena - Security Permissions ................. SKIPPED > [INFO] Apache Jena ........................................ SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 50.588 s > [INFO] Finished at: 2017-01-05T15:56:51+01:00 > [INFO] Final Memory: 60M/1801M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project jena-fuseki-core: Could not > resolve dependencies for project > org.apache.jena:jena-fuseki-core:jar:3.1.1-myfork-SNAPSHOT: The following > artifacts could not be resolved: > org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT, > org.apache.jena:jena-spatial:jar:3.1.1-myfork-SNAPSHOT: Failure to find > org.apache.jena:jena-text:jar:3.1.1-myfork-SNAPSHOT in > http://repository.apache.org/snapshots was cached in the local repository, > resolution will not be reattempted until the update interval of > apache.snapshots has elapsed or updates are forced -> [Help 1] > [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/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :jena-fuseki-core > > > Notice the jena spatial and text are there: > > ~/tools/jena-master-forked$ find . | grep text | grep jar > ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-javadoc.jar > ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT-sources.jar > ./jena-text/target/jena-text-3.1.1-myfork-SNAPSHOT.jar > > > ~/tools/jena-master-forked$ find . | grep spatial | grep jar > ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT.jar > ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-sources.jar > ./jena-spatial/target/jena-spatial-3.1.1-myfork-SNAPSHOT-javadoc.jar > > > Am I missing anything else? > > The fork I am trying to compile is this one: > > https://github.com/jmvanel/jena/commits/master > > > > On 5 January 2017 at 11:23, Andy Seaborne <a...@apache.org> wrote: > >> >> >> 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" <s.ara...@geophy.com> 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 <rve...@dotnetrdf.org> 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-myf >>> ork-SNAPSHOT >>>> >>>> Rob >>>> >>>> On 04/01/2017 16:23, "Andy Seaborne" <a...@apache.org> 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 <a...@apache.org> >>> 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 >>> >>> >>> >>> >>> >>> > > > -- > 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
