Re: Scanning for Projects... before
I think we have found one... We can create a wrapper around MavenCli and replace it in m2.conf... On 4/2/14, 8:35 PM, Wayne Fay [via Maven] wrote: repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790420.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790474.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
Well that is essentially a *very* basic way of my CI approach :) But it means you have to do it everywhere you have maven installed and need that behaviour. Also has the drawback of injecting this behaviour in any maven runs. So, as mentioned before a few times: switch to some standard use of maven :) On 04.04.2014 08:55, eugene wrote: I think we have found one... We can create a wrapper around MavenCli and replace it in m2.conf... On 4/2/14, 8:35 PM, Wayne Fay [via Maven] wrote: repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790420.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790474.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
Christian, you have no idea how much I wish this were a possibility, but this is the way the company has handled things for years. Changing this behavior would mean a revolution in their understanding, and I sure do not want to start one just yet. :) There is a much cooler way to do it actually... since we have Jenkins that builds the jobs (way too many to hook a pre-build event on them directly), we could implement an Extension Point for the Maven Reporter Plugin that has one called PreBuild - the only problem is that it works only for Maven 2 from what I tested. I asked their forums about this issue, no response so far. On 4/4/14, 9:59 AM, Christian Domsch [via Maven] wrote: Well that is essentially a *very* basic way of my CI approach :) But it means you have to do it everywhere you have maven installed and need that behaviour. Also has the drawback of injecting this behaviour in any maven runs. So, as mentioned before a few times: switch to some standard use of maven :) On 04.04.2014 08:55, eugene wrote: I think we have found one... We can create a wrapper around MavenCli and replace it in m2.conf... On 4/2/14, 8:35 PM, Wayne Fay [via Maven] wrote: repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790420.html To unsubscribe from Scanning for Projects... before, click here NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790474.html Sent from the Maven - Users mailing list archive at Nabble.com. If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790475.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790476.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
You're very likely to send some day an old version of a false releases, actually a snapshot, to production with this technique. I guess you should at least send a mail to some managers to explain things are going to go wrong some day. At least you will have taken your responsibility and they can't pretend it's your fault. Also, I hope nobody will ever use a vanilla version of Maven on their dev box since they're never going to get the rotten new releases downloaded :-/. 2014-04-04 9:06 GMT+02:00 eugene eugen.ra...@gmail.com: Christian, you have no idea how much I wish this were a possibility, but this is the way the company has handled things for years. Changing this behavior would mean a revolution in their understanding, and I sure do not want to start one just yet. :) There is a much cooler way to do it actually... since we have Jenkins that builds the jobs (way too many to hook a pre-build event on them directly), we could implement an Extension Point for the Maven Reporter Plugin that has one called PreBuild - the only problem is that it works only for Maven 2 from what I tested. I asked their forums about this issue, no response so far. On 4/4/14, 9:59 AM, Christian Domsch [via Maven] wrote: Well that is essentially a *very* basic way of my CI approach :) But it means you have to do it everywhere you have maven installed and need that behaviour. Also has the drawback of injecting this behaviour in any maven runs. So, as mentioned before a few times: switch to some standard use of maven :) On 04.04.2014 08:55, eugene wrote: I think we have found one... We can create a wrapper around MavenCli and replace it in m2.conf... On 4/2/14, 8:35 PM, Wayne Fay [via Maven] wrote: repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790420.html To unsubscribe from Scanning for Projects... before, click here NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790474.html Sent from the Maven - Users mailing list archive at Nabble.com. If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790475.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA== . NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790476.html Sent from the Maven - Users mailing list archive at Nabble.com. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Scanning for Projects... before
There is a *very* hacky way... I hesitate to suggest it... but as you seem stuck! Your delete mojo can take a wander through the dependency tree and record the details of all dependencies from the tree that will be affected by the deleting. You will need to do this for the entire set of reactor projects. You will need to do this only when you are the first reactor project in the reactor... for all other projects you will just do a no-op and return immediately. Then you do the delete. Then you request resolution of all the dependencies that were deleted, and you tell Maven to force the resolution (i.e. ignore the internal state that says it downloaded them already) There is a flag you can set that will do the forcing... but as this is an unrecommended HACK, you shall have to find that flag yourself. Thus when you mojo is finished executing, Maven's internal state that says it downloaded these dependencies already will be consistent with the on-disk state (because the files are present) and all will be right with the world. Beware! There be dragons! Dragon 1: If any of the dependencies you re-download have a different dependency list... you will be burned Dragon 2: If any of the dependencies you re-download have a dependency within the reactor... you will be burned There are more dragons... and you may find the rug pulled out from under you if you upgrade Maven... Beware! On 4 April 2014 07:55, eugene eugen.ra...@gmail.com wrote: I think we have found one... We can create a wrapper around MavenCli and replace it in m2.conf... On 4/2/14, 8:35 PM, Wayne Fay [via Maven] wrote: repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790420i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790420.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA== . NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790474.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Enforcer plugin
Hi, it would be really nice having a test case which reproduces the wrong behaviour ... Kind regards Karl-Heinz Marbaise On 4/3/14 2:25 AM, Mark Eggers wrote: Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the appropriate artifact, and removing the classifier gets the [other] appropriate artifact. Now I'm a bit paranoid that the artifact with the classifier will leak out into other releases, so I thought I would write an enforcer rule. I thought that the following would work: bannedDependencies excludes excludeorg.mdeggers:*:*:*:*:DEBUG/exclude /excludes /bannedDependencies based on: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html While this certainly blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type classifierDEBUG/classifier /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:DEBUG:1.5 It also blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:1.5 This I did not expect. The messages are also a bit suspect in that they don't match the pattern given in the documentation. I looked on JIRA and found the following (based on another thread): http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 These are all closed with a 'fixed' designation for release 1.3. I'm using version 1.3.1 However, I briefly looked at the code here: http://svn.apache.org/viewvc/maven/enforcer/tags/enforcer-1.3.1/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BannedDependencies.java?revision=1502671view=markup and classifier does not seem to have made it in. Have I walked through this correctly? If so, is there a fix (other than not using classifiers, or just hoping that a DEBUG classifier doesn't make it into a release)? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problems with com.github.github:site-maven-plugin:0.9:site
OK, the problem was in scm urlhttps://github.com/kolotyluk/java-file-utilities.git/url connectionscm:git:https://github.com/kolotyluk/java-file-utilities.git/connection developerConnectionscm:git:https://github.com/kolotyluk/java-file-utilities.git/developerConnection tagHEAD/tag /scm where url had .git in it. The fix was scm urlhttps://github.com/kolotyluk/java-file-utilities/url connectionscm:git:https://github.com/kolotyluk/java-file-utilities.git/connection developerConnectionscm:git:https://github.com/kolotyluk/java-file-utilities.git/developerConnection tagHEAD/tag /scm Cheers, Eric On 3/20/2014 10:34 AM, Eric Kolotyluk wrote: I copied what you had in your pom.xml, but I still get the same error. [ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.9:site (default) on project java-file-utilities: Error creating blob: Not Found (404) - [Help 1] What does your settings.xml look like? Mine is: server idgithub/id usernamekolotyluk/username password/secret//password /server Is there some other configuration/setup that needs to be done. Does the gh-pages branch need to be created manually first, or should the plug-in do that automatically? Cheers, Eric On 3/20/2014 9:48 AM, Manfred Moser wrote: I got a working setup for the release profile in the android maven plugin code. Check it out https://github.com/jayway/maven-android-plugin Benson Margulies wrote on 19.03.2014 19:20: Best ask them. This is a product of github, not the Apache Maven Project. On Wed, Mar 19, 2014 at 7:32 PM, Eric Kolotyluk eric.koloty...@gmail.com wrote: I configured things according tohttps://github.com/github/maven-plugins But when I try to run 'mvn site' I get the following errors. Does the gh-pages branch need to be created manually first, or should the plug-in do that automatically? Or am I chasing some other type of error. Cheers, Eric [ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.9:site (default) on project java-file-utilities: Error creating blob: Not Found (404) - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.github:site-maven-plugin:0.9:site (default) on project java-file-utilities: Error creating blob: Not Found (404) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating blob: Not Found (404) at com.github.maven.plugins.site.SiteMojo.createBlob(SiteMojo.java:289) at com.github.maven.plugins.site.SiteMojo.execute(SiteMojo.java:352) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: org.eclipse.egit.github.core.client.RequestException: Not Found (404) at org.eclipse.egit.github.core.client.GitHubClient.createException(GitHubClient.java:552) at org.eclipse.egit.github.core.client.GitHubClient.sendJson(GitHubClient.java:643) at org.eclipse.egit.github.core.client.GitHubClient.post(GitHubClient.java:757) at
Re: how to exclude log4j.properties when mvn assembly:single?
Hello Li Li, you might take a look at the maven-shade-plugin as well, which is easier to use IMO. Regards Mirko -- Sent from my mobile On Apr 4, 2014 3:20 AM, Li Li fancye...@gmail.com wrote: I want to make it runnable simply by java -jar xxx.jar build jars will copy all other dependencys On Thu, Apr 3, 2014 at 8:52 PM, Ron Wheeler rwhee...@artifact-software.com wrote: Why are you using the assembly-plugin? You normally don't need it to build jars. On 03/04/2014 5:24 AM, Li Li wrote: I want to jar my program with all the dependencies. I have a dependency of hadoop. the log4j.properties is included in my application. how to exclude it? I have tried this but no luck artifactIdmaven-assembly-plugin/artifactId configuration excludes exclude**/log4j.properties/exclude /excludes - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configuring SCM for github
Just to follow up, Russel, the .git is incorrect in the url element, and leads to problems when using groupIdcom.github.github/groupId artifactIdsite-maven-plugin/artifactId Cheers, Eric On 3/19/2014 12:06 PM, Russell Gold wrote: HI Eric, I think you are missing the “.git” extensions in your urls. Here’s the ones I use. scm urlhttps://github.com/meterware/simplestub.git/url developerConnectionscm:git:https://github.com/meterware/simplestub.git/developerConnection connectionscm:git:https://github.com/meterware/simplestub.git/connection /scm On Mar 19, 2014, at 2:58 PM, Eric Kolotyluk eric.koloty...@gmail.com wrote: I am having trouble getting mvn release:prepare to work with github scm connectionscm:git:http://github.com/kolotyluk/java-file-utilities/connection urlscm:git:http://github.com/kolotyluk/java-file-utilities/url developerConnectionscm:git:https://github.com/kolotyluk/java-file-utilities/developerConnection tagjava-file-utilities-0.0.1/tag /scm When I try to prepare the release I get [INFO] Checking in modified POMs... [INFO] Executing: cmd.exe /X /C git add -- pom.xml [INFO] Working directory: D:\Users\Eric\Software\Project\Repositories\java-file-utilities [INFO] Executing: cmd.exe /X /C git status [INFO] Working directory: D:\Users\Eric\Software\Project\Repositories\java-file-utilities [INFO] Executing: cmd.exe /X /C git commit --verbose -F C:\Users\Eric\AppData\Local\Temp\maven-scm-559613294.commit pom.xml [INFO] Working directory: D:\Users\Eric\Software\Project\Repositories\java-file-utilities [INFO] Executing: cmd.exe /X /C git symbolic-ref HEAD [INFO] Working directory: D:\Users\Eric\Software\Project\Repositories\java-file-utilities [INFO] Executing: cmd.exe /X /C git push https://github.com/kolotyluk/java-file-utilities master:master [INFO] Working directory: D:\Users\Eric\Software\Project\Repositories\java-file-utilities and mvn just hangs forever at that point. Is this a credentials problem or something else? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - Author, Getting Started with Apache Maven http://www.packtpub.com/getting-started-with-apache-maven/video Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/!
Re: how to exclude log4j.properties when mvn assembly:single?
Hi Li, seems very complicated Well, assembly makes the simple easy, and the difficult possible. That is, if all you want is to lump some JARs together, you can use the preconfigured assembly descriptor. But as soon as you want to do something custom, you have to create a custom descriptor. It takes a little while to wrap your head around (I hated the assembly plugin at first) but once you get into it, it is pretty powerful. where shoud I put this file? You can put the file wherever you want. You configure its location in the POM. Here is a project with several assembly examples: https://github.com/imagej/imagej/tree/imagej-2.0.0-beta-7.8/app Regards, Curtis On Thu, Apr 3, 2014 at 9:15 PM, Li Li fancye...@gmail.com wrote: seems very complicated, where shoud I put this file? On Fri, Apr 4, 2014 at 10:08 AM, Curtis Rueden ctrue...@wisc.edu wrote: Hi Li, the log4j.properties is included in my application. how to exclude it? Did you try with a custom assembly descriptor, and put the file in an exclude inside a fileSet? https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html Regards, Curtis On Thu, Apr 3, 2014 at 4:24 AM, Li Li fancye...@gmail.com wrote: I want to jar my program with all the dependencies. I have a dependency of hadoop. the log4j.properties is included in my application. how to exclude it? I have tried this but no luck artifactIdmaven-assembly-plugin/artifactId configuration excludes exclude**/log4j.properties/exclude /excludes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: how to exclude log4j.properties when mvn assembly:single?
Li-
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
artifactIdmaven-assembly-plugin/artifactId
configuration
dependencySets
dependencySet
excludes
excludelog4j:log4j/exclude
/excludes
/dependencySet
/dependencySets
/dependencySets
/configuration
although it might be easier to put dependencySets into
${project.basedir}/resources/assemblies/dependencySet-excludes.xml as seen here
!--
~ Copyright 2001-2006 The Apache Software Foundation.
~
~ Licensed under the Apache License, Version 2.0 (the License);
~ you may not use this file except in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an AS IS BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
--
assembly
xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd;
iddependencySet-excludes/id
formats
!-- zip, tar, or tar.gz --
formatzip/format
/formats
dependencySets
dependencySet
excludes
excludelog4j:log4j/exclude
/excludes
/dependencySet
/dependencySets
/dependencySets
/configuration
/assembly
On Thu, Apr 3, 2014 at 9:15 PM, Li Li fancye...@gmail.com wrote:
seems very complicated, where shoud I put this file?
On Fri, Apr 4, 2014 at 10:08 AM, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Li,
the log4j.properties is included in my application.
how to exclude it?
Did you try with a custom assembly descriptor, and put the file in an
exclude inside a fileSet?
https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
Regards,
Curtis
On Thu, Apr 3, 2014 at 4:24 AM, Li Li fancye...@gmail.com wrote:
I want to jar my program with all the dependencies. I have a
dependency of hadoop. the log4j.properties is included in my
application.
how to exclude it?
I have tried this but no luck
artifactIdmaven-assembly-plugin/artifactId
configuration
excludes
exclude**/log4j.properties/exclude
/excludes
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven Filtering
According to http://maven.apache.org/shared/maven-filtering/ I can define
properties
projectBuildDirectory\${project.build.directory}/projectBuildDirectory
/properties
and I should expect to see
${project.build.directory}
when the property projectBuildDirectory is used, but instead I get
\D:\Users\Eric\Software\Project\Repositories\csharp-windows-elevate\target
Am I going insane, is this a bug in Maven, or is the documentation wrong?
Is there some other way to escape the filtering?
Cheers, Eric
USER LIBRARIES
Hello, Is there a chance that instead of managing the dependencies, I will just add the USER LIBRARY I have created on Eclipse? Best Regards, Dan -- View this message in context: http://maven.40175.n5.nabble.com/USER-LIBRARIES-tp5790481.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: USER LIBRARIES
Dan- lib entries in Eclipse generated .classpath will give your version/artifact for your dependencies: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/ classpathentry kind=src path=tools/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=var path=JUNIT_HOME/junit.jar/ classpathentry exported=true kind=lib path=/mmisFramework/lib/1.1-myfaces-api.jar/ classpathentry exported=true kind=lib path=/mmisFramework/lib/1.2-myfaces-impl.jar/ ... /classpath HTH Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Fri, 4 Apr 2014 03:58:24 -0700 From: baylon.dan...@hotmail.com To: users@maven.apache.org Subject: USER LIBRARIES Hello, Is there a chance that instead of managing the dependencies, I will just add the USER LIBRARY I have created on Eclipse? Best Regards, Dan -- View this message in context: http://maven.40175.n5.nabble.com/USER-LIBRARIES-tp5790481.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: Maven Filtering
Eric-
Its friday nite most normal people are now engaging in insane activity called
'having fun'
i dont know what you have setup in environment variables so:
change
projectBuildDirectory\${project.build.directory}/projectBuildDirectory
to
project.build.directoryBaseFolderForYourProject/project.build.directory
HTH
Martin-
Date: Fri, 4 Apr 2014 17:13:04 -0700
From: e...@kolotyluk.net
To: users@maven.apache.org
Subject: Maven Filtering
According to http://maven.apache.org/shared/maven-filtering/ I can define
properties
projectBuildDirectory\${project.build.directory}/projectBuildDirectory
/properties
and I should expect to see
${project.build.directory}
when the property projectBuildDirectory is used, but instead I get
\D:\Users\Eric\Software\Project\Repositories\csharp-windows-elevate\target
Am I going insane, is this a bug in Maven, or is the documentation wrong?
Is there some other way to escape the filtering?
Cheers, Eric
Re: USER LIBRARIES
Is there a chance that instead of managing the dependencies, I will just add the USER LIBRARY I have created on Eclipse? I don't really understand the question. Provide more context and details in what you are doing vs what you expect. Also be clear if you are using M2E or command-line Maven as this list is primarily for support of command-line Maven. There are separate Eclipse lists that support M2E. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Filtering
I think you have to define the escape character in the configuration.
-Todd
On Apr 4, 2014, at 8:13 PM, Eric Kolotyluk e...@kolotyluk.net wrote:
According to http://maven.apache.org/shared/maven-filtering/ I can define
properties
projectBuildDirectory\${project.build.directory}/projectBuildDirectory
/properties
and I should expect to see
${project.build.directory}
when the property projectBuildDirectory is used, but instead I get
\D:\Users\Eric\Software\Project\Repositories\csharp-windows-elevate\target
Am I going insane, is this a bug in Maven, or is the documentation wrong?
Is there some other way to escape the filtering?
Cheers, Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Filtering
Am I going insane, is this a bug in Maven, or is the documentation wrong? Is there some other way to escape the filtering? Generally, this should work. Did you specify the escapeString configuration [1]? What version of plugins etc are you using? [1] http://maven.apache.org/plugins/maven-resources-plugin/examples/escape-filtering.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
