Bundle – bundle JRE with applications?

I've been debating whether to bundle JRE with my application I've listed some reasons why I think it will be useful, but I'm also hesitant because it makes the application bigger

Why do I think it will be useful:

>Now, run the application by running the batch file (well, the shortcut to the batch file, which runs through the batch file) It just calls Java - jar XXX. It needs JAVA in the path, but this is not always the case. > We are a small team and do not run completely on Java 7 (we are trying to debug some strange errors) If users use Java 7, they may encounter an unpleasant software experience - which is bad for us Packaging a specific version of JRE ensures that we have fully tested it. > We support 32 - bit and 64 - bit windows platforms When users download software, they choose 32-bit or 64 bit, but this is asking which version of Java they are using Most users don't know whether 32-bit Java is installed on their 64 bit platform. Even if their operating system is 64 bit, downloading 32-bit will be confusing

There are some good reasons not to package it:

>If there are security vulnerabilities in Java or other important updates to JRE, we need to use the new Java version to distribute the new version of the application We usually update our application every two weeks, so I don't care much about this now. > The application will now be larger because it contains a packaged JRE

Anyone can provide some guidance (based on these requirements) do they think packaging JRE is a good idea? If not, we just want java to have an alternative in the path (more importantly, if not, our users may not know how to add it)

Solution

> Java Web Start. JRE will be on track

So, "the bad idea of bundling JRE." Use web start.exe instead