Hi Eduardo,

it seems the repositories in "wildfly-jakartaee8-with-tools-21.0.0.Final.pom" don't work: the project created from the archetype will not compile with the same error, and maven does not even try to use the "jboss-enterprise-maven-repository".

I sent a pull request for the archetypes which updates the WildFly version to 21.0.0.Final, so you can test it.

Is inheritance of repositories supported at all?
I found http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Super_POM (but am not sure whether this also applies for bom):
Project Inheritance
Elements in the POM that are merged are the following:
    dependencies
    developers and contributors
    plugin lists (including reports)
    plugin executions with matching ids
    plugin configuration
    resources

If it does not work, at least the "jboss-enterprise-maven-repository" would have to added to the archetype pom.xml.

But I wonder why it worked for 20.0.0.Final - I don't see a difference in the repository declaration, and here the dependency "org.picketbox:picketbox:jar:5.0.3.Final-redhat-00005" is found.

Best regards

Wolfgang

Quick update on this, WFLY-13914 was now resolved, from now on any built BOMs will have the JBoss Public and RedHat GA Maven repos, starting with 21.0.0.Final. No need for any changes in other projects such as archetypes.

—E

On 1 Oct 2020, at 13:32, Eduardo Martins <emartins@redhat.com> wrote:

Hi Wolfgang, probably not needed since I am working on the plugin enhancement, WFLY 21 Final BOMs should have Maven repos already.

—E

On 30 Sep 2020, at 19:55, Wolfgang Knauf <wolfgang.knauf@gmx.de> wrote:

Thanks!

I will send a pull request for the updated archetype when 21.0.0.Final
is out.

Best regards

Wolfgang

Am 29.09.20 um 23:02 schrieb Eduardo Martins:

Hi Wolfgang, for now you need to add the
https://maven.repository.redhat.com/ga repo, this is due to the BOM
Builder maven plugin not adding maven repos to the BOMs it builds. Such
plugin enhancement is already planned tho (WFLY-13914
<https://issues.redhat.com/browse/WFLY-13914>).

—E

On 29 Sep 2020, at 21:45, Wolfgang Knauf <wolfgang.knauf@gmx.de
<mailto:wolfgang.knauf@gmx.de>> wrote:

Hi all,

I try to upgrade the "wildfly-archetypes" to 21.0.0.Beta1, and compiling
a project (named "multi") created from this archetype (profile:
arq-managed) fails with this error:

[WARNING] The POM for
org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006 is missing, no
dependency information available

[ERROR] Failed to execute goal on project multi: Could not resolve
dependencies for project foo.bar:multi:pom:0.1-SNAPSHOT: Failure to find
org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central
has elapsed or updates are forced -> [Help 1]

The file seems to be only available here:
https://maven.repository.redhat.com/ga/org/picketbox/picketbox/5.0.3.Final-redhat-00006/

This repository is defined in
https://repo.maven.apache.org/maven2/org/wildfly/bom/wildfly/21.0.0.Beta1/wildfly-21.0.0.Beta1.pom

When building a project from archetype for 20.0.0.Final, then picketbox
"5.0.3.Final-redhat-00005" is included, which is downloaded by maven
from somewhere (after deleting the files in my local repository first).


The archetype just defines a dependency
"org.wildfly.bom:wildfly-jakartaee8-with-tools:21.0.0.Beta1". It seems
this one does not use "wildfly-21.0.0.Beta1.pom" - maybe indirectly?

Does anybody have an idea? I probably could define the repository in the
pom.xml created of the archetype target project, but it worked before.


Attached ("dependencytree.txt") are the download log messages and the
dependency tree log.

Best regards

Wolfgang
<dependencytree.txt>_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s