Hell,
You have added a dependency to wagon-scm in your project ?
So you have to add a dependency to your scm provider too.
In your case, it should be
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-hg/artifactId
!-- not sure about the version
be
done through the wagon-scm plugin, which in turn relies upon the
maven-scm
plugin. Pertinent components of my pom are:*
*
*
...
distributionManagement
...
site
idgooglecode/id
namegwt-syntaxhighlighter Site/name
urlscm:hg:https://site.gwt-syntaxhighlighter.googlecode.com/hg
*I am hoping I am getting to the right people here... Anyway, here's the
situation: Attempting to set up Maven to be able to deploy a site to a
mercurial repository on Google Code, which from what I have read, should be
done through the wagon-scm plugin, which in turn relies upon the maven-scm
/executions
/plugin
/plugins
/build
/project
-Original Message-
From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter
Sent: Thursday, June 10, 2010 4:23 PM
To: Maven Users List
Subject: Re: wagon-maven-plugin and wagon-scm
This would
Hello all,
I was wondering if anyone has gotten the wagon-maven-plugin working with
wagon-scm? Specifically, I am trying to issue a command like this:
mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-3:merge-maven-repos
-Dwagon.source=file://E:\stage
-Dwagon.target=scm:svn:http://testserver
This would require that wagon-scm is in the build extensions, which is not
possible without a POM file.
An alternative is to use dav:http://, and turn on auto-versioning on your
subversion server (though it creates a revision per-file...)
On 11/06/2010, at 5:49 AM, Jim McCaskey wrote:
Hello
So looking at the git SCM code (git-commons and gitexe) and at the wagon-scm
code, the problem I see is that there is no syntax in the git SCM url to
specify a branch to which to deploy the site. Not a surprise, since git
generally wants to clone an entire repository and then push and pull
commit -a -m Deploy site documentation
git push
rm -Rf ${checkoutDirectory}
-K
On Apr 2, 2010, at 11:28 AM, Kathryn Huxtable wrote:
So looking at the git SCM code (git-commons and gitexe) and at the wagon-scm
code, the problem I see is that there is no syntax in the git SCM url to
specify
of the maven-scm-api!
Your attempt with first determining/setting the branch with native git commands
would actually work with git, but I'd prefer to give wagon-scm the branch as
parameter and use that inside the code.
txs and LieGrue,
strub
--- Kathryn Huxtable kath...@kathrynhuxtable.org schrieb am Fr
the version gets set via the -DscmVersion parameter which transfers
into the ScmVersion parameter in various functions of the maven-scm-api!
Your attempt with first determining/setting the branch with native git
commands would actually work with git, but I'd prefer to give wagon-scm the
branch
Okay, I'm not a CVS user, but I tried using wagon-scm with the
maven-scm-provider-cvsexe and a CVS URL and got:
Transfer error: org.apache.maven.scm.manager.NoSuchScmProviderException: No
such provider: 'cvs'.
I had given it the following site URL:
urlscm:cvs:ext:usern...@cvs.apache.org
incorrectly, it
sucks to be them, but it's not really your problem. If the API
contract needs clarification, that's a seperate issue, but I seem to
remember the Wagon API being relatively obvious.
IMHO, you should be writing your own wagon implementation and avoid
using wagon-scm. This use case
answerable. Wagon exposes an API and anyone is free to use it.
I've written a few (closed source) plugins which use putDirectory and
I suspect I'm not alone in this.
Well, yeah, but I was trying to get at the expectations. The wagon-scm thing
adds the target to the end of the repo, which, as has been
On Apr 2, 2010, at 2:22 PM, Kathryn Huxtable wrote:
On Apr 2, 2010, at 2:03 PM, Justin Edelson wrote:
IMHO, you should be writing your own wagon implementation and avoid
using wagon-scm. This use case is very specific to github. This way,
you're free to define your own URL syntax.
Well
Edelson wrote:
IMHO, you should be writing your own wagon implementation and avoid
using wagon-scm. This use case is very specific to github. This way,
you're free to define your own URL syntax.
Well, that's what I was thinking about doing. It looks to me as if
the wagon-scm is in pretty early
I've deployed it to the URL below but it sucks. Seriously, I hacked it with a
chainsaw.
http://github.com/khuxtable/wagon-gitsite
Actually, there are just a few changes necessary to the wagon-scm necessary to
get it to work with git and site:deploy
1) Don't append the target directory
I know the docs say that wagon-scm has only been tested with CVS and
Subversion, and I've run it with Subversion successfully.
Is anyone working on getting it to work with Git, or does it already?
I created a very simply project with a README and a pom.xml and nothing else.
It's
to be automated.
-K
On Apr 1, 2010, at 12:14 PM, Kathryn Huxtable wrote:
I know the docs say that wagon-scm has only been tested with CVS and
Subversion, and I've run it with Subversion successfully.
Is anyone working on getting it to work with Git, or does it already?
I created a very
Kathryn,
I haven't used wagon-scm, so I can only make vague assumptions.
Basically all the branches and tag stuff should be working in
maven-scm-provider-gitexe. But I'm not sure how wagon-scm tells us what branch
it likes to use.
From looking at the source [1] I only can see that all
Thanks, Mark,
These are good points.
I'm thinking that the issues are in wagon-scm, which is listed as being in
progress, so I can't really expect perfection. And they *do* say it's only
been tested with svn and cvs. I'm thinking that I may be modding wagon-svn,
more to see what's going
I honestly doubt that wagon-scm + CVS currently works when using branches (from
glimpsing at the sources).
And I'm not sure what you mean with forking it. Wouldn't it be much easier to
simply checkout wagon-scm and if you found a way to provide the branch as
ScmVersion (ScmBranch and ScmTag
Yeah, that's more or less what I mean. -K
On Apr 1, 2010, at 4:09 PM, Mark Struberg wrote:
I honestly doubt that wagon-scm + CVS currently works when using branches
(from glimpsing at the sources).
And I'm not sure what you mean with forking it. Wouldn't it be much easier to
simply
I don't think wagon-scm has been tested with git - while most is generic
there's a chance it won't work yet. You could file an issue in WAGON. You might
also get help from more general git / scm users on us...@maven.apache.org.
- Brett
On 31/03/2010, at 3:47 AM, Kathryn Huxtable wrote
On 29/03/2010, at 1:29 PM, Kathryn Huxtable wrote:
urls[1] =
file:/Users/huxtable/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
It looks like the project is using an older version of this library than is
needed (at least 1.5.6). You should add the newer
Okay, updating the plexus utils has other issues in my project, but I'll figure
them out. Reordering the extensions did the trick for the extension versions.
Thanks.
I've created a very simple project at http://github.com/khuxtable/test-project,
which has no source (or docs) just to test site
On Mar 30, 2010, at 11:29 AM, Kathryn Huxtable wrote:
[INFO] Executing: /bin/sh -c cd
/var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp- git clone
git+ssh//github.com/khuxtable/test-project.git/.
/var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp-/wagon-scm472467110.checkout
I especially
Okay, I see, looking at the source for maven-scm-provider-gitexe that list
isn't implemented. It is apparently used by the wagen-scm extension. I've
verified that the wagon-scm does work with my subversion repo.
So git just isn't as mature at this point.
Is anyone actively developing wagon-scm
On 30/03/2010, at 4:12 PM, Kathryn Huxtable wrote:
Okay, I see, looking at the source for maven-scm-provider-gitexe that list
isn't implemented. It is apparently used by the wagen-scm extension. I've
verified that the wagon-scm does work with my subversion repo.
So git just isn't
On Mar 28, 2010, at 9:29 PM, Kathryn Huxtable wrote:
And if so, what versions?
I'm working on a plugin, so I'm including a bunch of plexus and other stuff.
Is that important?
...
I should have mentioned that I'm running Maven 2.2.1.
-K
.apache
.maven
.artifact
.deployer
.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
... 20 more
--
View this message in context:
http://www.nabble.com/wagon-scm%3A-409-when-trying-to-deploy-tp25143236p25143236.html
Sent from the Wagon - Users mailing list archive at Nabble.com
Hi there,
I was wondering what the status of wagon-scm is with regard to Maven
2.0.10. I've read the usage page but the versions appear to be out of
date:
http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html
I've tried newer versions but end up with linking errors at runtime
beta-4 and above require 2.1.0+ for all wagons.
On 12/03/2009, at 10:30 PM, Mark Hobson wrote:
Hi there,
I was wondering what the status of wagon-scm is with regard to Maven
2.0.10. I've read the usage page but the versions appear to be out of
date:
http://maven.apache.org/wagon/wagon
Hello all,
I'm having a problem trying to use the wagon-scm plugin. I have added
the following to my pom (in this case, a parent pom):
build
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-2-SNAPSHOT/version
/extension
For anyone else having this problem, it seems to be fixed in
maven-2.0.5-SNAPSHOT.
Best wishes,
Dean.
On 1/3/07, Dean Jones [EMAIL PROTECTED] wrote:
Hello all,
I'm having a problem trying to use the wagon-scm plugin. I have added
the following to my pom (in this case, a parent pom):
build
If anyone is using the wagon-scm plugin, can you help me by posting the
sections of your pom.xml that apply to this plugin?
Thanks for the help,
-Nate
Here are the extensions I'm using for in my build:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon
Hello,
I'm getting the following error when I try to run site:deploy
Unsupported protocol: 'scm'
Here are the extensions I'm using for in my build:
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-scm/artifactId
version1.0-beta-1-SNAPSHOT/version
I realize I should be beat for not running with X before posting to the
users list, but better late then never. After running with debugging
enabled, I found the wagon-scm snapshot version used by maven was
1.0-beta-1-20060509.172247-7. However, maven cannot find a
wagon-providers-api POM
Does wagon-scm work with other providers besides cvs and svn?
Let say I have a provider that is already working with the scm-plugin, what
are the steps to get the provider to work with the wagon-scm?
Thank you very much.
--
View this message in context:
http://www.nabble.com/wagon-scm
it only works for svn, other providers will need to provide real
implementations of some methods of the api that currently throw
opperation not supported exceptions
On 8/17/06, ekio [EMAIL PROTECTED] wrote:
Does wagon-scm work with other providers besides cvs and svn?
Let say I have a provider
already but haven't tried
On 3/9/06, Olivier Lamy [EMAIL PROTECTED] wrote:
Great feature.
Deploying artifact with wagon-scm will be supported too ?
- Olivier
-Message d'origine-
De : rick rineholt [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 9 mars 2006 18:31
À : Maven Users List
Objet
AFAIK you can't access the plugins configuration
Take also into account that wagon-scm is very experimental yet, if you
get it working it'd be great if you could provide example and docs for
http://maven.apache.org/wagon/ref/1.0-alpha-7-SNAPSHOT/wagon-providers/wagon-scm/usage.html
Thanks
On 3
Ok I can expose my use case.
Do I have trouble with interet access (proxy).
But I don't see wagon-scm in
http://svn.apache.org/viewcvs.cgi/maven/wagon/trunk/wagon-providers/ ??
- Olivier
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Carlos
Sanchez
It's still in the sandbox
http://svn.apache.org/viewcvs.cgi/maven/sandbox
On 3/9/06, Olivier Lamy [EMAIL PROTECTED] wrote:
Ok I can expose my use case.
Do I have trouble with interet access (proxy).
But I don't see wagon-scm in
http://svn.apache.org/viewcvs.cgi/maven/wagon/trunk/wagon
.
artifact:install-provider artifactId=wagon-scm
version=1.0-alpha-5/
artifact:deploy
file=${pom.build.outputDirectory}/../${pom.artifactId}-${pom.version}.j
ar
remoteRepository
url=scm:svn:http://myserver/svnroot/repository
-remote-repo
description=Share the previously-packaged jar by installing to
the shared remote repository.
artifact:install-provider artifactId=wagon-scm
version=1.0-alpha-5/
artifact:deploy
file=${pom.build.outputDirectory}/../${pom.artifactId
:
'c:\projects\_artifact_\${user.home}\.m2\repository\_group_\_artifact_\_
version_\${user.home}\.m2\repository\_group_\_artifact_\_version_' is
not a working copy
The directory literal ${user.home} is created and the file does live in
the specified location. Even though wagon-scm
\_
version_\${user.home}\.m2\repository\_group_\_artifact_\_version_' is
not a working copy
The directory literal ${user.home} is created and the file does live in
the specified location. Even though wagon-scm is 'experimental', it is
extremely useful ;-)
-D
On 1/5/06, Darren
Hey all,
Has anyone used the wagon-scm provider for use with the antlib
artifact:deploy task?
We keep a separate repository of jar's in Subversion (for versioning
control and security of those jars/poms) and would like to automate this
task with the build.xml file using the maven2 antlibs
There are a few issues with the wagon-scm provider as it was only
prototyped earlier in the year and there hasn't been a lot of interest
since.
The URL needs to be like a Maven connection:
scm:svn:svn://...
IF you have any issues and are willing to help, join
wagon-dev@maven.apache.org ([EMAIL
49 matches
Mail list logo
