Does this latter error have anything to do withteh fact that I am using
JDK 1.6 Update 2?
________________________________
From: Vaidya, Supriya A (US - Chicago)
Sent: Tuesday, July 31, 2007 1:19 PM
To: 'Scott Ryan'
Subject: RE: Deploying EAR project to Weblogic
Hi Scott:
I have 4 directories that I deal with:
1. The parent directory - containing the parent POM.xml: this is the
file that contains all the dependencies
2. The EAR directory - containign teh EAR POM.xml - references teh
Parent POM.
3. The EJB directory - containing the EJB POM.xml - references the
Parent POM
4. The WAR directory - containing teh WAR POM.xml - references teh
Parent POM.
In order to build my EAR (which contains the WAR, and the JAR) - I do a
mvn clean install in my parent directory.
The mvn weblogic:appc command fails at the same directory, with the
error mentioned below. From what you seem to be telling me, it appears
that weblogic:appc needs the EAR packaging type to initialize
successfully. So here is what I did.
1. Open the parent directory - run the mvn clean install command
2. cd-ed to the EAR directory
3. ran teh mvn weblogic:appc comand.
Here is the eror that I now get -
--------------- nested within: ------------------
weblogic.utils.compiler.ToolFailureException: Provider
javax.xml.stream.XMLInputFactory could not be instantiated:
java.lang.InstantiationException - with nested exception:
[javax.xml.stream.FactoryConfigurationError: Provider
javax.xml.stream.XMLInputF
actory could not be instantiated: java.lang.InstantiationException]
at
weblogic.application.compiler.FlowDriver.handleStateChangeException(F
lowDriver.java:53)
at
weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:37
)
Did I fail to include the right dependencies in teh parent POM? Attached
here again for your referrence...
Thank you for taking the time to look into this!!
Regard,
Supriya
________________________________
From: Scott Ryan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 31, 2007 1:04 PM
To: Vaidya, Supriya A (US - Chicago)
Subject: Re: Deploying EAR project to Weblogic
Not sure what you mean by that but if the ear is valid and the ear pom
has the other pom as its parent then all is fine. I have hundreds of
projects set up this way and they all work fine. Let me know more
details and I can walk you though the best practices.
Scott Ryan
On Jul 31, 2007, at 11:58 AM, Vaidya, Supriya A (US - Chicago) wrote:
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]
Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]
