If there is a bug in your little library that is fixed and released, all
plugins using it will probably have to update the dependency and release a new
version of the plugin, until it appears in core.
If the library was a plugin all plugins would get the bugfix when the new icon
plugin version
Maybe there's a misunderstanding ... I created a jenkins-icon module
(a simple java jar containing just the icon taglib). It doesn't depend
on anything in Jenkins - it just depends on Stapler. Jenkins core
depends on this module to get the icon tag. Plugins can also
independently depend on
But wouldn't that be the case anyway if we defined the base tag in the
normal way inside Jenkins core i.e. plugins using the tag would need to
wait for a core update to get fixes on that tag?
On 01/07/2014 09:19, Sandell, Robert wrote:
If there is a bug in your little library that is fixed
Ah ok. Yeah that will work
On Tuesday, 1 July 2014, Tom Fennelly tom.fenne...@gmail.com wrote:
Maybe there's a misunderstanding ... I created a jenkins-icon module (a
simple java jar containing just the icon taglib). It doesn't depend on
anything in Jenkins - it just depends on Stapler.
and Product Configuration
Sony Mobile Communications
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On
Behalf Of Tom Fennelly
Sent: den 1 juli 2014 12:41
To: jenkinsci-dev@googlegroups.com
Subject: Re: New Jelly tags - via Jenkins Core + Plugin shim, or via simple
Java jar
@googlegroups.com] *On Behalf Of *Tom Fennelly
*Sent:* den 1 juli 2014 12:41
*To:* jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin shim, or
via simple Java jar dependency ??
But wouldn't that be the case anyway if we defined the base tag in the
normal way inside
] *On
Behalf Of *Tom Fennelly
*Sent:* den 1 juli 2014 12:41
*To:* jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin shim, or via
simple Java jar dependency ??
But wouldn't that be the case anyway if we defined the base tag in the
normal way inside Jenkins
Fennelly
*Sent:* den 1 juli 2014 12:41
*To:* jenkinsci-dev@googlegroups.com
mailto:jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin shim,
or via simple Java jar dependency ??
But wouldn't that be the case anyway if we defined the base tag
Communications
*From:* jenkinsci-dev@googlegroups.com [
mailto:jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com] *On
Behalf Of *Tom Fennelly
*Sent:* den 1 juli 2014 12:41
*To:* jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin shim, or via
*To:* jenkinsci-dev@googlegroups.com
mailto:jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin
shim, or via simple Java jar dependency ??
But wouldn't that be the case anyway if we defined the base
tag in the normal way inside
You can't update core to use the plugin, as circular dependency... So as
soon as you want to use your tag in core your plugin is... Oh look its a
shim!
Would a rose by any other name smell as sweet?
On Monday, 30 June 2014, Tom Fennelly tom.fenne...@gmail.com wrote:
Hi.
We're in the process
Anyway you have over complicated yourself.
Also you don't call the shim tag icon-shim you call it icon but in a
different namespace. That makes migration simples
We should chat tomorrow
On Tuesday, 1 July 2014, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
You can't update core to
12 matches
Mail list logo
