On Mon, April 16, 2012 2:13 pm, [email protected] wrote: > Our build has a dependency on the JRE. In order to build our final > distribution artifact, we need a JRE. To me, this means that the JRE > should be managed as a maven artifact in nexus. Otherwise, I can't use > the assembly plugin to build my distribution. I can't really find much on > this on the internet, though I do see a couple of people suggesting that > it's a whacky idea.
I am pretty sure that most people do not think that adding the JRE to your repo is a whacky idea but rather that shipping at JRE as part of your installer is. And I tend to agree with them. Imho it is an antipattern to do that. Get a proper installer going that ensures that the JRE or whatever is present or even gets installed but do NOT include it as part of your installer. Unless of course you also include your database , your command line tools and maybe your operating system as part of your installer.. > Why is it whacky? The JRE is a raw material upon which our build is > dependent, so how else should that be obtained? Other ways of making it > available to the build don't seem better . . . They are... and you got a solution on how to do it if you really still think you should.. manfred --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
