[ 
https://issues.apache.org/jira/browse/MJDEPS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MJDEPS-10:
---------------------------------
    Description: 
Moving this from 
[StackOverflow#46727928|https://stackoverflow.com/questions/46727928/error-unknown-option-m-while-using-module-option-of-maven-jdeps-plugin]

Using minimal pom.xml with Java9 as -
{code:xml}
    <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-jdeps-plugin</artifactId>
            <version>3.1.0</version>
            <configuration>
                <module>true</module>
            </configuration>
            <executions>
                <execution>
                    <goals>
                        <goal>jdkinternals</goal> <!-- verify main classes -->
                        <goal>test-jdkinternals</goal> <!-- verify test classes 
-->
                    </goals>
                </execution>
            </executions>
        </plugin>
{code}

Results into 
{noformat}
Error: unknown option: -M
Usage: jdeps <options> <path ...>]
use -h, -?, -help, or --help for a list of possible options
{noformat}

Also, {{-m <module-name>/ --module <module-name>}} in the tool I can see are 
used to specify the root module for analysis..would this also need a change in 
Type of the attribute? (not aware of what was the initial construct of the tool 
used to be)

  was:
Moving this from 
[StackOverflow#46727928|https://stackoverflow.com/questions/46727928/error-unknown-option-m-while-using-module-option-of-maven-jdeps-plugin]

Using minimal pom.xml with Java9 as -
    <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-jdeps-plugin</artifactId>
            <version>3.1.0</version>
            <configuration>
                <module>true</module>
            </configuration>
            <executions>
                <execution>
                    <goals>
                        <goal>jdkinternals</goal> <!-- verify main classes -->
                        <goal>test-jdkinternals</goal> <!-- verify test classes 
-->
                    </goals>
                </execution>
            </executions>
        </plugin>

Results into 
bq. Error: unknown option: -M
bq. Usage: jdeps <options> <path ...>]
bq. use -h, -?, -help, or --help for a list of possible options

Also, `-m <module-name>/ --module <module-name>` in the tool I can see are used 
to specify the root module for analysis..would this also need a change in Type 
of the attribute? (not aware of what was the initial construct of the tool used 
to be)


> Error: unknown option: -M while using module option of maven-jdeps-plugin
> -------------------------------------------------------------------------
>
>                 Key: MJDEPS-10
>                 URL: https://issues.apache.org/jira/browse/MJDEPS-10
>             Project: MJDEPS
>          Issue Type: Bug
>            Reporter: Naman Nigam
>
> Moving this from 
> [StackOverflow#46727928|https://stackoverflow.com/questions/46727928/error-unknown-option-m-while-using-module-option-of-maven-jdeps-plugin]
> Using minimal pom.xml with Java9 as -
> {code:xml}
>     <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-jdeps-plugin</artifactId>
>             <version>3.1.0</version>
>             <configuration>
>                 <module>true</module>
>             </configuration>
>             <executions>
>                 <execution>
>                     <goals>
>                         <goal>jdkinternals</goal> <!-- verify main classes -->
>                         <goal>test-jdkinternals</goal> <!-- verify test 
> classes -->
>                     </goals>
>                 </execution>
>             </executions>
>         </plugin>
> {code}
> Results into 
> {noformat}
> Error: unknown option: -M
> Usage: jdeps <options> <path ...>]
> use -h, -?, -help, or --help for a list of possible options
> {noformat}
> Also, {{-m <module-name>/ --module <module-name>}} in the tool I can see are 
> used to specify the root module for analysis..would this also need a change 
> in Type of the attribute? (not aware of what was the initial construct of the 
> tool used to be)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to