[GitHub] maven issue #88: [MNG-5910] Fixed the description of the POM reference & add...
Github user rajivpjs commented on the issue: https://github.com/apache/maven/pull/88 Will reopen issue if someone does take a look. Closing issue. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven pull request #88: [MNG-5910] Fixed the description of the POM referenc...
Github user rajivpjs closed the pull request at: https://github.com/apache/maven/pull/88 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)
Am 08/19/16 um 21:10 schrieb jieryn: > I am seeing a huge amount of additional warnings at the start of the > build now, that is intentional I believe? Do we have a wiki or any > documentation about resolving these issues? For example, I'm seeing > this because I use Arquillian and their standard dependencyManagement > bom scope=import style. Intentional. No release notes yet. Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven-surefire issue #81: Create better report for AssumptionFailure
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/81 @jimma Did you run `mvn install` and did it run the integration tests? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven-surefire issue #81: Create better report for AssumptionFailure
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/81 @jimma Can you create an issue in https://issues.apache.org/jira/browse/SUREFIRE as an improvement? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)
That seems to be working, thank you! I am seeing a huge amount of additional warnings at the start of the build now, that is intentional I believe? Do we have a wiki or any documentation about resolving these issues? For example, I'm seeing this because I use Arquillian and their standard dependencyManagement bom scope=import style. On Fri, Aug 19, 2016 at 2:01 PM, Karl Heinz Marbaise wrote: > Hi, > > can you please check here[1] for a current version of Maven 3.4.0-SNAPSHOT > and recheck your issues please... > > And if the keep being there please report... > > Many thanks for your help... > > [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x/ > > Kind regards > Karl Heinz Marbaise > On 19/08/16 05:11, jieryn wrote: >> >> Sorry I am so late to this party. >> >> I find that Apache Maven 3.4.0-SNAPSHOT >> (90f26c279af9738735be8f84f60dcf21b6244e24; 2016-07-22T11:23:04-04:00) >> prefers .mvn/maven.config options instead of specifically listed >> parameters. This is surprising to me. I expect the .mvn/maven.config >> options to be overriden by any actual parameters that I specify on the >> command line. >> >> Specifically, I am trying to override the maven.config --fail-at-end >> via --fail-fast, and also --threads 2.0C with --threads 1. When I >> invoke mvn, it seems the maven.config options are taken instead of my >> local cli invocation. These have a bad effect on my invocation and >> cause a lot of trouble. We do not check in our .mvn/maven.config, so I >> can not simply rm -rf it and then check it out after... it's a pita, >> and bad karma. Please examine it :) thank you. >> >> On Fri, Jul 22, 2016 at 11:27 AM, Karl Heinz Marbaise >> wrote: >>> >>> Hi to all Maven users, >>> >>> If you like to help making the next Maven release better it would be nice >>> if >>> you could help a little bit. >>> >>> Please be aware of this *** This is not an official release *** >>> >>> I have created downloadable packages which are available from here: >>> >>> >>> Windows: https://s.apache.org/vG4r >>> Linux/Mac: https://s.apache.org/FfRw >>> >>> Every kind of feedback is helpful. >>> >>> Important hint: >>> >>> This is only a current state of development (Git hash: >>> 90f26c279af9738735be8f84f60dcf21b6244e24) to get some feedback from the >>> community... >>> >>> The current list of changes can be seen in the issue tracker: >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.4.0 >>> >>> It would be nice if those who had found issues to retest their scenarios. >>> >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)
Hi, can you please check here[1] for a current version of Maven 3.4.0-SNAPSHOT and recheck your issues please... And if the keep being there please report... Many thanks for your help... [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x/ Kind regards Karl Heinz Marbaise On 19/08/16 05:11, jieryn wrote: Sorry I am so late to this party. I find that Apache Maven 3.4.0-SNAPSHOT (90f26c279af9738735be8f84f60dcf21b6244e24; 2016-07-22T11:23:04-04:00) prefers .mvn/maven.config options instead of specifically listed parameters. This is surprising to me. I expect the .mvn/maven.config options to be overriden by any actual parameters that I specify on the command line. Specifically, I am trying to override the maven.config --fail-at-end via --fail-fast, and also --threads 2.0C with --threads 1. When I invoke mvn, it seems the maven.config options are taken instead of my local cli invocation. These have a bad effect on my invocation and cause a lot of trouble. We do not check in our .mvn/maven.config, so I can not simply rm -rf it and then check it out after... it's a pita, and bad karma. Please examine it :) thank you. On Fri, Jul 22, 2016 at 11:27 AM, Karl Heinz Marbaise wrote: Hi to all Maven users, If you like to help making the next Maven release better it would be nice if you could help a little bit. Please be aware of this *** This is not an official release *** I have created downloadable packages which are available from here: Windows: https://s.apache.org/vG4r Linux/Mac: https://s.apache.org/FfRw Every kind of feedback is helpful. Important hint: This is only a current state of development (Git hash: 90f26c279af9738735be8f84f60dcf21b6244e24) to get some feedback from the community... The current list of changes can be seen in the issue tracker: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.4.0 It would be nice if those who had found issues to retest their scenarios. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven-archetype pull request #7: ARCHETYPE-487 Add input validation for requ...
Github user mryan43 closed the pull request at: https://github.com/apache/maven-archetype/pull/7 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven-archetype issue #7: ARCHETYPE-487 Add input validation for required pr...
Github user mryan43 commented on the issue: https://github.com/apache/maven-archetype/pull/7 thx --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Proposed solution + pull request for MNG-5909
Hello, I found this ticket : https://issues.apache.org/jira/browse/MNG-5909 to match one of my current problems. I have 3 profiles (A, B and C) each activated on file existence criteria. I need to change it so that : - if fileA is missing, none of these profiles must be active - if file A is present, then A must be active + B must be active if fileBC is missing - if file A is present, then A must be active + C must be active if fileBC is present, in which case B must NOT be active This can not be expressed in the current version of maven. Accepting multiple elements in the POM (changing the model), as suggested in the ticket, seemed complex to do and I was worried that I could break compatibility.Instead, I implemented a simple solution that fits my needs : my patched maven now understands basic logic in file-based profile activation.In my POM now I have : and(fileA,!fileBC) (this is for profile B, of course C has the same without the negation). My implementation accepts boolean operators AND (expressed as and() or all() ), OR (expressed as or() or any() ) and NOT (expressed with an exclamation mark, applicable only on the inner value, not left of the operator). Nested conditions are not supported.For more examples of supported expressions, please see the added unit test. If you think this can be useful to others, please consider merging the pull request here : MNG-5909 : Add combined expression evaluator to file activation property by lbndev · Pull Request #92 · apache/maven | | | | | | | | | | | MNG-5909 : Add combined expression evaluator to file act...Suggested solution for MNG-5909 : the file activation element will understand basic boolean expressions such as and(file1,file2) or(file3,!file4) etc... Please see ... | | | | Afficher sur github.com | Aperçu par Yahoo | | | | | If you think this simple "boolean conditions" feature could be usefully added to other activation criteria (properties and OS for example), please say so and I will happily wire it there too. Comments and feedback are welcome, Loïc
