Aaah ... ok ... if it's of type "pom", then you need to add a dependency of type pom. Otherwise it will expect it to be of type "jar" and try to get a jar file.
And you are correct, if you built the wayang RC locally, then the artifacts should be available in your local maven repo. Chris -----Ursprüngliche Nachricht----- Von: Gábor Gévay <[email protected]> Gesendet: Mittwoch, 29. September 2021 09:17 An: [email protected] Betreff: Re: [DISCUSS] Apache Wayang 0.6.0 RC1 Hi Chris, Hm, but I built Wayang locally with mvn install, so all the jars that are part of the release should be in my local Maven repo, right? And the other jars are there: I also have wayang-core, wayang-basic, wayang-java in the dependencies of my test project, and these are successfully resolved. I also tried adding the repository reference that you wrote, and it's still the same. I think the situation is that the wayang-api module is just an "aggregator" module (I'm not sure if this is the proper term) of the API modules wayang-api-scala-java and wayang-api-python, and this is why it doesn't have a jar by itself, because only its submodules have jars. And maybe it used to be that what is wayang-api-scala-java used to be just wayang-api, so maybe that's why the website has that? Best, Gábor Christofer Dutz <[email protected]> ezt írta (időpont: 2021. szept. 28., K, 22:20): > > Hi Gabor, > > the maven build would have succeeded, if wayang had been released. Right now > there's no 0.6.0 available in maven-central. > > You could have added a repositories reference to > https://repository.apache.org/content/repositories/orgapachewayang-100 > 2 > Then it problably would have worked. > > Will do my validation hopefully tomorrow. > > > Chris > > -----Ursprüngliche Nachricht----- > Von: Gábor E. Gévay <[email protected]> > Gesendet: Dienstag, 28. September 2021 20:05 > An: [email protected] > Betreff: Re: [DISCUSS] Apache Wayang 0.6.0 RC1 > > Hello, > > Successfully compiled with `mvn clean install` with both -Pscala-11 on Java 8 > and -Pscala-12 on Java 11. Verified the key and verified the sha checksum. > > I also tried creating an empty Maven project, adding Wayang as a dependency > as described on our documentation page > (https://wayang.apache.org/documentation/ ), and it worked after resolving a > minor issue: > > The documentation page lists a number of dependencies that the user should > add, and one of these is `wayang-api`, but this was not working for me. So > this is what I had in my pom: > > <dependency> > <groupId>org.apache.wayang</groupId> > <artifactId>wayang-api</artifactId> > <version>0.6.0</version> > </dependency> > > And Maven gave the following error: > > [ERROR] Failed to execute goal on project wayang-proba: Could not > resolve dependencies for project > org.example:wayang-proba:jar:1.0-SNAPSHOT: Could not find artifact > org.apache.wayang:wayang-api:jar:0.6.0 in central > (https://repo.maven.apache.org/maven2) -> [Help 1] > > Changing `wayang-api` to `wayang-api-scala-java_2.11` works. Maybe > `wayang-api` was left there from an older version? In that case, we could > just update the website. > > Another minor thing about the documentation page is that it still says “If > you need to rebuild Apache Wayang, e.g., to use a different Scala version, > you can simply do so via Maven: > Adapt the version variables (e.g., spark.version) in the main pom.xml file. > ...” > But this recently changed to the Maven profile stuff. > > But these would be just website changes, so I guess it doesn’t affect the > release itself. So I gave +1 in the other thread. > > Best, > Gábor
