Hi:
 
But if I do try running the command from the EAR directory, then all the
dependencies would have to be transferred to the EAR POM.xml... which
would be rather inconvenient.... 

________________________________

From: Scott Ryan [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 31, 2007 12:57 PM
To: Maven Users List
Cc: Vaidya, Supriya A (US - Chicago)
Subject: Re: Deploying EAR project to Weblogic


Try running the deploy mojo from the ear directory.  It is reading the
project type to figure out what to deploy and it is confused since your
pom.xml seems to have project type of pom rather than ear.  You can also
set the parameters manually and it will not try to guess but it will
need help in determining the project type and location of the
deployable. 

Scott

On Jul 31, 2007, at 10:21 AM, Vaidya, Supriya A ((US - Chicago)) wrote:


        
        Sorry - wrong POMs were attached previously - here are the right
ones, that generate the error....
         

________________________________

        From: Vaidya, Supriya A (US - Chicago) 
        Sent: Tuesday, July 31, 2007 11:11 AM
        To: 'Maven Users List'
        Subject: Deploying EAR project to Weblogic
        
        
        Hi:
         
        I have a project structure such that an EAR is created
containing a WAR, and an EJB JAR. Thus, each module has its own
directory and its own pom. THe parent directory (say projectOverAll) has
a pom with packaging = pom.
         
        Now, the project packages successfully - mvn clean install works
fine. I get my .ear file. I now want to deploy this to weblogic. I
understand that I have to use the maven-weblogic plugin. I tried
adding/installing all the dependencies into the parent POM as required
for teh plugin. and then did a mvn weblogic:appc on the parent
directory. However, this throws teh following error - 
        
         
        Downloading:
http://repo1.maven.org/maven2/web-maven/web-maven/1.0/web-maven-1.0
        .pom
        [INFO] [weblogic:appc]
        [INFO]
------------------------------------------------------------------------
        [ERROR] FATAL ERROR
        [INFO]
------------------------------------------------------------------------
        [INFO] Unsupported project packaging pom
        [INFO]
------------------------------------------------------------------------
        [INFO] Trace
        java.lang.IllegalArgumentException: Unsupported project
packaging pom
                at
org.codehaus.mojo.weblogic.util.WeblogicMojoUtilities.updateArtifactN
        ame(WeblogicMojoUtilities.java:109)
                at
org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:144)
                at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
        nManager.java:443)
                at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
        ultLifecycleExecutor.java:539)
                at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
        Goal(DefaultLifecycleExecutor.java:493) 
         
        Is the expectation different for deployment? How do I deploy
this on my webogic 9.2 server? Attached for reference is the parent POM
and EAR pom with all the dependencies (modified to hide some details). 
         
        Thanks and regards,
        Supriya


        This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message. 
        
        
        Any disclosure, copying, or distribution of this message, or the
taking of any action based on it, is strictly prohibited. [v.E.1]
        
        <pom for EAR.xml>
        
        <pom for project.xml>
        
---------------------------------------------------------------------
        To unsubscribe, e-mail: [EMAIL PROTECTED]
        For additional commands, e-mail: [EMAIL PROTECTED]


Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]


Reply via email to