I had to expired the cache on my nexus' apache-snapshot repo.
Now by build is ok. nexus may have picked up a bad deployment, and it
would take a day to get the next one.
-Dan
On Fri, Mar 12, 2010 at 1:46 PM, Benjamin Bentmann
wrote:
> Dan Tran wrote:
>
>> java.lang.NoSuchMethodError:
>> org.ap
Dan Tran wrote:
java.lang.NoSuchMethodError:
org.apache.maven.scm.provider.ScmProviderRepository.setPushChanges(Z)V
at
org.apache.maven.scm.plugin.AbstractScmMojo.getScmRepository(AbstractScmMojo.java:286)
Sounds like you don't have the latest snapshot version of maven-scm.
Benjamin
I am using subversion
where I call scm:checkout in my pom
-Dan
On Fri, Mar 12, 2010 at 1:35 PM, Olivier Lamy wrote:
> Hi,
> How can I reproduce this ?
>
> Which scm are you using ?
>
> 2010/3/12 Dan Tran :
>> Hello,
>>
>> My experimental build just pull down latest maven scm and see this
>> err
Hi,
How can I reproduce this ?
Which scm are you using ?
2010/3/12 Dan Tran :
> Hello,
>
> My experimental build just pull down latest maven scm and see this
> error. Did we break this or it is just a bad jar??
>
> i am using maven 2.2.1 and java 6
>
> [INFO] [scm:checkout {execution: checkout-w
Hello,
My experimental build just pull down latest maven scm and see this
error. Did we break this or it is just a bad jar??
i am using maven 2.2.1 and java 6
[INFO] [scm:checkout {execution: checkout-webservices}]
[FATAL ERROR] org.apache.maven.scm.plugin.CheckoutMojo#execute()
caused a linkag
+1
Downloaded the source tarball, checked signature, and built it using Maven
2.2.1, then ran the integration tests:
Tests run: 561, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 991.96 sec
Thanks!
BTW, it's interesting that the source tarball is larger than the binary one due
to the emb
+1
--
Regards,
Igor
Benjamin Bentmann wrote:
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16087
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
Stagin
+1
Tested on corporate and oss projects, working fine.
/Paul
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
While implementing a Maven environment for a customer where the signatures
for used Apache artifacts are verified, I've stumbled upon the fact that the
artifacts of wagon 1.0-beta-2 aren't signed. As all other versions (1.0
alphas and betas) have signatures, I'm confused. Does anyone know 1.0-beta-
+1
Vincent
2010/3/9 Benjamin Bentmann :
> Hi,
>
> We solved 22 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16087
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1
>
> Stag
+1
On 11 March 2010 18:46, Hervé BOUTEMY wrote:
> +1
>
> Hervé
>
> Le mardi 09 mars 2010, Benjamin Bentmann a écrit :
> > Hi,
> >
> > We solved 22 issues:
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16
> > 087
> >
> > There are still a couple of issues left in
Dear Developers,
currently i am working with Maven and first of all: Thanks!
It's a very nice program and makes all easier.
Right now i am configuring the site-plugin but have got a problem and i hope
you are able to help me.
In the category dependencies is the dependencie tree.
Is it possible to
12 matches
Mail list logo
