You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Alex Soto <as...@gmail.com> on 2014/07/18 09:38:18 UTC

Apache Maven plugin and remote deployer

Hello,

Maybe I have misunderstood something but I am trying to deploy a war file
to a remote tomEE, something like done with maven cargo plugin.

Plugin configuration looks like:

<plugin>
  <groupId>org.apache.openejb.maven</groupId>
  <artifactId>tomee-maven-plugin</artifactId>
  <version>1.6.0.2</version>
  <configuration>
    <tomeeHost>${ip}</tomeeHost>
    <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
    <context>test</context>
  </configuration>
</plugin>

and then I run

mvn clean package tomee:deploy

and although the build is success and next line is printed: INFO:
RemoteInitialContextCreated{providerUri=http://192.....:8080/tomee/ejb}

the war file is not deployed. Maybe cannot be used as remote? If I miss any
attribute then maybe the fact that the file cannot be deployed should make
fail the build?

Alex

-- 
+----------------------------------------------------------+
  Alex Soto Bueno
  www.lordofthejars.com
+----------------------------------------------------------+

Re: Apache Maven plugin and remote deployer

Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Documentation is not up to date at all ;-)
Lot of features missing.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Jul 18, 2014 at 10:37 AM, Alex Soto <as...@gmail.com> wrote:

> Cool it works, but documentation (
> http://tomee.apache.org/tomee-maven-plugin.html) is not updated with
> useBinaries attribute. I think it may be useful for other users :).
>
> Thanks :)
>
>
> 2014-07-18 10:18 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
> > Hi
> >
> > yes configuration doesn't seem enough for remote deployment. Default
> > is local deployment. You need to set <useBinaries> to true. It will
> > deploy path archive with the name of the file in the path. (context is
> > ignored in this case)
> >
> >
> > Romain Manni-Bucau
> > Twitter: @rmannibucau
> > Blog: http://rmannibucau.wordpress.com/
> > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > Github: https://github.com/rmannibucau
> >
> >
> > 2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
> > > Hello,
> > >
> > > Maybe I have misunderstood something but I am trying to deploy a war
> file
> > > to a remote tomEE, something like done with maven cargo plugin.
> > >
> > > Plugin configuration looks like:
> > >
> > > <plugin>
> > >   <groupId>org.apache.openejb.maven</groupId>
> > >   <artifactId>tomee-maven-plugin</artifactId>
> > >   <version>1.6.0.2</version>
> > >   <configuration>
> > >     <tomeeHost>${ip}</tomeeHost>
> > >
> <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
> > >     <context>test</context>
> > >   </configuration>
> > > </plugin>
> > >
> > > and then I run
> > >
> > > mvn clean package tomee:deploy
> > >
> > > and although the build is success and next line is printed: INFO:
> > > RemoteInitialContextCreated{providerUri=http://192.
> ....:8080/tomee/ejb}
> > >
> > > the war file is not deployed. Maybe cannot be used as remote? If I miss
> > any
> > > attribute then maybe the fact that the file cannot be deployed should
> > make
> > > fail the build?
> > >
> > > Alex
> > >
> > > --
> > > +----------------------------------------------------------+
> > >   Alex Soto Bueno
> > >   www.lordofthejars.com
> > > +----------------------------------------------------------+
> >
>
>
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno - Computer Engineer
>   www.lordofthejars.com
> +----------------------------------------------------------+
>

Re: Apache Maven plugin and remote deployer

Posted by Alex Soto <as...@gmail.com>.
Ok then I do not edit anything :)


2014-07-18 10:53 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:

> well actually this is one of the rare page we can't edit since it is
> generated ;). But yes we should ensure we update it with each release.
> I guess we need to add some comments in the code too to get it right
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-07-18 10:48 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> > Cool, I'll get that updated today. Thanks for pointing that out Alex, I'm
> > always looking to improve the docs. You know you can edit the page also
> ;-)
> > .
> >
> > Andy.
> >
> >
> > On 18/07/2014 10:37, Alex Soto wrote:
> >>
> >> Cool it works, but documentation (
> >> http://tomee.apache.org/tomee-maven-plugin.html) is not updated with
> >> useBinaries attribute. I think it may be useful for other users :).
> >>
> >> Thanks :)
> >>
> >>
> >> 2014-07-18 10:18 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> >>
> >>> Hi
> >>>
> >>> yes configuration doesn't seem enough for remote deployment. Default
> >>> is local deployment. You need to set <useBinaries> to true. It will
> >>> deploy path archive with the name of the file in the path. (context is
> >>> ignored in this case)
> >>>
> >>>
> >>> Romain Manni-Bucau
> >>> Twitter: @rmannibucau
> >>> Blog: http://rmannibucau.wordpress.com/
> >>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> >>> Github: https://github.com/rmannibucau
> >>>
> >>>
> >>> 2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
> >>>>
> >>>> Hello,
> >>>>
> >>>> Maybe I have misunderstood something but I am trying to deploy a war
> >>>> file
> >>>> to a remote tomEE, something like done with maven cargo plugin.
> >>>>
> >>>> Plugin configuration looks like:
> >>>>
> >>>> <plugin>
> >>>>    <groupId>org.apache.openejb.maven</groupId>
> >>>>    <artifactId>tomee-maven-plugin</artifactId>
> >>>>    <version>1.6.0.2</version>
> >>>>    <configuration>
> >>>>      <tomeeHost>${ip}</tomeeHost>
> >>>>
> >>>> <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
> >>>>      <context>test</context>
> >>>>    </configuration>
> >>>> </plugin>
> >>>>
> >>>> and then I run
> >>>>
> >>>> mvn clean package tomee:deploy
> >>>>
> >>>> and although the build is success and next line is printed: INFO:
> >>>> RemoteInitialContextCreated{providerUri=http://192.
> ....:8080/tomee/ejb}
> >>>>
> >>>> the war file is not deployed. Maybe cannot be used as remote? If I
> miss
> >>>
> >>> any
> >>>>
> >>>> attribute then maybe the fact that the file cannot be deployed should
> >>>
> >>> make
> >>>>
> >>>> fail the build?
> >>>>
> >>>> Alex
> >>>>
> >>>> --
> >>>> +----------------------------------------------------------+
> >>>>    Alex Soto Bueno
> >>>>    www.lordofthejars.com
> >>>> +----------------------------------------------------------+
> >>
> >>
> >>
> >
> > --
> >   Andy Gumbrecht
> >
> >   http://www.tomitribe.com
> >   agumbrecht@tomitribe.com
> >   https://twitter.com/AndyGeeDe
> >
> >   TomEE treibt Tomitribe! | http://tomee.apache.org
> >
>



-- 
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+

Re: Apache Maven plugin and remote deployer

Posted by Romain Manni-Bucau <rm...@gmail.com>.
well actually this is one of the rare page we can't edit since it is
generated ;). But yes we should ensure we update it with each release.
I guess we need to add some comments in the code too to get it right


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-07-18 10:48 GMT+02:00 Andy Gumbrecht <ag...@tomitribe.com>:
> Cool, I'll get that updated today. Thanks for pointing that out Alex, I'm
> always looking to improve the docs. You know you can edit the page also ;-)
> .
>
> Andy.
>
>
> On 18/07/2014 10:37, Alex Soto wrote:
>>
>> Cool it works, but documentation (
>> http://tomee.apache.org/tomee-maven-plugin.html) is not updated with
>> useBinaries attribute. I think it may be useful for other users :).
>>
>> Thanks :)
>>
>>
>> 2014-07-18 10:18 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>>
>>> Hi
>>>
>>> yes configuration doesn't seem enough for remote deployment. Default
>>> is local deployment. You need to set <useBinaries> to true. It will
>>> deploy path archive with the name of the file in the path. (context is
>>> ignored in this case)
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
>>>>
>>>> Hello,
>>>>
>>>> Maybe I have misunderstood something but I am trying to deploy a war
>>>> file
>>>> to a remote tomEE, something like done with maven cargo plugin.
>>>>
>>>> Plugin configuration looks like:
>>>>
>>>> <plugin>
>>>>    <groupId>org.apache.openejb.maven</groupId>
>>>>    <artifactId>tomee-maven-plugin</artifactId>
>>>>    <version>1.6.0.2</version>
>>>>    <configuration>
>>>>      <tomeeHost>${ip}</tomeeHost>
>>>>
>>>> <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
>>>>      <context>test</context>
>>>>    </configuration>
>>>> </plugin>
>>>>
>>>> and then I run
>>>>
>>>> mvn clean package tomee:deploy
>>>>
>>>> and although the build is success and next line is printed: INFO:
>>>> RemoteInitialContextCreated{providerUri=http://192.....:8080/tomee/ejb}
>>>>
>>>> the war file is not deployed. Maybe cannot be used as remote? If I miss
>>>
>>> any
>>>>
>>>> attribute then maybe the fact that the file cannot be deployed should
>>>
>>> make
>>>>
>>>> fail the build?
>>>>
>>>> Alex
>>>>
>>>> --
>>>> +----------------------------------------------------------+
>>>>    Alex Soto Bueno
>>>>    www.lordofthejars.com
>>>> +----------------------------------------------------------+
>>
>>
>>
>
> --
>   Andy Gumbrecht
>
>   http://www.tomitribe.com
>   agumbrecht@tomitribe.com
>   https://twitter.com/AndyGeeDe
>
>   TomEE treibt Tomitribe! | http://tomee.apache.org
>

Re: Apache Maven plugin and remote deployer

Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Cool, I'll get that updated today. Thanks for pointing that out Alex, 
I'm always looking to improve the docs. You know you can edit the page 
also ;-) .

Andy.

On 18/07/2014 10:37, Alex Soto wrote:
> Cool it works, but documentation (
> http://tomee.apache.org/tomee-maven-plugin.html) is not updated with
> useBinaries attribute. I think it may be useful for other users :).
>
> Thanks :)
>
>
> 2014-07-18 10:18 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
>> Hi
>>
>> yes configuration doesn't seem enough for remote deployment. Default
>> is local deployment. You need to set <useBinaries> to true. It will
>> deploy path archive with the name of the file in the path. (context is
>> ignored in this case)
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
>>> Hello,
>>>
>>> Maybe I have misunderstood something but I am trying to deploy a war file
>>> to a remote tomEE, something like done with maven cargo plugin.
>>>
>>> Plugin configuration looks like:
>>>
>>> <plugin>
>>>    <groupId>org.apache.openejb.maven</groupId>
>>>    <artifactId>tomee-maven-plugin</artifactId>
>>>    <version>1.6.0.2</version>
>>>    <configuration>
>>>      <tomeeHost>${ip}</tomeeHost>
>>>      <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
>>>      <context>test</context>
>>>    </configuration>
>>> </plugin>
>>>
>>> and then I run
>>>
>>> mvn clean package tomee:deploy
>>>
>>> and although the build is success and next line is printed: INFO:
>>> RemoteInitialContextCreated{providerUri=http://192.....:8080/tomee/ejb}
>>>
>>> the war file is not deployed. Maybe cannot be used as remote? If I miss
>> any
>>> attribute then maybe the fact that the file cannot be deployed should
>> make
>>> fail the build?
>>>
>>> Alex
>>>
>>> --
>>> +----------------------------------------------------------+
>>>    Alex Soto Bueno
>>>    www.lordofthejars.com
>>> +----------------------------------------------------------+
>
>

-- 
   Andy Gumbrecht

   http://www.tomitribe.com
   agumbrecht@tomitribe.com
   https://twitter.com/AndyGeeDe

   TomEE treibt Tomitribe! | http://tomee.apache.org


Re: Apache Maven plugin and remote deployer

Posted by Alex Soto <as...@gmail.com>.
Cool it works, but documentation (
http://tomee.apache.org/tomee-maven-plugin.html) is not updated with
useBinaries attribute. I think it may be useful for other users :).

Thanks :)


2014-07-18 10:18 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:

> Hi
>
> yes configuration doesn't seem enough for remote deployment. Default
> is local deployment. You need to set <useBinaries> to true. It will
> deploy path archive with the name of the file in the path. (context is
> ignored in this case)
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
> > Hello,
> >
> > Maybe I have misunderstood something but I am trying to deploy a war file
> > to a remote tomEE, something like done with maven cargo plugin.
> >
> > Plugin configuration looks like:
> >
> > <plugin>
> >   <groupId>org.apache.openejb.maven</groupId>
> >   <artifactId>tomee-maven-plugin</artifactId>
> >   <version>1.6.0.2</version>
> >   <configuration>
> >     <tomeeHost>${ip}</tomeeHost>
> >     <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
> >     <context>test</context>
> >   </configuration>
> > </plugin>
> >
> > and then I run
> >
> > mvn clean package tomee:deploy
> >
> > and although the build is success and next line is printed: INFO:
> > RemoteInitialContextCreated{providerUri=http://192.....:8080/tomee/ejb}
> >
> > the war file is not deployed. Maybe cannot be used as remote? If I miss
> any
> > attribute then maybe the fact that the file cannot be deployed should
> make
> > fail the build?
> >
> > Alex
> >
> > --
> > +----------------------------------------------------------+
> >   Alex Soto Bueno
> >   www.lordofthejars.com
> > +----------------------------------------------------------+
>



-- 
+----------------------------------------------------------+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+----------------------------------------------------------+

Re: Apache Maven plugin and remote deployer

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi

yes configuration doesn't seem enough for remote deployment. Default
is local deployment. You need to set <useBinaries> to true. It will
deploy path archive with the name of the file in the path. (context is
ignored in this case)


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-07-18 9:38 GMT+02:00 Alex Soto <as...@gmail.com>:
> Hello,
>
> Maybe I have misunderstood something but I am trying to deploy a war file
> to a remote tomEE, something like done with maven cargo plugin.
>
> Plugin configuration looks like:
>
> <plugin>
>   <groupId>org.apache.openejb.maven</groupId>
>   <artifactId>tomee-maven-plugin</artifactId>
>   <version>1.6.0.2</version>
>   <configuration>
>     <tomeeHost>${ip}</tomeeHost>
>     <path>${project.build.directory}/test-tomee-0.0.1-SNAPSHOT.war</path>
>     <context>test</context>
>   </configuration>
> </plugin>
>
> and then I run
>
> mvn clean package tomee:deploy
>
> and although the build is success and next line is printed: INFO:
> RemoteInitialContextCreated{providerUri=http://192.....:8080/tomee/ejb}
>
> the war file is not deployed. Maybe cannot be used as remote? If I miss any
> attribute then maybe the fact that the file cannot be deployed should make
> fail the build?
>
> Alex
>
> --
> +----------------------------------------------------------+
>   Alex Soto Bueno
>   www.lordofthejars.com
> +----------------------------------------------------------+