On 06/13/2014 10:26 PM, Barrie Treloar wrote:
On 14 June 2014 02:14, Robert Kuropkat rkurop...@t-sciences.com wrote:
snip
I'll add my cry of despair here as well. Modern Open Source documentation
efforts tend be mostly disappointing. First of all, it's never in a nice
neat collection.
: Complex Maven projects - Tutorials? Books?
If you are really aiming at doing continuous delivery (any potential build can
be pushed to prod), then SNAPSHOT is not a great way to deal with dependencies
since you will not be able to exactly know what you ship. To avoid this, one
practice is to use
. :)
Regards,
Gerrit
-Ursprüngliche Nachricht-
Von: Pascal Rapicault [mailto:pas...@rapicault.net]
Gesendet: Freitag, 13. Juni 2014 04:32
An: Maven Users List
Betreff: Re: Complex Maven projects - Tutorials? Books?
If you are really aiming at doing continuous delivery (any potential build
On Fri, Jun 13, 2014 at 09:23:31AM +0930, Barrie Treloar wrote:
On 13 June 2014 09:07, mike digioia mpd...@gmail.com wrote:
So how does this book help you any more than all the detailed online Maven
docs that exists and are updated?
It's just another source of information.
The docs
On 06/13/2014 10:27 AM, Mark H. Wood wrote:
On Fri, Jun 13, 2014 at 09:23:31AM +0930, Barrie Treloar wrote:
On 13 June 2014 09:07, mike digioia mpd...@gmail.com wrote:
So how does this book help you any more than all the detailed online Maven
docs that exists and are updated?
It's just
+1
Ron
On 13/06/2014 12:44 PM, Robert Kuropkat wrote:
On 06/13/2014 10:27 AM, Mark H. Wood wrote:
On Fri, Jun 13, 2014 at 09:23:31AM +0930, Barrie Treloar wrote:
On 13 June 2014 09:07, mike digioia mpd...@gmail.com wrote:
So how does this book help you any more than all the detailed
online
On 14 June 2014 02:14, Robert Kuropkat rkurop...@t-sciences.com wrote:
On 06/13/2014 10:27 AM, Mark H. Wood wrote:
On Fri, Jun 13, 2014 at 09:23:31AM +0930, Barrie Treloar wrote:
On 13 June 2014 09:07, mike digioia mpd...@gmail.com wrote:
So how does this book help you any more than all
Hello everyone, :)
I have a question which is not about a specific problem with Maven, but
more a general question.
I hope it is okay to ask this question here.
We use Maven and Jenkins for about 1.5 years now, I guess. Until now the
Maven projects have been very simple and - let's say -
Am 2014-06-12 16:46, schrieb Hohl, Gerrit:
Hello everyone, :)
[..]
Does someone know a good book or tutorial which handles all of these
issues around Maven and CI/CD in more depth?
Hi Gerrit,
here is the approach I have been using all the years, I think this is
quite common in companies:
Good questions.
I have never heard anything negative about SNAPSHOTs from those who use
them.
Notice - Free advice:
- Separate your utilities from your applications. If they have a life of
their own, you can manage the dependencies more easily.
- Test your utilities and libraries separately.
Great advice.
We depend on Nexus.
If you are serious about Maven, you need a repo.
The community version of Nexus is a great benefit to the Maven community.
Ron
On 12/06/2014 2:39 PM, Michael Osipov wrote:
Am 2014-06-12 16:46, schrieb Hohl, Gerrit:
Hello everyone, :)
[..]
Does someone know
On 13 June 2014 00:16, Hohl, Gerrit g.h...@aurenz.de wrote:
We use Maven and Jenkins for about 1.5 years now, I guess. Until now the
Maven projects have been very simple and - let's say - very monolithic.
But recently we identify more and more internal libraries in our
products. Of course we
So how does this book help you any more than all the detailed online Maven
docs that exists and are updated?
On Thu, Jun 12, 2014 at 4:10 PM, Barrie Treloar baerr...@gmail.com wrote:
On 13 June 2014 00:16, Hohl, Gerrit g.h...@aurenz.de wrote:
We use Maven and Jenkins for about 1.5 years
On 13 June 2014 09:07, mike digioia mpd...@gmail.com wrote:
So how does this book help you any more than all the detailed online Maven
docs that exists and are updated?
It's just another source of information.
The docs don't really walk you through everything, they are mostly focused
on a
Hello everyone, :)
I have a question which is not about a specific problem with Maven, but
more a general question.
I hope it is okay to ask this question here.
We use Maven and Jenkins for about 1.5 years now, I guess. Until now the
Maven projects have been very simple and - let's say -
If you are really aiming at doing continuous delivery (any potential
build can be pushed to prod), then SNAPSHOT is not a great way to deal
with dependencies since you will not be able to exactly know what you
ship. To avoid this, one practice is to use the build number in the
artifact version
16 matches
Mail list logo
