[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421122#comment-16421122
]
Tibor Digana commented on SUREFIRE-1480:
[~mlehky]
The XML is created in class {{StatelessXmlReporter}} but it is still strange to
me that we missed the xml element.
The problem is at the line 213. Most probably the {{methodEntryList.get( 0 )}}
is not skip entry.
Somebody should debug it.
> parallel tests may produce invalid .xml report
> --
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Mark Lehky
>Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
> * Jenkins 2.108
> * Maven 3.??
> * JUnit 4.12
> * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple
> JUnit methods), which are all run in parallel. Some of the tests may be
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
>
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being
> flagged as failed, and Jenkins simply has the message:
> "TEST-xml.[failed-to-read]" (the dots are replaced with the correct
> filename!).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1387) runTime always 0 in statistics, breaking runOrder=balanced
[
https://issues.apache.org/jira/browse/SUREFIRE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421104#comment-16421104
]
Tibor Digana commented on SUREFIRE-1387:
{{forkCount}} and {{balanced}} means new algorithm because we are streaming the
classes over JVMs.
You have to implemented it by your own. Feel free open a pull request on GitHub.
The enum should be different, i.e. {{runOrder=balancedForks}}. Have a look in
the class {{ForkStarter}} and the collection which handles the order of class
names dispatched over JVMs
Thx.
> runTime always 0 in statistics, breaking runOrder=balanced
> --
>
> Key: SUREFIRE-1387
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1387
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.20
>Reporter: Emond Papegaaij
>Assignee: Tibor Digana
>Priority: Major
> Fix For: Backlog
>
>
> We are using parallized tests to speed up the builds, however tests are
> executed in less than optimal order. `balanced` is
> supposed to improve the ordering, but it requires statistics in a
> `.surefire-X` file. A maven build does write this file, but runTime is
> reported as 0 for all tests. Every line in the file looks like (where n is
> the number of executions):
> {code}
> n,0,method(class)
> {code}
> I've traced the source of these '0's to nulls in the `ForkedBooter` protocol.
> These are written by `ForkingRunListener.testSucceeded` on this stack:
> {code}
> Thread [main] (Suspended (breakpoint at line 151 in ForkingRunListener))
> owns: Notifier (id=14012)
> ForkingRunListener.testSucceeded(ReportEntry) line: 151
> JUnit4RunListener.testFinished(Description) line: 140
> SynchronizedRunListener.testFinished(Description) line: 56
> RunNotifier$7.notifyListener(RunListener) line: 190
> RunNotifier$7(RunNotifier$SafeNotifier).run() line: 72
> Notifier(RunNotifier).fireTestFinished(Description) line: 187
> JUnitSupervisor.afterFeature(FeatureInfo) line: 193
> ParameterizedSpecRunner(BaseSpecRunner).runFeature() line: 239
> ParameterizedSpecRunner(BaseSpecRunner).runFeatures() line: 188
> ParameterizedSpecRunner(BaseSpecRunner).doRunSpec() line: 98
> BaseSpecRunner$1.invoke(Object, Object...) line: 84
> ParameterizedSpecRunner(BaseSpecRunner).invokeRaw(Object, MethodInfo,
> Object...) line: 481
> ParameterizedSpecRunner(BaseSpecRunner).invoke(Object, MethodInfo,
> Object...) line: 464
> ParameterizedSpecRunner(BaseSpecRunner).runSpec() line: 76
> ParameterizedSpecRunner(BaseSpecRunner).run() line: 67
> ArquillianSputnik.run(RunNotifier) line: 135
> JUnit4Provider.execute(Class, Notifier, Filter) line: 365
> JUnit4Provider.executeWithRerun(Class, Notifier) line: 272
> JUnit4Provider.executeTestSet(Class, RunListener, Notifier) line:
> 236
> JUnit4Provider.invoke(Object) line: 159
> ForkedBooter.invokeProviderInSameClassLoader(Object, Object,
> ProviderConfiguration, boolean, StartupConfiguration, boolean) line: 386
> ForkedBooter.runSuitesInProcess(Object, StartupConfiguration,
> ProviderConfiguration, PrintStream) line: 323
> ForkedBooter.main(String...) line: 143
> {code}
> `JUnit4RunListener.testFinished(Description)` always creates TestReports with
> 'elapsed == null'.
> We are using the following configuration:
> {code}
>
>3
>true
>balanced
>false
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421092#comment-16421092
]
Tibor Digana commented on SUREFIRE-1480:
{{g...@github.com:apache/maven-surefire.git}} is correct for making pull
requests on GitHub.
> parallel tests may produce invalid .xml report
> --
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Mark Lehky
>Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
> * Jenkins 2.108
> * Maven 3.??
> * JUnit 4.12
> * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple
> JUnit methods), which are all run in parallel. Some of the tests may be
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
>
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being
> flagged as failed, and Jenkins simply has the message:
> "TEST-xml.[failed-to-read]" (the dots are replaced with the correct
> filename!).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421090#comment-16421090
]
Tibor Digana commented on SUREFIRE-1480:
[~mlehky]
Can you attach a small project in Jira so that we would be able to reproduce
this issue?
Thx
> parallel tests may produce invalid .xml report
> --
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Mark Lehky
>Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
> * Jenkins 2.108
> * Maven 3.??
> * JUnit 4.12
> * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple
> JUnit methods), which are all run in parallel. Some of the tests may be
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
>
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being
> flagged as failed, and Jenkins simply has the message:
> "TEST-xml.[failed-to-read]" (the dots are replaced with the correct
> filename!).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MJAR-198) jar:jar without classifier replaces default jar
[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420979#comment-16420979 ] Karl Heinz Marbaise edited comment on MJAR-198 at 3/30/18 9:58 PM: --- First it would be nice if you have issues open a new issue with a reference to this one...furthermore no discussions within jira issues..better use [users- or dev list|http://maven.apache.org/mail-lists.html] for such things. was (Author: khmarbaise): First it would be nice if you have issue open a new issue with a reference to this one...furthermore no discussions within jira issues..better use [users- or dev list|http://maven.apache.org/mail-lists.html] for such things. > jar:jar without classifier replaces default jar > --- > > Key: MJAR-198 > URL: https://issues.apache.org/jira/browse/MJAR-198 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6 > Environment: Windows 8.1 Pro > JDK 1.8 45 > Maven 3.2.5 >Reporter: Elias Elmqvist Wulcan >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: newbie > Fix For: 3.0.0 > > Attachments: 0.tar, mvn.install.debug.txt > > > If I add an execution of jar:jar in a project of packaging jar and do not > configure a classifier for the additional jar, the additional jar will be > installed instead of the default jar. > Omitting a classifier in the configuration for the goal jar:jar is documented > to have the effect that the jar will not be attached and this is the behavior > that I want. Instead, the jar is attached and replaces the default jar. > AbstractJarMojo.java:254 checks nullness of classifier to decide whether to > attach or not. JarMojo.java:51 declares a default value the empty string for > classifier. Maybe the combination of these lines cause the bug. > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5883) Silence unnecessary legacy local repository warning
[
https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420983#comment-16420983
]
Ben Caradoc-Davies commented on MNG-5883:
-
I agree with Cristian: the new mode should be removed. The core problem is that
the new mode stores too much state in the local repository. In effect,
artifacts now have not only groupId, artifactId, and version, but also a
persistent origin that is set once and cannot be accessed from poms. The new
mode is broken because it neglects the possibility that the origin might
change, but this happens all the time in the real world. The new mode confuses
the means of access (repository) with the payload (artifact). This analogous to
mixing the transport and application layers in a network model.
The new behaviour increases stability but this is orthogonal to correctness. A
build can be stable and broken. Under the new behaviour, once the local
repository has been poisoned with a bad artifact (e.g. corrupt zero-length jar
or artifact built and deployed with wrong Java target), it will be stably
broken, and cannot be fixed by adding a good artifact to a different
repository. Manual repair of a local repository can be difficult if it is on a
remote CI machine (who has admin on that box?). Not to mention all the confused
developers who are unaware of Maven's broken default (new) behaviour, do not
know that their local repository is poisoned, cannot figure out why their build
is failing, and wander project developer mailing lists and stackexchange
seeking help.
If you want to bind artifacts to particular repositories (and I do not think
this is as useful as you think), please implement this behaviour in the pom
model, not as hidden state in the local repository.
Until the new mode is removed, I use and recommend "-llr".
> Silence unnecessary legacy local repository warning
> ---
>
> Key: MNG-5883
> URL: https://issues.apache.org/jira/browse/MNG-5883
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
>Affects Versions: 3.2.5, 3.3.3, 3.5.0
>Reporter: Ben Caradoc-Davies
>Priority: Trivial
>
> Having been burned on several occasions by the new local repository
> behaviour, which in effect scopes artifacts by their origin (when first
> stored in the local repository), I was delighted by the introduction of the
> -llr command line option in 3.0.3. I now use this behaviour for all builds to
> avoid the build instability caused by remote repository migration. This
> avoids the need to start each build with:
> {code}
> find ~/.m2/repository -name "_*.repositories" -exec rm -f {} \;
> {code}
> Given that users of -llr have made an informed choice to do so, please remove
> the (in my view unnecessary) warning that it generates:
> {code}
> [WARNING] Disabling enhanced local repository: using legacy is strongly
> discouraged to ensure build reproducibility.
> {code}
> Kind regards,
> Ben.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar
[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420979#comment-16420979 ] Karl Heinz Marbaise commented on MJAR-198: -- First it would be nice if you have issue open a new issue with a reference to this one...furthermore no discussions within jira issues..better use [users- or dev list|http://maven.apache.org/mail-lists.html] for such things. > jar:jar without classifier replaces default jar > --- > > Key: MJAR-198 > URL: https://issues.apache.org/jira/browse/MJAR-198 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6 > Environment: Windows 8.1 Pro > JDK 1.8 45 > Maven 3.2.5 >Reporter: Elias Elmqvist Wulcan >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: newbie > Fix For: 3.0.0 > > Attachments: 0.tar, mvn.install.debug.txt > > > If I add an execution of jar:jar in a project of packaging jar and do not > configure a classifier for the additional jar, the additional jar will be > installed instead of the default jar. > Omitting a classifier in the configuration for the goal jar:jar is documented > to have the effect that the jar will not be attached and this is the behavior > that I want. Instead, the jar is attached and replaces the default jar. > AbstractJarMojo.java:254 checks nullness of classifier to decide whether to > attach or not. JarMojo.java:51 declares a default value the empty string for > classifier. Maybe the combination of these lines cause the bug. > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup > http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar
[
https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420958#comment-16420958
]
Archie Cobbs commented on MJAR-198:
---
FYI, this broke my build, which used the jar plugin twice but with different
{{finalName}} configurations (and no {{classifier}}'s).
Not sure if that was intended or if my original configuration was somehow
"unauthorized".
Seems like the build should fail if the actual JAR file would get overridden,
not if the classifier happens to be the same. That is, the conflict is at the
actual filesystem level.
> jar:jar without classifier replaces default jar
> ---
>
> Key: MJAR-198
> URL: https://issues.apache.org/jira/browse/MJAR-198
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1, 2.3.2, 2.4, 2.5, 2.6
> Environment: Windows 8.1 Pro
> JDK 1.8 45
> Maven 3.2.5
>Reporter: Elias Elmqvist Wulcan
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Labels: newbie
> Fix For: 3.0.0
>
> Attachments: 0.tar, mvn.install.debug.txt
>
>
> If I add an execution of jar:jar in a project of packaging jar and do not
> configure a classifier for the additional jar, the additional jar will be
> installed instead of the default jar.
> Omitting a classifier in the configuration for the goal jar:jar is documented
> to have the effect that the jar will not be attached and this is the behavior
> that I want. Instead, the jar is attached and replaces the default jar.
> AbstractJarMojo.java:254 checks nullness of classifier to decide whether to
> attach or not. JarMojo.java:51 declares a default value the empty string for
> classifier. Maybe the combination of these lines cause the bug.
> http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java?revision=1664111=markup
> http://svn.apache.org/viewvc/maven/plugins/tags/maven-jar-plugin-2.6/src/main/java/org/apache/maven/plugin/jar/JarMojo.java?revision=1664111=markup
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6386) project.baseUri is not a valid URL on Windows
[
https://issues.apache.org/jira/browse/MNG-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420954#comment-16420954
]
Michael Osipov commented on MNG-6386:
-
Pushed branches to maven.git and maven-integration-testing.git runs flawlessly
on
{noformat}
Apache Maven 3.5.4-SNAPSHOT (fef1462102d8a3c42f31b6e43dae988767c814ff;
2018-03-30T21:54:36+02:00)
Maven home: D:\apache-maven-3.5.4-SNAPSHOT
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_162\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
and
{noformat}
Apache Maven 3.5.4-SNAPSHOT (43b34598629f086523a333dc18665389643832a5;
2018-03-30T22:23:14+02:00)
Maven home: /home/mosipov/apache-maven-3.5.4-SNAPSHOT
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "11.1-release-p8", arch: "i386", family: "unix"
{noformat}
> project.baseUri is not a valid URL on Windows
> -
>
> Key: MNG-6386
> URL: https://issues.apache.org/jira/browse/MNG-6386
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> {{File#toURI}} produces an invalid URL on Windows:
> {noformat}
> file:/C:/path/to/basedir{noformat}
> A valid URI has to be:
> {noformat}
> file:///C:/path/to/basedir{noformat}
> Using {{Path#toUri}} we can easily solve that problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420919#comment-16420919
]
Mark Lehky commented on SUREFIRE-1480:
--
[~tibor17] As per
http://maven.apache.org/surefire/maven-failsafe-plugin/source-repository.html I
tried:
{code}
$ git clone --branch surefire-2.21.0_vote-1
https://git-wip-us.apache.org/repos/asf/maven-surefire.git
Cloning into 'maven-surefire'...
fatal: repository 'https://git-wip-us.apache.org/repos/asf/maven-surefire.git/'
not found
{code}
:(
Instead I guessed:
{code}
$ git clone g...@github.com:apache/maven-surefire.git
$ cd maven-surefire/maven-failsafe-plugin
$ git checkout surefire-2.21.0_vote-1
{code}
So what am I looking at now? Not sure where to start.
> parallel tests may produce invalid .xml report
> --
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Mark Lehky
>Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
> * Jenkins 2.108
> * Maven 3.??
> * JUnit 4.12
> * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple
> JUnit methods), which are all run in parallel. Some of the tests may be
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
>
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being
> flagged as failed, and Jenkins simply has the message:
> "TEST-xml.[failed-to-read]" (the dots are replaced with the correct
> filename!).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPH-144.
---
Resolution: Done
Done in
[316656983d780c04031bbadd97d4ab245c84d014|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=316656983d780c04031bbadd97d4ab245c84d014]
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420912#comment-16420912
]
Hudson commented on MPH-144:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #27
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/27/
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420910#comment-16420910
]
Hudson commented on MPH-144:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-144 #4
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-144/4/
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-147) plexus-interactivity-api to 1.0-alpha-6
[ https://issues.apache.org/jira/browse/MPH-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420909#comment-16420909 ] Hudson commented on MPH-147: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-144 #4 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-144/4/ > plexus-interactivity-api to 1.0-alpha-6 > --- > > Key: MPH-147 > URL: https://issues.apache.org/jira/browse/MPH-147 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MJAR-240) maven-jar-plugin index.html - bad links in left column Examples section
[
https://issues.apache.org/jira/browse/MJAR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJAR-240:
-
Fix Version/s: 3.1.0
> maven-jar-plugin index.html - bad links in left column Examples section
> ---
>
> Key: MJAR-240
> URL: https://issues.apache.org/jira/browse/MJAR-240
> Project: Maven JAR Plugin
> Issue Type: Bug
> Components: site
>Reporter: Brian Brooks
>Priority: Trivial
> Labels: documentation
> Fix For: 3.1.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> At the site https://maven.apache.org/plugins/maven-jar-plugin/index.html in
> the leftColumn div there are some bad links
> # In leftColumn {{Creating an Executable JAR File}}
> {code}
>
>
> Creating an Executable JAR File
> {code}
> # In leftColumn {{Using Your Own Manifest File}}. Clicking on that hyperlink
> results in an HTTP 404 error.
> {code}
>
>
> Using Your Own Manifest File
> {code}
> # in
> [Usage|https://maven.apache.org/plugins/maven-jar-plugin/index.html#Usage]
> section hyperlink {{plugin's wiki page}}
> {code}
> href="http://docs.codehaus.org/display/MAVENUSER/JAR+Plugin;>plugin's wiki
> page
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJAR-240) maven-jar-plugin index.html - bad links in left column Examples section
[
https://issues.apache.org/jira/browse/MJAR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJAR-240.
Resolution: Implemented
Assignee: Karl Heinz Marbaise
> maven-jar-plugin index.html - bad links in left column Examples section
> ---
>
> Key: MJAR-240
> URL: https://issues.apache.org/jira/browse/MJAR-240
> Project: Maven JAR Plugin
> Issue Type: Bug
> Components: site
>Reporter: Brian Brooks
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Labels: documentation
> Fix For: 3.1.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> At the site https://maven.apache.org/plugins/maven-jar-plugin/index.html in
> the leftColumn div there are some bad links
> # In leftColumn {{Creating an Executable JAR File}}
> {code}
>
>
> Creating an Executable JAR File
> {code}
> # In leftColumn {{Using Your Own Manifest File}}. Clicking on that hyperlink
> results in an HTTP 404 error.
> {code}
>
>
> Using Your Own Manifest File
> {code}
> # in
> [Usage|https://maven.apache.org/plugins/maven-jar-plugin/index.html#Usage]
> section hyperlink {{plugin's wiki page}}
> {code}
> href="http://docs.codehaus.org/display/MAVENUSER/JAR+Plugin;>plugin's wiki
> page
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAR-236) Keep maven-compiler-plugin to 3.5.1 based on JDK9 issues
[ https://issues.apache.org/jira/browse/MJAR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420895#comment-16420895 ] Karl Heinz Marbaise commented on MJAR-236: -- Based on MJAR-246 maven-compiler-plugin is updated to 3.7.0 > Keep maven-compiler-plugin to 3.5.1 based on JDK9 issues > > > Key: MJAR-236 > URL: https://issues.apache.org/jira/browse/MJAR-236 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.1.0 > > > Undone the update of maven-compiler-plugin from 3.5.1 to 3.6.1 cause the > upgrade could cause issues related to JDK9 (automodules for example). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-3760) Support property ${baseurl} to get RFC-compliant URL of project base directory
[
https://issues.apache.org/jira/browse/MNG-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420891#comment-16420891
]
Michael Osipov commented on MNG-3760:
-
The given solution does to provide an RFC-compliant URL on Windows.
> Support property ${baseurl} to get RFC-compliant URL of project base directory
> --
>
> Key: MNG-3760
> URL: https://issues.apache.org/jira/browse/MNG-3760
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories, Inheritance and Interpolation
>Affects Versions: 2.0.9
>Reporter: Benjamin Bentmann
>Assignee: Brett Porter
>Priority: Minor
> Fix For: 2.1.0, 3.0-alpha-3
>
>
> If people currently need a URL to their project base directory or any file
> within, they need to write {{file://$\{basedir}}/}}. The problem about this
> approach is that it doesn't deliver a [RFC-compliant
> URL|http://tools.ietf.org/html/rfc3986] since characters are not properly
> percent-encoded. Also, the exact number of slashes between {{file:}} and
> {{${basedir}}} depends on the OS (e.g. {{file:///C:/user/}} and
> {{file:///home/user}}, Unix paths have a leading slash by themselves, Windows
> not). This makes it currently impossible to configure plugins that expect a
> URL as input and do strict URL parsing.
> For this reason, I suggest to support an additional property {{${baseurl}}}
> with the value
> {code:java}
> baseurl = new File( basedir ).toURI().toString()
> {code}
> for POM interpolation.
> Some day, when Maven/Wagon itself handle percent-encoded {{file:}} URLs
> correctly (WAGON-111), this property could also be used to define local
> deployment repos like we commonly use for testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-3760) Support property ${baseurl} to get RFC-compliant URL of project base directory
[
https://issues.apache.org/jira/browse/MNG-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420891#comment-16420891
]
Michael Osipov edited comment on MNG-3760 at 3/30/18 8:12 PM:
--
The given solution does not provide a RFC-compliant URL on Windows.
was (Author: michael-o):
The given solution does to provide an RFC-compliant URL on Windows.
> Support property ${baseurl} to get RFC-compliant URL of project base directory
> --
>
> Key: MNG-3760
> URL: https://issues.apache.org/jira/browse/MNG-3760
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories, Inheritance and Interpolation
>Affects Versions: 2.0.9
>Reporter: Benjamin Bentmann
>Assignee: Brett Porter
>Priority: Minor
> Fix For: 2.1.0, 3.0-alpha-3
>
>
> If people currently need a URL to their project base directory or any file
> within, they need to write {{file://$\{basedir}}/}}. The problem about this
> approach is that it doesn't deliver a [RFC-compliant
> URL|http://tools.ietf.org/html/rfc3986] since characters are not properly
> percent-encoded. Also, the exact number of slashes between {{file:}} and
> {{${basedir}}} depends on the OS (e.g. {{file:///C:/user/}} and
> {{file:///home/user}}, Unix paths have a leading slash by themselves, Windows
> not). This makes it currently impossible to configure plugins that expect a
> URL as input and do strict URL parsing.
> For this reason, I suggest to support an additional property {{${baseurl}}}
> with the value
> {code:java}
> baseurl = new File( basedir ).toURI().toString()
> {code}
> for POM interpolation.
> Some day, when Maven/Wagon itself handle percent-encoded {{file:}} URLs
> correctly (WAGON-111), this property could also be used to define local
> deployment repos like we commonly use for testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420886#comment-16420886 ] Hudson commented on MPIR-366: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » MPIR-366 #4 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-366/4/ > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420879#comment-16420879 ] Robert Scholte commented on MPIR-366: - It is kind of repeating the same trick. It is mainly about getting rid of usage of maven-compat. The Wagon change is new and huge and I'm kind of surprised everything still works. It also look like the number of tests is quite low, so I'm a bit afraid for the coverage. We might need a 3.0.0-M1 first if that's okay. > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPH-147) plexus-interactivity-api to 1.0-alpha-6
[ https://issues.apache.org/jira/browse/MPH-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-147. --- Resolution: Fixed Done in [af749d464c2eb026bcffdc8915bbb2c99a82ebb9|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=af749d464c2eb026bcffdc8915bbb2c99a82ebb9] > plexus-interactivity-api to 1.0-alpha-6 > --- > > Key: MPH-147 > URL: https://issues.apache.org/jira/browse/MPH-147 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSITE-814) How to filter site.xml when building site with maven-site-plugin?
[
https://issues.apache.org/jira/browse/MSITE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSITE-814.
Resolution: Invalid
Consider support from users@ or Stackoverflow where I lurk around. The question
on a SO is pretty lousy on details.
> How to filter site.xml when building site with maven-site-plugin?
> -
>
> Key: MSITE-814
> URL: https://issues.apache.org/jira/browse/MSITE-814
> Project: Maven Site Plugin
> Issue Type: Wish
>Reporter: Matthieu Ghilain
>Priority: Major
>
> This question originates from a post I have created on stackoverflow:
> [https://stackoverflow.com/questions/49569674/how-to-filter-site-xml-when-building-site-with-maven-site-plugin]
> Maybe it is worth answering there so that it gains visibility :).
> *Copy of the question:*
> I am building a site with maven-site-plugin.
> I would like to include a placeholder in my site.xml which should be replaced
> with an environment variable ${env.my_variable} unfortunately this does not
> seems to work. Is there a way to do this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6387) Pom files should have a dedicated mime type registered ("application/pom+xml" or similar)
[
https://issues.apache.org/jira/browse/MNG-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420867#comment-16420867
]
Michael Osipov commented on MNG-6387:
-
Can you elaborate what issues the current situation causes and what benefit
would be have by registered with IANA?
> Pom files should have a dedicated mime type registered ("application/pom+xml"
> or similar)
> -
>
> Key: MNG-6387
> URL: https://issues.apache.org/jira/browse/MNG-6387
> Project: Maven
> Issue Type: Wish
> Components: POM
>Reporter: Alex Dubov
>Priority: Trivial
>
> For the sake of convenience working with ever growing abundance of packages,
> and, thus, pom files, is not it time to give the humble pom file its own,
> dedicated mime type (something to the tune of "application/pom+xml")?
> Presently, the fact that pom files don't have a dedicated mime type causes
> all kinds of minor but annoying issues in all kinds of least expected places.
> Considering that registering a mime type with IANA is a pretty
> straightforward process and that pom files are widely used for all kinds of
> automation purposes (and not exclusively by maven anymore), I, on behalf of
> the wider community, urge you to consider registering a dedicated pom mime
> type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420866#comment-16420866 ] Michael Osipov commented on MPIR-366: - Please nag me when you are done. This change is massive...a lot of code looks very familiar from other plugins. It seems to be that we are repeating the same boiler plate code over and over again, aren't we? > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-147) plexus-interactivity-api to 1.0-alpha-6
[ https://issues.apache.org/jira/browse/MPH-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420864#comment-16420864 ] Hudson commented on MPH-147: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #26 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/26/ > plexus-interactivity-api to 1.0-alpha-6 > --- > > Key: MPH-147 > URL: https://issues.apache.org/jira/browse/MPH-147 > Project: Maven Help Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MRESOURCES-244) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MRESOURCES-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRESOURCES-244. -- Resolution: Fixed Done in [346e393077a6fc2882bf25b3e438108f69746c60|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commitdiff;h=346e393077a6fc2882bf25b3e438108f69746c60] > Upgrade plexus-utils 3.1.0 > -- > > Key: MRESOURCES-244 > URL: https://issues.apache.org/jira/browse/MRESOURCES-244 > Project: Maven Resources Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOURCES-244) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MRESOURCES-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420855#comment-16420855 ] Hudson commented on MRESOURCES-244: --- Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » master #7 See https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/master/7/ > Upgrade plexus-utils 3.1.0 > -- > > Key: MRESOURCES-244 > URL: https://issues.apache.org/jira/browse/MRESOURCES-244 > Project: Maven Resources Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPH-147) plexus-interactivity-api to 1.0-alpha-6
Karl Heinz Marbaise created MPH-147: --- Summary: plexus-interactivity-api to 1.0-alpha-6 Key: MPH-147 URL: https://issues.apache.org/jira/browse/MPH-147 Project: Maven Help Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420851#comment-16420851
]
Karl Heinz Marbaise commented on MPH-144:
-
Ah now I got it...But I hope I've already done them..
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420843#comment-16420843 ] Hudson commented on MPIR-366: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » MPIR-366 #3 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-366/3/ > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420841#comment-16420841
]
Michael Osipov commented on MPH-144:
I have a few comments on the first commit on the branch before your have force
pushed to it. Please have a look.
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MPH-146) JavaDoc Issues / Code cleanups
Karl Heinz Marbaise created MPH-146:
---
Summary: JavaDoc Issues / Code cleanups
Key: MPH-146
URL: https://issues.apache.org/jira/browse/MPH-146
Project: Maven Help Plugin
Issue Type: Task
Affects Versions: 3.1.0
Reporter: Karl Heinz Marbaise
Fix For: 3.1.0
* Currently building JavaDoc with JDK 8 fails.
* Each {{Version: $Id$}} should be removed
*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420832#comment-16420832
]
Karl Heinz Marbaise commented on MPH-144:
-
Can you give a hint what you have in mind? Maybe I'm little bit blockhead...
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MRESOURCES-244) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MRESOURCES-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRESOURCES-244: --- Issue Type: Dependency upgrade (was: Task) > Upgrade plexus-utils 3.1.0 > -- > > Key: MRESOURCES-244 > URL: https://issues.apache.org/jira/browse/MRESOURCES-244 > Project: Maven Resources Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.3 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MRESOURCES-244) Upgrade plexus-utils 3.1.0
Karl Heinz Marbaise created MRESOURCES-244: -- Summary: Upgrade plexus-utils 3.1.0 Key: MRESOURCES-244 URL: https://issues.apache.org/jira/browse/MRESOURCES-244 Project: Maven Resources Plugin Issue Type: Task Affects Versions: 3.0.3 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420824#comment-16420824
]
Michael Osipov commented on MPH-144:
The Javadoc still needs some polish.
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-144:
Description:
Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
help:evaluate -Dexpression=project.groupId -q}} you won't get anything printed
out at all.
It would be a good idea to have an output via a supplemental parameter like
this:
{{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to get
printed out the information like this only:
{code}
0.2.0-SNAPSHOT
{code}
this would give the opportunity to use the call within scripts without
filtering out things like {{[INFO]...}} etc.
This would work like this:
{{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
-q)}}
was:
Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
help:evaluate -Dexpression=project.groupId -q}} you won't get anything printed
out at all.
It would be a good idea to have an output via a supplemental parameter like
this:
{{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to get
printed out the information like this only:
{code}
0.2.0-SNAPSHOT
{code}
this would give the opportunity to use the call within scripts directory
without filtering out things lie {{[INFO]...}} etc. like this:
{{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
-q)}}
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts without
> filtering out things like {{[INFO]...}} etc.
> This would work like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJAR-245) Additional attached jar: role of classifyer
[ https://issues.apache.org/jira/browse/MJAR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAR-245. Resolution: Fixed Done in [3ec43fddd0aceb62b985fb9ff59bbeb6efd6d312|https://gitbox.apache.org/repos/asf?p=maven-jar-plugin.git;a=commitdiff;h=3ec43fddd0aceb62b985fb9ff59bbeb6efd6d312] > Additional attached jar: role of classifyer > > > Key: MJAR-245 > URL: https://issues.apache.org/jira/browse/MJAR-245 > Project: Maven JAR Plugin > Issue Type: Bug > Components: site >Affects Versions: 3.0.2 >Reporter: Ernst Reissner >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > On > [https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html,] > a classifier is given. > Missing information: creates a jar file: > project-version-classifier.jar. > This is vital. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-245) Additional attached jar: role of classifyer
[ https://issues.apache.org/jira/browse/MJAR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420789#comment-16420789 ] Hudson commented on MJAR-245: - Build succeeded in Jenkins: Maven TLP » maven-jar-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/master/9/ > Additional attached jar: role of classifyer > > > Key: MJAR-245 > URL: https://issues.apache.org/jira/browse/MJAR-245 > Project: Maven JAR Plugin > Issue Type: Bug > Components: site >Affects Versions: 3.0.2 >Reporter: Ernst Reissner >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > On > [https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html,] > a classifier is given. > Missing information: creates a jar file: > project-version-classifier.jar. > This is vital. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420786#comment-16420786
]
Hudson commented on MPH-144:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-144 #3
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-144/3/
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-144:
Fix Version/s: 3.1.0
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-144:
---
Affects Version/s: 3.0.1
> Add ability to print mvn help:evaluate output to stdout in quiet mode.
> --
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-144:
---
Summary: Add ability to print mvn help:evaluate output to stdout in quiet
mode (was: Add ability to print mvn help:evaluate output to stdout in quiet
mode.)
> Add ability to print mvn help:evaluate output to stdout in quiet mode
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420782#comment-16420782
]
Karl Heinz Marbaise commented on MPH-144:
-
Better title yes. Thanks.
> Add ability to print mvn help:evaluate output to stdout in quiet mode.
> --
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-144:
---
Component/s: evaluate
> Add ability to print mvn help:evaluate output to stdout in quiet mode.
> --
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: evaluate
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) Add ability to print mvn help:evaluate output to stdout in quiet mode.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-144:
Summary: Add ability to print mvn help:evaluate output to stdout in quiet
mode. (was: mvn help:evaluate -Dexpression=project.groupId -q does not print
anything)
> Add ability to print mvn help:evaluate output to stdout in quiet mode.
> --
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAR-245) Additional attached jar: role of classifyer
[ https://issues.apache.org/jira/browse/MJAR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420781#comment-16420781 ] Hudson commented on MJAR-245: - Build succeeded in Jenkins: Maven TLP » maven-jar-plugin » MJAR-245 #2 See https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-245/2/ > Additional attached jar: role of classifyer > > > Key: MJAR-245 > URL: https://issues.apache.org/jira/browse/MJAR-245 > Project: Maven JAR Plugin > Issue Type: Bug > Components: site >Affects Versions: 3.0.2 >Reporter: Ernst Reissner >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > On > [https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html,] > a classifier is given. > Missing information: creates a jar file: > project-version-classifier.jar. > This is vital. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-249) Get Build working on JDK 10
[ https://issues.apache.org/jira/browse/MJAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420780#comment-16420780 ] Hudson commented on MJAR-249: - Build succeeded in Jenkins: Maven TLP » maven-jar-plugin » MJAR-245 #2 See https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-245/2/ > Get Build working on JDK 10 > --- > > Key: MJAR-249 > URL: https://issues.apache.org/jira/browse/MJAR-249 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) mvn help:evaluate -Dexpression=project.groupId -q does not print anything
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420775#comment-16420775
]
Michael Osipov commented on MPH-144:
The title implies that there is a bug, but the issue type is improvement. There
is no bug, but default behavior. I'd change the title to: Add ability to print
mvn help:evaluate output to stdout in quiet mode.
> mvn help:evaluate -Dexpression=project.groupId -q does not print anything
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420771#comment-16420771 ] Hudson commented on MPH-145: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-144 #2 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-144/2/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) mvn help:evaluate -Dexpression=project.groupId -q does not print anything
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420772#comment-16420772
]
Hudson commented on MPH-144:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-144 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-144/2/
> mvn help:evaluate -Dexpression=project.groupId -q does not print anything
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJAR-249) Get Build working on JDK 10
[ https://issues.apache.org/jira/browse/MJAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAR-249. Resolution: Fixed Done in [39fc58f506136dea2ec1354dca18661a590d0984|https://gitbox.apache.org/repos/asf?p=maven-jar-plugin.git;a=commitdiff;h=39fc58f506136dea2ec1354dca18661a590d0984] > Get Build working on JDK 10 > --- > > Key: MJAR-249 > URL: https://issues.apache.org/jira/browse/MJAR-249 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJAR-249) Get Build working on JDK 10
[ https://issues.apache.org/jira/browse/MJAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420767#comment-16420767 ] Hudson commented on MJAR-249: - Build succeeded in Jenkins: Maven TLP » maven-jar-plugin » master #8 See https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/master/8/ > Get Build working on JDK 10 > --- > > Key: MJAR-249 > URL: https://issues.apache.org/jira/browse/MJAR-249 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-145. --- Resolution: Fixed Done in [bbaa0c0abc8ff826ab2095bd64ad2ab09cd4afcd|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=bbaa0c0abc8ff826ab2095bd64ad2ab09cd4afcd] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420764#comment-16420764 ] Hudson commented on MPH-145: Build succeeded in Jenkins: Maven TLP » maven-help-plugin » master #25 See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/master/25/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPH-145: Fix Version/s: (was: Backlog) 3.1.0 > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPH-145: Affects Version/s: (was: 3.1.0) 3.0.1 > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MPH-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPH-145: Affects Version/s: (was: 3.0.1) 3.1.0 > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MPH-145 > URL: https://issues.apache.org/jira/browse/MPH-145 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > > We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPH-145) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MPH-145: --- Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MPH-145 URL: https://issues.apache.org/jira/browse/MPH-145 Project: Maven Help Plugin Issue Type: Task Affects Versions: 3.0.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: Backlog We need to upgrade surefire/failsafe to get JDK10 builds running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-144) mvn help:evaluate -Dexpression=project.groupId -q does not print anything
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-144:
Summary: mvn help:evaluate -Dexpression=project.groupId -q does not print
anything (was: mvn help:evaluate -Dexpression=project.groupId Can't be used in
scripts.)
> mvn help:evaluate -Dexpression=project.groupId -q does not print anything
> -
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPH-144:
Description:
Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
help:evaluate -Dexpression=project.groupId -q}} you won't get anything printed
out at all.
It would be a good idea to have an output via a supplemental parameter like
this:
{{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to get
printed out the information like this only:
{code}
0.2.0-SNAPSHOT
{code}
this would give the opportunity to use the call within scripts directory
without filtering out things lie {{[INFO]...}} etc. like this:
{{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
-q)}}
was:
Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
help:evaluate -Dexpression=project.groupId -q}} you won't get anything printed
out.
It would be a good idea to have an output via a supplemental parameter like
this:
{{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
printed out the information like this (:
{code}
0.2.0-SNAPSHOT
{code}
this would give the opportunity to use the call within scripts etc.
Also might be possible in one go:
{{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
to write the expression result into a file.
Or the question is if it would be possible/good idea to print out the resulting
expression anyway (ignoring -q for only {{[INFO]...}} parts)
{{mvn help:evaluate -Dexpression=project.groupId -q}}
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} there
> are printed out some lines like {{[INFO] ...]]}}. If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out at all.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true -q}} to
> get printed out the information like this only:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts directory
> without filtering out things lie {{[INFO]...}} etc. like this:
> {{RESULT=$(mvn help:evaluate -Dexpression=project.groupId -DforceStdout=true
> -q)}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAR-249) Get Build working on JDK 10
[ https://issues.apache.org/jira/browse/MJAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420717#comment-16420717 ] Hudson commented on MJAR-249: - Build succeeded in Jenkins: Maven TLP » maven-jar-plugin » MJAR-249 #3 See https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-249/3/ > Get Build working on JDK 10 > --- > > Key: MJAR-249 > URL: https://issues.apache.org/jira/browse/MJAR-249 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420713#comment-16420713
]
Michael Osipov commented on MPH-144:
The title and the issue do not match at all. Of course, {{mvn help:evaluate}}
can be used in scripts already. You want a quite/minimal mode. Please change
the title accordingly because reading the git log does not reflect the change.
The rest will be commented on GitHub.
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}}
> there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
> printed out the information like this (:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts etc.
> Also might be possible in one go:
> {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
> to write the expression result into a file.
> Or the question is if it would be possible/good idea to print out the
> resulting expression anyway (ignoring -q for only {{[INFO]...}} parts)
> {{mvn help:evaluate -Dexpression=project.groupId -q}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420713#comment-16420713
]
Michael Osipov edited comment on MPH-144 at 3/30/18 5:10 PM:
-
The title and the issue do not match at all. Of course, {{mvn help:evaluate}}
can be used in scripts already. You want a quite/minimal mode. Please change
the title accordingly because reading the git log does not reflect the change.
The rest will be commented on GitHub.
The commit introduces many trailing space, please trim. As well as formatting
changes not related to the issue, please undo.
was (Author: michael-o):
The title and the issue do not match at all. Of course, {{mvn help:evaluate}}
can be used in scripts already. You want a quite/minimal mode. Please change
the title accordingly because reading the git log does not reflect the change.
The rest will be commented on GitHub.
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}}
> there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
> printed out the information like this (:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts etc.
> Also might be possible in one go:
> {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
> to write the expression result into a file.
> Or the question is if it would be possible/good idea to print out the
> resulting expression anyway (ignoring -q for only {{[INFO]...}} parts)
> {{mvn help:evaluate -Dexpression=project.groupId -q}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNGSITE-331) Links to JIRA are wrong
Karl Heinz Marbaise created MNGSITE-331: --- Summary: Links to JIRA are wrong Key: MNGSITE-331 URL: https://issues.apache.org/jira/browse/MNGSITE-331 Project: Maven Project Web Site Issue Type: Bug Reporter: Karl Heinz Marbaise Currently the links to JIRA on this page http://maven.apache.org/pom/ are simply wrong cause they produce a 404... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MTOOLCHAINS-22) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MTOOLCHAINS-22. -- Resolution: Fixed Done in [4b747bb2b76380de081f3f34c7a87573ddd4586b|https://gitbox.apache.org/repos/asf?p=maven-toolchains-plugin.git;a=commitdiff;h=4b747bb2b76380de081f3f34c7a87573ddd4586b] > Upgrade parent to 31 > > > Key: MTOOLCHAINS-22 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-22 > Project: Maven Toolchains Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MVERIFIER-26) JavaDoc issues
[
https://issues.apache.org/jira/browse/MVERIFIER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420554#comment-16420554
]
Karl Heinz Marbaise commented on MVERIFIER-26:
--
Blocked by https://github.com/codehaus-plexus/modello/issues/16
> JavaDoc issues
> ---
>
> Key: MVERIFIER-26
> URL: https://issues.apache.org/jira/browse/MVERIFIER-26
> Project: Maven Verifier Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.0
>
>
> {code}
> [WARNING] Error fetching link: http://junit.org/apidocs/package-list. Ignored
> it.
> [INFO]
> 2 errors
> 31 warnings
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 24.265 s
> [INFO] Finished at: 2018-03-30T15:55:25+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
> maven-verifier-plugin: Error generating maven-javadoc-plugin:3.0.0:javadoc
> report:
> [ERROR] Exit code: 1 -
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerificationResult.java:49:
> error: unknown tag: linke
> [ERROR] * @param file {@linke File}
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:237:
> error: unexpected content
> [ERROR] * @see {@link VerificationResultPrinter}
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:239:
> warning - Tag @see:illegal character: "123" in "{@link
> VerificationResultPrinter}"
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:239:
> warning - Tag @see:illegal character: "64" in "{@link
> VerificationResultPrinter}"
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:87:
> warning: no description for @param
> [ERROR] * @param contains
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:102:
> warning: no description for @param
> [ERROR] * @param exists
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:112:
> warning: no description for @param
> [ERROR] * @param location
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:40:
> warning: no description for @param
> [ERROR] * @param file
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:75:
> warning: no description for @param
> [ERROR] * @param file
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:85:
> warning: no description for @param
> [ERROR] * @param files
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:95:
> warning: no description for @param
> [ERROR] * @param modelEncoding
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:540:
> warning: no description for @param
> [ERROR] * @param reader
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:541:
> warning: no description for @param
> [ERROR] * @param strict
> [ERROR]^
> [ERROR]
> /Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:542:
> warning: no description for @throws
> [ERROR] * @throws IOException
> [ERROR]^
> [ERROR]
>
[jira] [Commented] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420521#comment-16420521
]
Jean-Luc Derrien commented on SUREFIRE-1263:
[~tibor17], I don't use Java or Surefire anymore (for now).
I took a few minutes today to run tests against the small project hosted on my
github account. What I can say:
- SUREFIRE-1263 is fixed with {{2.21.0}}
- About SUREFRE-1264, I cannot reproduce the problem with {{2.19.1}}. That's
weird.
[~tlemeur] could probably give you more details. He and his team are still
working on the project on which we faced those issues.
Thank you for the follow up.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>Priority: Major
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MVERIFIER-26) JavaDoc issues
Karl Heinz Marbaise created MVERIFIER-26:
Summary: JavaDoc issues
Key: MVERIFIER-26
URL: https://issues.apache.org/jira/browse/MVERIFIER-26
Project: Maven Verifier Plugin
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Fix For: 3.0.0
{code}
[WARNING] Error fetching link: http://junit.org/apidocs/package-list. Ignored
it.
[INFO]
2 errors
31 warnings
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 24.265 s
[INFO] Finished at: 2018-03-30T15:55:25+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
maven-verifier-plugin: Error generating maven-javadoc-plugin:3.0.0:javadoc
report:
[ERROR] Exit code: 1 -
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerificationResult.java:49:
error: unknown tag: linke
[ERROR] * @param file {@linke File}
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:237:
error: unexpected content
[ERROR] * @see {@link VerificationResultPrinter}
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:239:
warning - Tag @see:illegal character: "123" in "{@link
VerificationResultPrinter}"
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/src/main/java/org/apache/maven/plugins/verifier/VerifierMojo.java:239:
warning - Tag @see:illegal character: "64" in "{@link
VerificationResultPrinter}"
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:87:
warning: no description for @param
[ERROR] * @param contains
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:102:
warning: no description for @param
[ERROR] * @param exists
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/File.java:112:
warning: no description for @param
[ERROR] * @param location
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:40:
warning: no description for @param
[ERROR] * @param file
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:75:
warning: no description for @param
[ERROR] * @param file
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:85:
warning: no description for @param
[ERROR] * @param files
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/Verifications.java:95:
warning: no description for @param
[ERROR] * @param modelEncoding
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:540:
warning: no description for @param
[ERROR] * @param reader
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:541:
warning: no description for @param
[ERROR] * @param strict
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:542:
warning: no description for @throws
[ERROR] * @throws IOException
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:543:
warning: no description for @throws
[ERROR] * @throws XmlPullParserException
[ERROR]^
[ERROR]
/Users/kama/ws-git-maven/plugins/maven-verifier-plugin/target/generated-sources/modello/org/apache/maven/plugin/verifier/model/io/xpp3/VerificationsXpp3Reader.java:560:
warning: no description for @param
[ERROR] * @param reader
[jira] [Closed] (MVERIFIER-25) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MVERIFIER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MVERIFIER-25. Resolution: Fixed Done in [2fc16e8981e97d9e2b7f138ffae28f14bdf27cf2|https://gitbox.apache.org/repos/asf?p=maven-verifier-plugin.git;a=commitdiff;h=2fc16e8981e97d9e2b7f138ffae28f14bdf27cf2] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MVERIFIER-25 > URL: https://issues.apache.org/jira/browse/MVERIFIER-25 > Project: Maven Verifier Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MVERIFIER-25) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MVERIFIER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420509#comment-16420509 ] Hudson commented on MVERIFIER-25: - Build succeeded in Jenkins: Maven TLP » maven-verifier-plugin » master #10 See https://builds.apache.org/job/maven-box/job/maven-verifier-plugin/job/master/10/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MVERIFIER-25 > URL: https://issues.apache.org/jira/browse/MVERIFIER-25 > Project: Maven Verifier Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MVERIFIER-23) maven-failsafe-plugin IntegrationTestMojo @Override
[
https://issues.apache.org/jira/browse/MVERIFIER-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MVERIFIER-23.
Resolution: Won't Fix
Unfortunately this is related to failsafe plugin and not verifier plugin. Apart
from that I think it's already fixed in more recent versions of
surefire/failsafe plugins.
> maven-failsafe-plugin IntegrationTestMojo @Override
> ---
>
> Key: MVERIFIER-23
> URL: https://issues.apache.org/jira/browse/MVERIFIER-23
> Project: Maven Verifier Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: JDK 1.8
> Maven-3.2.5
>Reporter: Martin Gainty
>Priority: Minor
> Labels: easyfix
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> maven-failsafe-plugin-2.19.2-SNAPSHOT
> org.apache.maven.plugin.failsafe.IntegrationTestMojo.java contains
> superfluous @Override
> //@Override /* getReportSchemaLocation not exist in base class */
> protected String getReportSchemaLocation()
> {
> return
> "https://maven.apache.org/surefire/maven-failsafe-plugin/xsd/failsafe-test-report.xsd;;
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MVERIFIER-25) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MVERIFIER-25: Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MVERIFIER-25 URL: https://issues.apache.org/jira/browse/MVERIFIER-25 Project: Maven Verifier Plugin Issue Type: Bug Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MTOOLCHAINS-22) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MTOOLCHAINS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420502#comment-16420502 ] Hudson commented on MTOOLCHAINS-22: --- Build succeeded in Jenkins: Maven TLP » maven-toolchains-plugin » master #7 See https://builds.apache.org/job/maven-box/job/maven-toolchains-plugin/job/master/7/ > Upgrade parent to 31 > > > Key: MTOOLCHAINS-22 > URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-22 > Project: Maven Toolchains Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPOM-184) Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues
[ https://issues.apache.org/jira/browse/MPOM-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MPOM-184: - Fix Version/s: ASF-20 > Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues > --- > > Key: MPOM-184 > URL: https://issues.apache.org/jira/browse/MPOM-184 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: doxia-tools, maven-plugins, maven-shared-components >Affects Versions: MAVEN-31 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: ASF-20, MAVEN-32 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-184) Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues
[ https://issues.apache.org/jira/browse/MPOM-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPOM-184. Resolution: Fixed Done in [9f9963ad7d8616204afe8768b8597e5d9dad6697|https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commitdiff;h=9f9963ad7d8616204afe8768b8597e5d9dad6697] > Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues > --- > > Key: MPOM-184 > URL: https://issues.apache.org/jira/browse/MPOM-184 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: doxia-tools, maven-plugins, maven-shared-components >Affects Versions: MAVEN-31 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: ASF-20, MAVEN-32 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPOM-184) Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues
[ https://issues.apache.org/jira/browse/MPOM-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420495#comment-16420495 ] Hudson commented on MPOM-184: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #14 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/14/ > Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues > --- > > Key: MPOM-184 > URL: https://issues.apache.org/jira/browse/MPOM-184 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: doxia-tools, maven-plugins, maven-shared-components >Affects Versions: MAVEN-31 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: MAVEN-32 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MRAR-73) Fix JavaDoc issues which fail the site generation
[ https://issues.apache.org/jira/browse/MRAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRAR-73. --- Resolution: Fixed Done in [18fbb07e526c5961a6e51358ef1084568fe9f7dd|https://gitbox.apache.org/repos/asf?p=maven-rar-plugin.git;a=commitdiff;h=18fbb07e526c5961a6e51358ef1084568fe9f7dd] > Fix JavaDoc issues which fail the site generation > - > > Key: MRAR-73 > URL: https://issues.apache.org/jira/browse/MRAR-73 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRAR-73) Fix JavaDoc issues which fail the site generation
[ https://issues.apache.org/jira/browse/MRAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420492#comment-16420492 ] Hudson commented on MRAR-73: Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #6 See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/master/6/ > Fix JavaDoc issues which fail the site generation > - > > Key: MRAR-73 > URL: https://issues.apache.org/jira/browse/MRAR-73 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRAR-73) Fix JavaDoc issues which fail the site generation
[ https://issues.apache.org/jira/browse/MRAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420491#comment-16420491 ] Hudson commented on MRAR-73: Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » MRAR-73 #2 See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/MRAR-73/2/ > Fix JavaDoc issues which fail the site generation > - > > Key: MRAR-73 > URL: https://issues.apache.org/jira/browse/MRAR-73 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MRAR-73) Fix JavaDoc issues which fail the site generation
Karl Heinz Marbaise created MRAR-73: --- Summary: Fix JavaDoc issues which fail the site generation Key: MRAR-73 URL: https://issues.apache.org/jira/browse/MRAR-73 Project: Maven Rar Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRAR-56) Remove param properties that doesn't make sense for CLI usage
[ https://issues.apache.org/jira/browse/MRAR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420465#comment-16420465 ] Karl Heinz Marbaise commented on MRAR-56: - The following are candidates to be removed: * finalName > Remove param properties that doesn't make sense for CLI usage > - > > Key: MRAR-56 > URL: https://issues.apache.org/jira/browse/MRAR-56 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: n/a >Reporter: Anders Hammar >Priority: Major > Fix For: 3.0.0 > > > Currently the plugin supports configuring several of the parameters via CLI > properties. This doesn't make sense in many cases and encourages bad Maven > usage (builds should be reproducible). Remove the properties for those > parameters. The v3.0.0 release is a good time to do this. > First of all we need to identify candidates for removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JXR-138) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/JXR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed JXR-138. --- Resolution: Fixed Done in [a48977363adca2d394db27a2055c26c0756a04ec|https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=commitdiff;h=a48977363adca2d394db27a2055c26c0756a04ec] > Upgrade parent to 31 > > > Key: JXR-138 > URL: https://issues.apache.org/jira/browse/JXR-138 > Project: Maven JXR > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MRAR-45) Usage example errors
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRAR-45. --- Resolution: Fixed Done in [1b8d3abf33b77af8fedade43f2e4a6999dcd0aac|https://gitbox.apache.org/repos/asf?p=maven-rar-plugin.git;a=commitdiff;h=1b8d3abf33b77af8fedade43f2e4a6999dcd0aac] > Usage example errors > > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRAR-72) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MRAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420451#comment-16420451 ] Hudson commented on MRAR-72: Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #5 See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/master/5/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MRAR-72 > URL: https://issues.apache.org/jira/browse/MRAR-72 > Project: Maven Rar Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRAR-45) Usage example errors
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420452#comment-16420452 ] Hudson commented on MRAR-45: Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #5 See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/master/5/ > Usage example errors > > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MRAR-45) Usage example errors
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-45: Summary: Usage example errors (was: Usage example) > Usage example errors > > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MRAR-45) Usage example
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-45: Fix Version/s: 3.0.0 > Usage example > - > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MRAR-45) Usage example
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-45: Affects Version/s: 2.4 > Usage example > - > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MRAR-45) Usage example
[ https://issues.apache.org/jira/browse/MRAR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MRAR-45: --- Assignee: Karl Heinz Marbaise > Usage example > - > > Key: MRAR-45 > URL: https://issues.apache.org/jira/browse/MRAR-45 > Project: Maven Rar Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: lukasz.deputat >Assignee: Karl Heinz Marbaise >Priority: Minor > Labels: documentation, easyfix > Fix For: 3.0.0 > > > https://maven.apache.org/plugins/maven-rar-plugin/usage.html > Page has 2 errors in example of usage: > 1. Missing tag under section. > 2. Missing close tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420437#comment-16420437
]
Karl Heinz Marbaise edited comment on MPH-144 at 3/30/18 12:34 PM:
---
I have created an implementation on the appropriate branch...I use
{{forceStdout=true}}
was (Author: khmarbaise):
I have created an implementation on the appropriate branch...
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}}
> there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
> printed out the information like this (:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts etc.
> Also might be possible in one go:
> {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
> to write the expression result into a file.
> Or the question is if it would be possible/good idea to print out the
> resulting expression anyway (ignoring -q for only {{[INFO]...}} parts)
> {{mvn help:evaluate -Dexpression=project.groupId -q}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420437#comment-16420437
]
Karl Heinz Marbaise commented on MPH-144:
-
I have created an implementation on the appropriate branch...
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}}
> there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
> printed out the information like this (:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts etc.
> Also might be possible in one go:
> {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
> to write the expression result into a file.
> Or the question is if it would be possible/good idea to print out the
> resulting expression anyway (ignoring -q for only {{[INFO]...}} parts)
> {{mvn help:evaluate -Dexpression=project.groupId -q}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MPH-144) mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
[
https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MPH-144:
---
Assignee: Karl Heinz Marbaise
> mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts.
>
>
> Key: MPH-144
> URL: https://issues.apache.org/jira/browse/MPH-144
> Project: Maven Help Plugin
> Issue Type: New Feature
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}}
> there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn
> help:evaluate -Dexpression=project.groupId -q}} you won't get anything
> printed out.
> It would be a good idea to have an output via a supplemental parameter like
> this:
> {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get
> printed out the information like this (:
> {code}
> 0.2.0-SNAPSHOT
> {code}
> this would give the opportunity to use the call within scripts etc.
> Also might be possible in one go:
> {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}}
> to write the expression result into a file.
> Or the question is if it would be possible/good idea to print out the
> resulting expression anyway (ignoring -q for only {{[INFO]...}} parts)
> {{mvn help:evaluate -Dexpression=project.groupId -q}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (JXR-137) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/JXR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed JXR-137. --- Resolution: Fixed Done in [6b3107d4f8653b311fc4a17201ae3a26216a654e|https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=commitdiff;h=6b3107d4f8653b311fc4a17201ae3a26216a654e] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: JXR-137 > URL: https://issues.apache.org/jira/browse/JXR-137 > Project: Maven JXR > Issue Type: Task >Affects Versions: next-release >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: next-release > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JXR-138) Upgrade parent to 31
Karl Heinz Marbaise created JXR-138: --- Summary: Upgrade parent to 31 Key: JXR-138 URL: https://issues.apache.org/jira/browse/JXR-138 Project: Maven JXR Issue Type: Task Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MRAR-72) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MRAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRAR-72. --- Resolution: Fixed Done in [5ee75aaab8dec62e75e15c856c1ad073c8f1da05|https://gitbox.apache.org/repos/asf?p=maven-rar-plugin.git;a=commitdiff;h=5ee75aaab8dec62e75e15c856c1ad073c8f1da05] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MRAR-72 > URL: https://issues.apache.org/jira/browse/MRAR-72 > Project: Maven Rar Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420424#comment-16420424
]
Tibor Digana commented on SUREFIRE-1263:
[~jderrien]
I came back to the issues you reported in passed (SUREFIRE-1263 and
SUREFIRE-1264) because we are working on another multi-threading issue.
I want to ask you if you are facing any further issue with Parameterized JUnit
tests with latest Surefire Version {{2.21.0}} and I want to know if we fixed
these completely.
> No class name in log when running tests in parallel with parameterized tests
>
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>Priority: Major
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log
> when the tests are run in parallel with parameterized tests.
> According to this [small
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in
> parallel mode:
> {noformat}
> ---
> T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec -
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec -
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO]
>
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
> T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 -
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 -
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 -
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec -
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec -
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in
> parallel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420422#comment-16420422 ] Hudson commented on MPIR-366: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » MPIR-366 #2 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/MPIR-366/2/ > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6387) Pom files should have a dedicated mime type registered ("application/pom+xml" or similar)
Alex Dubov created MNG-6387:
---
Summary: Pom files should have a dedicated mime type registered
("application/pom+xml" or similar)
Key: MNG-6387
URL: https://issues.apache.org/jira/browse/MNG-6387
Project: Maven
Issue Type: Wish
Components: POM
Reporter: Alex Dubov
For the sake of convenience working with ever growing abundance of packages,
and, thus, pom files, is not it time to give the humble pom file its own,
dedicated mime type (something to the tune of "application/pom+xml")?
Presently, the fact that pom files don't have a dedicated mime type causes all
kinds of minor but annoying issues in all kinds of least expected places.
Considering that registering a mime type with IANA is a pretty straightforward
process and that pom files are widely used for all kinds of automation purposes
(and not exclusively by maven anymore), I, on behalf of the wider community,
urge you to consider registering a dedicated pom mime type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
