Problems building maven-plugin in Eclipse

[Christoph Kutzinski]

Hi,

I had several problems with building Jenkins/maven-plugin in the past,
but the errors I'm getting now are especial nasty:
Eclipse e.g. complains that it cannot find hudson.model.Queue.Item (in
MavenModuleSet) and several other compile errors.
I checked the the Jenkins core jar is intact (building with mvn works)
and no amount of refreshing in Eclipse and the usual other tricks to get
it working again got me anywhere.

Did anyone have similar problems and maybe a solution?
Eclipse Kepler 4.3.1, M2e 1.4.0

-
Kutzi

[Baptiste Mathus]

Hi, First thing I would ask is: does it build on the CLI outside Eclipse? That'll be a first step to see if this is likely a Maven issue or more an Eclipse or even a jenkins code one.

My 2 cents

2013/11/15 Christoph Kutzinski <ku...@gmx.de>

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Marcelo]

Kutzi, in the category "Maven Problems" of the view "Markers" inside eclipse, you see any error?

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

[Christoph Kutzinski]

Yes, it works on the CLI

Am 15.11.2013 21:55, schrieb Baptiste Mathus:

Hi, First thing I would ask is: does it build on the CLI outside Eclipse? That'll be a first step to see if this is likely a Maven issue or more an Eclipse or even a jenkins code one.

My 2 cents

2013/11/15 Christoph Kutzinski <ku...@gmx.de>

Hi,

I had several problems with building Jenkins/maven-plugin in the past, but the errors I'm getting now are especial nasty:
Eclipse e.g. complains that it cannot find hudson.model.Queue.Item (in MavenModuleSet) and several other compile errors.
I checked the the Jenkins core jar is intact (building with mvn works) and no amount of refreshing in Eclipse and the usual other tricks to get it working again got me anywhere.

Did anyone have similar problems and maybe a solution?
Eclipse Kepler 4.3.1, M2e 1.4.0

-
Kutzi

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

[Christoph Kutzinski]

No Maven Problems, only Java problems:


Description    Resource    Path    Location    Type
Cannot make a static reference to the non-static method save() from the type AbstractProject<MavenModuleSet,MavenModuleSetBuild>    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1320    Java Problem
AbstractProjectDescriptor cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1259    Java Problem
Cannot make a static reference to the non-static method save() from the type AbstractProject<MavenModuleSet,MavenModuleSetBuild>    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1278    Java Problem
The method alignToBaseDirectory(File) of type new ExpressionEvaluator(){} must override a superclass method    MojoInfoBuilder.java    /maven-plugin/src/test/java/hudson/maven    line 81    Java Problem
Cannot make a static reference to the non-static method save() from the type AbstractProject<MavenModuleSet,MavenModuleSetBuild>    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1290    Java Problem
Bound mismatch: The generic method getDescriptorByType(Class<T>) of type Jenkins is not applicable for the arguments (Class<MavenModuleSet.DescriptorImpl>). The inferred type MavenModuleSet.DescriptorImpl is not a valid substitute for the bounded parameter <T extends Descriptor>    MavenOptsTest.java    /maven-plugin/src/test/java/hudson/maven    line 20    Java Problem
The method annotate(ConsoleNote) of type SurefireArchiverUnitTest.NullBuildListener must override a superclass method    SurefireArchiverUnitTest.java    /maven-plugin/src/test/java/hudson/maven/reporters    line 303    Java Problem
The method apply(String) of type new Function<String,File>(){} must override a superclass method    TestMojo.java    /maven-plugin/src/main/java/hudson/maven/reporters    line 165    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1104    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1108    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1097    Java Problem
Cannot cast from Descriptor to MavenModuleSet.DescriptorImpl    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1219    Java Problem
The method apply(File) of type new Predicate<File>(){} must override a superclass method    SurefireArchiver.java    /maven-plugin/src/main/java/hudson/maven/reporters    line 140    Java Problem
AbstractProjectDescriptor cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1230    Java Problem
The method apply(File) of type new Predicate<File>(){} must override a superclass method    SurefireArchiver.java    /maven-plugin/src/main/java/hudson/maven/reporters    line 268    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1109    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1109    Java Problem
The method apply(String) of type new Function<String,File>(){} must override a superclass method    SurefireArchiver.java    /maven-plugin/src/main/java/hudson/maven/reporters    line 282    Java Problem
Queue.Item cannot be resolved to a type    MavenModuleSet.java    /maven-plugin/src/main/java/hudson/maven    line 1110    Java Problem

...

Am 15.11.2013 22:15, schrieb Marcelo:

Kutzi, in the category "Maven Problems" of the view "Markers" inside eclipse, you see any error?

On Fri, Nov 15, 2013 at 5:55 PM, Baptiste Mathus <bma...@batmat.net> wrote:

Hi, First thing I would ask is: does it build on the CLI outside Eclipse? That'll be a first step to see if this is likely a Maven issue or more an Eclipse or even a jenkins code one.

My 2 cents

2013/11/15 Christoph Kutzinski <ku...@gmx.de>

Hi,

I had several problems with building Jenkins/maven-plugin in the past, but the errors I'm getting now are especial nasty:
Eclipse e.g. complains that it cannot find hudson.model.Queue.Item (in MavenModuleSet) and several other compile errors.
I checked the the Jenkins core jar is intact (building with mvn works) and no amount of refreshing in Eclipse and the usual other tricks to get it working again got me anywhere.

Did anyone have similar problems and maybe a solution?
Eclipse Kepler 4.3.1, M2e 1.4.0

-
Kutzi

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Vincent Latombe]

Hi,

I have exactly the same issue. Compiling in command line works, however in Eclipse, some inner classes cannot be resolved (despite being able to browse them in the classpath of the eclipse project).

Eclipse is unable to resolve these 3 classes :

- hudson.model.AbstractProject.AbstractProjectDescriptor
- hudson.model.Queue.Task
- hudson.model.Queue.Item

I'm trying to isolate the problem, so far I found it depends on the core version, and the problem appeared between 1.517 and 1.524.

Vincent

Vincent

2013/11/16 Christoph Kutzinski <ku...@gmx.de>

[Vincent Latombe]

Problem appeared in core 1.520. Looking at the changes that happened for this release,

I see an update of com.infradna.tool:bridge-method-annotation from 1.4 to 1.8

Maybe this is generating some bytecode that is not understood correctly by the JDT, so it fails to index the corresponding class.

Vincent

2013/11/16 Vincent Latombe <vincent...@gmail.com>

[Christoph Kutzinski]

Makes sense.
Maybe we're missing this bug fix which comes with
bridge-method-annotation 1.9

https://github.com/infradna/bridge-method-injector/commit/ea528faf1f92724cc5db036116bae80a234de20d

Am 16.11.2013 10:09, schrieb Vincent Latombe:
> Problem appeared in core 1.520. Looking at the changes that happened for
> this release,
> I see an update of com.infradna.tool:bridge-method-annotation from 1.4
> to 1.8
>
> Maybe this is generating some bytecode that is not understood correctly
> by the JDT, so it fails to index the corresponding class.
>
> Vincent
>
>
> 2013/11/16 Vincent Latombe <vincent...@gmail.com

> <mailto:vincent...@gmail.com>>

>
> Hi,
>
> I have exactly the same issue. Compiling in command line works,
> however in Eclipse, some inner classes cannot be resolved (despite
> being able to browse them in the classpath of the eclipse project).
>
> Eclipse is unable to resolve these 3 classes :
> - hudson.model.AbstractProject.AbstractProjectDescriptor
> - hudson.model.Queue.Task
> - hudson.model.Queue.Item
>
> I'm trying to isolate the problem, so far I found it depends on the
> core version, and the problem appeared between 1.517 and 1.524.
>
> Vincent
>
> Vincent
>
>

> 2013/11/16 Christoph Kutzinski <ku...@gmx.de <mailto:ku...@gmx.de>>

>> <mailto:ku...@gmx.de>>

>>
>> Hi,
>>
>> I had several problems with building
>> Jenkins/maven-plugin in the past, but the errors I'm
>> getting now are especial nasty:
>> Eclipse e.g. complains that it cannot find
>> hudson.model.Queue.Item (in MavenModuleSet) and
>> several other compile errors.
>> I checked the the Jenkins core jar is intact (building
>> with mvn works) and no amount of refreshing in Eclipse
>> and the usual other tricks to get it working again got
>> me anywhere.
>>
>> Did anyone have similar problems and maybe a solution?
>> Eclipse Kepler 4.3.1, M2e 1.4.0
>>
>> -
>> Kutzi
>>
>> --
>> You received this message because you are subscribed
>> to the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving
>> emails from it, send an email to
>> jenkinsci-de...@googlegroups.com

>> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

>> For more options, visit
>> https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> --
>> You received this message because you are subscribed to
>> the Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails
>> from it, send an email to
>> jenkinsci-de...@googlegroups.com

>> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

>> For more options, visit
>> https://groups.google.com/groups/opt_out.
>>
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from
>> it, send an email to
>> jenkinsci-de...@googlegroups.com

>> <mailto:jenkinsci-de...@googlegroups.com>.

>> For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

[Vincent Latombe]

I could confirm it is definitely the bridge method injector which is causing the issue.

In Queue.Item, there is the following getter annotated

@WithBridgeMethods(Future.class)
public QueueTaskFuture<Executable> getFuture() { return future; }

Removing the annotation then recompiling core fixes the issue for this class.

Also, depending on a jenkins-core that is in the workspace workarounds the issue (because then the bridge method injector isn't called by JDT)

Given the fix you mentioned in 1.9, I doubt it will change anything.

Vincent

2013/11/16 Christoph Kutzinski <ku...@gmx.de>

Makes sense.

Maybe we're missing this bug fix which comes with bridge-method-annotation 1.9

https://github.com/infradna/bridge-method-injector/commit/ea528faf1f92724cc5db036116bae80a234de20d

Am 16.11.2013 10:09, schrieb Vincent Latombe:

Problem appeared in core 1.520. Looking at the changes that happened for
this release,
I see an update of com.infradna.tool:bridge-method-annotation from 1.4
to 1.8

Maybe this is generating some bytecode that is not understood correctly
by the JDT, so it fails to index the corresponding class.

Vincent


2013/11/16 Vincent Latombe <vincent...@gmail.com

<mailto:vincent.latombe@gmail.com>>

                jenkinsci-dev+unsubscribe@googlegroups.com

                <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

                For more options, visit
                https://groups.google.com/groups/opt_out.




            --
            Baptiste <Batmat> MATHUS - http://batmat.net
            Sauvez un arbre,
            Mangez un castor !
            --
            You received this message because you are subscribed to
            the Google Groups "Jenkins Developers" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to

            jenkinsci-dev+unsubscribe@googlegroups.com

            <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

            For more options, visit
            https://groups.google.com/groups/opt_out.


        --
        You received this message because you are subscribed to the
        Google Groups "Jenkins Developers" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to

        jenkinsci-dev+unsubscribe@googlegroups.com

        <mailto:jenkinsci-dev+unsub...@googlegroups.com>.

        For more options, visit https://groups.google.com/groups/opt_out.

        --
        You received this message because you are subscribed to the
        Google Groups "Jenkins Developers" group.
        To unsubscribe from this group and stop receiving emails from

        it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com

        <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

        For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send

an email to jenkinsci-dev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

[Ace Han]

Hi, All

The same issue in eclipse is driving me nuts while I was trying to upgrade my plugin code dependencies to latest LTS.

Removing the annotation @WithBridgeMethods just works like a charm, thanks

However, I would like to share a little more about how to recompile the jenkins-core-xxx.jar.

1. download the source.zip from https://github.com/jenkinsci/jenkins(I mean the root of the project, not just core folder since Jenkins CLI module is required for Jenkins core from the this recompilation build ), pick up any commit, branch as you like
2. unzip this source.zip to folder jenkins-xxx, (wherever as you like)
3. replace @WithBridgeMethods\(.*\) with // patching for debug  to jenkins-xxx/core/src/**/*.java
4. run mvn package -Dmaven.test.skip=true (you should get your maven working)
5. we should only care about the jenkins-core-xxx.jar is finally recompiled though some error may occur on other modules
6. done

Help this could help.

Best Regard,

Ace Han

On Saturday, November 16, 2013 8:48:27 PM UTC+8, Vincent Latombe wrote:

I could confirm it is definitely the bridge method injector which is causing the issue.

In Queue.Item, there is the following getter annotated

@WithBridgeMethods(Future.class)
public QueueTaskFuture<Executable> getFuture() { return future; }

Removing the annotation then recompiling core fixes the issue for this class.

Also, depending on a jenkins-core that is in the workspace workarounds the issue (because then the bridge method injector isn't called by JDT)

Given the fix you mentioned in 1.9, I doubt it will change anything.

Vincent

2013/11/16 Christoph Kutzinski <ku...@gmx.de>

Makes sense.
Maybe we're missing this bug fix which comes with bridge-method-annotation 1.9

https://github.com/infradna/bridge-method-injector/commit/ea528faf1f92724cc5db036116bae80a234de20d

Am 16.11.2013 10:09, schrieb Vincent Latombe:

Problem appeared in core 1.520. Looking at the changes that happened for
this release,
I see an update of com.infradna.tool:bridge-method-annotation from 1.4
to 1.8

Maybe this is generating some bytecode that is not understood correctly
by the JDT, so it fails to index the corresponding class.

Vincent


2013/11/16 Vincent Latombe <vincent...@gmail.com

<mailto:vincent...@gmail.com>>

                jenkinsci-de...@googlegroups.com

                <mailto:jenkinsci-dev%2Bunsubscr...@googlegroups.com>.

                For more options, visit
                https://groups.google.com/groups/opt_out.




            --
            Baptiste <Batmat> MATHUS - http://batmat.net
            Sauvez un arbre,
            Mangez un castor !
            --
            You received this message because you are subscribed to
            the Google Groups "Jenkins Developers" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to

            jenkinsci-de...@googlegroups.com

            <mailto:jenkinsci-dev%2Bunsubscr...@googlegroups.com>.

            For more options, visit
            https://groups.google.com/groups/opt_out.


        --
        You received this message because you are subscribed to the
        Google Groups "Jenkins Developers" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to

        jenkinsci-de...@googlegroups.com

        <mailto:jenkinsci-dev+unsubscri...@googlegroups.com>.

        For more options, visit https://groups.google.com/groups/opt_out.

        --
        You received this message because you are subscribed to the
        Google Groups "Jenkins Developers" group.
        To unsubscribe from this group and stop receiving emails from

        it, send an email to jenkinsci-de...@googlegroups.com

        <mailto:jenkinsci-dev%2Bunsubscr...@googlegroups.com>.

        For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send

an email to jenkinsci-de...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

[Jeff King]

Hi all,

Not sure if anyone else is experiencing this, but I've been seeing a
problem with running Jenkins as a Windows service starting with 1.559.
Basically, if you trigger something that causes Jenkins to restart
(install/update plugins, use the /restart URI, etc.), Jenkins stops but
does not start again.

Since Windows doesn't have an atomic service restart, the Jenkins
Windows service wrapper (jenkins.exe) handles the "restart" option by
doing a "stop", waits, and then "starts". The wrapper's "stop" handling
finds the Process ID of Jenkins, recursively halts all the children
processes of that PID, then stops the PID itself.

However, since WindowsServiceLifecycle.java is what called "jenkins.exe
restart", this instance of the wrapper is a child of the parent Jenkins
PID, so the wrapper ends up stopping itself!

It seemed like the simplest fix was to modify the service wrapper such
that, as it recurses through all the child processes of the Jenkins
process, it compares its own execution path against that of the child
PID. If they match, the wrapper doesn't stop that particular PID.

I've tested this change on my company's three build machines and it
resolves the issue.* A WinSW pull request with the above fix has been
submitted, and the issue was captured as JENKINS-22685. Hopefully this
is the right list and tracker for the problem; I didn't see ones
specifically for WinSW.

*Testing was tricky at first until I figured out that
WindowsServiceLifecycle checks if the current jenkins.exe is different
than the one packaged as a resource in jenkins-core-xxx.jar, and, if so,
replaces the current with the packaged when Jenkins is restarted.
Updating the JAR by replacing the \windows-service\jenkins.exe with my
modified copy took care of it.

Thanks,

Jeff

[Jeff King]

On 05/10/2014 02:12 PM, Jeff King wrote:
> Hi all,
>
> Not sure if anyone else is experiencing this, but I've been seeing a
> problem with running Jenkins as a Windows service starting with 1.559.
> Basically, if you trigger something that causes Jenkins to restart
> (install/update plugins, use the /restart URI, etc.), Jenkins stops but
> does not start again.

Thanks to Kohsuke for steering me back to winsw's "restart!" command, so
I realized my mistake in the initial test. All that's needed now is for
WindowsServiceLifecycle.java to use "restart!" instead of "restart".
I've submitted that as a pull request:

https://github.com/jenkinsci/jenkins/pull/1238

[Jesse Glick]

On Sat, Nov 16, 2013 at 4:46 AM, Christoph Kutzinski <ku...@gmx.de> wrote:
> Maybe we're missing this bug fix which comes with bridge-method-annotation 1.9

Well Jenkins 1.536+ uses 1.9.

[Karthik V S]

Hi,

I am getting the same error. Can anyone provide the solution for this? I am using Eclipse Kepler.

[Ace Han]

Hi, Karthik

plz refer to my post(Ace Han) for a short term solution

1. download the source.zip from https://github.com/jenkinsci/jenkins(I mean the root of the project, not just core folder since Jenkins CLI module is required for Jenkins core from the this recompilation build ), pick up any commit, branch as you like
2. unzip this source.zip to folder jenkins-xxx, (wherever as you like)
3. replace @WithBridgeMethods\(.*\) with // patching for debug  to jenkins-xxx/core/src/**/*.java
4. run mvn package -Dmaven.test.skip=true (you should get your maven working)
5. we should only care about the jenkins-core-xxx.jar is finally recompiled though some error may occur on other modules
6. done

[Tomas Kolda]

I used 1.554.3 that uses 1.9 and have same issue.

import hudson.model.Node.Mode; -> The import hudson.model.Node.Mode cannot be resolved

or

public static final Mode DEFAULT_MODE = Mode.EXCLUSIVE; -> Mode cannot be resolved to a type

Is there Jenkins issue already for this? I do not want to build my core as a workaround. What the people are using for development? I only found issue in JDT:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=424952

[Jakub Bocheński]

3 years later the issue is still there.

Is there any better workaround than changing and recompiling core locally?