On 24/02/2011 20:31,
Jason van Zyl wrote:
I'll try this again whilst not rushing out the
door and leaving
predictive text on..
"We are also in communication with a bunch of the
plugin writers who
are interested in keeping their plugins working in
both Hudson and
Which bunch of *plugin writers* would that be as
it certainly hasn't
included me (m2 release)
The two that I saw today were:
Both specifically supporting both Hudson and
Ok - maybe a bit more context...
Currently the source is in java.net
svn - it is to me
migrated to github jenkinsci (jenkinsci will be the
primary target from now as we use Nectar).
The next release has a bug that needs to be fixed in the
core - I am about to make that change in Jenkins.
As such I will declare the parent of my plugin to the the
hpi of the fixed jenkins version.
So - this will I presume lock out Hudson users (as the hpi
is built against the jenkins parent not the pre
So given that I would also need to put the equiv fix into
Hudson (and would require me to do more work by writing a
Unit / integration test for this) where do I go?
1) the fix would need to go into core as it is a core bug.
2) somehow my plugin needs to get to both update centers
and the version of jenkins != version of Hudson (due to
differeing release versions/timescales)
(The core bug is that it does not set and expose M2_HOME
as an environment variable to the Maven2 type job, nor
does it prepend M2_HOME to the path.