Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Plamen Totev]

On Jun 5, 2017 20:51, "Paul Hammant"  wrote:

The publishing binaries to Github
isn't the problem I'm trying to solve - it is the acquisition of deps as
builds needs them.  Want to take this offline ?


- Paul


That is interesting problem to solve. Unfortunatelly I don' t have the time
to participate right now. But I'll follow the development with interest.

Regards,
Plamen Totev

Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Paul Hammant]

Hi Plamen,

> Using GitHub as Maven repository?

Yup. At least to have it as a choice.

I'm imagining putting releases for my esoteric, long-tail ideas, on
Github *rather
than littering Maven Central.*  But also allowing Maven/Grade/Ivy projects
to source the deps from there directly.  The publishing binaries to Github
isn't the problem I'm trying to solve - it is the acquisition of deps as
builds needs them.  Want to take this offline ?

- Paul

On Mon, Jun 5, 2017 at 11:14 AM, Plamen Totev 
wrote:

> Hi,
>
> I think I had a similar idea. Could you please elaborate what you want to
> achieve? Using GitHub as Maven repository?
>
> I was looking at the matter myself. I didn't spend much time so I have only
> basic understanding of the problems involved and how to solve them.
> As far I know there are (even several) Maven plug-ins that allows you to
> publish Maven artifact to GitHub using the Releases API. But I didn't find
> a way to use GitHub Releases as Maven Repository.
>
> In any case I think the Wagon plug-in is the one that provides the
> transport
> and the one that should be extended in order to be able to reprieve
> artifacts from a new service, not the Dependency plug-in.
>
> Regards,
> Plamen Totev
>
> On Jun 4, 2017 14:23, "Paul Hammant"  wrote:
>
> > So I have 27 releases of XStream unzipped and pushed to
> > https://github.com/paul-hammant/mc-xs-classes
> >
> > (8.4M of Jars is now 2.4M of bare .git repo)
> >
> > All the jars are still available - here -
> > https://github.com/paul-hammant/mc-xs-classes/releases
> >
> > Perfect except:
> >
> >
> >1. .zip suffix instead of .jar
> >2. there's a pesky root folder inside the zip, that matches the tag
> name
> >(GitHub's policy I guess for downloads).
> >3. the signatures won't match those for the originals up on 'Central.
> >
> > I want to fork (experimentally) maven-dependency-plugin (it's in
> Subversion
> > now, but the fork should be on GitHub of course), and sprinkle in some
> > https://github.com/zeroturnaround/zt-zip in order to (1) rename the zip
> on
> > download from GitHub, and (2) remove the root folder inside the zip
> without
> > a mechanical unzip/rezip ... then put theresult in ~/.m2/repository/ as
> > normal.
> >
> > There's probably some pom.xml creativity needed too.
> >
> > Any takers?
> >
> > - Paul
> >
>

Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Plamen Totev]

Hi,

I think I had a similar idea. Could you please elaborate what you want to
achieve? Using GitHub as Maven repository?

I was looking at the matter myself. I didn't spend much time so I have only
basic understanding of the problems involved and how to solve them.
As far I know there are (even several) Maven plug-ins that allows you to
publish Maven artifact to GitHub using the Releases API. But I didn't find
a way to use GitHub Releases as Maven Repository.

In any case I think the Wagon plug-in is the one that provides the transport
and the one that should be extended in order to be able to reprieve
artifacts from a new service, not the Dependency plug-in.

Regards,
Plamen Totev

On Jun 4, 2017 14:23, "Paul Hammant"  wrote:

> So I have 27 releases of XStream unzipped and pushed to
> https://github.com/paul-hammant/mc-xs-classes
>
> (8.4M of Jars is now 2.4M of bare .git repo)
>
> All the jars are still available - here -
> https://github.com/paul-hammant/mc-xs-classes/releases
>
> Perfect except:
>
>
>1. .zip suffix instead of .jar
>2. there's a pesky root folder inside the zip, that matches the tag name
>(GitHub's policy I guess for downloads).
>3. the signatures won't match those for the originals up on 'Central.
>
> I want to fork (experimentally) maven-dependency-plugin (it's in Subversion
> now, but the fork should be on GitHub of course), and sprinkle in some
> https://github.com/zeroturnaround/zt-zip in order to (1) rename the zip on
> download from GitHub, and (2) remove the root folder inside the zip without
> a mechanical unzip/rezip ... then put theresult in ~/.m2/repository/ as
> normal.
>
> There's probably some pom.xml creativity needed too.
>
> Any takers?
>
> - Paul
>

Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

[Paul Hammant]

So I have 27 releases of XStream unzipped and pushed to
https://github.com/paul-hammant/mc-xs-classes

(8.4M of Jars is now 2.4M of bare .git repo)

All the jars are still available - here -
https://github.com/paul-hammant/mc-xs-classes/releases

Perfect except:


   1. .zip suffix instead of .jar
   2. there's a pesky root folder inside the zip, that matches the tag name
   (GitHub's policy I guess for downloads).
   3. the signatures won't match those for the originals up on 'Central.

I want to fork (experimentally) maven-dependency-plugin (it's in Subversion
now, but the fork should be on GitHub of course), and sprinkle in some
https://github.com/zeroturnaround/zt-zip in order to (1) rename the zip on
download from GitHub, and (2) remove the root folder inside the zip without
a mechanical unzip/rezip ... then put theresult in ~/.m2/repository/ as
normal.

There's probably some pom.xml creativity needed too.

Any takers?

- Paul