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" <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).
>>>
>>>
>>>>
>>
>
