I think you should try one of the Cargo mailing lists:
http://cargo.codehaus.org/Mailing+Lists
Here on the Maven user list we're more of users of Cargo than developers of
it.
/Anders
On Fri, Feb 19, 2010 at 17:30, Jim Collings wrote:
> This looks pretty complex... then again maybe I had better
This looks pretty complex... then again maybe I had better look again
after I've had more sleep. ;-)
On Fri, Feb 19, 2010 at 6:51 AM, Jim Collings wrote:
>> Cargo supports Jetty and Tomcat, so it's not only for full Java EE
>> containers no.
>>
>> /Anders
>
>
> OK, then I'll have a closer look.
>
> Cargo supports Jetty and Tomcat, so it's not only for full Java EE
> containers no.
>
> /Anders
OK, then I'll have a closer look.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: us
Cargo supports Jetty and Tomcat, so it's not only for full Java EE
containers no.
/Anders
On Thu, Feb 18, 2010 at 22:32, Jim C. wrote:
> On 2/18/2010 3:20 PM, Anders Hammar wrote:
> > By writing a container extension for Cargo?
> > http://cargo.codehaus.org/Adding+a+container
> >
> > /Anders
>
On 2/18/2010 3:20 PM, Anders Hammar wrote:
> By writing a container extension for Cargo?
> http://cargo.codehaus.org/Adding+a+container
>
> /Anders
I was looking at that. Do you know if it is only for full J2EE
containers? From the looks of what I saw, the answer seemed to be "Yes".
Might bear f
> Is there a plugin out there that I've not yet found which will deploy
> to Webserver 7 in a more friendly/agnostic fashion or will I have to
> use a bunch of exec commands to utilize the command line interface for
> Webserver 7?
Perhaps ask Sun/Oracle or the proper Sun Webserver Users list for a
By writing a container extension for Cargo?
http://cargo.codehaus.org/Adding+a+container
/Anders
On Thu, Feb 18, 2010 at 20:57, Jim Collings wrote:
> For those just starting this, I'm automating a deployment of a
> two-part project that has one part on Sun Webserver 7 and another on
> Weblogic.
On Thu, Feb 18, 2010 at 2:56 PM, Wayne Fay wrote:
>> Profiles? Aren't those used for different platforms? I think you
>> mistake my meaning. We have a project that has two subcomponents, one
>> of which runs on a full J2EE container, Weblogic and the other which
>> runs on Sun Webserver 7.
>
> An
For those just starting this, I'm automating a deployment of a
two-part project that has one part on Sun Webserver 7 and another on
Weblogic. Each dev should be able to have his or her own special
configuration so in the previous thread I figured out how to load
stuff from a centralized properties
> Profiles? Aren't those used for different platforms? I think you
> mistake my meaning. We have a project that has two subcomponents, one
> of which runs on a full J2EE container, Weblogic and the other which
> runs on Sun Webserver 7.
Any time you are thinking "I need to do X for some builds of
> Profiles are used to just swap between configurations, run plugins that
> normally don't run, etc.
>
> Stuff you'd like to be able to switch on and off.
>
> If your goal is to just load properties, that seems like a good approach.
>
> Now if you had a properties file for each server type, then y
Re: Deployment Properties file
>> all have their stuff in different places. What I want is a properties
>> file that the dev can stash in his home directory which will be read
>> by Maven to establish installation parameters and JVM options for each
>
> Maybe use settings.xml
>> all have their stuff in different places. What I want is a properties
>> file that the dev can stash in his home directory which will be read
>> by Maven to establish installation parameters and JVM options for each
>
> Maybe use settings.xml in user home dir? Otherwise this calls for a profile
On Thursday February 18 2010, Jim Collings wrote:
> OK, so I've a project that uses two different containers. Sun
> Webserver 7 and Weblogic. I'm trying to set up an automated
> deployment that is easily configurable for the individual
> developers, cause they all have their stuff in different plac
> all have their stuff in different places. What I want is a properties
> file that the dev can stash in his home directory which will be read
> by Maven to establish installation parameters and JVM options for each
Maybe use settings.xml in user home dir? Otherwise this calls for a profile.
Way
OK, so I've a project that uses two different containers. Sun
Webserver 7 and Weblogic. I'm trying to set up an automated deployment
that is easily configurable for the individual developers, cause they
all have their stuff in different places. What I want is a properties
file that the dev can sta
16 matches
Mail list logo
