[jira] (MNGSITE-164) Explanation of default value for useAllReactorProjects is at best confusing, possibly wrong
Duncan Jones created MNGSITE-164:
Summary: Explanation of default value for useAllReactorProjects is
at best confusing, possibly wrong
Key: MNGSITE-164
URL: https://jira.codehaus.org/browse/MNGSITE-164
Project: Maven Project Web Site
Issue Type: Bug
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.7.0
Java home: C:\Program Files\Java\jdk1.7.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
Reporter: Duncan Jones
Attachments: parent.zip
See page:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_moduleSet
The explanation of {{useAllReactorProjects}} is given as follows:
bq. If set to true, the plugin will include all projects in the current reactor
for processing in this ModuleSet. These will be subject to include/exclude
rules. Default value is true. (Since 2.2)
Default value is: false.
I'm using Maven 2.2.1, so I assumed this would default to {{true}}. However, it
appears to be {{false}}. Attached is a small example project which seems to
require {{useAllReactorProjects}} to be specified as true in order to build
correctly with Maven 2.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-530) Allow configuration of encoding
[ https://jira.codehaus.org/browse/MASSEMBLY-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309755#comment-309755 ] Lars Corneliussen commented on MASSEMBLY-530: - I need the same thing! > Allow configuration of encoding > > > Key: MASSEMBLY-530 > URL: https://jira.codehaus.org/browse/MASSEMBLY-530 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Max Schaefer > > Zips, that encode the file names with e.g. UTF-8 are not properly unpacked > because the system default encoding is assumed. > I tracked down that PlexusIoZipFileResourceCollection initialises a ZipFile > instance passing in just the file. However, a second parameter of ZipFile > allows to control the encoding. I would like to be able to specify that > encoding when unpacking a dependencySet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-736) Add dryRun flag to release:perform
[
https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309785#comment-309785
]
Jesse Glick commented on MRELEASE-736:
--
Perhaps I am missing something but rev. 1299865 seems incomplete. At least
according to
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#dryRun
[t]he goals (by default at least {{deploy}}) will be executed against the
current project. Is this just a matter of updating the Javadoc for
{{PerformReleaseMojo.dryRun}}?
> Add dryRun flag to release:perform
> --
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
>Affects Versions: 2.2.2
> Environment: mvn 3.0.3
>Reporter: Dominik Bartholdi
>Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the
> "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help
> the user to trigger a maven release. This plugin allows to define a
> commandline which should be executed in case of a release build. The common
> configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when
> triggering a build and in this case it would just add "-DdryRun=true" to the
> configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets
> executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean
> I have to remove "release:perform" from the passed argument, which is relay
> ugly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5294) Attempt to restore backward compatibility for the MavenEmbedder
[
https://jira.codehaus.org/browse/MNG-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309790#comment-309790
]
Matt Raible commented on MNG-5294:
--
Any update on this issue?
> Attempt to restore backward compatibility for the MavenEmbedder
> ---
>
> Key: MNG-5294
> URL: https://jira.codehaus.org/browse/MNG-5294
> Project: Maven 2 & 3
> Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
>
> Problem reported by Matt Raible where Appfuse uses the MavenEmbedder in the
> app fuse-maven-plugin:full-source goal:
> http://issues.appfuse.org/browse/APF-1220
> Here is the specific block of code used in the Appfuse Plugin:
> {code}
> private MavenProject createProjectFromPom(File pom) {
> MavenEmbedder maven = new MavenEmbedder();
> maven.setOffline(true);
> maven.setClassLoader(Thread.currentThread().getContextClassLoader());
> maven.setLogger(new MavenEmbedderConsoleLogger());
> MavenProject p = null;
> try {
> maven.setAlignWithUserInstallation(true);
> maven.start();
> p = maven.readProjectWithDependencies(pom);
> maven.stop();
> } catch (Exception e) {
> e.printStackTrace();
> }
> return p;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-252) [JIRA report] some configuration of the changes plugin are not passed to JiraDownloader
[ https://jira.codehaus.org/browse/MCHANGES-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309793#comment-309793 ] Alain MAHIER commented on MCHANGES-252: --- Verified with last 2.8. No exceptions anymore. Best regards Alain > [JIRA report] some configuration of the changes plugin are not passed to > JiraDownloader > --- > > Key: MCHANGES-252 > URL: https://jira.codehaus.org/browse/MCHANGES-252 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: Alain MAHIER > > When executing jira-report, i have the following message > maven-changes-plugin: None of the configured sortColumnNames 'null' are > correct > As I can see in the source of the plugin, sortColumnNames of the > jiraDownloader is not initialized > It implies an empty (no release actions) announcement (even those from the > changes.xml) generation. > Some configuration parameters (declared in the plugin documentation) seems to > be ignored now : > - component > - columnNames > - sortColumnNames > If a specific filter is given in the changes plugin configuration, the below > error is not raised -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-252) [JIRA report] some configuration of the changes plugin are not passed to JiraDownloader
[ https://jira.codehaus.org/browse/MCHANGES-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-252. Resolution: Fixed Fix Version/s: 2.8 Assignee: Dennis Lundberg Thanks for testing! > [JIRA report] some configuration of the changes plugin are not passed to > JiraDownloader > --- > > Key: MCHANGES-252 > URL: https://jira.codehaus.org/browse/MCHANGES-252 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.5 >Reporter: Alain MAHIER >Assignee: Dennis Lundberg > Fix For: 2.8 > > > When executing jira-report, i have the following message > maven-changes-plugin: None of the configured sortColumnNames 'null' are > correct > As I can see in the source of the plugin, sortColumnNames of the > jiraDownloader is not initialized > It implies an empty (no release actions) announcement (even those from the > changes.xml) generation. > Some configuration parameters (declared in the plugin documentation) seems to > be ignored now : > - component > - columnNames > - sortColumnNames > If a specific filter is given in the changes plugin configuration, the below > error is not raised -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-736) Add dryRun flag to release:perform
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309800#comment-309800 ] Robert Scholte commented on MRELEASE-736: - Jesse, what would you expect? Any suggestion to improve the javadocs is appreciated. > Add dryRun flag to release:perform > -- > > Key: MRELEASE-736 > URL: https://jira.codehaus.org/browse/MRELEASE-736 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform >Affects Versions: 2.2.2 > Environment: mvn 3.0.3 >Reporter: Dominik Bartholdi >Assignee: Robert Scholte > Fix For: 2.3 > > > Please consider to add the "dryRun" flag from the "release:prepare" to the > "release:perform" goal too. > I have the following use case: > Jenkins/Hudson has a plugin called m2release which basically is there to help > the user to trigger a maven release. This plugin allows to define a > commandline which should be executed in case of a release build. The common > configuration of this arguments are: > "-Dresume=false release:prepare release:perform" > the next version of the plugin would like to add a "dryRun" option when > triggering a build and in this case it would just add "-DdryRun=true" to the > configured arguments and thats it. > Unfortunately this will not work, as the "release:perform" still gets > executed and will fail. > Of course I could also change the Jenkins/Hudson plugin, but this would mean > I have to remove "release:perform" from the passed argument, which is relay > ugly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-164) Explanation of default value for useAllReactorProjects is at best confusing, possibly wrong
[
https://jira.codehaus.org/browse/MNGSITE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309802#comment-309802
]
Dennis Lundberg commented on MNGSITE-164:
-
The "(Since 2.2)" you see in the documentation refers to the version of Maven
Assembly Plugin - not Maven itself. It means that the parameter was first
introduced in Maven Assembly Plugin 2.2.
I tried building your sample project like this:
{noformat}
mvn clean verify
{noformat}
The build succeeds and the only problems I see are warnings like this one:
{noformat}
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
{noformat}
What is the behavior you expect and what is the behavior that you currently see?
> Explanation of default value for useAllReactorProjects is at best confusing,
> possibly wrong
> ---
>
> Key: MNGSITE-164
> URL: https://jira.codehaus.org/browse/MNGSITE-164
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
> Java version: 1.7.0
> Java home: C:\Program Files\Java\jdk1.7.0\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
>Reporter: Duncan Jones
> Attachments: parent.zip
>
>
> See page:
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_moduleSet
> The explanation of {{useAllReactorProjects}} is given as follows:
> bq. If set to true, the plugin will include all projects in the current
> reactor for processing in this ModuleSet. These will be subject to
> include/exclude rules. Default value is true. (Since 2.2)
> Default value is: false.
> I'm using Maven 2.2.1, so I assumed this would default to {{true}}. However,
> it appears to be {{false}}. Attached is a small example project which seems
> to require {{useAllReactorProjects}} to be specified as true in order to
> build correctly with Maven 2.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-318) detectLinks should work together with links, or allow overrides for docs it can't locate
[ https://jira.codehaus.org/browse/MJAVADOC-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309804#comment-309804 ] Jenni Syed commented on MJAVADOC-318: - It looks like this is working on 2.9. I dropped back a few versions and couldn't reproduce this (with my simple project), so I'm not sure if something else was going on. > detectLinks should work together with links, or allow overrides for docs it > can't locate > > > Key: MJAVADOC-318 > URL: https://jira.codehaus.org/browse/MJAVADOC-318 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Reporter: Jenni Syed >Assignee: Herve Boutemy > > When detectLinks is true, it tends to find the correct javadoc link for 80%+ > of the referenced classes. If I add the few locations that are not able to be > detected to the links section, these will be ignored. Ideally, detectLinks > would find whatever it could automatically, but work in conjuction with an > override that can be provided for the locations you know it won't be able to > find. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-736) Add dryRun flag to release:perform
[
https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309807#comment-309807
]
Jesse Glick commented on MRELEASE-736:
--
@Robert your comment of Mar 12 suggests that this Javadoc is quite wrong, and
that it should say something like:
The {{deploy}} goal (or whatever is configured in {{goals}}) will _not_ be
executed.
> Add dryRun flag to release:perform
> --
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
>Affects Versions: 2.2.2
> Environment: mvn 3.0.3
>Reporter: Dominik Bartholdi
>Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the
> "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help
> the user to trigger a maven release. This plugin allows to define a
> commandline which should be executed in case of a release build. The common
> configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when
> triggering a build and in this case it would just add "-DdryRun=true" to the
> configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets
> executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean
> I have to remove "release:perform" from the passed argument, which is relay
> ugly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-144) Using compiler API instead of tools.jar
[ https://jira.codehaus.org/browse/MCOMPILER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309809#comment-309809 ] David M. Lloyd commented on MCOMPILER-144: -- https://github.com/sonatype/plexus-compiler/pull/6 (PLXCOMP-1) is relevant here. > Using compiler API instead of tools.jar > --- > > Key: MCOMPILER-144 > URL: https://jira.codehaus.org/browse/MCOMPILER-144 > Project: Maven 2.x Compiler Plugin > Issue Type: New Feature >Reporter: Markus KARG >Priority: Minor > > Currently (MVN 3.0) java compilation needs tools.jar provided by the Sun JDK: > [ERROR] Unable to locate the Javac Compiler in: > [ERROR] C:\Program Files\Java\jre6\..\lib\tools.jar > [ERROR] Please ensure you are using JDK 1.4 or above and > [ERROR] not a JRE (the com.sun.tools.javac.Main class is required). > [ERROR] In most cases you can change the location of your Java > [ERROR] installation by setting the JAVA_HOME environment variable. > In fact, this is bad because (a) it assumes that a full JDK is installed just > for this sole tool where a JRE would be sufficient, (b) tools.jar is not > contained in any standards documents and such possibly is not existing on > future or non-sun JDK. > Since JRE 6 (i. e. for many years) the JRE (not JDK!) comes with a > standardized (!) API for compilation: The Java Compiler API. It would make > sense to use that standardized API instead of forcing the user to have Sun > JDK installed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-736) Add dryRun flag to release:perform
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309817#comment-309817 ] Robert Scholte commented on MRELEASE-736: - You're right, fixed in [r1390723|http://svn.apache.org/viewvc?rev=1390723&view=rev] > Add dryRun flag to release:perform > -- > > Key: MRELEASE-736 > URL: https://jira.codehaus.org/browse/MRELEASE-736 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform >Affects Versions: 2.2.2 > Environment: mvn 3.0.3 >Reporter: Dominik Bartholdi >Assignee: Robert Scholte > Fix For: 2.3 > > > Please consider to add the "dryRun" flag from the "release:prepare" to the > "release:perform" goal too. > I have the following use case: > Jenkins/Hudson has a plugin called m2release which basically is there to help > the user to trigger a maven release. This plugin allows to define a > commandline which should be executed in case of a release build. The common > configuration of this arguments are: > "-Dresume=false release:prepare release:perform" > the next version of the plugin would like to add a "dryRun" option when > triggering a build and in this case it would just add "-DdryRun=true" to the > configured arguments and thats it. > Unfortunately this will not work, as the "release:perform" still gets > executed and will fail. > Of course I could also change the Jenkins/Hudson plugin, but this would mean > I have to remove "release:perform" from the passed argument, which is relay > ugly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-181) Upgrade to Checkstyle 5.6
[ https://jira.codehaus.org/browse/MCHECKSTYLE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Baron Roberts updated MCHECKSTYLE-181: -- Attachment: checkstyle-5.6-upgrade.patch Patch for upgrading from Checkstyle 5.5 to Checkstyle 5.6. > Upgrade to Checkstyle 5.6 > - > > Key: MCHECKSTYLE-181 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-181 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: Baron Roberts > Attachments: checkstyle-5.6-upgrade.patch > > > Checkstyle 5.6 was recently released with critical fixes for Java 7 > constructs (e.g. try-with-resource). Please release a version of the > maven-checkstyle-plugin using Checkstyle 5.6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
