Re: Adoption of the native2ascii maven plugin (Codehaus)

Ticket filed: https://issues.sonatype.org/browse/OSSRH-35087 Wrt teh docs I don't know. All mojos so far har sites so I think we should for this one as well. One of the benefits of these maven sites is that they follow the same structure so it's easy to find the info you're looking for. You could

Re: Adoption of the native2ascii maven plugin (Codehaus)

It seems nobody's interested. Today I updated pom.xml to use the mojo-parent, fixed some requirements and tried to deploy. Now I can login (401 has gone) but I have no rights to deploy to codehaus group in snapshot repository (HTTP 403). What should I do now? Thanks, David. -- You received

Re: Adoption of the native2ascii maven plugin (Codehaus)

It is the same problem - I am not authorized to do that now (rename repo) because I am not in the Owners group: https://github.com/orgs/mojohaus/people I do have access to Travis but I am not allowed to authorize Travis to use MojoHause's project and build it. More here:

Re: Adoption of the native2ascii maven plugin (Codehaus)

Done, thank you! :-) On 18 September 2017 at 06:33, Anders Hammar wrote: > I've sent an invitation in Github. > > Welcome, > /Anders > > On Sun, Sep 17, 2017 at 9:53 PM, David Matějček > wrote: > >> I know that MojoHaus exists and I already wrote my

Re: Adoption of the native2ascii maven plugin (Codehaus)

I've sent an invitation in Github. Welcome, /Anders On Sun, Sep 17, 2017 at 9:53 PM, David Matějček wrote: > I know that MojoHaus exists and I already wrote my GitHub id: dmatej :-) > After you give me permission to transfer the repo ownership, only I can do > it as GitHub

Re: Adoption of the native2ascii maven plugin (Codehaus)

I know that MojoHaus exists and I already wrote my GitHub id: dmatej :-) After you give me permission to transfer the repo ownership, only I can do it as GitHub says here: https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/ And here: [image: Inline images 1]

Re: Adoption of the native2ascii maven plugin (Codehaus)

David, The MojoHaus organization already exists. If you send us your Github user id we can grant you privs so you can create repo and import. Wrt to deploying release you should follow the MojoHaus development guideline [1] and release process [2] including voting. We'd appreciate if you could

Re: Adoption of the native2ascii maven plugin (Codehaus)

So ... GitHub wants only to tell "New owner’s GitHub username or organization name" - I expect the name is MojoHaus Can I still push to it then? (GitHub says yes) How about deploy of the final version? How is it managed under the Mojohaus? Will it make it to the Maven Central and when? It seems

Re: Adoption of the native2ascii maven plugin (Codehaus)

Definitely the second option makes a lot of sense. This plugin was not reimported because nobody bothered filing the associated PR. I think we should simply move your repo into the org. 2017-09-10 22:01 GMT+02:00 David Matějček : > The second option (maybe much better) is

Re: Adoption of the native2ascii maven plugin (Codehaus)

The second option (maybe much better) is that my repository would move to Mojohaus and I will be somehow responsible for this plugin ... (there is not much work on it, only to publish and maybe to create some site for the plugin). -- You received this message because you are subscribed to

Adoption of the native2ascii maven plugin (Codehaus)

Hi, some time ago I have rewritten the native2ascii maven plugin. I was contacted several times to publish it on Maven Central servers. The Codehaus is dead now (2017) ... can I still use the same POM id? Who is the authority to answer this question? License is unchanged. org.codehaus.mojo