<div dir="ltr">Hey,<div><br></div><div>I just replied to Wei's mail, which addresses a similar concern. If a dependency is not properly maintained, and released, there is always room for that kinda stuff.</div><div>If we do it, we should be doing it w/ different packages (e.g. org.aerogear.<span style="color:rgb(51,51,51);font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:12px;white-space:pre">com.offbytwo.jenkins</span>), as a last resort :-) </div><div><br></div><div>I'd suggest to get in touch w/ the maintainer, and explain him, that we are interested in helping, and would also like to have frequent releases :) Perhaps that's the first strategy, before going hard on a fork - that has the risk of being always different than the rest of the usptream community. </div><div><br></div><div><br></div><div>-M</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <span dir="ltr"><<a href="mailto:aliok@redhat.com" target="_blank">aliok@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi,</div><div><br></div><div>In order to make our Digger Java client working as we like, we needed to make changes in the underlying Jenkins Java client [1].</div><div>We sent a PR, but we don't know when the project owner will merge it. So, for testing purposes of our own, we would like to release our fork of Jenkins Java client in a snapshot repository.</div></div><div><br></div><div>What do you say? Any other and better approach?</div><div><br></div><div>Where can we publish the snapshots of our fork?</div><div><br></div><div>Note: The project owner is a kind guy and will perhaps publish a snapshot release for us after merging our PR, but we cannot rely on that workflow for long time for other needed changes.</div><span class="HOEnZb"><font color="#888888"><div><br></div>-- <br><div class="m_3418752125548392244gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>ALI</span> <span>OK</span></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM</span></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat <span><br><br></span></a></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a></td></tr></tbody></table></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div>