I did look at dpkg as we use debian however the dpkg maven plugin will
only generate jar libraries. It wont make packages for installing a war.
I would be very grateful for a pom skeleton.
Thanks David
On 25 Feb 2009, at 00:14, Dave Whitla wrote:
> What I'm saying is you aren't meant to use maven as a deployment
> tool - or deployment artifact dependency management tool - that is
> what RPM, YUM, pkg, dpkg, apt, port etc are for depending on your
> operating system.
> But I can have a crack at a POM for you - it just seems kinda
> pointless to invest time in what is clearly not a good idea.
>
> On Feb 25, 2009, at 12:20 AM, David Hunnisett wrote:
>
>> Thanks for the quick response.
>> I don't have a deployment pom at the moment as I can work out
>> where to start!
>> The development poms for the two web apps work correctly in the way
>> you describe for local deployments during the first part of the
>> development cycle.
>>
>> could you outline how you would deploy a collection of web apps to
>> a local glassfish server ideally using maven to manage the versions.
>>
>> Thanks again David
>>
>> On 24 Feb 2009, at 03:18, Dave Whitla wrote:
>>
>>> Hi David,
>>>
>>> I think I understand what you are trying to accomplish.
>>> All of what you are asking is possible - through a combination of
>>> configurations of the maven-war-plugin and maven-glassfish-plugin.
>>>
>>> There are some issues however.
>>> The maven-glassfish-plugin is intended purely as a development/
>>> continuous-integration tool.
>>> That is it is only designed to be invoked during building and
>>> testing of glassfish artifacts during the developer lifecycle.
>>> For this reason its focus is more on integrating the configuration
>>> and run-control of glassfish domains into the inner development
>>> loop.
>>> I think there are better ways to accomplish what you are trying to
>>> do - either by scripting asadmin or by using JSR-88 directly.
>>>
>>> If you send me your current pom.xml (which I assume isn't doing
>>> what you want) I will make corrections.
>>>
>>> Dave
>>>
>>> On Feb 24, 2009, at 1:26 AM, David Hunnisett wrote:
>>>
>>>> Hi
>>>> Thanks very much for the plugin its proving to be very useful so
>>>> far.
>>>> I have a few questions and clarifications on the usage.
>>>> Am I correct in my understanding that the plugin can only be used
>>>> to deploy onto the local machine?
>>>> There is currently no way to deploy to a remote glassfish server.
>>>>
>>>> With this in mind I am trying to use the plugin to control
>>>> deployment when the web applications have already been built. I
>>>> hope I have been able to describe this in the following
>>>> deployment scenario:
>>>>
>>>>
>>>> I have a two independent development and two independent
>>>> production servers.
>>>> Each server does not ever communicate with any other server, they
>>>> are stand alone not part of any fall over or load balancing.
>>>>
>>>> Both of the production servers must run the same code.
>>>> Both of the development servers will typically run the same code.
>>>>
>>>> The code for both production and development is built on a third
>>>> (build) server.
>>>> The code consists of a number standalone war files that access a
>>>> common database structure (the database is stored on the server
>>>> i.e. there are four databases).
>>>> For the rest of this I will refer to the web applications as
>>>> app-1.war and app-2.war.
>>>>
>>>> I would like to have a deployment pom that I can use to deploy to
>>>> a local server (either development or production) a specific
>>>> collection of app-1.war and app-2.war.
>>>>
>>>> For the development server this would point to the -snapshot
>>>> revision of app-1.war and app-2.war.
>>>>
>>>> running mvn glassfish:deploy should locally deploy the app-1.war-
>>>> SNAPSHOT to a domain called app-1 and app-2.war-SNAPSHOT to a
>>>> domain called app-2.
>>>> The SNAPSHOT version should be downloaded from our local maven
>>>> repository (running on the build server).
>>>>
>>>> For production specific versions of app-1 and app-2 would be
>>>> referenced.
>>>>
>>>> Running mvn glassfish:deploy should locally deploy the
>>>> app-1.war-1.4.1 to a domain called app-1 and app-2.war-1.1.1 to a
>>>> domain called app-2
>>>>
>>>> The specific versions should again be downloaded from our local
>>>> maven repository (running on the build server).
>>>>
>>>>
>>>> To deploy I new version to production I would them simply change
>>>> the version numbers in the production pom and log into each
>>>> production server and run mvn glassfish:deploy with the new pom.
>>>>
>>>> If this is possible could some one provide an example deployment
>>>> pom.
>>>>
>>>> Thanks David
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> David Hunnisett
>>>> ETL Solutions Ltd
>>>> Tel:01248 675070
>>>>
>>>> daveh_at_etlsolutions.com
>>>> ***************************************************************************
>>>>
>>>> ETL Solutions Ltd
>>>> Registered in England and Wales No 04327381
>>>> Registered Office: Unit 4, Glanypwll Workshops, Blaenau
>>>> Ffestiniog, Gwynedd LL41 3NW
>>>>
>>>>
>>>> ***************************************************************************
>>>>
>>>> Confidentiality Statement
>>>>
>>>> This communication is for informational purposes only. Any
>>>> comments, statements, views or opinions made herein are
>>>> solely those of the author and do not necessarily represent those
>>>> of ETL Solutions Ltd. This transmission may contain information
>>>> that is privileged, confidential, legally privileged, and/or
>>>> exempt from disclosure under applicable law.
>>>> If you are not the intended recipient, you are hereby notified
>>>> that any disclosure, copying, distribution, or use of the
>>>> information contained herein (including any reliance thereon) is
>>>> STRICTLY PROHIBITED. If you received this e-mail in error,
>>>> please notify the sender by reply email immediately and
>>>> permanently delete the original and any copy of the e-mail,
>>>> attachment(s) and any printout thereof. Thank you.
>>>>
>>>> ***************************************************************************
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_maven-glassfish-plugin.dev.java.net
>>>> For additional commands, e-mail: users-help_at_maven-glassfish-plugin.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_maven-glassfish-plugin.dev.java.net
>>> For additional commands, e-mail: users-help_at_maven-glassfish-plugin.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_maven-glassfish-plugin.dev.java.net
>> For additional commands, e-mail: users-help_at_maven-glassfish-plugin.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_maven-glassfish-plugin.dev.java.net
> For additional commands, e-mail: users-help_at_maven-glassfish-plugin.dev.java.net
>