I think Roberts' idea about "svu upgrade"ing is good
just need to revert locally and test, or we'll get the same problem in some
time, when svn 1.9 is out
Regards,
Hervé
Le mardi 6 mai 2014 15:00:58 Dan Tran a écrit :
> Thanks Hervé, it works on my local windows build with svn client 1.8.5
>
Thanks Hervé, it works on my local windows build with svn client 1.8.5
-D
On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY wrote:
> I updated content to svn 1.8: not really a long term solution, but at least
> give us time to find a better solution
>
> Regards,
>
> Hervé
>
> Le lundi 5 mai 2014
Just tried it and still failing ( but not known why yet)
[INFO] --- maven-invoker-plugin:1.8:run (integration-test) @
maven-scm-plugin ---
[INFO] Building: scm-741-validate-scm-url-matches-working-copy\pom.xml
[INFO] run script prepare.groovy
[INFO] ..FAILED (6.6 s)
[INFO] The build exited with
I updated content to svn 1.8: not really a long term solution, but at least
give us time to find a better solution
Regards,
Hervé
Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit :
> perhaps, we need to disable this specific test for now?
>
> -D
>
> On Mon, May 5, 2014 at 9:18 PM, Dan Tran wrot
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Olivier Lamy, Hervé Boutemy
+1 (non binding): Tony Chemit, Uwe Pachler, fr2fy972rv
I will promote the artifacts to the central repo.
-
To unsubscr
here is my +1
Regards,
Hervé
Le samedi 3 mai 2014 21:50:56 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 23 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=H
> tml&version=18959
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/s
Would it help if this was added to the prepare.groovy?
try
{
"""svn upgrade""".execute()
}
catch( Exception e )
{
// noop, no need to upgrade
}
return true
I seem to have a matching client version, so the IT works on my system.
Could someone verify the code above?
thanks,
Robert
Op Tue,
Yes, try what Igor suggested. I only saw the lookup exception, which in general
is often caused by missing metadata.
On May 6, 2014, at 11:03 AM, Jochen Wiedmann wrote:
> Beg your pardon, Jason, but couldb't the reason be that simply need one of
> the aether jar files (Whatever provides Reposi
Beg your pardon, Jason, but couldb't the reason be that simply need one of
the aether jar files (Whatever provides RepositorySystem with hint "basic"?
On Tue, May 6, 2014 at 3:51 PM, Jason van Zyl wrote:
> Hard to tell without the code, but a lot of times the error is the
> component metadata
You are probably missing maven-compat from your plugin dependencies. I
usually add this with scope=test unless my code explicitly depends on
classes from that artifact.
--
Regards,
Igor
On 2014-05-06, 9:33, Jochen Wiedmann wrote:
Hi,
I am trying to implement a test case for a plugin, utilizing
Hard to tell without the code, but a lot of times the error is the component
metadata is not present or it's wrong. If you hand wrote it you might have a
typo, or you might not have the metadata generators configured.
On May 6, 2014, at 6:33 AM, Jochen Wiedmann wrote:
> Hi,
>
> I am trying to
Hi,
I am trying to implement a test case for a plugin, utilizing the Plugin
testing harness. I am getting the exception below.
Any ideas what I might be doing wrong?
Thanks,
Jochen
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
java.util.NoSuchElementException
12 matches
Mail list logo
