I have my project setup like this:

connect
------ pom.xml (POM)
------ connect-ear
------------ pom.xml (EAR)
------ connect-web
------------ pom.xml (WAR)
------ connect-util
------------ pom.xml (JAR)
------ tia-web
------------ pom.xml (WAR)

I have the connect pom.xml (POM) configured like this:

<modules>
<module>connect-util</module>
<module>connect-web</module>
<module>tia-web</module>
<module>connect-ear</module>
</modules>

And the connect-ear pom.xml (EAR) configured like this:

<parent>
<groupId>warnerwebware</groupId>
<artifactId>connect</artifactId>
<version>1.0</version>
</parent>
<artifactId>connect-ear</artifactId>
<packaging>ear</packaging>
<name>Connect Ear</name>

Then I run mvn install on the connect (POM) project to build all 4
sub-projects.  Is this the correct way to have it setup to use this was
plugin?  Or do I need to change how I have it setup to get the plugin to
work (i.e. have the EAR project named connect instead of connect-ear)?

Thanks Bobby

On Tue, Jan 5, 2010 at 3:05 PM, Bobby Warner <[email protected]> wrote:

> Here is the build section of my connect EAR POM.
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.0.2</version>
> <configuration>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <version>1.4</version>
> <modules>
> <webModule>
> <groupId>warnerwebware</groupId>
> <artifactId>connect-web</artifactId>
> <contextRoot>/</contextRoot>
> </webModule>
> <webModule>
> <groupId>warnerwebware</groupId>
> <artifactId>tia-web</artifactId>
> <contextRoot>/tia</contextRoot>
> </webModule>
> </modules>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>was6-maven-plugin</artifactId>
> <version>1.1.1</version>
> <executions>
> <execution>
> <id>integration-test</id>
> <phase>integration-test</phase>
> <goals>
> <goal>wsUninstallApp</goal>
> <goal>installApp</goal>
> <goal>wsStartApp</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <verbose>true</verbose>
> <wasHome>${was61home}</wasHome>
> </configuration>
> </plugin>
> </plugins>
> <finalName>connect</finalName>
> </build>
>
>
>
> On Tue, Jan 5, 2010 at 2:26 PM, quints quad <[email protected]> wrote:
>
>> Could we see your connect ear's pom file?
>>
>> I see three goals that you're running:  uninstall app, install app, and
>> start app.  For now, I'm not worried about the first and the last.  The
>> first error could just mean it's not deployed (and thus, not found).  The
>> last error could be because of the second error (it can't start something
>> that wasn't installed).
>>
>> By default, the was6 plugin uses ${project.build.finalName} as the name of
>> the application that you'll deploy.  Based on that and your log, it seems
>> like you've added the plugin execution to the "connect" module, and not the
>> "connect ear" module?  Or your ear is called connect-ear.ear, and not just
>> connect?
>>
>>
>>
>> The first error is not a big deal...it On Tue, Jan 5, 2010 at 2:19 PM,
>> Wayne Fay <[email protected]> wrote:
>>
>>> > help me figure out what is wrong?  I tried googling for this (Java
>>> returned:
>>> > 105) for quite sometime without any luck.  Thanks, Bobby
>>>
>>> That's not the error, this is:
>>>
>>> [INFO]   [wsadmin] WASX7017E: Exception received while running file
>>> "C:\DOCUME~1
>>> \e78239\LOCALS~1\Temp\wsant5636jacl"; exception information:
>>> com.ibm.ws.scriptin
>>> g.ScriptingException: WASX7280E: An application with name "connect" does
>>> not exi
>>> st.
>>>
>>> I don't use WAS and have no experience with this plugin but perhaps
>>> that means something to you or other WAS developers?
>>>
>>> Wayne
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>

Reply via email to