Maven child modules not being built -


Pre> & lt; Module & gt; & Lt; Module & gt; WebApp & lt; / Module & gt; & Lt; Module & gt; WebService & lt; / Module & gt; & Lt; / Module & gt;

When I clear mvn at top level palm & amp; Establishes the required module of each child, however I am now trying to add a plugin (CodeHouse Weblogic) target to deploy WebApp. For weblog 10.3.4 eg Install MVN Clean Weblogic: For some reason it does not clean and install steps, but deploys if I run commands from within the webpage directory then it works and deploys Before it is installed, it is installed.

Am I missing something which will not run the stages of the child's life cycle when running a goal? Here is the command line output at the top level: 

  [ Information] Scans for projects ... [INFORMATION] The sequence of the construction of the reactor: [INFORMATION] SupportClient [INFO] SupportClient-WebServices [INFO] SupportClient-WebApp [INFO] Search for plug-ins with prefix: 'Weblogic' [INFO] org.apache.maven.plugins: Central [INFO] updates from org.codehaus.mojo Checking: Check for updates from central [INFO] ----------------- ------------------ ------------------------------- ----- [INFO] Building Support Client [INFO] Task-Segment: [ Clean, install, weblogic: deployed] [INFO] --------------------- ------------------ --------------------------------- [INFO] [Clean: Clean] [INFO] [site: Giving-descriptor ] [information] [install: install] [information] is installed C: \ development \ Destin8SupportClient \ Pomkxml to C: \ Users \ FinchajkHPH \ Km2 \ storage \ com \ mcpplc \ supportClient \ supportClient \ 1.0 \ supportClient-1.0.pom [h Denied] [Weblogic: deployment] [information] Weblogic deployment beginning with standards DeployMojoBase [adminServerHostName = localhost, adminServerProtocol = t3, adminServerPort = 8001, userId = xx, Password = ****, artifactPath = C: \ Development \ Destin8SupportClient / WebApp / target / WebApp.war, projectPackaging = war, name = support client webapp, targetNames = AdminServer, remote = false] [in FO] Weblogic deployment parameters [-adminurl, t3: // localhost: 8001, - username, xx, -password, xx, -name, support client-webapp, -targets, AdminServer, source, c: \ D applied with \ Destin8SupportClient /WebApp/target/WebApp.war, -deploy] option c Veblogik. Employer: -adminurl t3: // localhost: 8001- username xx- name support client webapp -targets AdminServer -source C: \ Development \ Destin8SupportClient / Vebpackej / target / Vebapkwar- Depreshn file 'C: \ Development \ Destin8SupportClient / WebApp / target / WebApp.war 'does not exist.    
  itemprop = "text"> 
 This is running weblogic: (! POM) module positioned at the top level . This goal can only be run on war or ear modules.  
 You need to force the target in the webpage sub-module that is to run in the established phase. It's currently running on the top-level (Pod!) Module.  
 For example, try adding the following in your weblogic configuration in the webpoint sub-module.  
  & lt; Executions & gt; & Lt; Execution & gt; & Lt; Step & gt; Install & lt; / Step & gt; & Lt; Goals & gt; & Lt; Goal & gt; Posted & lt; / Target & gt; & Lt; / Targets & gt; & Lt; / Execution & gt; & Lt; / Hanging & gt;   
 See also  
 If you want to run this at the end of your creation, then all other modules have been created, you need it either  
     
  •  Reorder your sub-modules, so WebApp is the last, then do the above  
  •  Or, add another sub-module that Will execute the final, which depends on your webpage's subdomain. Then, Veblogik plugin state to use the .war file to specify the applicant: maven.weblogic.war you might want to use the first goal is to get the direct target of the last sub-module Are there.

Comments

Post a Comment