[ 
https://jira.codehaus.org/browse/MNG-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348032#comment-348032
 ] 

Jason van Zyl commented on MNG-4713:
------------------------------------

Fair enough. I'm going to do another purge based on issues that affect pre-3.0 
versions that I can't easily reproduce. In the last few weeks I have worked 
pretty hard to take another pass at cleaning up JIRA but still couldn't get it 
under 200 after 25 issues being closed. In practice I'm the only one closing 
out issues so I'm to get more extreme in closing out anything that's not easy 
for me to reproduce. If someone is not willing to put in the number of hours to 
reproduce the issue then neither am I. If someone gives me consumable pull 
requests with tests I will start trying my best to absorb them. Which I think 
I've done a pretty good job during this release.

I'm not trying to be accusatory toward you specifically but I just don't have 
the time to sift through time consuming issues which require me to reproduce 
everything to validate. I want to get the issue count down to zero and I'm 
going to do whatever I have to in order to get there.

> ${basedir} variable makes portable builds overly difficult
> ----------------------------------------------------------
>
>                 Key: MNG-4713
>                 URL: https://jira.codehaus.org/browse/MNG-4713
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Design, Patterns & Best Practices
>    Affects Versions: 2.2.1
>            Reporter: Gili
>             Fix For: Issues to be reviewed for 3.x
>
>
> Please reopen MNG-3198. I believe that Brett misunderstood what Jochen wrote. 
> There is no simple workaround with the current Maven implementation. Jochen 
> was saying that Maven should use unix-style slashes under Windows for the 
> sake of portability and let users convert to Windows-style slashes themselves 
> if they wish to use an external script.
> Simple use-case: try passing a $\{basedir\}-relative path into the 
> "java.library.path" property. It's impossible to do this portably under 
> Maven's existing implementation.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to