[jira] [Commented] (MNG-7424) "systemPath" of dependency can't set cross system platform
[ https://issues.apache.org/jira/browse/MNG-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558733#comment-17558733 ] shalk commented on MNG-7424: For your problem , You can set two profile to windows and linux to handle different systemPath Value. Also I don't think write systemPath and deploy it to private repo is a good idea. > "systemPath" of dependency can't set cross system platform > -- > > Key: MNG-7424 > URL: https://issues.apache.org/jira/browse/MNG-7424 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.8.4 >Reporter: RayLee >Priority: Minor > Fix For: waiting-for-feedback > > Original Estimate: 1h > Remaining Estimate: 1h > > In my team we work on both linux and windows . > And we use some jar library not in maven repository，so we use "system" scope > to help. > "systemPath" must set a absolute path, but: > on windows "c:/xxx" is absolute path, "/opt/xxx" not > on linux "/opt/xxx" is absolute path, "c:/xxx" not > If we develop a private library witch has a system dependency and deploy it > in a private maven repo, there will be some error when maven download > dependency. > > I write a test.jar, > when we set "/xxx/xxx/xx.jar" as "systemPath" in test.pom , on linux it > works, even "xx.jar" file does not exist, the test.jar can download correctly. > but same "/xxx/xxx/xx.jar" on windows will cause a warning: "must specify an > absolute path but is xxx", and will not download the test.jar. > > I think since maven will not require the existence of the system scope jar it > depends on when downloading the test.jar, then it can friendly support set > "systemPath" as cross-platform absolute path. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MPMD-409) Support maven-pmd-extension
[ https://issues.apache.org/jira/browse/MPMD-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shalk updated MPMD-409: --- Summary: Support maven-pmd-extension (was: how about to support maven-pmd-extension) > Support maven-pmd-extension > --- > > Key: MPMD-409 > URL: https://issues.apache.org/jira/browse/MPMD-409 > Project: Maven PMD Plugin > Issue Type: New Feature >Reporter: shalk >Priority: Major > > Maven have a ability _Extensions. > https://maven.apache.org/guides/mini/guide-using-extensions.html_ > If pmd can support extension , that will make many exist procjets not need > to change pom.xml. > > ref : > https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPMD-409) how about to support maven pmd extension
shalk created MPMD-409: -- Summary: how about to support maven pmd extension Key: MPMD-409 URL: https://issues.apache.org/jira/browse/MPMD-409 Project: Maven PMD Plugin Issue Type: New Feature Reporter: shalk Maven have a ability _Extensions. https://maven.apache.org/guides/mini/guide-using-extensions.html_ If pmd can support extension , that will make many exist procjets not need to change pom.xml. ref : https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-409) how about to support maven-pmd-extension
[ https://issues.apache.org/jira/browse/MPMD-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shalk updated MPMD-409: --- Summary: how about to support maven-pmd-extension (was: how about to support maven pmd extension) > how about to support maven-pmd-extension > > > Key: MPMD-409 > URL: https://issues.apache.org/jira/browse/MPMD-409 > Project: Maven PMD Plugin > Issue Type: New Feature >Reporter: shalk >Priority: Major > > Maven have a ability _Extensions. > https://maven.apache.org/guides/mini/guide-using-extensions.html_ > If pmd can support extension , that will make many exist procjets not need > to change pom.xml. > > ref : > https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPMD-409) Support maven-pmd-extension
[ https://issues.apache.org/jira/browse/MPMD-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shalk updated MPMD-409: --- Description: Maven have a ability _Extensions. [https://maven.apache.org/guides/mini/guide-using-extensions.html_] If pmd can support extension , may exist procjets can be more easy to use pmd when continuous integration (CI) ref : [https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension] was: Maven have a ability _Extensions. https://maven.apache.org/guides/mini/guide-using-extensions.html_ If pmd can support extension , that will make many exist procjets not need to change pom.xml. ref : https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension > Support maven-pmd-extension > --- > > Key: MPMD-409 > URL: https://issues.apache.org/jira/browse/MPMD-409 > Project: Maven PMD Plugin > Issue Type: New Feature >Reporter: shalk >Priority: Major > > Maven have a ability _Extensions. > [https://maven.apache.org/guides/mini/guide-using-extensions.html_] > If pmd can support extension , may exist procjets can be more easy to use > pmd when continuous integration (CI) > > ref : > [https://github.com/apache/maven-enforcer/tree/master/maven-enforcer-extension] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
