search

faresd / appengine-maven-plugin

Automatically exported from code.google.com/p/appengine-maven-plugin
Apache License 2.0
0 stars 0 forks source link

ear file being built twice #38

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I have a project that is setup very similar to this one 
(https://github.com/GoogleCloudPlatform/appengine-modules-sample-java), except 
I just have one war and one 'interfaces' project.

I'm trying to do my build with this:

mvn --projects tick-i,tick-webapp install
cd tick-ear
mvn appengine:update

The first mvn command works just fine. When it comes to the second one 
(appengine:update), things go down hill...

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Voost - interface ................................. SUCCESS [2.710s]
[INFO] Voost - webapp .................................... SUCCESS [1:18.791s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:21.655s
[INFO] Finished at: Tue Sep 10 20:52:57 PDT 2013
[INFO] Final Memory: 35M/415M
[INFO] ------------------------------------------------------------------------
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Voost - ear 1.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> appengine-maven-plugin:1.8.4:update (default-cli) @ voost-tick-ear 
>>>
Downloading: 
http://repo.maven.apache.org/maven2/st/voo/voost-tick/1.0/voost-tick-1.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.289s
[INFO] Finished at: Tue Sep 10 20:53:01 PDT 2013
[INFO] Final Memory: 8M/128M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project voost-tick-ear: Could not resolve 
dependencies for project st.voo.tick:voost-tick-ear:ear:1.0: Failed to collect 
dependencies at st.voo.tick:tick-webapp:war:1.0: Failed to read artifact 
descriptor for st.voo.tick:tick-webapp:war:1.0: Could not find artifact 
st.voo:voost-tick:pom:1.0 in central (http://repo.maven.apache.org/maven2) -> 
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Now, if I change my build to do something like this:

mvn install
cd tick-ear
mvn appengine:update

Things work just fine.

The problem with that though is that the ear file essentially gets built twice 
if I do that because mvn appengine:update runs the maven-ear-plugin again. I'd 
love to avoid having to do that.

Original issue reported on code.google.com by latch...@gmail.com on 11 Sep 2013 at 4:08