[jira] [Created] (MNG-6175) Regression from version 3.0.4: Whitespaces get deleted in "pom.xml".
Jesko Jochum created MNG-6175: - Summary: Regression from version 3.0.4: Whitespaces get deleted in "pom.xml". Key: MNG-6175 URL: https://issues.apache.org/jira/browse/MNG-6175 Project: Maven Issue Type: Sub-task Components: Plugin API Affects Versions: 3.3.9 Reporter: Jesko Jochum Priority: Minor Fix For: 3.0.4 Leading and trailing whitespaces in the "pom.xml" get deleted. Exemplary excerpt of a "pom.xml" file: ... 1 ... Checking the "effective pom" results in: ... ... 1 ... ... So the leading and trailing whitespaces have been deleted. [MNG-5380] states this to be resolved since version 3.0.4. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-5438) cli parameter to use a custom path settings-security.xml
[ https://issues.apache.org/jira/browse/MNG-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876195#comment-15876195 ] Paul Landolt commented on MNG-5438: --- This has been a big "missing" for a long time. Any team using shared build machines and enterprise build tools (Bamboo, Jenkins, TeamCity, etc) must patch around this on the fly. The proposed solution worked at the time. What are the odds of an updated patch / pull request getting accepted? > cli parameter to use a custom path settings-security.xml > > > Key: MNG-5438 > URL: https://issues.apache.org/jira/browse/MNG-5438 > Project: Maven > Issue Type: New Feature > Components: Command Line >Affects Versions: 3.0.4, 3.0.5 >Reporter: Sarah Haselbauer > Attachments: apache-maven-3.0.4-ssec-bin.tar.gz, > apache-maven-3.0.4-ssec-bin.zip, > maven-3.0.4-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch, > maven-latest-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch > > > added -ssec as cli param, so that you have the same flexibility to place your > settings-security.xml as you have to point to a custom settings.xml file > mvn -s /path/to/my/custom/settings.xml -ssec > /path/to/my/custom/settings-security.xml > I attached to patches: one that can be run on the maven-3.0.4 tag and one > that can be run on trunk (latest code state of today). > I also attached a maven-3.0.4-bin.zip (linux) so you can quickly try out the > feature and test it yourself. > if you like the idea, I would welcome to have this feature merged into one of > the next releases. I need it to write a puppet-maven module that allows to > download artifacts from maven repositories with encrypted passwords in the > puppet recipe. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MPMD-232) Enable typeResolution by default
Juan Martín Sotuyo Dodero created MPMD-232: -- Summary: Enable typeResolution by default Key: MPMD-232 URL: https://issues.apache.org/jira/browse/MPMD-232 Project: Maven PMD Plugin Issue Type: Improvement Components: PMD Reporter: Juan Martín Sotuyo Dodero For some time now PMD has supported type resolution, allowing PMD rules to make better decisions by having knowledge of all classes in both the project, and the classpath. However, when using PMD through the Maven plugin, the auxclasspath for type resolution is not populated by default. There is a property to control this behavior, but it's set to false by default. See https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#typeResolution I believe there is no reason to have it off by default (actually, I don't think there is any valid reason to have it off at all!). Type resolution means better and more accurate analysis results. If there are no rules configured requiring type resolution, the type resolution analysis is skipped completely, meaning there is no performance impact either. I've not checked, but just in case the classpath passed to PMD should include: - all dependencies - the .class files generated by compiling the project's source code -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SCM-763) Password masking on linux does not work
[
https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876320#comment-15876320
]
Weston Bustraan commented on SCM-763:
-
This also occurs on Macs.
The culprit is actually
{{org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.cryptPassword(Commandline)}}
It has a rather... naïve, to be polite, implementation of the password masking.
It only works if there is _exactly_ one space after {{--password}}. Any other
condition and the password is not masked.
So, if the command line string is this:
{code}svn --username myusername --password swordfish --no-auth-cache
--non-interactive --trust-server-cert info{code}
... the output is:
{code}svn --username myusername --password '*' --no-auth-cache
--non-interactive --trust-server-cert info{code}
However, it appears that, at some point, a change was made elsewhere that wraps
everything in quotes on *nix OSes:
{code}
'svn' '--username' 'myusername' '--password' 'swordfish' '--no-auth-cache'
'--non-interactive' '--trust-server-cert' 'info'
{code}
Now, since {{--password}} is followed immediately by a single quote, instead of
a single space, the mask is inserted but does not replace the actual password:
{code}'svn' '--username' 'myusername' '--password''*' 'swordfish'
'--no-auth-cache' '--non-interactive' '--trust-server-cert' 'info'{code}
Here is an improved version of {{cryptPassword}} using a regex in order to
handle more diverse input:
{code}
public static String cryptPassword( Commandline cl )
{
String clString = cl.toString();
final String mask = "'**'";
final Matcher matcher =
Pattern.compile("(--password\\S*?\\s+)('[^']+?'|\"[^\"]+?\"|\\S+)")
.matcher(clString);
final StringBuffer replaced = new StringBuffer();
while (matcher.find()) {
final String argPrefix = matcher.group(1);
matcher.appendReplacement(replaced, argPrefix + mask);
}
matcher.appendTail(replaced);
return replaced.toString();
}
{code}
> Password masking on linux does not work
> ---
>
> Key: SCM-763
> URL: https://issues.apache.org/jira/browse/SCM-763
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.9
> Environment: Jenkins 1.502 on a SLES11
>Reporter: Tobias Kalmes
>
> Passwords are not masked in the log output on Linux machines. The masking
> works as intended on Windows machines. On linux machines tho the password is
> printed in clear text. This seems to be a problem due to the additional
> single quotes that are added around the parameters on linux machines.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MJAVADOC-478) NullPointerException thrown by Javadoc tool
[
https://issues.apache.org/jira/browse/MJAVADOC-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876498#comment-15876498
]
Robert Scholte commented on MJAVADOC-478:
-
[JDK-8175263|https://bugs.openjdk.java.net/browse/JDK-8175263] is closed as
'not an issue' with feedback.
> NullPointerException thrown by Javadoc tool
> ---
>
> Key: MJAVADOC-478
> URL: https://issues.apache.org/jira/browse/MJAVADOC-478
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Windows 10 64-bit
>Reporter: Gili
> Attachments: javadoc-npe.zip, testcase2.zip
>
>
> When running the javadoc goal I am getting a NullPointerException back.
> Unfortunately, the maven plugin does not provide me with enough information
> to figure out what command-line is being passed to the external javadoc tool,
> so I am unable to report this bug to Oracle.
> Here is the debug output from Maven:
> {code}
> cd C:\Users\Gili\Documents\requirements\core; "JAVA_HOME=C:\\Program
> Files\\Java\\jdk1.8.0_121" "M2_HOME=C:\\Program Files\\apache-maven-3.3.9"
> cmd /c "\"\"C:\\Program Files\\apache-maven-3.3.9\\bin\\mvn.cmd\"
> -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
> 8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" generate-sources
> javadoc:javadoc -X\""
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: C:\Program Files\apache-maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_121\jre
> Default locale: en_CA, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> Included C:\Program Files\NetBeans
> 8.2\java\maven-nblib\netbeans-eventspy.jar
> Populating class realm maven.ext
> Included C:\Program Files\NetBeans
> 8.2\java\maven-nblib\netbeans-eventspy.jar
> Created new class realm maven.api
> Importing foreign packages into class realm maven.api
> Imported: javax.enterprise.inject.* < maven.ext
> Imported: javax.enterprise.util.* < maven.ext
> Imported: javax.inject.* < maven.ext
> Imported: org.apache.maven.* < maven.ext
> Imported: org.apache.maven.artifact < maven.ext
> Imported: org.apache.maven.classrealm < maven.ext
> Imported: org.apache.maven.cli < maven.ext
> Imported: org.apache.maven.configuration < maven.ext
> Imported: org.apache.maven.exception < maven.ext
> Imported: org.apache.maven.execution < maven.ext
> Imported: org.apache.maven.execution.scope < maven.ext
> Imported: org.apache.maven.lifecycle < maven.ext
> Imported: org.apache.maven.model < maven.ext
> Imported: org.apache.maven.monitor < maven.ext
> Imported: org.apache.maven.plugin < maven.ext
> Imported: org.apache.maven.profiles < maven.ext
> Imported: org.apache.maven.project < maven.ext
> Imported: org.apache.maven.reporting < maven.ext
> Imported: org.apache.maven.repository < maven.ext
> Imported: org.apache.maven.rtinfo < maven.ext
> Imported: org.apache.maven.settings < maven.ext
> Imported: org.apache.maven.toolchain < maven.ext
> Imported: org.apache.maven.usability < maven.ext
> Imported: org.apache.maven.wagon.* < maven.ext
> Imported: org.apache.maven.wagon.authentication < maven.ext
> Imported: org.apache.maven.wagon.authorization < maven.ext
> Imported: org.apache.maven.wagon.events < maven.ext
> Imported: org.apache.maven.wagon.observers < maven.ext
> Imported: org.apache.maven.wagon.proxy < maven.ext
> Imported: org.apache.maven.wagon.repository < maven.ext
> Imported: org.apache.maven.wagon.resource < maven.ext
> Imported: org.codehaus.classworlds < maven.ext
> Imported: org.codehaus.plexus.* < maven.ext
> Imported: org.codehaus.plexus.classworlds < maven.ext
> Imported: org.codehaus.plexus.component < maven.ext
> Imported: org.codehaus.plexus.configuration < maven.ext
> Imported: org.codehaus.plexus.container < maven.ext
> Imported: org.codehaus.plexus.context < maven.ext
> Imported: org.codehaus.plexus.lifecycle < maven.ext
> Imported: org.codehaus.plexus.logging < maven.ext
> Imported: org.codehaus.plexus.personality < maven.ext
> Imported: org.codehaus.plexus.util.xml.Xpp3Dom < maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException <
> maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < maven.ext
> Imported: org.eclipse.aether.* < maven.ext
> Imported: org.eclipse.aether.artifact < maven.ext
> Imported: org.eclipse.aether.collection < maven.ext
> Imported: org.eclipse.aether.deployment < maven.ext
> Imported: org.eclipse.aether.graph < maven.ext
> Imported: org.eclipse.aether.impl
[jira] [Commented] (MJAVADOC-478) NullPointerException thrown by Javadoc tool
[
https://issues.apache.org/jira/browse/MJAVADOC-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876627#comment-15876627
]
Gili commented on MJAVADOC-478:
---
Ugh. I think the evaluator missed the fact that the generated Javadoc contains
broken/incorrect links. If you look up the bad interface in the "Exception
summary" or Search Box and click on the link, you will get redirected to the
good interface. Meaning, the generated links are actually wrong.
I'm okay with using {{@hidden}} for the rest of the issues.
> NullPointerException thrown by Javadoc tool
> ---
>
> Key: MJAVADOC-478
> URL: https://issues.apache.org/jira/browse/MJAVADOC-478
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Windows 10 64-bit
>Reporter: Gili
> Attachments: javadoc-npe.zip, testcase2.zip
>
>
> When running the javadoc goal I am getting a NullPointerException back.
> Unfortunately, the maven plugin does not provide me with enough information
> to figure out what command-line is being passed to the external javadoc tool,
> so I am unable to report this bug to Oracle.
> Here is the debug output from Maven:
> {code}
> cd C:\Users\Gili\Documents\requirements\core; "JAVA_HOME=C:\\Program
> Files\\Java\\jdk1.8.0_121" "M2_HOME=C:\\Program Files\\apache-maven-3.3.9"
> cmd /c "\"\"C:\\Program Files\\apache-maven-3.3.9\\bin\\mvn.cmd\"
> -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
> 8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" generate-sources
> javadoc:javadoc -X\""
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T11:41:47-05:00)
> Maven home: C:\Program Files\apache-maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_121\jre
> Default locale: en_CA, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> Included C:\Program Files\NetBeans
> 8.2\java\maven-nblib\netbeans-eventspy.jar
> Populating class realm maven.ext
> Included C:\Program Files\NetBeans
> 8.2\java\maven-nblib\netbeans-eventspy.jar
> Created new class realm maven.api
> Importing foreign packages into class realm maven.api
> Imported: javax.enterprise.inject.* < maven.ext
> Imported: javax.enterprise.util.* < maven.ext
> Imported: javax.inject.* < maven.ext
> Imported: org.apache.maven.* < maven.ext
> Imported: org.apache.maven.artifact < maven.ext
> Imported: org.apache.maven.classrealm < maven.ext
> Imported: org.apache.maven.cli < maven.ext
> Imported: org.apache.maven.configuration < maven.ext
> Imported: org.apache.maven.exception < maven.ext
> Imported: org.apache.maven.execution < maven.ext
> Imported: org.apache.maven.execution.scope < maven.ext
> Imported: org.apache.maven.lifecycle < maven.ext
> Imported: org.apache.maven.model < maven.ext
> Imported: org.apache.maven.monitor < maven.ext
> Imported: org.apache.maven.plugin < maven.ext
> Imported: org.apache.maven.profiles < maven.ext
> Imported: org.apache.maven.project < maven.ext
> Imported: org.apache.maven.reporting < maven.ext
> Imported: org.apache.maven.repository < maven.ext
> Imported: org.apache.maven.rtinfo < maven.ext
> Imported: org.apache.maven.settings < maven.ext
> Imported: org.apache.maven.toolchain < maven.ext
> Imported: org.apache.maven.usability < maven.ext
> Imported: org.apache.maven.wagon.* < maven.ext
> Imported: org.apache.maven.wagon.authentication < maven.ext
> Imported: org.apache.maven.wagon.authorization < maven.ext
> Imported: org.apache.maven.wagon.events < maven.ext
> Imported: org.apache.maven.wagon.observers < maven.ext
> Imported: org.apache.maven.wagon.proxy < maven.ext
> Imported: org.apache.maven.wagon.repository < maven.ext
> Imported: org.apache.maven.wagon.resource < maven.ext
> Imported: org.codehaus.classworlds < maven.ext
> Imported: org.codehaus.plexus.* < maven.ext
> Imported: org.codehaus.plexus.classworlds < maven.ext
> Imported: org.codehaus.plexus.component < maven.ext
> Imported: org.codehaus.plexus.configuration < maven.ext
> Imported: org.codehaus.plexus.container < maven.ext
> Imported: org.codehaus.plexus.context < maven.ext
> Imported: org.codehaus.plexus.lifecycle < maven.ext
> Imported: org.codehaus.plexus.logging < maven.ext
> Imported: org.codehaus.plexus.personality < maven.ext
> Imported: org.codehaus.plexus.util.xml.Xpp3Dom < maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException <
> maven.ext
> Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < maven.ext
> Imported: org.eclipse.aether.* < maven.ext
> Imported: org.ecli
[jira] [Created] (SUREFIRE-1336) Sure-Fire test run totals don't match TestNG report on failure.
Jeff Vincent created SUREFIRE-1336: -- Summary: Sure-Fire test run totals don't match TestNG report on failure. Key: SUREFIRE-1336 URL: https://issues.apache.org/jira/browse/SUREFIRE-1336 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.19.1 Environment: Oracle JDK 1.8.0_121, Maven 3.3.9, TestNG 6.10 Reporter: Jeff Vincent Priority: Minor Attachments: testng-console.png, testng-reportnghtml.png One of my TestNG test classes has 2 multi-threaded test methods that use DataProviders to feed in unique parameter values. In total, I have a test run that runs a total of 530,000 unique test instances between the two test methods. In all test output files (XML, HTML, etc.), the test totals are correct (530,000 total, 22 failed, 529,978 passed.) The first test method runs 10,000 times, the 2nd test method runs 520,000 times. If all 520,000 pass, it reports 520,000 test cases succeed, but if any one of the iterations fail (or even multiple failures), then it only reports the single test method as a failure which is not accurate. It seems that it isn't counting failures the same as it counts successes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MENFORCER-263) Upgrade mrm-maven-plugin to 1.0.0
Karl Heinz Marbaise created MENFORCER-263: - Summary: Upgrade mrm-maven-plugin to 1.0.0 Key: MENFORCER-263 URL: https://issues.apache.org/jira/browse/MENFORCER-263 Project: Maven Enforcer Plugin Issue Type: Improvement Components: Plugin Affects Versions: 1.4.2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MENFORCER-263) Upgrade mrm-maven-plugin to 1.0.0
[ https://issues.apache.org/jira/browse/MENFORCER-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MENFORCER-263. - Resolution: Fixed Fixed in [r1783939|https://svn.apache.org/r1783939] > Upgrade mrm-maven-plugin to 1.0.0 > - > > Key: MENFORCER-263 > URL: https://issues.apache.org/jira/browse/MENFORCER-263 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Affects Versions: 1.4.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 1.4.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MENFORCER-263) Upgrade mrm-maven-plugin to 1.0.0
[ https://issues.apache.org/jira/browse/MENFORCER-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876691#comment-15876691 ] Hudson commented on MENFORCER-263: -- FAILURE: Integrated in Jenkins build maven-enforcer #254 (See [https://builds.apache.org/job/maven-enforcer/254/]) [MENFORCER-263] Upgrade mrm-maven-plugin to 1.0.0 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1783939]) * (edit) maven-enforcer-plugin/pom.xml > Upgrade mrm-maven-plugin to 1.0.0 > - > > Key: MENFORCER-263 > URL: https://issues.apache.org/jira/browse/MENFORCER-263 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Affects Versions: 1.4.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 1.4.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-5438) cli parameter to use a custom path settings-security.xml
[ https://issues.apache.org/jira/browse/MNG-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Landolt updated MNG-5438: -- Attachment: MNG-5438-maven-embedder.patch Patch file against code as of Feb-20-2017. Follows current checkstyle rules > cli parameter to use a custom path settings-security.xml > > > Key: MNG-5438 > URL: https://issues.apache.org/jira/browse/MNG-5438 > Project: Maven > Issue Type: New Feature > Components: Command Line >Affects Versions: 3.0.4, 3.0.5 >Reporter: Sarah Haselbauer > Attachments: apache-maven-3.0.4-ssec-bin.tar.gz, > apache-maven-3.0.4-ssec-bin.zip, > maven-3.0.4-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch, > maven-latest-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch, > MNG-5438-maven-embedder.patch > > > added -ssec as cli param, so that you have the same flexibility to place your > settings-security.xml as you have to point to a custom settings.xml file > mvn -s /path/to/my/custom/settings.xml -ssec > /path/to/my/custom/settings-security.xml > I attached to patches: one that can be run on the maven-3.0.4 tag and one > that can be run on trunk (latest code state of today). > I also attached a maven-3.0.4-bin.zip (linux) so you can quickly try out the > feature and test it yourself. > if you like the idea, I would welcome to have this feature merged into one of > the next releases. I need it to write a puppet-maven module that allows to > download artifacts from maven repositories with encrypted passwords in the > puppet recipe. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARCHETYPE-519) archetype:generate with specified remote archetypeCatalog falls back to internal catalog
[
https://issues.apache.org/jira/browse/ARCHETYPE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877059#comment-15877059
]
Henry Saputra commented on ARCHETYPE-519:
-
I dont this is really thought through.
In some cases, it is cumbersome to make user to change his/her settings.xml or
they dont even know they have settings.xml file.
Could we have the original behavior or at least config to turn it back on as
optional param?
> archetype:generate with specified remote archetypeCatalog falls back to
> internal catalog
>
>
> Key: ARCHETYPE-519
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-519
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.0.0
> Environment: Mac OS X 10.11.6, Apache Maven 3.2.3
>Reporter: Philip Mundt
>Assignee: Robert Scholte
> Fix For: 3.0.1
>
>
> We were surprised to find out that our archetype was "suddenly" not working
> anymore. It turns out it was the release of
> {{org.apache.maven.plugins:maven-archetype-plugin:3.0.0}} from 12/Feb/17 that
> was the culprit.
> When running:
> {{mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.0:generate
> -DarchetypeCatalog=}} we end up with the
> plugin falling back to the internal catalog:
> {code}
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [INFO]
> [INFO] >>> maven-archetype-plugin:3.0.0:generate (default-cli) >
> generate-sources @ standalone-pom >>>
> [INFO]
> [INFO] <<< maven-archetype-plugin:3.0.0:generate (default-cli) <
> generate-sources @ standalone-pom <<<
> [INFO]
> [INFO] --- maven-archetype-plugin:3.0.0:generate (default-cli) @
> standalone-pom ---
> [INFO] Generating project in Interactive mode
> [INFO] No catalog defined. Using internal catalog
> [INFO] No archetype defined. Using maven-archetype-quickstart
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: internal -> org.apache.maven.archetypes:maven-archetype-archetype (An
> archetype which contains a sample archetype.)
> 2: internal -> org.apache.maven.archetypes:maven-archetype-j2ee-simple (An
> archetype which contains a simplifed sample J2EE application.)
> 3: internal -> org.apache.maven.archetypes:maven-archetype-plugin (An
> archetype which contains a sample Maven plugin.)
> 4: internal -> org.apache.maven.archetypes:maven-archetype-plugin-site (An
> archetype which contains a sample Maven plugin site.
> This archetype can be layered upon an existing Maven plugin project.)
> 5: internal -> org.apache.maven.archetypes:maven-archetype-portlet (An
> archetype which contains a sample JSR-268 Portlet.)
> 6: internal -> org.apache.maven.archetypes:maven-archetype-profiles ()
> 7: internal -> org.apache.maven.archetypes:maven-archetype-quickstart (An
> archetype which contains a sample Maven project.)
> 8: internal -> org.apache.maven.archetypes:maven-archetype-site (An archetype
> which contains a sample Maven site which demonstrates
> some of the supported document types like APT, XDoc, and FML and
> demonstrates how
> to i18n your site. This archetype can be layered upon an existing Maven
> project.)
> 9: internal -> org.apache.maven.archetypes:maven-archetype-site-simple (An
> archetype which contains a sample Maven site.)
> 10: internal -> org.apache.maven.archetypes:maven-archetype-webapp (An
> archetype which contains a sample Maven Webapp project.)
> Choose a number or apply filter (format: [groupId:]artifactId, case sensitive
> contains):
> {code}
> Version 2.4 works as expected (the archetype catalog exists under given URL
> and can be downloaded).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
