[jira] Closed: (MASSEMBLY-540) Web site uses the 1.1.0.xsd but 1.1.2 recommended
[ http://jira.codehaus.org/browse/MASSEMBLY-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MASSEMBLY-540. - Resolution: Fixed Fixed in [r1067614|http://svn.apache.org/viewvc?view=revision&revision=1067614]. I converted the necessary files to .apt.vm and injected the "mdoVersion" property that is defined in the POM, to get automatic updates to the latest schema version. > Web site uses the 1.1.0.xsd but 1.1.2 recommended > - > > Key: MASSEMBLY-540 > URL: http://jira.codehaus.org/browse/MASSEMBLY-540 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: all >Reporter: Karl Heinz Marbaise >Assignee: Dennis Lundberg > Fix For: 2.2.1 > > Attachments: patch-xsd.diff > > > On The [Web > Site|http://maven.apache.org/plugins/maven-assembly-plugin/index.html] is > stated that starting with 2.2-beta-6 the > http://maven.apache.org/xsd/assembly-1.1.2.xsd (for version 2.2-beta-6 and > higher) should be used but all examples are using 1.1.0.xsd instead. > I have attached a patch which contains fixes for the web-site. I'm not sure > if the integration tests and the resources assemblies should be updated as > well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGSITE-129) Plugins page does not mention Clirr
Plugins page does not mention Clirr --- Key: MNGSITE-129 URL: http://jira.codehaus.org/browse/MNGSITE-129 Project: Maven Project Web Site Issue Type: Bug Environment: http://maven.apache.org/plugins/ Reporter: SebbASF The Clirr plugin is widely used, but is not mentioned on the plugins page. Please could it be added? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-644) Do a pre-check for Git repositories to make sure the name and email are set
Do a pre-check for Git repositories to make sure the name and email are set --- Key: MRELEASE-644 URL: http://jira.codehaus.org/browse/MRELEASE-644 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Jason van Zyl I went to do a release on a new machine and forgot to run: git config --global user.email "y...@example.com" git config --global user.name "Your Name" And it got to the very end of release:prepare and blew up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-696) Improve the design of the class Classpath
Improve the design of the class Classpath - Key: SUREFIRE-696 URL: http://jira.codehaus.org/browse/SUREFIRE-696 Project: Maven Surefire Issue Type: Improvement Components: Maven Surefire Plugin Affects Versions: 2.7.2 Reporter: Stefan Birkner Priority: Minor Attachments: SUREFIRE-Classpath.patch This patch contains some improvements for the class Classpath: * Only use a set for storing the elements. * append(Classpath) has been changed to Classpath.join(Classpath, Classpath), because the classpath doesn't get appended. Instead a new one is created. * Renamed setForkProperties to writeToForkProperties. * Renamed setAsSystemProperty to writeToSystemProperty. * Moved getClassPathAsString() into writeToSystemProperty and only call writeToSystemProperty from outside. * Added readFromForkProperties in order to have serialization and deseralization being part of the same class. >From my point of view these changes improve the readability of the Surefire >code and are another step on the way to clean code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-645) Allow File/Directory Patterns for the checkModificationExcludes Option
Allow File/Directory Patterns for the checkModificationExcludes Option
--
Key: MRELEASE-645
URL: http://jira.codehaus.org/browse/MRELEASE-645
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: branch, prepare, scm
Affects Versions: 2.1
Environment: all
Reporter: Stefan Ferstl
Priority: Minor
Attachments: modification-excludes.patch
The {{checkModificationExcludes}} option does currently only allow the
definition single files to be excluded from the SCM modification check. If this
option is defined, all files anywhere in the maven project structure with the
specified name will be excluded from the check. It is currently not possible to
exclude files only within a specific directory or to exclude classes of files,
i.e. all files matching a specific file name pattern.
If the {{checkModificationExcludes}} option allowed the definition of file and
directory patterns, these things would be possible.
*Example 1*: I'd like to exclude a test resource
{{src/test/resources/foo.properties}} from the modification check but the real
foo.properties in {{src/main/resources}} should still be checked.
{code:xml}
src/test/resources/foo.properties
{code}
*Example 2*: I'd like to exclude all properties files with the prefix {{bar}}
from the modification check:
{code:xml}
**/bar*.properties
{code}
The attached patch modifies the {{ScmCheckModificationsPhase}} to use the
{{DirectoryScanner}} from plexus-utils instead of doing a strict file name
comparison. The patch does not provide more unit tests for this feature but it
adjusts the existing tests to run without any failures.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-129) Plugins page does not mention Clirr
[ http://jira.codehaus.org/browse/MNGSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNGSITE-129. Resolution: Fixed Assignee: Brett Porter done. It's debatable whether that list is all that useful, though - there's several good plugins missing, and I'm not sure how popular the ones there are. I'll file that separately. > Plugins page does not mention Clirr > --- > > Key: MNGSITE-129 > URL: http://jira.codehaus.org/browse/MNGSITE-129 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/plugins/ >Reporter: SebbASF >Assignee: Brett Porter > > The Clirr plugin is widely used, but is not mentioned on the plugins page. > Please could it be added? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGSITE-130) External plugins list is not up to date
External plugins list is not up to date --- Key: MNGSITE-130 URL: http://jira.codehaus.org/browse/MNGSITE-130 Project: Maven Project Web Site Issue Type: Improvement Reporter: Brett Porter See also MNGSITE-129. Regarding plugins list at http://maven.apache.org/plugins/, there's several good plugins missing, and I'm not sure how popular the ones there are. We might want to consider some alternatives here: - better edit the list for popular plugins - refer to something generated from the repository index that is more comprehensive -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-128) Inconsistent, missing docs for maven plugin naming conventions and auto operations based on that
[ http://jira.codehaus.org/browse/MNGSITE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNGSITE-128. Resolution: Fixed Assignee: Brett Porter > Inconsistent, missing docs for maven plugin naming conventions and auto > operations based on that > > > Key: MNGSITE-128 > URL: http://jira.codehaus.org/browse/MNGSITE-128 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Marshall Schor >Assignee: Brett Porter >Priority: Minor > > The page > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html has > a small entry under "shortening the command line" which says that artifactId > patterns maven-$name-plugin and $name-maven-plugin are treated specially (by > convention). > The email of Sep 27, 2008 to maven users list, from Stephen Connolly says > AFAIK only plugins with the groupId org.apache.maven.plugins are allowed to > use the maven-__-plugin pattern. I could not find this documented (other > than on the users email list.). > The page > http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html > says that the conventional mappings only happen for the "maven-$name-plugin" > style, and don't mention the other style ($name-maven-plugin). > I recommend using the text from the 1st ref (which seems to be the clearest) > as a starting point, to augment and expand the text in the 3rd ref. > The Complete Reference book is missing this information, as well, I believe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNGSITE-128) Inconsistent, missing docs for maven plugin naming conventions and auto operations based on that
[ http://jira.codehaus.org/browse/MNGSITE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254823#action_254823 ] Brett Porter commented on MNGSITE-128: -- actually, the first description wasn't very accurate when you read the whole paragraph. I've clarified the 3rd, and made the 1st reference it for more information. We don't have any influence over the Sonatype books, you'd need to file bugs there with them. > Inconsistent, missing docs for maven plugin naming conventions and auto > operations based on that > > > Key: MNGSITE-128 > URL: http://jira.codehaus.org/browse/MNGSITE-128 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Marshall Schor >Priority: Minor > > The page > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html has > a small entry under "shortening the command line" which says that artifactId > patterns maven-$name-plugin and $name-maven-plugin are treated specially (by > convention). > The email of Sep 27, 2008 to maven users list, from Stephen Connolly says > AFAIK only plugins with the groupId org.apache.maven.plugins are allowed to > use the maven-__-plugin pattern. I could not find this documented (other > than on the users email list.). > The page > http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html > says that the conventional mappings only happen for the "maven-$name-plugin" > style, and don't mention the other style ($name-maven-plugin). > I recommend using the text from the 1st ref (which seems to be the clearest) > as a starting point, to augment and expand the text in the 3rd ref. > The Complete Reference book is missing this information, as well, I believe. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-549) Not possible to easily customise footer
Not possible to easily customise footer --- Key: MSITE-549 URL: http://jira.codehaus.org/browse/MSITE-549 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Reporter: SebbASF It's currently extremely difficult to customise the site footer - the only way to do it seems to be to create one's own VM stylesheet. Given that a lot of sites may need to add trademark notices etc, this is a serious restriction (hence bug rather than enhancement). It would be very easy to add an extra field on the LHS of the footer which could be provided via a property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-418) "Some rights reserved" Instead of "All Rights Reserved"
[ http://jira.codehaus.org/browse/MSITE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-418. --- Resolution: Duplicate Assignee: Lukas Theussl > "Some rights reserved" Instead of "All Rights Reserved" > --- > > Key: MSITE-418 > URL: http://jira.codehaus.org/browse/MSITE-418 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Improvement >Reporter: Andres Gomez Casanova >Assignee: Lukas Theussl > > I'm creating the web site for my application, but I see that there is a (C) > mark in the footer of all pages with the text all rights reserved. > My web site is license with a Creative Commons Shared Alike license, so that > symbols does not reflect the real license. It's against my license. > I would like to have a way to change that, without changing the VM > (https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site.vm) > Something like a customizable footer (as in JavaDoc pluing) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIASITETOOLS-50) Add a footer element
Add a footer element Key: DOXIASITETOOLS-50 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-50 Project: Maven Doxia Sitetools Issue Type: New Feature Components: Decoration model Affects Versions: 1.1 Reporter: Lukas Theussl A la m1 navigation.xml: http://maven.apache.org/maven-1.x/plugins/xdoc/reference/navfile.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIASITETOOLS-50) Add a footer element
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIASITETOOLS-50: Fix Version/s: 1.2 > Add a footer element > > > Key: DOXIASITETOOLS-50 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-50 > Project: Maven Doxia Sitetools > Issue Type: New Feature > Components: Decoration model >Affects Versions: 1.1 >Reporter: Lukas Theussl > Fix For: 1.2 > > > A la m1 navigation.xml: > http://maven.apache.org/maven-1.x/plugins/xdoc/reference/navfile.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
