Closed tsedmik closed 5 years ago
This should work correctly once we get the work for https://github.com/jboss-fuse/fuse-apicurito-generator/issues/12 merged.
After some investigation, this appears to be due to the lack of these repository entries in the pom.xml for the generated project. Do we want to add them?
<repository>
<id>jboss-ea</id>
<url>https://repository.jboss.org/nexus/content/groups/ea</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<pluginRepository>
<id>jboss-ea</id>
<url>https://origin-repository.jboss.org/nexus/content/groups/ea</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
@tsedmik @apupier @hiram wdyt? about adding the extra early access repo to generated projects until we have a final release of the springboot bom?
wdyt? about adding the extra early access repo to generated projects until we have a final release of the springboot bom?
if repository is public, I vote to include it to have generated projects working out of the box.
@tsedmik Can you verify?
@bfitzpat verified with master branch
Maven repositories defined in pom.xml are not sufficient to build the project. If I try to execute
mvn clean package
with clean .m2 folder (without additional repositories in settings.xml file), the build is not successful (see below).