Jason,
Thinking more about this, why do we even have the "defaultAssemblyId"
param there ? Why not have set the default-value on the "assemblyId"
parameter to be jetty ?
Having two params doing almost the same thing seems not only redudant
but also confusing. Am I missing something else here ?
Cheers
Prasad
On 12/1/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
The recommended and documented way to change the assembly is using
assemblyId, as in:
mvn -DassemblyId=tomcat
NOT -DdefaultAssemblyId as listed below. Also, while assemblyArchive
exists it is not recommended to use.
--jason
On Dec 1, 2006, at 6:50 AM, Prasad Kashyap wrote:
> Simple answer:
> ----------------------
> That configuration is set in the trunk/pom.xml. Grep for
> "defaultAssemblyId".
>
> To change it, pass any of of the following params to the 'mvn'
> execution
> -DdefaultAssemblyId="tomcat"
> or
> -DassemblyArchive=/path/to/tomcat/binary.zip
> or
> -DgeronimoHome=/path/to/tomcat/install/dir
>
>
> In-depth answer:
> -----------------------
> This configuration belongs to the geronimo-maven-plugin and is used by
> it's start-server and iinstall-assembly goals.
>
> http://geronimo.apache.org/maven/server/maven-plugins/geronimo-
> maven-plugin/install-assembly-mojo.html
>
> The java file is InstallerMojoSupport.java under geronimo-maven-
> plugins.
>
> It's usage is as follows -
> http://geronimo.apache.org/maven/server/maven-plugins/geronimo-
> maven-plugin/usage/server.html
>
> Cheers
> Prasad
>
> On 12/1/06, Krishnakumar B <[EMAIL PROTECTED]> wrote:
>> hi Prasad,
>>
>> Thanks.
>>
>> Another query. How to get the testsuites to use a tomcat assembly? It
>> always picks jetty assembly by default to run the tests.
>>
>> Regards
>> Krish
>>
>> On 11/30/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
>> > Hi Krishna,
>> >
>> > You are not limited to the browser (console) related tests. You can
>> > test almost anything as long as the tests are written in JUnit or
>> > TestNG.
>> >
>> > Hopefully soon, we should be able to drop the ejbcontainer-
>> testsuite
>> > into it. You will see that this will not have anything to do
>> with the
>> > browser.
>> >
>> > Cheers
>> > Prasad
>> >
>> > On 11/30/06, Krishnakumar B <[EMAIL PROTECTED]> wrote:
>> > > Hi,
>> > >
>> > > I am trying to understand how the test framework works and
>> what kind
>> > > of integration test scenarios can be covered using the test
>> suite. I
>> > > have some doubts that may sound stupid and they are listed below.
>> > >
>> > > * Can this be used only for browser(console) related tests.
>> > > * What kind of functionality can i test using the suite. Is it
>> > > components like deployment, console only or other features in the
>> > > server like SSO, Virtual hosts, Database Pools etc.
>> > >
>> > > ( For e.g - If i want to test SSO can i write a test case and
>> use a
>> > > suitable app with the test suite to check all options in SSO)
>> > >
>> > > Regards
>> > > Krish
>> > >
>> >
>>
