[
https://issues.apache.org/jira/browse/MNG-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318048#comment-16318048
]
Matt Biggs commented on MNG-6326:
---------------------------------
I've been experimenting with an extension for gitflow that reads the git branch
information and then adds a new remote repository to the build dynamically.
I've had to use afterSessionStart() method to inject the repository as it
doesn't work in afterProjectsRead() as i'm guessing that's too late in the
lifecycle. Since it is using afterSessionStart() i've had to put my extension
in the external extensions.xml file as the method isn't called if the extension
is defined within a pom.
However on initial first use the extension isn't obviously in your repository.
It's actually housed in our local company nexus instance and so it can't be
found (hence MNG-6327). The build issues a warning at the very beginning and
then continues. That then leads to strange behaviour and it's also not very
easy to spot the missing extension as it's a warning at the very beginning and
unless you happen to browse to the top of the build log/console you won't know.
> Build continues when core extensions aren't found
> -------------------------------------------------
>
> Key: MNG-6326
> URL: https://issues.apache.org/jira/browse/MNG-6326
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.5.2
> Reporter: Matt Biggs
> Priority: Critical
>
> If you define a core extension in *.mvn/extensions.xml* which then can't be
> retrieved/found the build issues a warning and then continues leading to
> unexpected behaviour depending on the functionality provided by the
> extension.
> If the extension is defined in the pom and not found the build fails. I would
> have expected it to fail when not found in the external extensions.xml file
> too as it's quite easy to miss the fact it failed to retrieve it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
