jira-importer commented on issue #481: URL: https://github.com/apache/maven-scm/issues/481#issuecomment-2964598214
**[Grzeg Plotnicki](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=plotek)** commented The ability to provide a complex filespec using perforce's own clientspec rather than the minimal path in the scm url seems like a FUNDAMENTAL issue to be resolved in order for the maven perforce plug-in to be useable. (please, correct me if I'm wrong!!! ;-)) this inability is made worst by the fact that the current implementation of the maven perforce plug-in will actually overwrite the existing clientspec making it unusable as well. Considering that it's been over 6 months since the issue has been reported and it's still not fixed, the question is really: is my understanding of what is fundamental to the functioning of maven perforce plug-in incorrect or is the development of the plug-in stagnated? p.s. please, excuse (and redirect) if this is not the right forum to ask this question. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
