Finally I understand what was the problem.
First, I have to put only one time "@extension"; Second when i do a package
firstly i must do a clean.

2012/7/12 Simone <[email protected]>

> I thought that it was the problem but it doesn't.
> A day it works (whit that method), the day after it appears twice...
>
> The source code is the same, so the problem is in Jenkins.
> Maybe i try a different version of plugin that wasn't fixed and it
> corrupted the configuration?
> I unistall the plugin deleting the .hpi file and the directory in
> /.jenkins/plugin
>
>
> 2012/7/11 Simone <[email protected]>
>
>> I've solved the problem!!
>> I put 2 times "@Extension" in the main class:
>>
>> - @Extension
>>    public static final DescriptorImpl DESCRIPTOR = new DescriptorImpl();
>>
>> - @Extension
>>    public static final class DescriptorImpl ....
>>
>> So was enough remove one.
>> Thanks anyway for the interest.
>>
>> 2012/7/9 simomex90 <[email protected]>
>>
>>> Sorry but the source code is not available.
>>> I can give you some info: when i save a job configuration, in the xml
>>> file, where the form's data are saved, I see a mix of the 2 configuration
>>> form; for example, in the first an optionalblock is false, in the second
>>> the same is true, for the plugin that optionalblock is true even if the
>>> second form is disabled (not selected).
>>> So, I think that is an issue in the .jelly files. I add some external
>>> dependencies but i don't think that are not responsible because they have
>>> nothing to do whit the graphic part.
>>>
>>> 2012/7/7 Gavin Davies <[email protected]>
>>>
>>>> Hi, is your source code available somewhere so I can look at the
>>>> problem?
>>>>
>>>>
>>>> On 7 July 2012 08:54, SimoneMex <[email protected]> wrote:
>>>>
>>>>> Hi guys,
>>>>> I just started to write plugins for Jenkins but now I have this
>>>>> problem: after I installed the .hpi file, in a Job configuration and in 
>>>>> the
>>>>> global configuration the plugin's form appears twice.
>>>>> How is it possible??
>>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to