Congrats Oliver! Keep up the good work!
/B
On Fri, Apr 1, 2016 at 10:14 PM, R. Tyler Croy wrote:
> (replies inline)
>
> On Mon, 07 Mar 2016, R. Tyler Croy wrote:
>
> > Based on the team lead structure
> > (
>
Indeed! and thanks for all your work Oliver!!
On Tue, Apr 5, 2016 at 7:19 AM, Robert Sandell
wrote:
> Congrats Oliver! Keep up the good work!
>
> /B
>
> On Fri, Apr 1, 2016 at 10:14 PM, R. Tyler Croy
> wrote:
>
>> (replies inline)
>>
>> On Mon, 07
I'm trying to write a unit test that will exercise the UI for my plugin and
to do that I need to configure it's global properties.
I can get to the global configuration page but when I look in the config
form for my plugin settings it's not there. The wiki only touches this
area very lightly
I'm trying to write a unit test that will exercise the UI for my plugin and
to do that I need to configure it's global properties.
I can get to the global configuration page but when I look in the config
form for my plugin settings it's not there. The wiki only touches this
area very lightly
I'm trying to write a unit test that will exercise the UI for my plugin and
to do that I need to configure the plugins global properties.
I can get to the global configuration page but when I look in the config
form for my plugin settings it's not there. The wiki only touches this
area very
(replies inline)
On Mon, 04 Apr 2016, Arshad Khan wrote:
> I have tried to redesign the Jenkins 2.0 website to make it look even more
> beautiful. I have attached a full-website screenshot and a link for a
> video. Have a look!
>
> Video link: https://youtu.be/3QUOjm0
>
> Code:
*TEXT capitalization in buttons -* I thinks as long as text in buttons are
not long, capitalization is good. Capitalization makes the text stand out
from the rest of the text(I know there is background color to make it look
different but capitalization also serves the purpose) and it grabs the
*TEXT capitalization in buttons -* I think as long as text in buttons are
not long, capitalization is good. Capitalization makes the text stand out
from the rest of the text(I know there is background color to make it look
different but capitalization also serves the purpose) and it grabs the
I'm trying to write a unit test that will exercise the UI for my plugin and
to do that I need to configure it's global properties.
I can get to the global configuration page but when I look in the config
form for my plugin settings it's not there. The wiki only touches this
area very
I'm trying to write a unit test that will exercise the UI for my plugin and
to do that I need to configure it's global properties.
I can get to the global configuration page but when I look in the config
form for my plugin settings it's not there. The wiki only touches this
area very lightly
(replies inline)
On Tue, 05 Apr 2016, Michael O'Cleirigh wrote:
> Hello,
>
> Just to give an update.
>
> I've switched over to using Java and JGit for rewriting/splitting out the
> plugins.
>
> I have some repo cleaning code that I'm adapting fit this case.
>
> My splitter can extract the
Hello,
Just to give an update.
I've switched over to using Java and JGit for rewriting/splitting out the
plugins.
I have some repo cleaning code that I'm adapting fit this case.
My splitter can extract the module where it exists. And preserve the
release tags.
The current issue I'm solving is
See http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html
Daniel
On Tue, Apr 5, 2016 at 7:25 AM, Michael Neale wrote:
> I had this problem some months ago when releasing and the javadoc phase -
> I never did get to the bottom of it.
>
> Can you paste the
13 matches
Mail list logo