Re: Adding dependency management to parent pom causes errors
The problem is resolved I started with a minimal child pom and ran mvn dependency:analyze - then added dependencies until I had all the relevant dependencies I no longer get the compile failure I attempted to identify the differences between the 'good' and 'bad' poms, but without success Thanks to all who replied Geoff -- View this message in context: http://maven.40175.n5.nabble.com/Adding-dependency-management-to-parent-pom-causes-errors-tp5784035p5784760.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 is dependency:analyze lying to me?
Hello, you see this a lot with runtime dependencies (which should probably be ignored during analyze anyway), so I mostly just ignore these in the output. It would be a cool thing, if you could suppress warnings for gavs directly in the analyze goal, so you see new stuff coming up more easily. Regards Mirko -- Sent from my mobile On Feb 13, 2014 11:01 PM, Wayne Fay wayne...@gmail.com wrote: This may fall into the “How the hell is Maven supposed to know?” category, Yes, it most certainly does. [WARNING] org.springframework.security:spring-security-taglibs:jar:3.1.1.RELEASE:compile ... Anyway, not sure if the plugin can be configured to detect these kind of things, but a guy can dream, can’t he?? You would need to write code that performs the following tasks: 1. look in jar files related to dependencies 2. find taglib files and other configuration files [each file type needs its own parser] 3. store tag uris that are discovered along with the associated jar 4. check those tag uris vs what is in your code (keep in mind some may be in config files you wrote, so gotta parse those too - more code to write) 5. output the list of jars (dependencies) which are not actually used in code or config This is nontrivial, so no one has done it. I'm sure we'd take a contribution if you did the work. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to minimize quantity of profiles in pom.xml file
I need to build project for many kinds of environment so i need a lot of profiles with settings for this env. There is a cutted module pom.xml - pom.xml file http://www.mediafire.com/view/47gt5jiegta7auq/pom.xml -- View this message in context: http://maven.40175.n5.nabble.com/How-to-minimize-quantity-of-profiles-in-pom-xml-file-tp5784478p5784835.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: How to minimize quantity of profiles in pom.xml file
fred wrote:
I need to build project for many kinds of environment so i need a lot of
profiles with settings for this env.
There is a cutted module pom.xml - pom.xml file
http://www.mediafire.com/view/47gt5jiegta7auq/pom.xml
All you need in the profile is a simple property:
= %
build
plugins
...
plugin
... your plugin ...
configuration
... your configuration ...
targetURLhttp://${profile.host}:
${port}/crx/packmgr/service.jsp/targetURL
/configuration
...
/plugin
/plugins
...
/build
profiles
profile
idauto-deploy/id
properties
profile.host${host}/profile.host
/properties
/profile
profile
iddev/id
properties
profile.host${dev.host}/profile.host
/properties
/profile
...
/profiles
= %
As rule of thumb: Just put the stuff into the profile that *is* actually
different.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
Even though Hervé has given the best answer, I thought I'd chime in and say that The Maven Way would probably have you add the additional dependency at the plugin level, and not the configuration.reportPlugins.plugin level.. So, sorry, but you were wrong twice. :-) On Thu, Feb 13, 2014 at 10:34 AM, Alex Potsides a...@achingbrain.net wrote: plugin artifactIdmaven-site-plugin/artifactId version3.3/version configuration reportPlugins plugin groupId../groupId artifactId../artifactId version../version dependencies dependency artifactId../artifactId groupId../groupId ... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter
On 13/02/2014 4:23 PM, Barrie Treloar wrote: On 13 February 2014 23:25, Ron Wheeler rwhee...@artifact-software.com wrote: Good point. After I fixed the spelling, it works fine. Is was a great help to have a second set of eyes to find my stupid mistakes. It would have been nice to have a better error message. [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'com.artifact-software.taw:taw-localized-iumessage-ws:war' o 'com.artifact-software.taw:taw-dataccess-ws:war' A file not found would have been more helpful. I tested to see if the file was not found by adding a deliberate spelling mistake but I drew the wrong conclusion when I got the same error message. You're welcome to make a patch :) You probably don't want me writing patches! I could probably drive your car but you would not be very happy if I tried to help you by reprogramming your engine control unit to get more horsepower. I person who is using Maven to build tar files and webapps is not necessarily the best person to start mucking with internals. I dont think it is working with files at the point it is doing all the checking, especially if the filter has a * in it. The message could be clearer about what it was complaining about: Found Include in a Dependency Set that is not declared as a dependency If the message is triggered by other events, perhaps it might need to be a bit more general. The following patterns were never triggered in this artifact inclusion filter makes one think that the problem has something to do with the flow control (triggered) rather than the artifact itself. It looks like the message has more to do with the way the plug-in is structured internally than the way the configuration is specified. Ron I guess you could use http://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringUtils.html#getLevenshteinDistance%28java.lang.CharSequence,%20java.lang.CharSequence%29 And if they are close include a Did you mean this instead? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Code coverage with debug logs: 100% branch coverage not possible?...
I have also been annoyed with what you describe, and have wondered how
to fill the gap of missing coverage.
Outside of copying the testcase and dynamically changing the log level
inside of it, which in addition to being burdensome, also offends my
DRY sensibility, the best idea I've had about this involves a
relatively new feature of JUnit called @Theories[1].
You could create @DataPoints {Level.ALL, Level.NONE} and then pass
them in to your test method. Then you dynamically set the class under
test's Logger.Level with the data point. I think this ought to work
just fine unless you execute your tests in parallel mode, as most
Logger declarations are as static instances.
There's one other problem which has prevented me from exploiting this
technique: @Theories needs a dedicated @RunWith(Theories.class). Which
would tend to preclude execution under @RunWith(Arquillian.class)
since @RunWith takes a singular runner argument, unless Aslak/someone
makes some tweaks[2].
[1] https://github.com/junit-team/junit/wiki/Theories
[2] https://issues.jboss.org/browse/ARQ-561
On Wed, Feb 12, 2014 at 3:30 PM, Benoît Berthonneau
ben...@berthonneau.com wrote:
Hi all,
I need your opinion/way to tackle the following problem:
In many projects we use a Logger (doesn't matter which implementation). It
is often recommend to test if the debug level is activated before logging a
debug trace like the following:
if (logger.isDebugEnabled()) {
logger.debug(blah + i + in the loop that contains + max);
}
Now when you run unit tests on this kind of code you need to make a choice:
run tests with INFO level or run tests with ALL traces activated. I choose
the second option in order to:
* Check that debug traces doesn't throw unwanted exception (like
NPE)
* Have a better code coverage in term of covered lines
But in term of branches coverage we could never have a 100% :(
To me the only way to cover this is to run the tests suite 2 times: one with
INFO traces configured, and another one with ALL traces activated.
Did you face this issue and how did you solve it ?
Thanks,
Benoît.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
Not sure I follow. Are you saying that if I need to add a dependency to a project.build.plugins.plugin.configuration.reportPlugins.plugin I should do it at project.build.plugins.plugin instead? E.g. as an additional dependency of the maven-site-plugin itself? If so, I tried that and was unsurprised when it didn't work. The maven-site-plugin does not appear to share it's classpath with child reportPlugins and quite rightly so. Following Hervé's advice I'm now using the older project.reporting.plugins config instead. However due to http://jira.codehaus.org/browse/MSITE-444(unresolved since 2007) project.reporting.plugins.plugin can't hold a dependencies element so the whole thing is a bust. a. On Fri, Feb 14, 2014 at 12:19 PM, jieryn jie...@gmail.com wrote: Even though Hervé has given the best answer, I thought I'd chime in and say that The Maven Way would probably have you add the additional dependency at the plugin level, and not the configuration.reportPlugins.plugin level.. So, sorry, but you were wrong twice. :-) On Thu, Feb 13, 2014 at 10:34 AM, Alex Potsides a...@achingbrain.net wrote: plugin artifactIdmaven-site-plugin/artifactId version3.3/version configuration reportPlugins plugin groupId../groupId artifactId../artifactId version../version dependencies dependency artifactId../artifactId groupId../groupId ... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
On Fri, Feb 14, 2014 at 7:55 AM, Alex Potsides a...@achingbrain.net wrote: E.g. as an additional dependency of the maven-site-plugin itself? Yes. If so, I tried that [...] The maven-site-plugin does not appear to share it's classpath with child reportPlugins and quite rightly so. Boo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to minimize quantity of profiles in pom.xml file
Have you thought about using an installer like IzPack that can organize your configurations for each environment. Installers know about different OSs and different combinations of modules. Build tools build modules and generally don't care much about deployment. I mention IzPack since it is FOSS and has a Maven plug-in so it fits well and understands about platform-specific configurations. Ron On 14/02/2014 5:06 AM, fred wrote: I need to build project for many kinds of environment so i need a lot of profiles with settings for this env. There is a cutted module pom.xml - pom.xml file http://www.mediafire.com/view/47gt5jiegta7auq/pom.xml -- View this message in context: http://maven.40175.n5.nabble.com/How-to-minimize-quantity-of-profiles-in-pom-xml-file-tp5784478p5784835.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 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Prevent installing archives to local repository
Hi everybody, one of my project create multiple jar and zip files during the build life cycle, and each archive was created with the maven assembly plugin. And now i see, that some of the files are installing to the local repository and some not. The files that i need are installed to the repository, but there is also a file that should not be installed. My question is how maven install plugin detect which file should be installed and which not, and is there a possibility to control this process and define that a specific file shouldn't be installed. Thank you in advance! Regards, DenisDasKind -- View this message in context: http://maven.40175.n5.nabble.com/Prevent-installing-archives-to-local-repository-tp5784848.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
Why does Maven fail to compile my project occasionally?
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 -- Levski Weng
Re: Prevent installing archives to local repository
i see, that some of the files are installing to the local repository and some not. The files that i need are installed to the repository, but there is also a file that should not be installed. My question is how maven Can you be more specific about the file that should not be installed? What is special about it? install plugin detect which file should be installed and which not, and is there a possibility to control this process and define that a specific file shouldn't be installed. Perhaps share your pom so we can comment on improvements? Please don't just email it here - post to pastebin or a similar service and send us the link. Wayne - 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?
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: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - 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?
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
Re: Why does Maven fail to compile my project occasionally?
clean should delete your compiler output and force a new compile. The repo has nothing to do with this. Ron On 14/02/2014 10:08 AM, LevskiWeng wrote: 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 -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - 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
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?
Where is the compiler version and options line? Ron On 14/02/2014 10:36 AM, LevskiWeng wrote: 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
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?
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
Possible build collision between CI snapshot build and Release build
Hello It is possible that while release:prepare cutting the tag and CI for snapshot build wakeup at the same time. Is there a way to prevent this? like a a profile to fail the build if the version happen to be a release version. Ie is there a way to detect this in a profile? I currently have to keep remind my self to turn off CI snapshot build while release is in progress, and too many to remember. Advice is greatly appreciated -Dan
