Quantcast

Plugin missing requiredCore

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Plugin missing requiredCore

Marco Ambu
Hi,
is the page http://pastebin.com/SpM4yrir updated?
 
If yes can anybody explain what should be done to fix the problem reported?
Thanks,
--
Marco Ambu
E-mail: [hidden email]
LinkedIn profile: <http://www.linkedin.com/in/marcoambu>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plugin missing requiredCore

Ulli Hafner
On 03/28/2011 10:26 AM, Marco Ambu wrote:
Hi,
is the page http://pastebin.com/SpM4yrir updated?
 
If yes can anybody explain what should be done to fix the problem reported?
Thanks,
--
Marco Ambu
E-mail: [hidden email]
LinkedIn profile: <http://www.linkedin.com/in/marcoambu>

You need to release your plug-in with the latest version of the maven-hpi-plugin. This will automatically fix your plug-in meta data.

Ulli
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plugin missing requiredCore

Alan Harder-2
In reply to this post by Marco Ambu
Yesterday I patched the update-center builder to set a requiredCore of 1.398 if the value is missing, so once the "push update-center.json to mirrors" job is fixed up then a file will go out that will resolve this issue for these plugin releases (though it'll say you need 1.398 even if the plugin was built for 1.393 thru 1.397).

To see the plugins still missing requiredCore in the .hpi file, look at:
http://ci.jenkins-ci.org/view/Infrastructure/job/infra_update_center/lastSuccessfulBuild/consoleText
and search for "** requiredCore missing"
This log writes this warning for each plugin where it put in the 1.398 default.

Running a new release using parent version 1.399 or newer will properly write the requiredCore in your release's hpi file.

    - Alan


On 3/28/11 1:26 AM, Marco Ambu wrote:
Hi,
is the page http://pastebin.com/SpM4yrir updated?
 
If yes can anybody explain what should be done to fix the problem reported?
Thanks,
--
Marco Ambu
E-mail: [hidden email]
LinkedIn profile: <http://www.linkedin.com/in/marcoambu>
Previous Thread Next Thread
Loading...