(not sure I can vote, but here's the deal)

I installed Apache TomEE+ 1.5.1 from
http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/, on a
64-bit Windows 7 machine, after having added a suitable JRE_HOME into
startup.bat. I tried to register TomEE+ as a service :
1. set JRE_HOME=c:\Program Files\Java\jdk1.7.0_09
2. From a command prompt with current working directory in TomEE's bin/
directory, typed:
            service.bat install
    Here's what I get:


E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin>service.bat install
Installing the service 'TomEE' ...
Using CATALINA_HOME:    "E:\NoSave\tomEE\apache-tomee-plus-1.5.1"
Using CATALINA_BASE:    "E:\NoSave\tomEE\apache-tomee-plus-1.5.1"
Using JAVA_HOME:        ""
Using JRE_HOME:         "c:\Program Files\Java\jdk1.7.0_09"
Using JVM:              "auto"
""E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin\TomEE.AMD64.exe"" //IS//TomEE
[2012-12-13 16:51:53] [error] Unrecognized cmd option
E:\NoSave\tomEE\apache-tom
ee-plus-1.5.1\bin\TomEE.AMD64.exe
[2012-12-13 16:51:53] [error] Invalid command line arguments
[2012-12-13 16:51:53] [error] Commons Daemon procrun failed with exit
value: 1 (
Failed to parse command line arguments)
Failed installing 'TomEE' service

Baseline, TomEE registry as a Windows service seems to be broken like it
was in 1.5.0 and in 1.0.0, but in a slightly different way.

I doubt it can be released as is, don't you think?

Thanks,
Alex




On Thu, Dec 13, 2012 at 3:43 PM, Alan Cabrera <l...@toolazydogs.com> wrote:

>
> +1
>
> Regards,
> Alan
>
> On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO wrote:
>
> > [generated email]
> >
> > SVN Tag:
> >
> > https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/
> >
> > Maven Repo:
> >
> > https://repository.apache.org/content/repositories/orgapacheopenejb-132
> >
> > Binaries & Source:
> >
> > http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/
> >
> > Legal:
> >
> > http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html
> >
> >
> > Vote will be open for 72 hours or as needed.
>
>

Reply via email to