Re: Testing the maven build system: Symlink error on duplicate inputs

["Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>]

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

On Sun, 20 Sep 2020 07:35:44 -0400
Julien Lepiller <julien@lepiller.eu> wrote:

> >Does someone have plans to add real-world packages that make use of
> >the maven-build-system? Next, an automated importer with
> >dependency-resolution would be nice :-)  
> 
> The issue with the importer is that maven doesn't record source
> information. We could have dependency resolution, but the resulting
> packages will lack any source (and for most packages also homepage
> and description).
> 
> One thing we have to decide on is what to do with maven build
> dependencies. Currently, things like test dependencies of
> dependencies are in the graph below maven, which means we have a lot
> of packages that cannot use the maven-build-system.
> 
> There are two possibilities: we can change the bootstrap path to
> maven to be minimal and only include runtime dependencies, and
> eventually rebuild maven with the maven-build-system. The other
> possibility is to keep it as is, and convert packages to install to
> lib/m2 as needed.
> 
> I tend to prefer the first solution, but that's also a lot of work.
> Our current maven package has bugs that are probably due to the way
> we build it (it doesn't honor user config, the build and test targets
> are mixed together, so are dependencies…). Building a proper maven
> with a minimal maven could help ensure it's built in the intended
> way, so these bugs could go away.
> 
> wdyt?

I think the former is much more work but cleaner and would worth it.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]