Hi,

I am experiencing the same problem even though I have cloned the source 
today doing a

 git clone http://github.com/jenkinsci/jenkins.git

where I would expect to get the patched code. Any suggestion ?

Regards 
Esben

On Tuesday, January 10, 2012 7:32:22 PM UTC+1, domi wrote:
>
> Hi Jim,
> I had exactly the same issue…
> should be fixed now: 
> https://github.com/jenkinsci/jenkins/commit/cabb5f010a9c450c4604f693644b685791f0fac5
> /Domi
>
> On 09.01.2012, at 20:45, Jim L. wrote:
>
> > A couple of interesting things here: Using Eclipse 3.6 (Helios) on Mac
> > OSX Lion (JVM 1.6):
> > 
> > I followed the directions for building core on the wiki page
> > https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins, and
> > posted this comment below on that wiki page as well.  I thought I
> > would try this group list and see if anyone knows what this problem
> > is, or if it is a problem at all.  Thanks.
> > 
> > ---
> > I generated the Eclipse projects and imported them, and received build
> > errors stating Access exceptions to the JVM libraries.  I solved that
> > problem by deleting the specified JVM (JSE 1.5) in each project build
> > path and then re-specified the local JVM.
> > Now I'm getting an interesting error in Eclipse: The method
> > configRoundtrip(MavenModuleSet) is ambiguous for the type
> > MavenModuleSetTest MavenModuleSetTest.java
> > 
> > So in project jenkins-test-harness, code module
> > hudson.maven.MavenModuleSetTest.java:
> > 
> > public class MavenModuleSetTest extends HudsonTestCase {
> > 
> >    public void testConfigRoundtripLocalRepository() throws Exception {
> > 
> >        MavenModuleSet p = createMavenProject();
> > 
> >        configRoundtrip(p);  <-- The Error
> > 
> >        assertNull(p.getExplicitLocalRepository());
> > 
> >        // make sure it roundtrips
> > 
> >        PerJobLocalRepositoryLocator before = new
> > PerJobLocalRepositoryLocator();
> > 
> >        p.setLocalRepository(before);
> > 
> >        configRoundtrip(p); <-- The Error
> > 
> >        assertEqualDataBoundBeans(p.getLocalRepository(),before);
> > 
> >        assertTrue(before!=p.getLocalRepository());
> > 
> >    }
> > 
> > }
> > 
> > 
> > 
> > configRoundTrip(...) is found in 
> org.jvnet.hudson.test.HudsonTestCase.java:
> > 
> > [snip .. org.jvnet.hudson.test.HudsonTestCase.java]
> > 
> > 
> > /**
> > 
> >     * Loads a configuration page and submits it without any 
> modifications, to
> > 
> >     * perform a round-trip configuration test.
> > 
> >     * <p>
> > 
> >     * See 
> http://wiki.jenkins-ci.org/display/JENKINS/Unit+Test#UnitTest-Configurationroundtriptesting
> > 
> >     */
> > 
> >    protected <P extends Job> P configRoundtrip(P job) throws Exception {
> > 
> >       
>  submit(createWebClient().getPage(job,"configure").getFormByName("config"));
> > 
> >        return job;
> > 
> >    }
> > 
> >    protected <P extends Item> P configRoundtrip(P job) throws Exception {
> > 
> >        submit(createWebClient().getPage(job,
> > "configure").getFormByName("config"));
> > 
> >        return job;
> > 
> >    }
> > 
> > 
> > [snip]
> > 
> > 
> > 
> > 
> > The references are ambiguous because Interface Job extends Item as
> > well, so the compiler cannot choose which method signature to use.
> > If I comment out the first overloaded method protected <P extends Job>
> > P configRoundtrip(P job)... This allows the Eclipse build to complete
> > successfully, although I know this is not the correct solution.
> > 
> > So ... what is the correct solution?  Is it an Eclipse/Project config 
> issue?
> > 
> > I know I can just build everything using Maven command line, but I'd
> > like to find a solution to this problem if I can.  The code I'm using
> > is a fork in my own account.
> > 
> > Thanks - Jim L.
> > 
> > Description Resource Path Location Type
> > The method configRoundtrip(MavenModuleSet) is ambiguous for the type
> > MavenModuleSetTest MavenModuleSetTest.java
> > /jenkins-test-harness/src/test/java/hudson/maven line 12 Java Problem
>
>

Reply via email to