Re: [glassfish-dev] Grizzly 3.0.0-M1 staged

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

Hi,

On 5/28/20 3:57 PM, arjan tijms wrote:
> Hi,
>
> I just (finally) staged Grizzly 3.0.0-M1. Besides the issues with the CI 
> (which hadn't been migrated yet, and had issues with expired 
> certificates etc), a major issue was in the way how Grizzly uses a bom.
>
> In essence the logical structure is:
>
> grizzly
> - pom.pom extends bom/pom.xml
> - bom/pom.xml extends EE4J 1.0.6 pom
>
> This seems logical,

but is not following original design. The way it should be is:

- bom/pom.xml extends EE4J 1.0.6 pom
- pom.xml extends EE4J 1.0.6 pom
- pom.xml has dependency on a non-snapshot version of bom/pom.xml with 
scope set to import

where bom has its own release job/cycle, so it is basically independent 
project


 but with this structure, Maven is absolutely
> hell-bent on using oss.sonatype.org <http://oss.sonatype.org> instead of 
> jakarta.oss.sonatype.org <http://jakarta.oss.sonatype.org> for 
> everything except bom/pom.xml itself.
>
> No amount of specifying nexusUrls or other properties can convince Maven 
> in this setup to use jakarta.oss.sonatype.org 
> <http://jakarta.oss.sonatype.org>. The phrase stubborn as a mule comes 
> to mind here.
>
> Investigating a number of other projects that use boms, it seems the 
> "solution" is to put an extra subdirectory in between:

I can only guess why we ended with current "solution". Right now it 
somehow works for most projects and there are more important things to 
work on instead of trying to fix this.

thanks,
--lukas


> grizzly
> - pom.pom extends boms/bom/pom.xml
> - boms/bom/pom.xml extends EE4J 1.0.6 pom
>
> I suspect this might have to do with bugs in Maven regarding the concept 
> of an "aggregator root", e.g like in this bug fix: 
> https://github.com/mojohaus/versions-maven-plugin/commit/783f9ce97ed4749aaf3343dcf507776524501878#diff-39626ad8ab6dfea365e39d7daff2f3b9L1392
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
> _______________________________________________
> glassfish-dev mailing list
> glassfish-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev