I've seen (and installed as part of a proof of concept in a previous job - and not JSW, it was Ghostscript or something) some software that, rather than packaging things like this with the product, simply provided long instructions that included downloading and installing the third-party software then configuring it to work with their software, thereby avoiding any such license violations.
To me, this would seem to violate the spirit though perhaps not the legal wording/requirements of any such license... On Sat, Feb 15, 2014 at 6:27 PM, Steven Siebert <[email protected]> wrote: > You only need to pay the license if you're planning on commercially > selling your product: > http://wrapper.tanukisoftware.com/doc/english/licenseCommunity.html > > "Closed Source Use: > > The GPL does not restrict private software from being developed for > internal use which depends on software under the GPL as long as that > software is never redistributed without making the full source of the > entire application available to all users." > > > > > On Thu, Feb 13, 2014 at 3:21 PM, clay <[email protected]> wrote: > >> I was happy with using a trivial /etc/init.d service wrapper that just >> calls "java -jar <myapp>.jar" on startup and does a process kill for >> shutdown. >> >> It seems silly to use a more heavy-weight tool that actually requires a >> license purchase. >> >> There are tons of conversations on this exact topic of Java service >> wrappers on stackexhange >> >> >> On Monday, February 10, 2014 4:34:42 AM UTC-6, rakesh mailgroups wrote: >> >>> Hi Kevin, >>> >>> I think the idea of an embedded container inside the stack a la Play >>> is what Spring boot is trying to emulate. Its irrelevant whether it is >>> jetty or tomcat. >>> >>> What I need is an easy way to do : java -jar <myapp>.jar >>> >>> Cheers >>> >>> Rakesh >>> >>> On 10 February 2014 10:13, Kevin Wright <[email protected]> wrote: >>> > The best advice is probably to "use Jetty" >>> > >>> > It seems to have much better support for running as an embedded >>> container, >>> > I've never seen a solution with Tomcat that didn't look cumbersome. >>> > >>> > You might also investigate if you *truly* need a container. I'm >>> guessing >>> > that your dependency on Spring demands one, but an increasing number >>> of >>> > frameworks and libraries (such as play) are happily doing away with >>> > containers altogether. This is certainly the trend in the Scala >>> ecosystem, >>> > but I'd be awfully surprised if the trickle down effect didn't mean >>> that >>> > similar ideas weren't also being adopted by someone somewhere in pure >>> Java. >>> > >>> > >>> > >>> > On 10 February 2014 10:05, Rakesh <[email protected]> wrote: >>> >> >>> >> Hi guys, >>> >> >>> >> decided to do something different and deploy my app with an embedded >>> >> Tomcat instance. >>> >> >>> >> The new Spring Boot project actively encourages this and it is very >>> >> nice from a purely dev perspective not having to configure a >>> container >>> >> externally to test things. >>> >> >>> >> However, I deploy to Unix (AWS has their own variant) and am stumped >>> >> with getting the app to automatically start. >>> >> >>> >> Googling around has uncovered some very complicated solutions, >>> >> including an apache project to achieve this. >>> >> >>> >> Any advice? Does it have to be so hard? >>> >> >>> >> Thanks >>> >> >>> >> Rakesh >>> >> >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "Java Posse" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > To post to this group, send email to [email protected]. >>> > Visit this group at http://groups.google.com/group/javaposse. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Java Posse" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/javaposse. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "Java Posse" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/javaposse. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
