slachiewicz opened a new pull request, #215:
URL: https://github.com/apache/maven-doap-plugin/pull/215

   A `scm:git:` connection was written as a generic `<Repository>` with the 
location `git:https://…`, which the plugin's own validation rejects, so a 
project with a Git connection failed with "Error parsing the generated DOAP 
file". Maven SCM was only there to recognise Subversion (`svnexe` was the only 
provider shipped).
   
   The connection is now split as `scm:<provider>:<url>` (or `|`) and mapped to 
DOAP's `SVNRepository`, `GitRepository`, `HgRepository` or `BazaarBranch`; 
other providers such as CVS keep the generic `<Repository>`. User information 
is removed from `http`, `https`, `svn` and `git` URLs, as Maven SCM did for 
Subversion, so Subversion output is unchanged. This drops `maven-scm-api`, 
`maven-scm-provider-svn-commons`, `maven-scm-manager-plexus` and 
`maven-scm-provider-svnexe` (23 to 19 runtime dependencies).
   
   Stacked on #214.
   
   Verified: `mvn -Prun-its verify` → 21 unit tests (existing Subversion 
assertions unchanged) and 1 IT pass; `testGitRepository` fails with the Git 
mapping removed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to