Hi Tim! Yes, you've encountered one of my more annoying issues with testing Maven. These tests seem to be pretty "tempermental" at best, so my first suggestion would be to try deleting the parts of your maven repo that the test uses for its work (delete as high up as you are comfortable,) then try again. I know this is a bit of a ... lame... suggestion, but there's not really a good way to test this stuff other than actually hitting the internet. If you have any ideas on how to improve this, I would be in your debt.<br>
<br>~Lincoln<br><br><div class="gmail_quote">On Wed, May 11, 2011 at 4:18 PM, Tim Pedone <span dir="ltr"><<a href="mailto:macdude357@gmail.com">macdude357@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
First off, I think Forge is totally cool. So much so, that I'd like<br>
to contribute in some way. So I've forked the repo in GitHub and am<br>
trying to build it but am getting a few unit test failures in<br>
RepositoryLookupTest.testResolveVersions() and a few others. In<br>
stepping through the code, it seems like the Aether code isn't working<br>
properly. I assume this must be something unique to my setup: MacOS<br>
10.6 + JDK 1.6.0_24, Maven 3.0.3, JBoss Dev Studio 4.0. The tests<br>
fail on both the command line and in Dev Studio.<br>
<br>
Any ideas?<br>
<br>
Thanks,<br>
<br>
Tim<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>