I agree with Tim here. Compare the maven[1] and gradle[2] homepages. The
gradle page is pretty clean (too clean?) and you know immediately where to
download the bundle.The maven site has a huge amount of text, all links look
the same so I can imagine that newbies get a bit lost, already on th
+1
hERVÉ
Le mercredi 6 juillet 2011, Stephen Connolly a écrit :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=
> Html&version=17165
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-021/
>
> Source distribu
+1
2011/7/6 Stephen Connolly :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&styleName=Html&version=17165
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-021/
>
> Source distribution:
> https://repository.apache.org/co
Hello,
The vote has passed with the following result :
+1 (binding) : Hervé Boutemy, Dennis Lundberg, Kristian Rosenvold,
Stephen Connolly, Mark Struberg, Olivier Lamy
+1 (non binding) : Lukas Theussl, Tony Chemit, Robert Scholte
I will promote artifacts to central repo.
Thanks,
--
Olivier Lamy
You are right, that's the contra argument:
Historical versions rely on information on a given nexus.
But this can be a CNAME or whatever, so it's easy to move it inside a company.
At the end, you still have to add the sections in your own poms
somewhere for your _own_ company intern artifacts.
