Is the name of a renamed plugin available via code?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Is the name of a renamed plugin available via code?

Ulli Hafner-2
Hi,

is the actual directory (hpi-name) of a plugin programmatically available?
My plugin does not find its images if someone renames the plugin from tasks.hpi to tasks-1.5.hpi.
since I use absolute references in the jelly script /tasks/path (as all other plug-ins:-).

/plugin/findbugs/icons/findbugs-48x48.gif

Thanks, Ulli
--
Avaloq - essential for banking.

Avaloq Evolution AG
Allmendstrasse 140, 8027 Z├╝rich
T +41 44 488 6790, F +41 44 488 6868, http://www.avaloq.com 
Dr. Ullrich Hafner mailto:[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Is the name of a renamed plugin available via code?

Kohsuke Kawaguchi
Administrator
Hafner Ullrich wrote:
> Hi,
>
> is the actual directory (hpi-name) of a plugin programmatically available?
> My plugin does not find its images if someone renames the plugin from tasks.hpi to tasks-1.5.hpi.
> since I use absolute references in the jelly script /tasks/path (as all other plug-ins:-).
>
> /plugin/findbugs/icons/findbugs-48x48.gif

Good point.

I think what we should do is to bake the real plugin name inside hpi, so
that Hudson always extract it using the real name, not the versioned
name taken from the maven repository.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment