Re: Any plans to fix/update maven-scm-provider-hg ?
Got it working today. Thanks for the update. Some quick things -Why does this not work when you put it in the area? -Will this work with other plugins that deploy like a source deploy? -Shouldn't it url encode the username and password? My username has a @ symbol in it which breaks the url and the initial clone Thanks again for the update, Leon From: Olivier Lamy To: [email protected] Sent: Thu, January 20, 2011 5:32:39 PM Subject: Re: Any plans to fix/update maven-scm-provider-hg ? Hello, Fixed in scm trunk you can use (note where the dependency is declared) org.apache.maven.plugins maven-site-plugin 3.0-beta-3 org.apache.maven.scm maven-scm-api 1.5-SNAPSHOT org.apache.maven.scm maven-scm-provider-hg 1.5-SNAPSHOT And use this repo (until scm 1.5 is released ) : https://repository.apache.org/content/groups/snapshots-group/ let us know if you still have issues. 2011/1/20 Lord.Quackstar : > Sorry for the delay, I sent this with another email address that wasn't > subscribed. > > I have this in my POM > > > > org.apache.maven.wagon > wagon-webdav > 1.0-beta-2 > > > org.apache.maven.scm > maven-scm-provider-hg > 1.4 > > > org.apache.maven.wagon > wagon-scm > 1.0-beta-7 > > >.. > > > > > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.7 > > Leon Blakey > ${project.version} > > http://download.oracle.com/javase/6/docs/api > > > > > > > > ... > > maven-general-repo.googlecode.com > General Maven Repo on Google Code > scm:hg:https://site.pircbotx.googlecode.com/hg > false > > > maven-general-repo.googlecode.com > scm:hg:https://site.pircbotx.googlecode.com/hg/ > > > > > Leon > > > From: Olivier Lamy > To: [email protected] > Sent: Fri, January 14, 2011 4:27:51 PM > Subject: Re: Any plans to fix/update maven-scm-provider-hg ? > > Hello > Can you give more details ? > version of wagon scm you are using in your pom ? > > 2011/1/13 Lord.Quackstar : >> It seems that the only way to use Mercurial in Maven is through >> maven-scm-provider-hg. However there are so many problems that the plugin >> is >> unusable >> >> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by >> working I mean it detects that it exists and tries to use it), but in >> Maven >> 3.0.2 you get this: >> >> Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException: >> No >> such provider: 'hg'. >> >> Second, you have the list command bug, which seems to affect even people >> using hudsun. They were able to fix it by creating their own plugin, which >> doesn't work with Maven-only installations. Following is the error message >> >> [INFO] [deploy:deploy {execution: default-deploy}] >> [INFO] Retrieving previous build number from >> pircbotx.googlecode.com >> [INFO] Removing >> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir >> cbotx\pircbotx\1.3-SNAPSHOT >> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip >> >>https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT >>T >> >>C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT" >>" >> [INFO] EXECUTING: cmd.exe /X /C "hg locate" >> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT' >> could not be found on repository: pircbotx.googlecode.com, so will be >> created Uploading: >> >>scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar >>r >> [INFO]
Re: Any plans to fix/update maven-scm-provider-hg ?
Hello,
Fixed in scm trunk you can use (note where the dependency is declared)
org.apache.maven.plugins
maven-site-plugin
3.0-beta-3
org.apache.maven.scm
maven-scm-api
1.5-SNAPSHOT
org.apache.maven.scm
maven-scm-provider-hg
1.5-SNAPSHOT
And use this repo (until scm 1.5 is released ) :
https://repository.apache.org/content/groups/snapshots-group/
let us know if you still have issues.
2011/1/20 Lord.Quackstar :
> Sorry for the delay, I sent this with another email address that wasn't
> subscribed.
>
> I have this in my POM
>
>
>
> org.apache.maven.wagon
> wagon-webdav
> 1.0-beta-2
>
>
> org.apache.maven.scm
> maven-scm-provider-hg
> 1.4
>
>
> org.apache.maven.wagon
> wagon-scm
> 1.0-beta-7
>
>
> ..
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.7
>
> Leon Blakey
> ${project.version}
>
> http://download.oracle.com/javase/6/docs/api
>
>
>
>
>
>
>
> ...
>
> maven-general-repo.googlecode.com
> General Maven Repo on Google Code
> scm:hg:https://site.pircbotx.googlecode.com/hg
> false
>
>
> maven-general-repo.googlecode.com
> scm:hg:https://site.pircbotx.googlecode.com/hg/
>
>
>
>
> Leon
>
>
> From: Olivier Lamy
> To: [email protected]
> Sent: Fri, January 14, 2011 4:27:51 PM
> Subject: Re: Any plans to fix/update maven-scm-provider-hg ?
>
> Hello
> Can you give more details ?
> version of wagon scm you are using in your pom ?
>
> 2011/1/13 Lord.Quackstar :
>> It seems that the only way to use Mercurial in Maven is through
>> maven-scm-provider-hg. However there are so many problems that the plugin
>> is
>> unusable
>>
>> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by
>> working I mean it detects that it exists and tries to use it), but in
>> Maven
>> 3.0.2 you get this:
>>
>> Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException:
>> No
>> such provider: 'hg'.
>>
>> Second, you have the list command bug, which seems to affect even people
>> using hudsun. They were able to fix it by creating their own plugin, which
>> doesn't work with Maven-only installations. Following is the error message
>>
>> [INFO] [deploy:deploy {execution: default-deploy}]
>> [INFO] Retrieving previous build number from
>> pircbotx.googlecode.com
>> [INFO] Removing
>> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir
>> cbotx\pircbotx\1.3-SNAPSHOT
>> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip
>>
>> https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT
>>
>> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT"
>> [INFO] EXECUTING: cmd.exe /X /C "hg locate"
>> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT'
>> could not be found on repository: pircbotx.googlecode.com, so will be
>> created Uploading:
>>
>> scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar
>> [INFO]
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>>
>> [INFO] Error deploying artifact: Error listing repository: No such command
>> 'list'.
>>
>> (This is replicated on site:deploy as well).
>>
>> Third, you have the complete lack of documentation on using it. It took me
>> 3+ hours to get the results above; everything else kept erroring out as I
>> slipp
Re: Any plans to fix/update maven-scm-provider-hg ?
Hello
Can you give more details ?
version of wagon scm you are using in your pom ?
2011/1/13 Lord.Quackstar :
> It seems that the only way to use Mercurial in Maven is through
> maven-scm-provider-hg. However there are so many problems that the plugin is
> unusable
>
> First, you have it being out of date. In Maven 2.2.1 it works somewhat (by
> working I mean it detects that it exists and tries to use it), but in Maven
> 3.0.2 you get this:
>
> Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException: No
> such provider: 'hg'.
>
> Second, you have the list command bug, which seems to affect even people
> using hudsun. They were able to fix it by creating their own plugin, which
> doesn't work with Maven-only installations. Following is the error message
>
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from
> pircbotx.googlecode.com
> [INFO] Removing
> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pir
> cbotx\pircbotx\1.3-SNAPSHOT
> [INFO] EXECUTING: cmd.exe /X /C "hg clone -r tip
> https://*SNIP*@site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT
> C:\DOCUME~1\Owner\LOCALS~1\Temp\wagon-scm1210107000.checkout\pircbotx\pircbotx\1.3-SNAPSHOT"
> [INFO] EXECUTING: cmd.exe /X /C "hg locate"
> [INFO] repository metadata for: 'snapshot pircbotx:pircbotx:1.3-SNAPSHOT'
> could not be found on repository: pircbotx.googlecode.com, so will be
> created Uploading:
> scm:hg:https://site.pircbotx.googlecode.com/hg/maven2/snapshots/pircbotx/pircbotx/1.3-SNAPSHOT/pircbotx-1.3-SNAPSHOT.jar
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error deploying artifact: Error listing repository: No such command
> 'list'.
>
> (This is replicated on site:deploy as well).
>
> Third, you have the complete lack of documentation on using it. It took me
> 3+ hours to get the results above; everything else kept erroring out as I
> slipped further into dependency hell. None of the projects have docs on how
> to use this.
>
> Fourth, you have the abandonment of the user support mailing list (
> http://mail-archives.apache.org/mod_mbox/maven-scm-users/ ). This is more
> general to maven-scm, but does affect this plugin. The last email talks
> about this very same problem, however it's been almost 2 months with no
> response. Even for the past year none of the support questions have been
> answered.
>
> ---
>
> Combined, this leads to a plugin that isn't usable at all and can mislead
> people into thinking that it works. Are their any plans to update it? Are
> their any plans to depreciate it?
>
> Thanks,
> Leon
>
>
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
