[jira] (MINVOKER-181) Create single summary file
[ https://jira.codehaus.org/browse/MINVOKER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365527#comment-365527 ] Robert Scholte commented on MINVOKER-181: - IMHO we can remove the success lines, because it doesn't really add much info and will make this file unnecessary long in case of a lot of ITs. > Create single summary file > -- > > Key: MINVOKER-181 > URL: https://jira.codehaus.org/browse/MINVOKER-181 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Robert Scholte >Assignee: Karl-Heinz Marbaise > Fix For: 1.9.1 > > > When you execute ITs from a console and you close it, it is very hard to > figure out which ITs failed. There should be a single summary file which > shows the results of all ITs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-181) Create single summary file
[ https://jira.codehaus.org/browse/MINVOKER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365528#comment-365528 ] Karl-Heinz Marbaise commented on MINVOKER-181: -- Ok we could remove the success lines and only put something in there which is NOT success. > Create single summary file > -- > > Key: MINVOKER-181 > URL: https://jira.codehaus.org/browse/MINVOKER-181 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Robert Scholte >Assignee: Karl-Heinz Marbaise > Fix For: 1.9.1 > > > When you execute ITs from a console and you close it, it is very hard to > figure out which ITs failed. There should be a single summary file which > shows the results of all ITs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-427) add support for SCM urls with IPv6
[
https://jira.codehaus.org/browse/WAGON-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed WAGON-427.
---
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Herve Boutemy
applied PR https://github.com/apache/maven-wagon/pull/17 in
[479f7bea|http://git-wip-us.apache.org/repos/asf/maven-wagon/commit/479f7bea]
> add support for SCM urls with IPv6
> --
>
> Key: WAGON-427
> URL: https://jira.codehaus.org/browse/WAGON-427
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
>Affects Versions: 2.8
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.9
>
>
> with IPv6 coming, we should support it in scm urls
> {noformat}http://[2001:db8:a88:85a3::ac1f:8001]/index.html
> http://[2001:db8:a88:85a3::ac1f:8001]:8080/index.html
> http://[::1]:8080/{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-424) upgrade parent pom to latest
[ https://jira.codehaus.org/browse/WAGON-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed WAGON-424. --- Resolution: Fixed Assignee: Herve Boutemy done in [5fcf54b9|http://git-wip-us.apache.org/repos/asf/maven-wagon/commit/5fcf54b9] > upgrade parent pom to latest > > > Key: WAGON-424 > URL: https://jira.codehaus.org/browse/WAGON-424 > Project: Maven Wagon > Issue Type: Task >Affects Versions: 2.7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Critical > Fix For: 2.9 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-154) invoker:report doesn't show pom.xml name & description of the project
[
https://jira.codehaus.org/browse/MINVOKER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365531#comment-365531
]
Robert Scholte commented on MINVOKER-154:
-
Right now, if you have an {{invoker.name}} and an {{invoker.description}} in
your {{invoker.properties}}, these values are used.
> invoker:report doesn't show pom.xml name & description of the project
> -
>
> Key: MINVOKER-154
> URL: https://jira.codehaus.org/browse/MINVOKER-154
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Herve Boutemy
>
> when the IT pom.xml defines name and description, it should be displayed in
> the report instead of only the path to pom.xml
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-155) Invoker plugin does not allow multiple environment variables to be set
[
https://jira.codehaus.org/browse/MINVOKER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MINVOKER-155:
Fix Version/s: 1.9.1
> Invoker plugin does not allow multiple environment variables to be set
> --
>
> Key: MINVOKER-155
> URL: https://jira.codehaus.org/browse/MINVOKER-155
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Observed with Maven 3.0.4, both Windows 7 and RedHat
> Linux
>Reporter: Laura Llewellyn
>Assignee: Robert Scholte
> Fix For: 1.9.1
>
> Attachments: maven-env-test.zip
>
>
> Multiple environment variables may be specified using the
> {{environmentVariables}} parameter as shown below. However, only one of the
> variables is actually passed to the test cases.
> {code:title=Plugin Configuration}
>
>white
>blue
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-100) MavenVersion + ToolChain instead of mavenHome
[ https://jira.codehaus.org/browse/MINVOKER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MINVOKER-100: --- Assignee: Robert Scholte > MavenVersion + ToolChain instead of mavenHome > - > > Key: MINVOKER-100 > URL: https://jira.codehaus.org/browse/MINVOKER-100 > Project: Maven Invoker Plugin > Issue Type: New Feature >Affects Versions: 1.5 >Reporter: Robert Scholte >Assignee: Robert Scholte > Attachments: MINVOKER-100.patch > > > Jdk-paths are just as personal as maven-paths. It's already great to have the > opportunity to change the mavenHome, but combining it with toolchain would > provide an even more elegant way of defining the Maven installation to use. > Just set the mavenVersion property of this plugin and let toolchain provide > you the right mavenHome. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-168) Document the supplemental information about the maven version
[ https://jira.codehaus.org/browse/MINVOKER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MINVOKER-168. --- Resolution: Fixed Assignee: Anders Hammar fixed in [r1537603|http://svn.apache.org/r1537603] > Document the supplemental information about the maven version > - > > Key: MINVOKER-168 > URL: https://jira.codehaus.org/browse/MINVOKER-168 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Karl-Heinz Marbaise >Assignee: Anders Hammar > Fix For: 1.9 > > > The information about the mavenVersion variable should be documented > somewhere. > http://maven.apache.org/plugins/maven-invoker-plugin/examples/post-build-script.html > Currently it is not documented. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-125) Global variable about the target folder into the groovy scripts.
[
https://jira.codehaus.org/browse/MINVOKER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MINVOKER-125:
Description: Often (may be everytime) groovy scripts (post-build) which are
doing work in relationship with integration-tests must access the *target*
folder to check results etc. But currently i have to hard code the folder
"target" by contrast in the pom.xml there already exists a good replacement for
that $\{project.build.directory} so it would be very helpful to have an context
information like "target" which represents the target folder. (was: Often (may
be everytime) groovy scripts (post-build) which are doing work in relationship
with integration-tests must access the *target* folder to check results etc.
But currently i have to hard code the folder "target" by contrast in the
pom.xml there already exists a good replacement for that
${project.build.directory} so it would be very helpful to have an context
information like "target" which represents the target folder.)
> Global variable about the target folder into the groovy scripts.
>
>
> Key: MINVOKER-125
> URL: https://jira.codehaus.org/browse/MINVOKER-125
> Project: Maven Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.5
>Reporter: Karl-Heinz Marbaise
>Priority: Minor
>
> Often (may be everytime) groovy scripts (post-build) which are doing work in
> relationship with integration-tests must access the *target* folder to check
> results etc. But currently i have to hard code the folder "target" by
> contrast in the pom.xml there already exists a good replacement for that
> $\{project.build.directory} so it would be very helpful to have an context
> information like "target" which represents the target folder.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
