[aerogear-dev] Jenkins Java client - fork?

[Matthias Wessendorf]

Hey,

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.
If we do it, we should be doing it w/ different packages (e.g. org.aerogear.
com.offbytwo.jenkins), as a last resort :-)

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.


-M


On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <aliok at redhat.com> wrote:

> Hi,
>
> In order to make our Digger Java client working as we like, we needed to
> make changes in the underlying Jenkins Java client [1].
> 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.
>
> What do you say? Any other and better approach?
>
> Where can we publish the snapshots of our fork?
>
> 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.
>
> --
>
> ALI OK
>
> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>
> Red Hat
>
> <https://www.redhat.com/>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/17ce5b85/attachment-0001.html