[forge-dev] Unit Test failures

[Tim Pedone]

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 at gmail.com> 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 at gmail.com> 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 at gmail.com> 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 at gmail.com> 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 at gmail.com>
>> >> 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 at 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 at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>> >
>> >
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>