Wonder why you didnt use the maven-core implementation ?

[ltearno]

Hi, funny i just had exactly the same idea as you 3 weeks ago !

So i started a similar project : https://github.com/ltearno/mvn-run

I just wonder why you parse maven files yourself, instead of using maven-core, shrinkwrap or aether ?

At this stage the current mvn-run version uses shrinkwrap, and with only a few lines of code, it already does eat the maven settings.xml, does the artifact download if needed (using the settings.xml which may specify a nexus repository and credentials for example), and uses the maven core to resolve dependencies (so that the code doesn't have to cope with variables).

So maybe, since we had the same idea at the same time, it may be beneficial that we collaborate to the same project, what do you think ?

Thanks
Arnaud
www.lteconsulting.fr

[jernst]

Hi Arnaud, I'm all in favor of collaborating. I just sent you an invite.

I don't want to download things automatically (and least not by default) because that opens up big security problems. And I'd like to be able to run this even if maven itself is not installed on the server (maven is a build tool for development servers, diet4j is for production servers). And work with other dependency frameworks in the future (e.g. project igsaw) But none of those is cast in stone... all suggestions / pull requests / ... welcome!

Cheers,

Johannes.

[ltearno]

Hi Johannes,

Thanks for your invite ! I understand we have kind of different needs, but
also some common requirements. Actually i am at the very beginning of this
project, i will take some time to gather all my requirements and write up a
little document.
This way, we will be able to see more clearer which parts could be shared
between diet4j and mvn-run, and if that would benefit the development of
both...

Thanks

Arnaud

Le ven. 5 juin 2015 à 00:09, Johannes Ernst notifications@github.com a
écrit :

Hi Arnaud, I'm all in favor of collaborating. I just sent you an invite.

I don't want to download things automatically (and least not by default)
because that opens up big security problems. And I'd like to be able to run
this even if maven itself is not installed on the server (maven is a build
tool for development servers, diet4j is for production servers). And work
with other dependency frameworks in the future (e.g. project igsaw) But
none of those is cast in stone... all suggestions / pull requests / ...
welcome!

Cheers,

Johannes.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[jernst]

Looking forward to seeing it!