Thanks Jesse, If your guess is right, how to avoid it. Because I assume we are packaging proper hpi file and Jenkins takes care of loading the classes appropriately. Now after skipping tests while packaging it gives exception for classes.jar being not found.
Noticed that two things happen: 1) If Jenkins server is started with war, classes.jar is present in the lib folder of the plugin. 2) If Jenkins is started as windows services (after normal windows installation) the classes are exploded to the plugin directory. Quite not sure in which scenarios it might be looking for classes.jar or exploded class files. Thanks Mohan On Fri, Sep 13, 2013 at 11:14 PM, Jesse Glick <[email protected]> wrote: > On Thu, Sep 5, 2013 at 4:02 PM, mohan kumar Muddana <[email protected]> > wrote: > > lib\classes.jar might need to be rebuilt: > java.lang.ClassNotFoundException > > (I mean the main project class file) > > at net.java.sezpoz.IndexItem.element(IndexItem.java:144) > > Something is very wrong with your class loading: your > @Extension-annotated plugin class seems to be present on the JRE’s > boot classpath. Or at least that is my reading of the exception. I > cannot really guess at what is actually going on. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/za3PR_2KFTo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
