Re: Why does Maven fail to compile my project occasionally?
Wayne Fay wrote > I rarely use any parameters as you have done here. Can you try a > simple "mvn clean install" and see how that goes? Also -U and -X may > be useful shortcuts for you to know about. > > And I agree with Stephen and Ron - Eclipse sometimes does helpful > things which produce hard to explain results. I would suggest either > using Eclipse or Maven CLI but not both simultaneously on the same > project (close Eclipse & just use Maven CLI, or just use Eclipse). > > Wayne Well, Eclipse is not installed on my daily-build server, so I guess it has nothing to do with Eclipse. ;-) I guess when Maven encounters the missing-dependency compilation error, it doesn't stop compiling immediately, and it tries its best to compile other unrelated modules. When I compile the whole project again, the missing dependent modules may appear in the local repository because the unrelated modules compiled previously have declared them as dependencies. Anyway, the long-lasting problem has been solved perfectly. Thank you guys! -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5786423.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does Maven fail to compile my project occasionally?
Wayne Fay wrote > Maven calls out to your system JDK to do the compilation step. With > the [ERROR] lines you provided previously, Maven is simply passing > along the error that was reported by javac. I bet, if you constructed > the proper javac call (which can be seen in Maven's logs if you use -X > for debug mode), you would see the same error produced without > involving Maven (or Jenkins) at all. > > IIRC you had some "cannot find symbol" errors. What do you expect > Maven to do about code defects reported by the Java compiler? Why are > you blaming Maven for this? After digging into the dependency tree described in each module's pom.xml for several days, I found that you're right. It's my fault, not Maven's. It's because my code depends some other modules which I didn't put it into pom.xml explicitly. And I'm adding them into the corresponding pom.xml. Thank you for directing me back to the right track! However, I'm curious that I succeed to compile the project after several compilation failure. How does it happen? I've passed the parameter 'clean install -Dmaven.test.skip=true --update-snapshots --batch-mode --fail-fast --debug -Dmaven.compiler.forceJavacCompilerUse=true -Dmaven.compiler.verbose=true' to Maven, but it doesn't get the same error when I compile the project the second time. And it mislead me to blame Maven ;-) Could anyone explain the somewhat weird behavior of Maven? Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5785441.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does Maven fail to compile my project occasionally?
Robert Scholte-4 wrote
> "My code is correct because I could successfully build the whole project
> in Eclipse again and again."
> This is 100% true. Within Eclipse you can manually add libraries.
> Actually, if you create your first JUnit test, Eclipse will ask if the
> JUnit4 library should be added. If you do so, it's added as an Eclipse
> library, but your Maven build won't have junit as a dependency, resulting
> in uncompilable tests.
I'm add all necessary dependent libraries that I know in pom.xml. It looks
weird and I've no idea about it. Could you help me to diagnose the problem
further?
Robert Scholte-4 wrote
> Did you open this file?
> AgentIdResourceMapIpHandle.java:[36,24] refers to line 36, column 24. Just
> open that file with notepad (copy/paste the fully qualified path to ensure
> you're picking up the correct file, not some copy)
> Where is that "symbol"/Class coming from? It seems to be on the classpath
> of your Eclipse, but it is not a dependency for Maven.
>
> Robert
I guess I've declared all dependent packages in the pom.xml.
The content of AgentIdResourceMapIpHandle.java is: (I omit the unimportant
lines)
> package com.xxx.system.devicecenter.network;
>
> import com.xxx.system.common.ResourceTypeDef;
> import com.xxx.system.network.IResourceMapIpHandle;
> // Imports some other packages...
>
> public class AgentIdResourceMapIpHandle implements IResourceMapIpHandle {
> @Override
> public Integer getType() {
> return ResourceTypeDef.TYPE_AGENT_ID;
> }
> // Implements other methods declared in interface
> IResourceMapIpHandle...
> }
And the content of the pom.xml for com.xxx.system.devicecenter is:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
>
> 4.0.0
>
>
>
>
>
> systempom
>
>
>
> com.xxx.system
>
>
>
> 1.0.0
>
>
>
>
>
> com.xxx.system
>
>
>
>
> devicecenter
>
>
>
> 1.0.0-SNAPSHOT
>
>
>
>
>
>
>
> com.xxx.system
>
>
>
> network
>
>
>
> 1.1.0
>
>
>
>
>
>
>
>
>
>
>
>
>
> maven-release-plugin
>
>
>
> 2.3.1
>
>
>
>
>
> https://192.168.49.48:8443/svn/cms/tag/cdms_plugins/com.xxx.core/com.xxx.core.jettyweb
>
>
>
> false
>
>
>
>
>
>
>
>
>
> maven-antrun-plugin
>
>
>
>
>
>
>
> maven-dependency-plugin
>
>
>
>
>
>
>
> maven-source-plugin
>
>
>
>
>
>
>
> org.apache.maven.plugins
>
>
>
> maven-jar-plugin
>
>
>
> 2.3.1
>
>
>
>
>
>
>
> package
>
>
>
>
>
>
>
>
>
>
>
>
>
> com.xxx.core.web.PluginActive
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> src/main/java/
>
>
>
>
>
> **/*.xml
>
>
>
>
>
>
>
>
>
> src/main/resources/
>
>
>
>
>
> *.xml
>
>
>
>
>
>
>
>
>
>
The content of pom.xml of com.xxx.system.systempom is:
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>
>
>
>
> pom
>
>
>
> com.xxx
>
>
>
> 1.0.0
>
>
>
>
>
> 4.0.0
>
>
>
> com.xxx.system
>
>
>
> systempom
>
>
Re: Why does Maven fail to compile my project occasionally?
Thanks for your suggestion. But I don't think it's the Jenkins fault because: I've written a Windows batch file to invoke Maven to build the project before I choose Jenkins as my daily build system. And at that time I got the same Maven error as I described in this thread. I'll post some other source code and POM files later. Please help me to diagnose my problem then. Thanks. P.S: I'll diagnose my POM configuration of package dependency, and I'll post the result here tomorrow. On Sun, Feb 16, 2014 at 2:59 AM, stephenconnolly [via Maven] < ml-node+s40175n5785002...@n5.nabble.com> wrote: > > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html > > Using the evil one makes Maven behave in ways that it doesn't intend to... > Please try with a FreeStyle job using a Maven Build step to see if it is > the evil job type causing issues for you > > -- Levski Weng -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5785057.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Why does Maven fail to compile my project occasionally?
Parsing POMs Downloaded artifact http://192.168.4.172:8081/nexus/content/groups/public/com/xxx/system/systempom/1.0.0-SNAPSHOT/maven-metadata.xml Downloaded artifact http://192.168.4.172:8081/nexus/content/groups/public/com/xxx/pom/1.0.0-SNAPSHOT/maven-metadata.xml Modules changed, recalculating dependency graph [managerpom] $ "C:\Program Files\Java\jdk1.6.0_35/bin/java" -Xms256m -Xmx1024m -cp "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-agent-1.4.jar;C:\Program Files\apache-maven-3.1.1\boot\plexus-classworlds-2.5.1.jar;C:\Program Files\apache-maven-3.1.1/conf/logging" jenkins.maven3.agent.Maven31Main "C:\Program Files\apache-maven-3.1.1" C:\Windows\Temp\jetty-0.0.0.0-80-jenkins.war--any-\webapp\WEB-INF\lib\remoting-2.33.jar "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-interceptor-1.4.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.4.jar" 52434 <===[JENKINS REMOTING CAPACITY]===>channel started log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\common\managerpom\pom.xml -Dmaven.repo.local=C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository clean install -Dmaven.test.skip=true --update-snapshots --batch-mode --fail-fast --debug -Dmaven.compiler.forceJavacCompilerUse=true -Dmaven.compiler.verbose=true Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 23:22:22+0800) Maven home: C:\Program Files\apache-maven-3.1.1 Java version: 1.6.0_35, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_35\jre Default locale: zh_CN, platform encoding: GBK OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from C:\Program Files\apache-maven-3.1.1\conf\settings.xml [DEBUG] Reading user settings from C:\.m2\settings.xml Ron Wheeler wrote > Where is the compiler version and options line? > > Ron -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5784947.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does Maven fail to compile my project occasionally?
Parsing POMs Downloaded artifact http://192.168.4.172:8081/nexus/content/groups/public/com/centerm/system/systempom/1.0.0-SNAPSHOT/maven-metadata.xml Downloaded artifact http://192.168.4.172:8081/nexus/content/groups/public/com/centerm/pom/1.0.0-SNAPSHOT/maven-metadata.xml Modules changed, recalculating dependency graph [managerpom] $ "C:\Program Files\Java\jdk1.6.0_35/bin/java" -Xms256m -Xmx1024m -cp "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-agent-1.4.jar;C:\Program Files\apache-maven-3.1.1\boot\plexus-classworlds-2.5.1.jar;C:\Program Files\apache-maven-3.1.1/conf/logging" jenkins.maven3.agent.Maven31Main "C:\Program Files\apache-maven-3.1.1" C:\Windows\Temp\jetty-0.0.0.0-80-jenkins.war--any-\webapp\WEB-INF\lib\remoting-2.33.jar "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven31-interceptor-1.4.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.4.jar" 52434 <===[JENKINS REMOTING CAPACITY]===>channel started log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\common\managerpom\pom.xml -Dmaven.repo.local=C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository clean install -Dmaven.test.skip=true --update-snapshots --batch-mode --fail-fast --debug -Dmaven.compiler.forceJavacCompilerUse=true -Dmaven.compiler.verbose=true Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 23:22:22+0800) Maven home: C:\Program Files\apache-maven-3.1.1 Java version: 1.6.0_35, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_35\jre Default locale: zh_CN, platform encoding: GBK OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from C:\Program Files\apache-maven-3.1.1\conf\settings.xml [DEBUG] Reading user settings from C:\.m2\settings.xml Ron Wheeler wrote > Where is the compiler version and options line? > > Ron > > For additional commands, e-mail: > users-help@.apache -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5784945.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does Maven fail to compile my project occasionally?
The parameters is missing, sorry: clean install -Dmaven.test.skip=true --update-snapshots --batch-mode --fail-fast --debug -Dmaven.compiler.forceJavacCompilerUse=true -Dmaven.compiler.verbose=true LevskiWeng wrote > After changing the compiler to javac, and add verbose parameters as the > following: -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5784861.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why does Maven fail to compile my project occasionally?
After changing the compiler to javac, and add verbose parameters as the following: the problem remains the same, but the console output reveals the compile procedure in details, could you help me to find what is missing? Thanks. BEGIN ... [DEBUG] Command line options: [DEBUG] -d C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\target\classes -classpath C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\target\classes;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\com\centerm\system\network\1.1.0\network-1.1.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\apache\ws\commons\schema\XmlSchema\1.4.5\XmlSchema-1.4.5.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-all\1.2.6\xfire-all-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-aegis\1.2.6\xfire-aegis-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\net\java\dev\stax-utils\stax-utils\20040917\stax-utils-20040917.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-ws-security\1.2.6\xfire-ws-security-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\jmock\jmock\1.0.1\jmock-1.0.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\xfire\opensaml\1.0.1\opensaml-1.0.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\bouncycastle\bcprov-jdk15\133\bcprov-jdk15-133.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\xml-security\xmlsec\1.3.0\xmlsec-1.3.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\wss4j\wss4j\1.5.1\wss4j-1.5.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\commons-discovery\commons-discovery\0.2\commons-discovery-0.2.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-core\1.2.6\xfire-core-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\javax\activation\activation\1.1\activation-1.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\javax\mail\mail\1.4\mail-1.4.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\wsdl4j\wsdl4j\1.6.1\wsdl4j-1.6.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\woodstox\wstx-asl\3.2.0\wstx-asl-3.2.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\commons-httpclient\commons-httpclient\3.0\commons-httpclient-3.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-java5\1.2.6\xfire-java5-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\xfire\xfire-jsr181-api\1.0-M1\xfire-jsr181-api-1.0-M1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-generator\1.2.6\xfire-generator-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-jaxb2\1.2.6\xfire-jaxb2-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\com\sun\xml\bind\jaxb-xjc\2.0.1\jaxb-xjc-2.0.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\com\sun\xml\bind\jaxb-impl\2.0.1\jaxb-impl-2.0.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-xmlbeans\1.2.6\xfire-xmlbeans-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\xmlbeans\xbean\2.2.0\xbean-2.2.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-annotations\1.2.6\xfire-annotations-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\commons-beanutils\commons-beanutils\1.7.0\commons-beanutils-1.7.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\commons-attributes\commons-attributes-api\2.1\commons-attributes-api-2.1.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\qdox\qdox\1.5\qdox-1.5.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\org\codehaus\xfire\xfire-jaxws\1.2.6\xfire-jaxws-1.2.6.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\javax\xml\ws\jaxws-api\2.0\jaxws-api-2.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\javax\xml\bind\jaxb-api\2.0\jaxb-api-2.0.jar;C:\Program Files (x86)\Jenkins\jobs\CDMS-web-server\workspace\.repository\javax\xml\bind\jsr173_api\1.0\js
Re: Why does Maven fail to compile my project occasionally?
Sorry for that, I forgot to translate all the Chinese characters into English, those Chinese characters have the same meaning of 'Cannot find the symbol'. I will change the compilers to javac and see what will happen. I'll post my result later. The reason why I'm deleting my local repository is that when I delete a .java file in my project when developing, the maven treats the module as unmodified and skips to the next module. And I use this workaround to make sure all the modules are up-to-date. Ron Wheeler wrote > Since the error message is in Chinese it is a bit difficult to tell. > Why are you deleting your local repo? > Is it possible that you are using different compilers? > How is TYPE_AGENT_ID source com compiles - same pom? > > On 14/02/2014 9:12 AM, Levski Weng wrote: >> Hello, I'm new to Maven. Currently I use Maven 3.1.1 to compile my >> project >> (using Jenkins). But occasionally, maven report error messages like the >> following: >> >> Begin of the console output >> ... >> >> [INFO] Compiling 132 source files to C:\Program Files >> (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\target\classes >> >> [INFO] >> -[ERROR] >> COMPILATION ERROR : [INFO] >> -[ERROR] >> \Program Files >> (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\src\main\java\com\xxx\system\devicecenter\network\AgentIdResourceMapIpHandle.java:[36,24] >> 找不到符号Symbol： Variable TYPE_AGENT_ID >> Location： Class com.xxx.system.common.ResourceTypeDef[ERROR] \Program >> Files >> (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\src\main\java\com\xxx\system\devicecenter\network\AgentUuidResourceMapIpHandle.java:[38,24] >> 找不到符号Symbol： Variable TYPE_AGENT_UUID >> Location： Class com.xxx.system.common.ResourceTypeDef[ERROR] \Program >> Files >> (x86)\Jenkins\jobs\CDMS-web-server\workspace\src\com.xxx.system\com.xxx.system.devicecenter\src\main\java\com\xxx\system\devicecenter\network\AgentIdAgentUpdateMapIpHandle.java:[32,24] >> 找不到符号Symbol： Variable TYPE_COMPUTER_ID_FOR_UPDATE >> Location： Class com.xxx.system.common.ResourceTypeDef >> [INFO] 3 errors >> [INFO] - >> ... >> >> End of the console output >> >> However, when I build the Jenkins job again without any modification, >> maven builds the project successfully. >> My code is correct because I could successfully build the whole >> project in Eclipse again and again. >> >> I use the following Maven parameters: >> clean install -Dmaven.test.skip=true --update-snapshots --batch-mode >> --fail-fast --debug >> >> I could reproduce the scenario by rebuild the project after deleting >> all the sub-folders and files in the maven local repository: >> >> .repository/com/xxx/ >> >> I'm confused about this, and on internet, nobody seems to have the >> same problem. >> >> Any suggestions? Thanks in advanced. >> >> -- >> >> Levski Weng >> >> >> >> >> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: > rwheeler@ > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > - > To unsubscribe, e-mail: > users-unsubscribe@.apache > For additional commands, e-mail: > users-help@.apache -- View this message in context: http://maven.40175.n5.nabble.com/Why-does-Maven-fail-to-compile-my-project-occasionally-tp5784849p5784853.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
