Maven Plugin Testing Tools deprecated
Hi. I want to invoke a maven build as part of the unit test. I thought that http://maven.apache.org/plugin-testing/maven-plugin-testing-tools/ was the right tool, but its javadoc is completly deprecated and no replacement mentioned. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
prevent automatic adaptation of scm connection url
Hi list. I have a multi-module project. The parent pom has something like: scm:git:http://0.0.0.0/dummy/for/buildnumber-maven-plugin.git Strangely, in the effective pom of submodules the module directory name is appended to the urls: scm:git:http://0.0.0.0/dummy/for/buildnumber-maven-plugin.git/submodule I know it makes sense for SVN, but git urls can't contain subdirs, do they? And where is this documented? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-war-plugin addClasspath useless, because it cannot add absolute paths
Hi List. As far as I know, Class-Path in MANIFEST.MF of a .war file is only useful when you need to add jars that are not in WEB-INF/lib and not provided by the container. But can maven add paths that are absolute or relative? I tried this: nah nah 1.0.0 system /C:/1/ccc.jar true ... org.apache.maven.plugins maven-war-plugin true The Class-Path was indeed added to MANIFEST.MF, but not the "ccc.jar". - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn site:deploy SCM: No such provider: 'cvs'
Thanks Hervé. My ultimate goal was to deploy maven artifacts to a private github repo, because we already have a paid github account. I can see there're too many unsolved problems with this. Here's a pom that almost does it: http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 foo bar 0.1-SNAPSHOT bar org.apache.maven.plugins maven-deploy-plugin org.apache.maven.wagon wagon-scm 3.0.0 org.apache.maven.scm maven-scm-manager-plexus 1.9.5 org.apache.maven.scm maven-scm-provider-gitexe 1.9.5 xxx scm:git:/.snapshots/persist/builds/scm/repo.git my.cvs.server scm:jgit:/.snapshots/persist/builds/scm/repo.git On 24.01.2018 9:47, Hervé BOUTEMY wrote: > Hi, > > I didn't really tried, but please read carefully the 2 notes in the page: > Prefer maven-scm-publish-plugin to publish your site to SCM > > Note for Maven 3 users: The site plugin behaves differently, require > these > be added as dependencies instead of extensions. See Adding a Protocol to > Deploy the Site. > > and even the list of limitations that is explained just before. > > I'm not sure this documentation should remain so visible: maven-scm-publish- > plugin is really the solution to the use case > > Regards, > > Hervé > > Le mardi 23 janvier 2018, 14:52:10 CET Basin Ilya a écrit : >> Hi list. >> I'm trying to make work the deploy maven site example from >> http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html >> >> I have an empty java project. First I do `mvn site:site` and a site is >> created in target/ Then I do `mvn site:deploy` and it fails with "No such >> provider". It doesn't seem to reach the point where it calls the cvs >> binary. >> >> >> Here's my pom.xml : >> >> >> http://maven.apache.org/POM/4.0.0; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd;> >> 4.0.0 >> >> foo >> bar >> 0.1-SNAPSHOT >> bar >> >> >> >> >> >> org.apache.maven.wagon >> wagon-scm >> 3.0.0 >> >> >> org.apache.maven.scm >> >> maven-scm-manager-plexus >> 1.9.5 >> >> >> org.apache.maven.scm >>
mvn site:deploy SCM: No such provider: 'cvs'
Hi list. I'm trying to make work the deploy maven site example from http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html I have an empty java project. First I do `mvn site:site` and a site is created in target/ Then I do `mvn site:deploy` and it fails with "No such provider". It doesn't seem to reach the point where it calls the cvs binary. Here's my pom.xml : http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 foo bar 0.1-SNAPSHOT bar org.apache.maven.wagon wagon-scm 3.0.0 org.apache.maven.scm maven-scm-manager-plexus 1.9.5 org.apache.maven.scm maven-scm-provider-cvsexe 1.9.5 my.cvs.server scm:cvs:local:/cygdrive/d/1/cvs_repository:myprojects Here're the commands to create a local cvs repo: mkdir cvs_repository export CVSROOT=:local:`pwd`/cvs_repository cvs init mkdir empty_dir cd empty_dir cvs import -mroot myprojects vtag rtag cd .. mkdir work_dir cd work_dir cvs co myprojects cd myprojects touch a b c cvs add a b c ; echo $? cvs commit -mabc - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
