[jira] (MCHANGES-283) Add GitHub reporter
Bryan Baugher created MCHANGES-283: -- Summary: Add GitHub reporter Key: MCHANGES-283 URL: https://jira.codehaus.org/browse/MCHANGES-283 Project: Maven 2.x Changes Plugin Issue Type: New Feature Reporter: Bryan Baugher Attachments: MCHANGES-GitHubReport.patch Maven changes plugin should support downloading issues from github repos and creating a github report. -- 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] (MECLIPSE-726) Limit project references to modules only
Jean-Pierre Froud created MECLIPSE-726: -- Summary: Limit project references to modules only Key: MECLIPSE-726 URL: https://jira.codehaus.org/browse/MECLIPSE-726 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects Affects Versions: 2.8 Environment: Win. XP sp3 Reporter: Jean-Pierre Froud Attachments: ScreenShot278.jpg In my workspace, I have a multi-module project A with A1, A2 modules. I also have another multi-module project B with B1, B2 modules. A1 has a dependency on B1 and I'm using 'useProjectReferences' (true) and A2 depends on A1. !ScreenShot278.jpg! When I'm doing mvn eclipse:eclipse on A, the result I want: A2 references workspace project A1 A1 uses repository artifact B1 (not the workspace project) Is there a way to limit 'useProjectReferences' only to modules? Or listing the projects to reference? The reason I want that is because I had weird behaviour on versions: A1 depends on C version 2.0 B1 depends on C version 1.5 and the version of C taken during runtime of A1 is the one from B1 (1.5) instead of 2.0 version. -- 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] (SCM-679) enhance scm api to support limited number of returned changesets by changelog command
[
https://jira.codehaus.org/browse/SCM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed SCM-679.
Resolution: Fixed
Fix Version/s: 1.8
Assignee: Olivier Lamy
applied.
Thanks!
enhance scm api to support limited number of returned changesets by changelog
command
-
Key: SCM-679
URL: https://jira.codehaus.org/browse/SCM-679
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-api, maven-scm-provider-bazaar,
maven-scm-provider-git, maven-scm-provider-mercurial (hg),
maven-scm-provider-svn
Affects Versions: 1.7, 1.8
Reporter: Petr Kozelka
Assignee: Olivier Lamy
Fix For: 1.8
Attachments: scm-changelog-limit.patch,
scm-changelog-limit-wrapped.patch
The current api returns changesets between specified/unspecified
dates/revisions.
This leaves some important usecases unsupported; some of them are:
- get last changeset on given repository/path
- get last n changesets there (first page when browsing changes)
The only workarround currently possible is, list all commits and filter them
- but this is very time consuming.
For this reason, I propose attached enhancement which overloads the changeLog
method, adding the limit parameter:
{code}
ChangeLogScmResult changeLog( ScmRepository repository, ScmFileSet
fileSet, Date startDate, Date endDate,
int numDays, ScmBranch branch, String
datePattern, Integer limit )
throws ScmException;
{code}
For the last changeset usecase, the client sets limit = 1.
For paged browsing, it can specify null startDate/endDate on firstPage, and
then work with dates for next/previous pages, still using the limit to
specify page size.
Note that the limit parameter can be null (as it is Integer, not int) to
specify unlimited number of returned changesets.
The suggested patch includes deprecations of enhanced methods, I hope this is
a good way to reduce the number of actively used overloaded variants of
changelog in future.
--
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-283) Add GitHub reporter
[ https://jira.codehaus.org/browse/MCHANGES-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MCHANGES-283: - Assignee: Olivier Lamy Add GitHub reporter --- Key: MCHANGES-283 URL: https://jira.codehaus.org/browse/MCHANGES-283 Project: Maven 2.x Changes Plugin Issue Type: New Feature Reporter: Bryan Baugher Assignee: Olivier Lamy Attachments: MCHANGES-GitHubReport.patch Maven changes plugin should support downloading issues from github repos and creating a github report. -- 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-283) Add GitHub reporter
[ https://jira.codehaus.org/browse/MCHANGES-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-283. - Resolution: Fixed Fix Version/s: 2.8 applied (with minor code formatting). Great Patch! Thanks! Add GitHub reporter --- Key: MCHANGES-283 URL: https://jira.codehaus.org/browse/MCHANGES-283 Project: Maven 2.x Changes Plugin Issue Type: New Feature Reporter: Bryan Baugher Assignee: Olivier Lamy Fix For: 2.8 Attachments: MCHANGES-GitHubReport.patch Maven changes plugin should support downloading issues from github repos and creating a github report. -- 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-176) Make ConversionTool available in the VelocityContext
[ https://jira.codehaus.org/browse/MCHANGES-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301696#comment-301696 ] Olivier Lamy commented on MCHANGES-176: --- current version depends on Velocity 1.7. So can me marked as Fixed ? Make ConversionTool available in the VelocityContext Key: MCHANGES-176 URL: https://jira.codehaus.org/browse/MCHANGES-176 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.1 Reporter: Antonin Stefanutti Fix For: backlog It would be very useful to have access to an instance of ConversionTool in the Velocity templace so that one can convert String to List for example. See : http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/generic/ConversionTool.html In my special case, I want to pass a list of packages as a comma-separated String in the announceParameters as configuration of the changes plugin and convert this comma-separated String as a List in the Velocity template to iterate over to send e-mails containing the packages I deployed in addition to the changes report. -- 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-176) Make ConversionTool available in the VelocityContext
[ https://jira.codehaus.org/browse/MCHANGES-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCHANGES-176: -- Fix Version/s: backlog Make ConversionTool available in the VelocityContext Key: MCHANGES-176 URL: https://jira.codehaus.org/browse/MCHANGES-176 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.1 Reporter: Antonin Stefanutti Fix For: backlog It would be very useful to have access to an instance of ConversionTool in the Velocity templace so that one can convert String to List for example. See : http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/generic/ConversionTool.html In my special case, I want to pass a list of packages as a comma-separated String in the announceParameters as configuration of the changes plugin and convert this comma-separated String as a List in the Velocity template to iterate over to send e-mails containing the packages I deployed in addition to the changes report. -- 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] (MPLUGIN-213) NullPointerException in descriptor goal
[
https://jira.codehaus.org/browse/MPLUGIN-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MPLUGIN-213:
-
Fix Version/s: 3.1
NullPointerException in descriptor goal
---
Key: MPLUGIN-213
URL: https://jira.codehaus.org/browse/MPLUGIN-213
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-java
Affects Versions: 3.0
Reporter: Tony Chemit
Assignee: Olivier Lamy
Priority: Blocker
Fix For: 3.1
Attachments: patch.diff
I have this definition :
{code}
@Mojo( name = aggregate-add-third-party, requiresProject = true, aggregator
= true,
defaultPhase = LifecyclePhase.GENERATE_RESOURCES )
@Execute( goal = add-third-party )
{code}
And this exeception then while building :
{code}
Caused by: java.lang.NullPointerException
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.toMojoDescriptors(JavaAnnotationsMojoDescriptorExtractor.java:522)
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:110)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:108)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:245)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:88)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
I had a look to the code and it is normal (I think)
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
{code}
but should be
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
if ( execute.phase() != null )
{
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
}
{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] (MPLUGIN-213) NullPointerException in descriptor goal
[
https://jira.codehaus.org/browse/MPLUGIN-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reassigned MPLUGIN-213:
Assignee: Olivier Lamy
NullPointerException in descriptor goal
---
Key: MPLUGIN-213
URL: https://jira.codehaus.org/browse/MPLUGIN-213
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-java
Affects Versions: 3.0
Reporter: Tony Chemit
Assignee: Olivier Lamy
Priority: Blocker
Fix For: 3.1
Attachments: patch.diff
I have this definition :
{code}
@Mojo( name = aggregate-add-third-party, requiresProject = true, aggregator
= true,
defaultPhase = LifecyclePhase.GENERATE_RESOURCES )
@Execute( goal = add-third-party )
{code}
And this exeception then while building :
{code}
Caused by: java.lang.NullPointerException
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.toMojoDescriptors(JavaAnnotationsMojoDescriptorExtractor.java:522)
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:110)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:108)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:245)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:88)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
I had a look to the code and it is normal (I think)
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
{code}
but should be
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
if ( execute.phase() != null )
{
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
}
{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] (MPLUGIN-213) NullPointerException in descriptor goal
[
https://jira.codehaus.org/browse/MPLUGIN-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MPLUGIN-213.
Resolution: Fixed
applied.
Thanks!
NullPointerException in descriptor goal
---
Key: MPLUGIN-213
URL: https://jira.codehaus.org/browse/MPLUGIN-213
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: maven-plugin-tools-java
Affects Versions: 3.0
Reporter: Tony Chemit
Assignee: Olivier Lamy
Priority: Blocker
Fix For: 3.1
Attachments: patch.diff
I have this definition :
{code}
@Mojo( name = aggregate-add-third-party, requiresProject = true, aggregator
= true,
defaultPhase = LifecyclePhase.GENERATE_RESOURCES )
@Execute( goal = add-third-party )
{code}
And this exeception then while building :
{code}
Caused by: java.lang.NullPointerException
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.toMojoDescriptors(JavaAnnotationsMojoDescriptorExtractor.java:522)
at
org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:110)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:108)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:245)
at
org.apache.maven.plugin.plugin.HelpGeneratorMojo.execute(HelpGeneratorMojo.java:88)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
{code}
I had a look to the code and it is normal (I think)
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
{code}
but should be
{code}
if ( execute != null )
{
mojoDescriptor.setExecuteGoal( execute.goal() );
mojoDescriptor.setExecuteLifecycle( execute.lifecycle() );
if ( execute.phase() != null )
{
mojoDescriptor.setExecutePhase( execute.phase().id() );
}
}
{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] (SCM-680) Changelog parse date fails
[
https://jira.codehaus.org/browse/SCM-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed SCM-680.
Resolution: Fixed
Fix Version/s: 1.8
Assignee: Olivier Lamy
applied.
Thanks !
Changelog parse date fails
--
Key: SCM-680
URL: https://jira.codehaus.org/browse/SCM-680
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-mercurial (hg)
Affects Versions: 1.7
Environment: Debian Linux, possibly any other.
Reporter: Leonardo Bueno Postacchini
Assignee: Olivier Lamy
Fix For: 1.8
Attachments: MNG-SCM-680-maven-scm-provider-hg.patch,
MNG-SCM-maven-scm-provider-hg.patch
When system locale disagrees with maven locale the date becomes unparsable.
The patch changes the time format used by the changelog to comply with
ISO8601 date format and changes the mercurial command log call to template
instead of verbose to gain control over the date format output and uses
{date|isdodatesec} so that the command becomes locale agnostic.
--
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-555) update versions does not update intermodule dependencies
[ https://jira.codehaus.org/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301702#comment-301702 ] Marcin Zajaczkowski commented on MRELEASE-555: -- This works fine also with release:branch. The same could be used in update-versions. update versions does not update intermodule dependencies Key: MRELEASE-555 URL: https://jira.codehaus.org/browse/MRELEASE-555 Project: Maven 2.x Release Plugin Issue Type: Bug Components: update-versions Affects Versions: 2.0 Environment: Maven 2.2.1, JDK 6, XP SP3 Reporter: Michael Osipov I recently tried the update-versions goal which is really nice and worked well. I cleaned my local repo today and reran mvn package on a multi-module project. It failed due tue a depenceny error. My project was previously on version 2.6.1-SNAPSHOT. Module war depends on module jar with the same version. When doing a release:prepare, the plugin perfectly bumps this intermodule dependency. The release:update-versions missed that dep spot. My build process failed. The goal should crawl for those deps too and update them if autoVersionSubmodules is on. (Same behavior as the prepare goal) -- 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] (MRAR-30) Filtering of RA.xml
Markus KARG created MRAR-30:
---
Summary: Filtering of RA.xml
Key: MRAR-30
URL: https://jira.codehaus.org/browse/MRAR-30
Project: Maven 2.x Rar Plugin
Issue Type: New Feature
Affects Versions: 2.2
Environment: Win7 64Bit JDK1.6.0_26
Reporter: Markus KARG
Priority: Minor
It would be great if one could specify filteringtrue/filtering in the
pom.xml to make the RAR plugin filter the custom RA.xml file provided in src.
Using this feature, one could put ${project.version} into the custom RA.xml's
resourceadapter-version/ section.
--
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] (SUREFIRE-878) redirectTestOutputToFile is empty when text is written to output too early (SpringJUnit4ClassRunner)
Jakub Berlinski created SUREFIRE-878: Summary: redirectTestOutputToFile is empty when text is written to output too early (SpringJUnit4ClassRunner) Key: SUREFIRE-878 URL: https://jira.codehaus.org/browse/SUREFIRE-878 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12, 2.11, 2.10 Environment: tested on Windows XP + JDK 1.6.29 and Linux (2.6.32) JDK 1.6.24, Maven 2.2.1 Reporter: Jakub Berlinski Priority: Minor Attachments: RedirectTest-output.txt, redirect.zip I'm using a trivial test using SpringJUnit4ClassRunner (RedirectTest.java). The test prints a simple message to the standard output. I run the test with mvn test command. When log4j is configured to print some spring execution details (logger set to level INFO) the RedirectTest-output.txt file is empty. To reproduce: unzip redirect.zip file run mvn test confirm that the file target/surefire-reports/RedirectTest-output.txt is empty Optionally: edit pom.xml file, change maven-surefire-plugin version to 2.9 . run mvn test confirm that the file target/surefire-reports/RedirectTest-output.txt is not empty. See attached RedirectTest-output.txt captured using maven-surefire-plugin version 2.9. -- 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] (MRESOURCES-168) Don't overwrite unchanged resource to prevent unnecessary subsequent processing
Markus KARG created MRESOURCES-168: -- Summary: Don't overwrite unchanged resource to prevent unnecessary subsequent processing Key: MRESOURCES-168 URL: https://jira.codehaus.org/browse/MRESOURCES-168 Project: Maven 2.x Resources Plugin Issue Type: Improvement Components: filtering Environment: MVN3.0.4 Win7 Pro SP1 64 Bit JDK 1.6.0_07 Reporter: Markus KARG Priority: Minor When filtering resources, the resulting files' last-modified date is updated. This is correct, as the file just got produced. But, there might be lots of files that passed the filter unchanged -- but now have changed last-modified date, too. This induces unneccesary subsequent processing and should be prevented. Example: Filtering of Java sources, then compiling those. The Java compiler typically will only compile modified files, but not thinks ALL files are modified. A solution could be to check whether at least one property was actually found in the filtered file and to reset the last-modified date in all other cases. Another solution could be to rename the previous output file and compare both files after filtering. If they are identical, the new fill can be discarded and the previous file can be renamed back. -- 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] (MRESOURCES-140) Plugin shows always '[debug] execute contextualize' despite the logging level
[
https://jira.codehaus.org/browse/MRESOURCES-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301716#comment-301716
]
Jukka Zitting commented on MRESOURCES-140:
--
Any chance of a new 2.6 release in near future? It's almost a year since this
issue was fixed.
Plugin shows always '[debug] execute contextualize' despite the logging level
-
Key: MRESOURCES-140
URL: https://jira.codehaus.org/browse/MRESOURCES-140
Project: Maven 2.x Resources Plugin
Issue Type: Improvement
Affects Versions: 2.5
Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_23\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: x86, family: windows
Reporter: Robert Scholte
Assignee: Robert Scholte
Priority: Minor
Fix For: 2.6
While running Maven with the default logging level, it shows the following
text in my console.
{noformat}
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ project
---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
{noformat}
Reason seems to be, that the {{contextualize()}} is called before the plugin
is fully setup, so there's no proper logger yet.
Please remove this debug-line.
--
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-176) Make ConversionTool available in the VelocityContext
[ https://jira.codehaus.org/browse/MCHANGES-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MCHANGES-176: --- Assignee: Robert Scholte Make ConversionTool available in the VelocityContext Key: MCHANGES-176 URL: https://jira.codehaus.org/browse/MCHANGES-176 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.1 Reporter: Antonin Stefanutti Assignee: Robert Scholte Fix For: backlog It would be very useful to have access to an instance of ConversionTool in the Velocity templace so that one can convert String to List for example. See : http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/generic/ConversionTool.html In my special case, I want to pass a list of packages as a comma-separated String in the announceParameters as configuration of the changes plugin and convert this comma-separated String as a List in the Velocity template to iterate over to send e-mails containing the packages I deployed in addition to the changes report. -- 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-176) Make ConversionTool available in the VelocityContext
[ https://jira.codehaus.org/browse/MCHANGES-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCHANGES-176. --- Resolution: Fixed Fix Version/s: (was: backlog) 2.8 Fixed in [r1352964|http://svn.apache.org/viewvc?rev=1352964view=rev] Make ConversionTool available in the VelocityContext Key: MCHANGES-176 URL: https://jira.codehaus.org/browse/MCHANGES-176 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.1 Reporter: Antonin Stefanutti Assignee: Robert Scholte Fix For: 2.8 It would be very useful to have access to an instance of ConversionTool in the Velocity templace so that one can convert String to List for example. See : http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/generic/ConversionTool.html In my special case, I want to pass a list of packages as a comma-separated String in the announceParameters as configuration of the changes plugin and convert this comma-separated String as a List in the Velocity template to iterate over to send e-mails containing the packages I deployed in addition to the changes report. -- 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] (MPMD-11) targetJdk parameter cannot be set in maven 2
[ https://jira.codehaus.org/browse/MPMD-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301738#comment-301738 ] Raymond Kroeker commented on MPMD-11: - I noticed a difference between configuring the plugin as a reporting plugin vs a build plugin: This does not work: ... reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.7.1/version configuration targetJdk1.6/targetJdk /configuration /plugin /plugins /reporting ... this does: ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.7.1/version configuration targetJdk1.6/targetJdk /configuration /plugin /build ... targetJdk parameter cannot be set in maven 2 Key: MPMD-11 URL: https://jira.codehaus.org/browse/MPMD-11 Project: Maven 2.x PMD Plugin Issue Type: Bug Reporter: Tony Nys My code is java 5 and has the special for-loop syntax pmd says that the for loop is incorrect in jdk1.4 mode However, there is a parameter targetJdk but it cannot be set , plugin.xml does not define it and there is no setter in the sourcecode -- 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-138) release:prepare fails when checking in modified POMs of a multi-modules project
[
https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-138.
---
Resolution: Incomplete
Assignee: Robert Scholte (was: Emmanuel Venisse)
No feedback from users, closing it as {{incomplete}}
release:prepare fails when checking in modified POMs of a multi-modules
project
---
Key: MRELEASE-138
URL: https://jira.codehaus.org/browse/MRELEASE-138
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-4
Environment: WinXP + Eclipse
Reporter: ol
Assignee: Robert Scholte
Priority: Critical
Here is the project structure on the disk :
c:\javadev\prj\myproject\module1
c:\javadev\prj\myproject\module2
c:\javadev\prj\myproject\master
These 3 folders represent the 3 eclipse projects, each one containing a
pom.xml.
The master project's pom is the parent of the modules.
When I execute the release:prepare goal, Everything works fine (it asks to me
the tag name, the next dev version, ...) until I receive this error :
[INFO] Checking in modified POMs...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the checkin process:
C:\javadev\prj\myproject\module1\pom.xml was not contained in
C:\javadev\prj\myproject\master
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred
in the checkin process: C:\javadev\prj\myproject\module1\pom.xml was not
contained in C:\javadev\prj\myproject\master
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
The problem is that the project structure is the only one that can be used
with eclipse.
--
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] (MSITE-639) sub-project tries to fetch a site_en.xml even though no locales are configured
[ https://jira.codehaus.org/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301744#comment-301744 ] Tim Pizey commented on MSITE-639: - I have the same problem, even though there is no site.xml associated with the parent pom. This means no generation of child sites in Jenkins or I remove all parent/child relationships. I cannot add a site.xml as the parent pom is at the top of a twenty wide tree of modules, alays installed with install -N sub-project tries to fetch a site_en.xml even though no locales are configured -- Key: MSITE-639 URL: https://jira.codehaus.org/browse/MSITE-639 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0-beta-3 Environment: Windows 7 64bit, Sun JDK 1.6.0_27 Reporter: Martin Goldhahn Attachments: parent-project.zip, sub-project.zip I have a parent project that has a site descriptor and a pom project that has the parent project as parent. Neither of them defines the locales parameter of the site plugin. When I try to build the sub-project, I get an error that Maven cannot find the site_en.xml descriptor of the parent project. Why doesn't it just use the site.xml? -- 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] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301745#comment-301745 ] Andrew Gaul commented on SUREFIRE-827: -- This still fails for me with 2.13-20120620.212637-15 running on Ubuntu 12.04. Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Junit 4.7+ (parallel) support Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul Assignee: Kristian Rosenvold Fix For: 2.13 Attachments: BUG-827.zip # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- 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] (MSITE-645) Menu no longer accepts href attribute
Paul Benedict created MSITE-645:
---
Summary: Menu no longer accepts href attribute
Key: MSITE-645
URL: https://jira.codehaus.org/browse/MSITE-645
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: documentation
Affects Versions: 3.1
Reporter: Paul Benedict
Section Including Generated Content:
http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
I used the example:
{noformat}
menu name=Foo href=foo.html /
{noformat}
Error reported:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.1:site (default-cli) on project
leave: SiteToolException: Error parsing site descriptor: Unknown attribute
'href' for tag 'menu' (position: START_TAG seen ...body\r\nmenu
name=Foo href=foo.html /... @3:40) - [Help 1]
Either the documentation is wrong or the site schema has changed.
--
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-750) String index out of range: -1 in ReleaseUtils.loadResolvedDependencies() when using Parent-Module-Layout
[
https://jira.codehaus.org/browse/MRELEASE-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-750.
---
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in [r1353035|http://svn.apache.org/viewvc?rev=1353035view=rev]
I've been able reproduce the {{StringIndexOutOfBOundsException}} and it exposed
another bug, which could solve a lot of other issues.
So I've been quite happy I did some investigation instead of going for the
defensive strategy.
Main reason was a wrong calculation of the {{startIndex}} and {{endIndex}}.
String index out of range: -1 in ReleaseUtils.loadResolvedDependencies() when
using Parent-Module-Layout
Key: MRELEASE-750
URL: https://jira.codehaus.org/browse/MRELEASE-750
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.3
Reporter: Thomas Baldauf
Assignee: Robert Scholte
Fix For: 2.4
Attachments: MNG-750-release.patch, ReleaseUtils.java
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.XXX:prepare (default-cli) on
project XXX: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.XXX:prepare failed: String
index out of range: -1 - [Help 1]
This is happening in
org.apache.maven.shared.release.config.ReleaseUtils.loadResolvedDependencies(..),
line number 250:
artifactVersionlessKey = propertyName.substring( startIndex, endIndex );
Apparently endIndex can be -1 under special circumstances. Defensive
programming fixes the problem.
Proposed patch (see attachment):
if (endIndex startIndex) {
artifactVersionlessKey = propertyName.substring( startIndex,
endIndex );
} else {
artifactVersionlessKey = propertyName.substring( startIndex );
}
--
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] (MRESOURCES-169) Silently fails to import properties from a properties file
Tim Pizey created MRESOURCES-169:
Summary: Silently fails to import properties from a properties file
Key: MRESOURCES-169
URL: https://jira.codehaus.org/browse/MRESOURCES-169
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Components: filtering
Environment: ubuntu/openjdk6/maven 3.0.4
Reporter: Tim Pizey
I have tried inherited from parent, defined in pom and with and without
encoding:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.5/version
configuration
encoding${project.build.sourceEncoding}/encoding
/configuration
/plugin
invoked with
filters
filter/etc/${project.artifactId}/repository.properties/filter
/filters
This fails if the file does not exist, but if it does exist the properties are
not included.
I have tried the properties file as a normal key=value file and as an XML
properties file.
This mechanism would be REALLY useful if it worked, as it would enable
passwords not to be stored in our SCM, nor in settings.xml
--
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] (MPLUGIN-209) use maven-plugin-tools' java 5 annotations
[
https://jira.codehaus.org/browse/MPLUGIN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=301747#comment-301747
]
Robert Scholte commented on MPLUGIN-209:
Could it be that this commit causes the {{HelpMojo}} to be generated in the
root of generated sources (package-less)?
use maven-plugin-tools' java 5 annotations
--
Key: MPLUGIN-209
URL: https://jira.codehaus.org/browse/MPLUGIN-209
Project: Maven 2.x Plugin Tools
Issue Type: Task
Components: Plugin Plugin
Affects Versions: 3.0
Reporter: Herve Boutemy
Assignee: Herve Boutemy
Fix For: 3.1
apply to self :)
--
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-5302) Include thread number in output messages
George Lindholm created MNG-5302: Summary: Include thread number in output messages Key: MNG-5302 URL: https://jira.codehaus.org/browse/MNG-5302 Project: Maven 2 3 Issue Type: Improvement Components: Logging Affects Versions: 3.0.4 Reporter: George Lindholm Priority: Minor When doing a parallel build the log messages are mixed up making it hard to determine what module a message comes from. If the thread number is included in the log message it would make it easier to see what is going on, especially when the debug flag is used. -- 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
