Re: [forge-dev] Unit Test failures

Interesting... I'm willing to bet this is a maven bug, but then again, I can check our usage of the APIs. Thanks for looking in to this. It's surprising that the tests are being run in offline mode. Did you set that in your settings.xml? I don't think other devs are having this issue, so I'm wondering if there's something specific about your environment. ~Lincoln On Mon, May 16, 2011 at 12:43 AM, Tim Pedone <macdude357(a)gmail.com&gt; wrote: > > I did a bit more digging around this and found out a couple of things. >  It seems that the tests are run in offline mode so the maven runtime > in the shell won't fetch any remote dependencies.  Another thing I > found out was that if the maven code cannot load the > maven-metadata.xml file, then the dependency resolution fails.  This > explains why the tests failed even when I had the prettyfaces-jsf2 > jars in my local repo; I didn't have a maven-metadata.xml file.  And > since the tests are running in offline mode, it wouldn't fetch the > metadata from the remote repo so it failed. > > On Thu, May 12, 2011 at 11:56 AM, Tim Pedone <macdude357(a)gmail.com&gt; wrote: > > Yes, my machine is connected to the internet.  It downloads all the > > plugins, compile time dependencies, etc. > > > > On Thu, May 12, 2011 at 11:12 AM, Lincoln Baxter, III > > <lincolnbaxter(a)gmail.com&gt; wrote: > >> Do you have an internet connection when you are running the tests? > >> > >> On Thu, May 12, 2011 at 1:21 AM, Tim Pedone <macdude357(a)gmail.com&gt; > >> wrote: > >>> > >>> My first thought would be to test out of a separate local repo but > >>> that might really slow down the tests. > >>> > >>> BTW, I still can't get the tests to pass.  The artifacts in question > >>> (com.ocpsoft:prettyfaces-jsf2, etc.) we not in my local repo at all. > >>> I tried adding them to the pom so they'd get downloaded and I also > >>> tried wiping out my entire local repo but neither seemed to work.  I > >>> guess I'll just ignore the tests for now.  I was looking at enhancing > >>> the maven support so I really would like to get those tests working at > >>> some point though. > >>> > >>> On Wed, May 11, 2011 at 1:32 PM, Lincoln Baxter, III > >>> <lincolnbaxter(a)gmail.com&gt; wrote: > >>> > Otherwise, I'd just skip this test for now. It's known to cause > >>> > issues > >>> > sometimes. > >>> > > >>> > On Wed, May 11, 2011 at 4:31 PM, Lincoln Baxter, III > >>> > <lincolnbaxter(a)gmail.com&gt; wrote: > >>> >> > >>> >> 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. > >>> >> > >>> >> ~Lincoln > >>> >> > >>> >> On Wed, May 11, 2011 at 4:18 PM, Tim Pedone <macdude357(a)gmail.com&gt; > >>> >> wrote: > >>> >>> > >>> >>> First off, I think Forge is totally cool.  So much so, that I'd > >>> >>> like > >>> >>> to contribute in some way.  So I've forked the repo in GitHub and > >>> >>> am > >>> >>> trying to build it but am getting a few unit test failures in > >>> >>> RepositoryLookupTest.testResolveVersions() and a few others. In > >>> >>> stepping through the code, it seems like the Aether code isn't > >>> >>> working > >>> >>> properly. I assume this must be something unique to my setup: > >>> >>>  MacOS > >>> >>> 10.6 + JDK 1.6.0_24, Maven 3.0.3, JBoss Dev Studio 4.0.  The tests > >>> >>> fail on both the command line and in Dev Studio. > >>> >>> > >>> >>> Any ideas? > >>> >>> > >>> >>> Thanks, > >>> >>> > >>> >>> Tim > >>> >>> _______________________________________________ > >>> >>> forge-dev mailing list > >>> >>> forge-dev(a)lists.jboss.org > >>> >>> https://lists.jboss.org/mailman/listinfo/forge-dev > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Lincoln Baxter, III > >>> >> http://ocpsoft.com > >>> >> http://scrumshark.com > >>> >> "Keep it Simple" > >>> > > >>> > > >>> > > >>> > -- > >>> > Lincoln Baxter, III > >>> > http://ocpsoft.com > >>> > http://scrumshark.com > >>> > "Keep it Simple" > >>> > > >>> > _______________________________________________ > >>> > forge-dev mailing list > >>> > forge-dev(a)lists.jboss.org > >>> > https://lists.jboss.org/mailman/listinfo/forge-dev > >>> > > >>> > > >>> > >>> _______________________________________________ > >>> forge-dev mailing list > >>> forge-dev(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/forge-dev > >> > >> > >> > >> -- > >> Lincoln Baxter, III > >> http://ocpsoft.com > >> http://scrumshark.com > >> "Keep it Simple" > >> > >> _______________________________________________ > >> forge-dev mailing list > >> forge-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/forge-dev > >> > >> > > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev