[
https://issues.apache.org/jira/browse/UIMA-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-6143:
---------------------------------
Description:
The eclipse plugin build when doing a release prepare, at the end pushes the
head to the remote. For the repo url, it uses what you have in the scm
developer-connection. That must point to the repo, not to a folder within the
repo. Fix this for all projects in uimaj
Two ways to fix this. 1) require Maven 3.6.1 or later, using the
maven-enforcer-plugin, and use the scm attributes
child.scm.developerConnection.inherit.append.path=false
and remove all child scm elements, or 2) update all child scm elements.
Probably do the latter, because it doesn't require maven 3.6.1.
was:The eclipse plugin build when doing a release prepare, at the end pushes
the head to the remote. For the repo url, it uses what you have in the scm
developer-connection. That must point to the repo, not to a folder within the
repo. Fix this for all projects in uimaj
> for Git releases the developer connection scm needs to point to a repo
> ----------------------------------------------------------------------
>
> Key: UIMA-6143
> URL: https://issues.apache.org/jira/browse/UIMA-6143
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test, Eclipse plugins
> Affects Versions: 2.10.4SDK, 3.1.0SDK
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Major
> Fix For: 3.1.1SDK, 2.10.5SDK
>
>
> The eclipse plugin build when doing a release prepare, at the end pushes the
> head to the remote. For the repo url, it uses what you have in the scm
> developer-connection. That must point to the repo, not to a folder within
> the repo. Fix this for all projects in uimaj
> Two ways to fix this. 1) require Maven 3.6.1 or later, using the
> maven-enforcer-plugin, and use the scm attributes
> child.scm.developerConnection.inherit.append.path=false
> and remove all child scm elements, or 2) update all child scm elements.
> Probably do the latter, because it doesn't require maven 3.6.1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
