Hi,
merging the 2 plugins definitely makes sense. I just wonder why I did not
find the other one before :(
I will come back to you soon, this is just a quick reply as I'm not at my
PC today.
Regards,
Michael
Am 13.05.2012 09:40 schrieb "domi" <[email protected]>:
> Michael,
> I have granted you commit access to the plugins, but lets really talk
> about merging the two plugins, I really think this would make sense and
> give a great benefit for users.
> e.g. global repositories are to be configured for both plugins otherwise.
> regards Domi
>
> On 13.05.2012, at 09:22, domi wrote:
>
>
> Hi Michael,
> this is close to the functionality of this plugin:
> https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin
> I think we should check if it would make sense to merge the two…
> About your proxy implementation, you should have a look at this:
> https://wiki.jenkins-ci.org/display/JENKINS/Async+Http+Client+Plugin
> what do you think?
> regards Domi
>
>
> On 12.05.2012, at 22:48, Michael Rumpf wrote:
>
> Hi,
>
> I have written a Maven Repository Client Plugin and put the source code on
> github:
> https://github.com/mrumpf/repoclient-plugin
>
> My github ID is "mrumpf".
>
> ### TODOs ###
> * DONE Adapt pom.xml to Jenkins plugin structure
> * Initial Wiki page created, but the plugin id is missing
> https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repository+Client
> * Add documentation
> * Classification (Wiki Labels)
> The plugin is behaving like a build wrapper, although it does not
> implement the BuildWrapper API.
> * CI Build
>
> Is there anything else left to do?
>
> Regards,
> Michael
>
>
>
>
