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
>
>
>
