+1 for the rename, 
but would we not need some kind of aliasing in the core for to ease renaming.
after all, there are plugins which have dependencies to others in the code by 
there name like this (or similar):  updateCenter.getPlugin(“ghprb”) 
Domi

On 10.11.2014, at 14:38, Daniel Beck <[email protected]> wrote:

> 
> On 10.11.2014, at 11:30, Stephen Connolly <[email protected]> 
> wrote:
> 
>> There should be two components:
>> 
>> literate-api
>> literate-plugin
>> 
>> The literate-api is a separate beast that is potentially independent of 
>> Jenkins in order to allow people to develop additional tooling, we may even 
>> move it to its own github org if it proves popular enough (which presupposes 
>> I get enough time to push it to a 1.0)
> 
> Thanks for the clarification!
> 
> ----
> 
> I'd like to add
> 
>    rename ghprb-plugin to github-pull-request-builder-plugin
> 
> to the list of suggestions. The current name appears to be difficult to find 
> for end users.
> 
> -- 
> 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/d/optout.

-- 
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/d/optout.

Reply via email to