[
https://issues.apache.org/jira/browse/UIMA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785930#action_12785930
]
Marshall Schor commented on UIMA-1694:
--------------------------------------
I'm glad this is fixed - it was affecting users (see recent post in uima-users
mailing list).
Looking through some documentation, it seems the developerConnection is usually
the "https" style (not http). And, at least for some things in my local maven
repo (which I "grepped" for developerConnection), the url pointed to is often a
"tag", as opposed to the trunk.
The documentation ( http://maven.apache.org/scm/maven-scm-plugin/ ) implies
that https is needed for the developerConnection.
I think none of this matters, right now, because this information is not used
by our build process, because it's used by some continuous integration build
processes (which we haven't yet set up), or by the maven "release" plugin,
which we're not using (primarily because it doesn't work for "flat" structural
layouts, such as we have for our pom's - due to Eclipse workspace lack of
support for hierarchical multi-project layouts).
If we do start to make use of this information, will it be necessary to have
specific versions of this tag in each project's pom, pointing to that project's
pom's trunk url?
> Error 'scm url cannot be null' on uimaj POM
> -------------------------------------------
>
> Key: UIMA-1694
> URL: https://issues.apache.org/jira/browse/UIMA-1694
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.3S
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 2.3
>
>
> When launching 'mvn -Dmaven.repo.local=/tmp/uimaj-rc5 clean install' for
> testing the new 2.3.0-rc5, an error 'scm url cannot be null' on uimaj POM
> comes out
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
