This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 222618 - running a maven-generated ear twice in a row causes failure
Summary: running a maven-generated ear twice in a row causes failure
Status: RESOLVED DUPLICATE of bug 210857
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 7.2.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-22 18:26 UTC by primeq
Modified: 2012-11-22 20:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description primeq 2012-11-22 18:26:06 UTC
to replicate:
1 - stop Weblogic
2 - clean "target" directory
3 - build POJOs, EJB, WAR, and then assemble EAR.
4 - run the new EAR in Netbeans - works as expected.
5 - right click and "Run" same EAR. Netbeans tries to run, but after the build the deploy fails immediately (every time, until WLS is stopped - then the next run succeeds)

<project-base-dir>\xyz-ear\target\wldeploy\xyz-ear_ear_1.0\xyz-web-1.0.war\index.jsp (The system cannot find the path specified).

I have verified the path exists up to here
<project-base-dir>\xyz-ear\target\wldeploy\

background info:
- this happens every single time. The only thing I can do is 
  a) kill Weblogic
  b) clean & rebuild
  c) right-click Run again

- Does not occur with Netbeans 6.9.1.
- what also works every time is stopping WLS (Services tab) and running again
- these are rock-solid Maven builds - part of large-scope project in progress for  the last 2 years (point being "it's not the Maven build")
Comment 1 Petr Hejl 2012-11-22 19:15:21 UTC
I believe this is duplicate of #210857, right Martin? primeq can you verify it is fixed in 7.3?

*** This bug has been marked as a duplicate of bug 210857 ***
Comment 2 Martin Janicek 2012-11-22 20:04:00 UTC
(In reply to comment #1)
> I believe this is duplicate of #210857, right Martin?

Yep, 219795 looks quite identical.