[jira] [Commented] (ARCHETYPE-487) Input validation for required properties defined in artifact descriptor
[ https://issues.apache.org/jira/browse/ARCHETYPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428323#comment-15428323 ] ASF GitHub Bot commented on ARCHETYPE-487: -- Github user mryan43 closed the pull request at: https://github.com/apache/maven-archetype/pull/7 > Input validation for required properties defined in artifact descriptor > --- > > Key: ARCHETYPE-487 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-487 > Project: Maven Archetype > Issue Type: New Feature > Components: Archetypes, Generator, Plugin >Reporter: Manuel Ryan >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.5 > > > Add the possibility to define validation regular expressions for required > properties in artifact descriptors. > Use the regular expressions to validate user input (and ask the user to try > again if the expression doesn't match) > here's an example of a property that is required by the archetype to be only > lower case alphabet characters: > --- in archetype-metadata.xml : > > ^[a-z]*$ > > --- at prompt : > Define value for property 'username' (should match expression '^[a-z]*$'): > John > Value does not match the expression, please try again: john > Define value for property... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ARCHETYPE-487) Input validation for required properties defined in artifact descriptor
[ https://issues.apache.org/jira/browse/ARCHETYPE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428322#comment-15428322 ] ASF GitHub Bot commented on ARCHETYPE-487: -- Github user mryan43 commented on the issue: https://github.com/apache/maven-archetype/pull/7 thx > Input validation for required properties defined in artifact descriptor > --- > > Key: ARCHETYPE-487 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-487 > Project: Maven Archetype > Issue Type: New Feature > Components: Archetypes, Generator, Plugin >Reporter: Manuel Ryan >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.5 > > > Add the possibility to define validation regular expressions for required > properties in artifact descriptors. > Use the regular expressions to validate user input (and ask the user to try > again if the expression doesn't match) > here's an example of a property that is required by the archetype to be only > lower case alphabet characters: > --- in archetype-metadata.xml : > > ^[a-z]*$ > > --- at prompt : > Define value for property 'username' (should match expression '^[a-z]*$'): > John > Value does not match the expression, please try again: john > Define value for property... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6075) Increase the model validation level to the next minor level version.
[ https://issues.apache.org/jira/browse/MNG-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428559#comment-15428559 ] Hudson commented on MNG-6075: - SUCCESS: Integrated in Jenkins build maven-3.x #1365 (See [https://builds.apache.org/job/maven-3.x/1365/]) [MNG-6075] Increase the model validation level to the next minor level (schulte: rev 1c633fa9062cf56f90d8f534508cbdcabfe4e82c) * (edit) maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java > Increase the model validation level to the next minor level version. > > > Key: MNG-6075 > URL: https://issues.apache.org/jira/browse/MNG-6075 > Project: Maven > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > Maven 3 has warned about various model related issues clearly stating that > not reacting to those warnings may break with a future Maven version. > Starting with Maven 3.4, the model validation level has been increased to the > next minor version so that such warnings will become errors as of 3.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1257) incorrect XML for JUnit provider
[ https://issues.apache.org/jira/browse/SUREFIRE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1257. -- Resolution: Fixed commit 230a8f8d9fb235809059f7465b8707eb4dec6da2 > incorrect XML for JUnit provider > > > Key: SUREFIRE-1257 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1257 > Project: Maven Surefire > Issue Type: Documentation >Reporter: Alain Hélaïli >Assignee: Tibor Digana > Fix For: 2.19.2 > > > In > http://maven.apache.org/surefire/maven-failsafe-plugin/examples/junit.html, > under *Using Custom Listeners and Reporters*, the tag is not > closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1255) Surefire 2.19.1 hangs before starting test execution
[
https://issues.apache.org/jira/browse/SUREFIRE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428856#comment-15428856
]
Tibor Digana commented on SUREFIRE-1255:
[~mxm]
Can you make a try with the version 2.19.2-SNAPSHOT?
In the next step we will add some logs to watch instead of debugging.
What platform, OS, and CPU you use?
> Surefire 2.19.1 hangs before starting test execution
>
>
> Key: SUREFIRE-1255
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1255
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.19.1
>Reporter: Maximilian Michels
>Priority: Critical
>
> Seeing the same error as SUREFIRE-1193 in Apache Flink builds after upgrading
> from 2.18.1 to 2.19.1. No errors, builds just gets stuck at the beginning of
> tests with no log output from the test itself, e.g.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/137118454/log.txt
> After a couple of minutes Surefire reports
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test
> (integration-tests) on project flink-scala-shell_2.10: ExecutionException The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was /bin/sh -c cd
> /home/travis/build/mxm/flink/flink-scala-shell/target &&
> /usr/lib/jvm/java-8-oracle/jre/bin/java -Xms256m -Xmx800m -Dmvn.forkNumber=1
> -XX:-UseGCOverheadLimit -jar
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefirebooter372520169616801479.jar
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire8229439069544382018tmp
>
> /home/travis/build/mxm/flink/flink-scala-shell/target/surefire/surefire_26373613144387982724tmp
> [ERROR] -> [Help 1]
> {noformat}
> We have a a couple of test classes that suffer from this problem. Tests don't
> read from STDIN or replace it. Switching back to 2.18.1 eliminates the
> problem (Ran over 100 builds). It seems to be a race condition because it
> only occurs every once in a while, i.e. ~ 2 out of 10 builds on Travis. I
> haven't been able to reproduce the problem locally.
> More logs:
> https://s3.amazonaws.com/flink-logs-us/travis-artifacts/mxm/flink/849/849.1.tar.gz
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1257) incorrect XML for JUnit provider
[ https://issues.apache.org/jira/browse/SUREFIRE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428899#comment-15428899 ] Hudson commented on SUREFIRE-1257: -- SUCCESS: Integrated in Jenkins build maven-surefire #1591 (See [https://builds.apache.org/job/maven-surefire/1591/]) [SUREFIRE-1257] incorrect XML for JUnit provider (tibor17: rev 230a8f8d9fb235809059f7465b8707eb4dec6da2) * (edit) maven-surefire-plugin/src/site/apt/examples/junit.apt.vm > incorrect XML for JUnit provider > > > Key: SUREFIRE-1257 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1257 > Project: Maven Surefire > Issue Type: Documentation >Reporter: Alain Hélaïli >Assignee: Tibor Digana > Fix For: 2.19.2 > > > In > http://maven.apache.org/surefire/maven-failsafe-plugin/examples/junit.html, > under *Using Custom Listeners and Reporters*, the tag is not > closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1240) failsafe documentation on skipping tests by property does not use property
[ https://issues.apache.org/jira/browse/SUREFIRE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1240. -- Resolution: Fixed commit 0d3458633e32c738c77a567b2edc69666253d331 > failsafe documentation on skipping tests by property does not use property > -- > > Key: SUREFIRE-1240 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1240 > Project: Maven Surefire > Issue Type: Bug > Components: documentation >Affects Versions: 2.19.1 >Reporter: Jörg Sesterhenn >Assignee: Tibor Digana > Fix For: 2.19.2 > > > The example in the > [docs|http://maven.apache.org/surefire/maven-failsafe-plugin/examples/skipping-test.html] > for skipping tests by using a property does not use the configured property > in the plugin configuration. > For a correct example see [surefire > docs|https://maven.apache.org/surefire/maven-surefire-plugin/examples/skipping-test.html]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1240) failsafe documentation on skipping tests by property does not use property
[ https://issues.apache.org/jira/browse/SUREFIRE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428990#comment-15428990 ] Hudson commented on SUREFIRE-1240: -- SUCCESS: Integrated in Jenkins build maven-surefire #1592 (See [https://builds.apache.org/job/maven-surefire/1592/]) [SUREFIRE-1240] failsafe documentation on skipping tests by property (tibor17: rev 0d3458633e32c738c77a567b2edc69666253d331) * (edit) maven-surefire-plugin/src/site/apt/examples/skipping-tests.apt.vm > failsafe documentation on skipping tests by property does not use property > -- > > Key: SUREFIRE-1240 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1240 > Project: Maven Surefire > Issue Type: Bug > Components: documentation >Affects Versions: 2.19.1 >Reporter: Jörg Sesterhenn >Assignee: Tibor Digana > Fix For: 2.19.2 > > > The example in the > [docs|http://maven.apache.org/surefire/maven-failsafe-plugin/examples/skipping-test.html] > for skipping tests by using a property does not use the configured property > in the plugin configuration. > For a correct example see [surefire > docs|https://maven.apache.org/surefire/maven-surefire-plugin/examples/skipping-test.html]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5971) Imported dependencies should be available to inheritance processing
[
https://issues.apache.org/jira/browse/MNG-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429239#comment-15429239
]
Hudson commented on MNG-5971:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1366 (See
[https://builds.apache.org/job/maven-3.x/1366/])
[MNG-5971] Imported dependencies should be available to inheritance (schulte:
rev eaa4cdfb8e2f32306b425ecad68fde25f21271fa)
* (edit)
maven-model-builder/src/main/java/org/apache/maven/model/composition/DefaultDependencyManagementImporter.java
> Imported dependencies should be available to inheritance processing
> ---
>
> Key: MNG-5971
> URL: https://issues.apache.org/jira/browse/MNG-5971
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.3.3
>Reporter: Stephane Nicoll
>Assignee: Christian Schulte
>Priority: Trivial
> Fix For: 3.4.0
>
> Attachments: bom-cloud.zip
>
>
> When a project extends from a parent with a {{dependencyManagement}} section,
> it is not always possible to properly override (and align) the version to use
> for a group of dependencies.
> We typically use Bill Of Materials to gather a group of modules and make sure
> their versions are consistent.
> The following project demonstrates the issue:
> https://github.com/snicoll-scratches/maven-dependency-management
> The first commit is a working use case where the parent uses a bom with
> version A and we use the same bom with version B in the child. Version B is
> used as expected.
> The second commit demonstrates the faulty scenario. Rather than using a bom
> in the parent, we use a direct dependency (provided by that bom). We still
> use the bom with a different version. In that case all the dependencies but
> the one provided by the parent are overridden (leading to mixed versions for
> the dependencies provided by the BOM).
> It looks like the distance is still used to compute the version while the
> graph of dependencies should be flatten at each step for a proper override.
> Thoughts? Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5910) Using both {{exists}} and {{missing}} in the same {{file}} element should lead to an exception
[
https://issues.apache.org/jira/browse/MNG-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429256#comment-15429256
]
ASF GitHub Bot commented on MNG-5910:
-
Github user rajivpjs closed the pull request at:
https://github.com/apache/maven/pull/88
> Using both {{exists}} and {{missing}} in the same {{file}} element should
> lead to an exception
> --
>
> Key: MNG-5910
> URL: https://issues.apache.org/jira/browse/MNG-5910
> Project: Maven
> Issue Type: Bug
> Components: core, Profiles
>Affects Versions: 3.3.3
>Reporter: Konrad Windszus
>
> Currently it is not clear from the POM reference
> (https://maven.apache.org/pom.html#Activation), that the elements {{exists}}
> and {{missing}} below {{file}} are mutually exclusive, because only
> {{exists}} is considered if it is there (see also
> https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/FileProfileActivator.java#L91).
> Please make it clearer in the POM reference that not both of them should be
> used at the same time and also throw an exception during build time if that
> is the case (in the effective POM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5910) Using both {{exists}} and {{missing}} in the same {{file}} element should lead to an exception
[
https://issues.apache.org/jira/browse/MNG-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429257#comment-15429257
]
ASF GitHub Bot commented on MNG-5910:
-
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.
> Using both {{exists}} and {{missing}} in the same {{file}} element should
> lead to an exception
> --
>
> Key: MNG-5910
> URL: https://issues.apache.org/jira/browse/MNG-5910
> Project: Maven
> Issue Type: Bug
> Components: core, Profiles
>Affects Versions: 3.3.3
>Reporter: Konrad Windszus
>
> Currently it is not clear from the POM reference
> (https://maven.apache.org/pom.html#Activation), that the elements {{exists}}
> and {{missing}} below {{file}} are mutually exclusive, because only
> {{exists}} is considered if it is there (see also
> https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/FileProfileActivator.java#L91).
> Please make it clearer in the POM reference that not both of them should be
> used at the same time and also throw an exception during build time if that
> is the case (in the effective POM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
