On 10/05/2021 22:42, Bögershausen, Merlin wrote:
I usually work less maven centric ;) Stumbled across the compile problem, 
because install with tests  fails due to missing configuration.
Tomorrow I'll do a fresh clone, set it up with install and see what's happening.

Generally, I use maven for the build step and running the entire test suite; IDE during development.

It is the shading and renaming of Google guava that complicates things, we may able to remove the shading though it's hard to tell about downstream usage and any dependency/versions issues.

The other uses of shading are building combined runnable jar files and don't do renaming.

    Andy


Cheers

Am 10.05.2021 22:51 schrieb Andy Seaborne <[email protected]>:


On 10/05/2021 19:36, Merlin Bögershausen wrote:
Hi Adam,
thanks for explaining. So install followed by compile should work.
$ mvn clean install -Pdev -DskipTests && mvn compile -Pdev
lead to same failure "package org.apache.jena.ext.com.google.common.cache does not 
exist", full log in gist: 
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d#file-mvn-clean-compile

mvn clean install -Pdev -DskipTests

and then after that:

cd jena-arq
mvn compile

I don't know why "mvn compile" at the top level doesn't work (I get the
same as you). shading doesn't happen in the compile stage and the
classes are no in target/classes. So a maven thing.

I guess if you omit the shading it would default to looking i the local
repo. I don't work that way.

It's done by my IDE (Eclipse with projects imported as maven modules) so
I don't step up into maven for a compile step.

      Andy


best Merlin
BesOn Mai 10 2021, at 7:53 pm, [email protected] wrote:
No, as Andy said, you must first run an 'install' to "bootstrap" the build.
Then you can use other goals.

Adam
On Mon, May 10, 2021, 1:39 PM Merlin Bögershausen <
[email protected]> wrote:

Hi,
On Mai 10 2021, at 6:12 pm, Andy Seaborne <[email protected]> wrote:

On 10/05/2021 16:19, Merlin Bögershausen wrote:
Hi,
for maven install (full log see attachments) it is:

No attachments - the list software rejects them
gist?
makes sence ;D see gist:
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d

Is this after a "mvn clean install -Pdev"?
No full install, but same result for -Pdev

That's solved by "mvn clean install"
"mvn clean install -Pdev" is slightly faster and enough.
So running anything other than install is no Option?







Am 10.05.2021 22:51 schrieb Andy Seaborne <[email protected]>:


On 10/05/2021 19:36, Merlin Bögershausen wrote:
Hi Adam,
thanks for explaining. So install followed by compile should work.
$ mvn clean install -Pdev -DskipTests && mvn compile -Pdev
lead to same failure "package org.apache.jena.ext.com.google.common.cache does not 
exist", full log in gist: 
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d#file-mvn-clean-compile

mvn clean install -Pdev -DskipTests

and then after that:

cd jena-arq
mvn compile

I don't know why "mvn compile" at the top level doesn't work (I get the
same as you). shading doesn't happen in the compile stage and the
classes are no in target/classes. So a maven thing.

I guess if you omit the shading it would default to looking i the local
repo. I don't work that way.

It's done by my IDE (Eclipse with projects imported as maven modules) so
I don't step up into maven for a compile step.

      Andy


best Merlin
BesOn Mai 10 2021, at 7:53 pm, [email protected] wrote:
No, as Andy said, you must first run an 'install' to "bootstrap" the build.
Then you can use other goals.

Adam
On Mon, May 10, 2021, 1:39 PM Merlin Bögershausen <
[email protected]> wrote:

Hi,
On Mai 10 2021, at 6:12 pm, Andy Seaborne <[email protected]> wrote:

On 10/05/2021 16:19, Merlin Bögershausen wrote:
Hi,
for maven install (full log see attachments) it is:

No attachments - the list software rejects them
gist?
makes sence ;D see gist:
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d

Is this after a "mvn clean install -Pdev"?
No full install, but same result for -Pdev

That's solved by "mvn clean install"
"mvn clean install -Pdev" is slightly faster and enough.
So running anything other than install is no Option?







Am 10.05.2021 22:51 schrieb Andy Seaborne <[email protected]>:


On 10/05/2021 19:36, Merlin Bögershausen wrote:
Hi Adam,
thanks for explaining. So install followed by compile should work.
$ mvn clean install -Pdev -DskipTests && mvn compile -Pdev
lead to same failure "package org.apache.jena.ext.com.google.common.cache does not 
exist", full log in gist: 
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d#file-mvn-clean-compile

mvn clean install -Pdev -DskipTests

and then after that:

cd jena-arq
mvn compile

I don't know why "mvn compile" at the top level doesn't work (I get the
same as you). shading doesn't happen in the compile stage and the
classes are no in target/classes. So a maven thing.

I guess if you omit the shading it would default to looking i the local
repo. I don't work that way.

It's done by my IDE (Eclipse with projects imported as maven modules) so
I don't step up into maven for a compile step.

      Andy


best Merlin
BesOn Mai 10 2021, at 7:53 pm, [email protected] wrote:
No, as Andy said, you must first run an 'install' to "bootstrap" the build.
Then you can use other goals.

Adam
On Mon, May 10, 2021, 1:39 PM Merlin Bögershausen <
[email protected]> wrote:

Hi,
On Mai 10 2021, at 6:12 pm, Andy Seaborne <[email protected]> wrote:

On 10/05/2021 16:19, Merlin Bögershausen wrote:
Hi,
for maven install (full log see attachments) it is:

No attachments - the list software rejects them
gist?
makes sence ;D see gist:
https://gist.github.com/MBoegers/81c4cfd9c029bf75f149f1201f2aa73d

Is this after a "mvn clean install -Pdev"?
No full install, but same result for -Pdev

That's solved by "mvn clean install"
"mvn clean install -Pdev" is slightly faster and enough.
So running anything other than install is no Option?






Reply via email to