How to take over the computer of a Maven Central user

Re:How to take over the computer of a Maven Central user by jimrandomh on Monday July 28, 2014 @11:04PM (#8100507)

My main experience with Maven has been downloading some source code, and having to use Gradle to compile it. It went and downloaded a bunch of binaries, insecurely. There were no actual unsatisfied dependencies; it was just downloading pieces of Gradle itself.

I would've much rather had a Makefile. Build scripts and package managers need to be separate.

[ Parent | on HN ]

Re:How to take over the computer of a Maven Central user by yourad_io on Monday July 28, 2014 @11:11PM (#8100523)

> Build scripts and package managers need to be separate.

This. Especially when there's broken links, you're gonna have a bad (and long) time.

[ Parent | on HN ]

Re:How to take over the computer of a Maven Central user by taeric on Tuesday July 29, 2014 @01:47PM (#8103633)

I will join the small chorus agreeing that build scripts and package managers should be separate. Most folks I work with disagree.

Curious if anyone knows of any well done takes on this. In either way. (If I'm actually wrong, I'd like to know.) (I fully suspect there really is no "right" answer.)

[ Parent | on HN ]

Re:How to take over the computer of a Maven Central user by dmacvicar on Tuesday July 29, 2014 @05:36AM (#8101370)

Finally someone who sees the real problem.

[ Parent | on HN ]