Hi Stevo,
so let me summarize what I understood:
- There are some modules in mahout that are built with Scala, some with java
and some with both (At least that's what I see when checking out the project)
- The current build uses Scala 2.11 to build the Scala code.
- The resulting libraries are only compatible with Scala 2.11
Now you want to also publish versions compatible with Scala 2.12?
If that's the case I think Maven could easily add multiple executions where
each compile compiles to different output directories:
- Java --> target/classes
- Scala 2.11 --> target/classes-2.11
- Scala 2.12 --> target/classes-2.12
Then the packaging would also need a second execution ... each of the
executions bundling the classes and the corresponding scala output.
Ideally I would probably use maven classifiers to distinguish the artifacts.
<dependency>
<groupId>org.apache.mahout</groupId>
<artifactId>mahout-spark</artifactId>
<version>14.1-SNAPSHOT</version>
<classifier>2.11</classifier>
</dependency>
Then it should all work in a normal maven build. In the distributions you could
also filter the versions according to their classifiers.
So if this is the case, I could help you with this.
Chris
Am 16.04.20, 09:39 schrieb "Stevo Slavić" <ssla...@gmail.com>:
Disclaimer: I'm not active Mahout maintainer for quite a while, have some
historical perspective, take it with a grain of salt, could be I'm missing
the whole point you were approached for by a wide margin of error.
At a point Mahout, some of its modules, have turned into a scala
library, and there was need to cross publish those modules, across
different scala versions. Back than Maven scala plugin didn't support cross
publishing, it doesn't fit well with Maven's build lifecycle concept
(multiple compile phases - one for each scala version, and what not would
be needed). Switching to sbt could have solved the problem. Switch was
deemed to be too big task, even though ages have been spent on trying to
apply Maven (profiles) + bash scripts and what not to solve the problem.
Trying to apply same approach over and over again and expecting different
results is not smart, no expert can help there. Mahout maintainers and
contributors, should consider alternative approach, one of them being
switching to sbt - it's scala native, supports scala cross publishing,
supports publishing Maven compatible release metadata and binaries.
Kind regards,
Stevo Slavic.
On Thu, Apr 16, 2020 at 9:15 AM Christofer Dutz <christofer.d...@c-ware.de>
wrote:
> Hi folks,
>
> my name is Chris and I’m involved in quite a lot of Apache projects.
> Justin approached me this morning, asking me if I could perhaps help you.
> He told me you were having trouble with doing Maven releases.
>
> As Maven releases are my specialty, could you please summarize the issues
> you are having?
>
> Chris
>
