[jira] (MDEP-376) -Dincludes and -Dexcludes filtering not working anymore
[
https://jira.codehaus.org/browse/MDEP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Le Berrigaud updated MDEP-376:
-
Attachment: maven-dependency-plugin-includes.jpg
The includes parameter doesn't seem to even be available at all! See screen
shotâ¦
> -Dincludes and -Dexcludes filtering not working anymore
> ---
>
> Key: MDEP-376
> URL: https://jira.codehaus.org/browse/MDEP-376
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.5.1
>Reporter: Ryan Gardner
> Attachments: maven-dependency-plugin-includes.jpg
>
>
> running
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
> {code}
> will restrict the tree that is printed to just show the artifacts that match
> the includes pattern (a much smaller tree)
> in version 2.5+
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
> {code}
> on a project will show the entire tree with no filtering.
--
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] (MDEP-376) -Dincludes and -Dexcludes filtering not working anymore
[
https://jira.codehaus.org/browse/MDEP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309191#comment-309191
]
sleberrig commented on MDEP-376:
This also affects version 2.5 AFAICT. Works fine in version 2.4.
> -Dincludes and -Dexcludes filtering not working anymore
> ---
>
> Key: MDEP-376
> URL: https://jira.codehaus.org/browse/MDEP-376
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.5.1
>Reporter: Ryan Gardner
> Attachments: maven-dependency-plugin-includes.jpg
>
>
> running
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:tree -Dincludes=foo
> {code}
> will restrict the tree that is printed to just show the artifacts that match
> the includes pattern (a much smaller tree)
> in version 2.5+
> {code}
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.5.1:tree -Dincludes=foo
> {code}
> on a project will show the entire tree with no filtering.
--
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-505) Feature Request: useStrictFiltering option for FileSets
[
https://jira.codehaus.org/browse/MASSEMBLY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309195#comment-309195
]
Jonas Berlin commented on MASSEMBLY-505:
The same issue occurs also when the {{...}} specified
does not exist. I hope the implementation will check for this as well.
> Feature Request: useStrictFiltering option for FileSets
> ---
>
> Key: MASSEMBLY-505
> URL: https://jira.codehaus.org/browse/MASSEMBLY-505
> Project: Maven 2.x Assembly Plugin
> Issue Type: New Feature
>Affects Versions: 2.2
> Environment: Maven 2.2.1, RHEL4
>Reporter: John Casey
> Attachments: fail_strictfiltering.zip
>
>
> *NOTE:* This is a clone of MASSEMBLY-488. The original issue will be closed
> Won't Fix, since the plexus-utils class DirectoryScanner, which is the core
> of the FileSet functionality, doesn't support strict include/exclude
> filtering.
> This issue is a feature request to have that added.
> -
> I'm trying to turn on useStrictFiltering in a fileSet in an assembly
> descriptor, but maven doesn't fail when the file does not exist. Here
> is an example of what the assembly descriptor looks like:
>
>
> tar.gz
>
>
>
> true
> src/main
>
> nonexistant.txt*
>
>
>
>
> Running "mvn package" happily produces a tarball with no indication that
> anything is wrong.
--
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] (MWAR-248) Plugin warns about missing webxml attribute even if one exists
[ https://jira.codehaus.org/browse/MWAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309210#comment-309210 ] Valentin Jacquemin commented on MWAR-248: - Starting with an empty war project containing only the web.xml file I still get the warning. > mvn --version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\utils\apache-maven\bin\.. Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: C:\Program Files (x86)\Java\jdk1.6.0_20\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" > more pom.xml http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0 test maven-war-warning war 1.0 > mvn package ... [WARNING] Warning: selected war files include a WEB-INF/web.xml which will be ig nored (webxml attribute is missing from war task, or ignoreWebxml attribute is specifi ed as 'true') To get rid of the warning I had to modify the pom to include this unintuitive addition: org.apache.maven.plugins maven-war-plugin WEB-INF/web.xml > Plugin warns about missing webxml attribute even if one exists > -- > > Key: MWAR-248 > URL: https://jira.codehaus.org/browse/MWAR-248 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Gili >Assignee: Dennis Lundberg > Fix For: 2.2 > > Attachments: debug.log > > > I am attaching a debug log that clearly demonstrates how the WAR plugin warns > about a missing webxml attribute which exists. I am attempting to let the > plugin know that the web.xml file it is encountering is the same one > specified by the webxml attribute. > My pom file contains: > > org.apache.maven.plugins > maven-war-plugin > 2.1.1 > > true > src/main/webapp/WEB-INF/web.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] (MWAR-248) Plugin warns about missing webxml attribute even if one exists
[
https://jira.codehaus.org/browse/MWAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309210#comment-309210
]
Valentin Jacquemin edited comment on MWAR-248 at 9/20/12 3:58 AM:
--
Starting with an empty war project containing only the web.xml file I still get
the warning.
{code}
> mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\utils\apache-maven\bin\..
Java version: 1.6.0_20, vendor: Sun Microsystems Inc.
Java home: C:\Program Files (x86)\Java\jdk1.6.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
{code}
{code}
> more pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
test
maven-war-warning
war
1.0
{code}
{code}
> mvn package
...
[WARNING] Warning: selected war files include a WEB-INF/web.xml which will be ig
nored
(webxml attribute is missing from war task, or ignoreWebxml attribute is specifi
ed as 'true')
{code}
To get rid of the warning I had to modify the pom to include this unintuitive
addition:
{code}
org.apache.maven.plugins
maven-war-plugin
WEB-INF/web.xml
{code}
was (Author: jacqueminv):
Starting with an empty war project containing only the web.xml file I still
get the warning.
> mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\utils\apache-maven\bin\..
Java version: 1.6.0_20, vendor: Sun Microsystems Inc.
Java home: C:\Program Files (x86)\Java\jdk1.6.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
> more pom.xml
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
test
maven-war-warning
war
1.0
> mvn package
...
[WARNING] Warning: selected war files include a WEB-INF/web.xml which will be ig
nored
(webxml attribute is missing from war task, or ignoreWebxml attribute is specifi
ed as 'true')
To get rid of the warning I had to modify the pom to include this unintuitive
addition:
org.apache.maven.plugins
maven-war-plugin
WEB-INF/web.xml
> Plugin warns about missing webxml attribute even if one exists
> --
>
> Key: MWAR-248
> URL: https://jira.codehaus.org/browse/MWAR-248
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Gili
>Assignee: Dennis Lundberg
> Fix For: 2.2
>
> Attachments: debug.log
>
>
> I am attaching a debug log that clearly demonstrates how the WAR plugin warns
> about a missing webxml attribute which exists. I am attempting to let the
> plugin know that the web.xml file it is encountering is the same one
> specified by the webxml attribute.
> My pom file contains:
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1.1
>
> true
> src/main/webapp/WEB-INF/web.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] (MWAR-248) Plugin warns about missing webxml attribute even if one exists
[ https://jira.codehaus.org/browse/MWAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309214#comment-309214 ] Anders Hammar commented on MWAR-248: @Valentin: You most likely need to specify the version of the war plugin. I don't think Maven 3.0.4 uses v2.2 by default. Please continue this usage thread on the Maven users list. > Plugin warns about missing webxml attribute even if one exists > -- > > Key: MWAR-248 > URL: https://jira.codehaus.org/browse/MWAR-248 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Gili >Assignee: Dennis Lundberg > Fix For: 2.2 > > Attachments: debug.log > > > I am attaching a debug log that clearly demonstrates how the WAR plugin warns > about a missing webxml attribute which exists. I am attempting to let the > plugin know that the web.xml file it is encountering is the same one > specified by the webxml attribute. > My pom file contains: > > org.apache.maven.plugins > maven-war-plugin > 2.1.1 > > true > src/main/webapp/WEB-INF/web.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] (MSKINS-70) external.png is used in css but not present in code base
[ https://jira.codehaus.org/browse/MSKINS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MSKINS-70: -- Assignee: Olivier Lamy > external.png is used in css but not present in code base > > > Key: MSKINS-70 > URL: https://jira.codehaus.org/browse/MSKINS-70 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Eric Barboni >Assignee: Olivier Lamy >Priority: Trivial > Attachments: maven-theme.css.patch > > > Proposed patch is to remove reference in css. > But can be the other way around adding external.png to code base. -- 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] (MSKINS-70) external.png is used in css but not present in code base
[ https://jira.codehaus.org/browse/MSKINS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309228#comment-309228 ] Olivier Lamy commented on MSKINS-70: @simone any idea on this file ? maybe you have it locally ? :-) > external.png is used in css but not present in code base > > > Key: MSKINS-70 > URL: https://jira.codehaus.org/browse/MSKINS-70 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Eric Barboni >Assignee: Olivier Lamy >Priority: Trivial > Attachments: maven-theme.css.patch > > > Proposed patch is to remove reference in css. > But can be the other way around adding external.png to code base. -- 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-333) Diacritics (accents) in project path prevent the plugin from working on Windows.
[ https://jira.codehaus.org/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Pecka updated MJAVADOC-333: -- Attachment: options I've attached the options file. Note that it is in UTF-8 encoding (ProgramovánÃ) while maven reads it in CP1250 (ProgramovÄËnÄÂ) which is wrong (maven creates a directory D:\ProgramovÄËnÄÂ\Java\beam-3D-data-viewer\target\site\apidocs and then reports it has no source files). > Diacritics (accents) in project path prevent the plugin from working on > Windows. > > > Key: MJAVADOC-333 > URL: https://jira.codehaus.org/browse/MJAVADOC-333 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.7, 2.8 > Environment: Win7 >Reporter: Martin Pecka > Attachments: options, pom.xml > > > My project is located in "E:\ProgramovánÃ\Java\beam-3D-data-viewer". Notice > the diacritics in the path. > When launching the javadoc:javadoc goal, the build fails: > . > . > . > [ERROR] javadoc: warning - No source files for package org.esa.beam.util > [ERROR] javadoc: error - No public or protected classes found to document. > I looked on the generated "options" file, and that's the problem. Windows > apparentely don't have their filenames encoded in UTF8 when passing them to > the command line, but the options file is saved in UTF8. That's the reason > why the plugin cannot find the source files. When I manually edit the file > and save it in cp1250 encoding, running javadoc.bat works perfectly. > This should obviously be fixed, but is there a quick workaround? Eg. a way to > alter the generated javadoc.bat to prepend a call to iconv or something else. > Now I can use the generated files, manually edit the options file, and run > the task, but if I want to run the jar goal, this bug makes it impossible. > Thanks for cooperation! -- 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-333) Diacritics (accents) in project path prevent the plugin from working on Windows.
[ https://jira.codehaus.org/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309239#comment-309239 ] Martin Pecka commented on MJAVADOC-333: --- Outch! This site is not served in UTF8 and so the diacritics in my previous comment are wrong. Manually set this page to display as UTF8 to see it correctly. > Diacritics (accents) in project path prevent the plugin from working on > Windows. > > > Key: MJAVADOC-333 > URL: https://jira.codehaus.org/browse/MJAVADOC-333 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.7, 2.8 > Environment: Win7 >Reporter: Martin Pecka > Attachments: options, pom.xml > > > My project is located in "E:\ProgramovánÃ\Java\beam-3D-data-viewer". Notice > the diacritics in the path. > When launching the javadoc:javadoc goal, the build fails: > . > . > . > [ERROR] javadoc: warning - No source files for package org.esa.beam.util > [ERROR] javadoc: error - No public or protected classes found to document. > I looked on the generated "options" file, and that's the problem. Windows > apparentely don't have their filenames encoded in UTF8 when passing them to > the command line, but the options file is saved in UTF8. That's the reason > why the plugin cannot find the source files. When I manually edit the file > and save it in cp1250 encoding, running javadoc.bat works perfectly. > This should obviously be fixed, but is there a quick workaround? Eg. a way to > alter the generated javadoc.bat to prepend a call to iconv or something else. > Now I can use the generated files, manually edit the options file, and run > the task, but if I want to run the jar goal, this bug makes it impossible. > Thanks for cooperation! -- 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=309268#comment-309268 ] Jenni Syed commented on MJAVADOC-318: - Sorry, I didn't see the comment in May. It's been a while since I've tried to test this (not sure what version you were using to test) - what I was seeing before is that if I turned on detectLinks, and added the link entries for sites it could not find automatically, it would ignore the link entries provided. I can try to put together a small project that demonstrates this. > 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] (MPLUGIN-228) Change RetentionPolicy to RetentionPolicy.RUNTIME
Jeff Maxwell created MPLUGIN-228: Summary: Change RetentionPolicy to RetentionPolicy.RUNTIME Key: MPLUGIN-228 URL: https://jira.codehaus.org/browse/MPLUGIN-228 Project: Maven 2.x Plugin Tools Issue Type: Improvement Components: maven-plugin-tools-annotations Affects Versions: 3.1 Reporter: Jeff Maxwell It would be convenient to have access to the annotations at runtime. Example: In order to get access to the executing goal name the MojoExecution needs to be injected. It would be simpler to access the goal name via reflection. -- 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] (DOXIATOOLS-16) NullPointerException when site URL is being generated
[ https://jira.codehaus.org/browse/DOXIATOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIATOOLS-16. - Resolution: Fixed > NullPointerException when site URL is being generated > - > > Key: DOXIATOOLS-16 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-16 > Project: Maven Doxia Tools > Issue Type: Bug > Components: Doxia Integration Tools > Environment: environment independent >Reporter: Marc Claessens >Assignee: Dennis Lundberg > Fix For: doxia-integration-tools-1.5 > > > We have a parent POM where the site url is generated via the Maven Groovy > plugin, unless it is explicitly defined in the child POM > i.e. > >project-sites >Our project Nexus server Site > > > ... > >org.codehaus.groovy.maven >gmaven-plugin > > > pre-site > > execute > > > > > > > > > > } > This leads to a NullPointerException in DefaultSiteTool.java: > at java.io.File.(File.java:222) > at > org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478) > at > org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451) > The if statement in getDistMgntSiteUrl (for both methods) should test for > null on project.getDistributionManagement().getSite().getUrl() -- 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] (DOXIATOOLS-16) NullPointerException when site URL is being generated
[ https://jira.codehaus.org/browse/DOXIATOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309301#comment-309301 ] Dennis Lundberg commented on DOXIATOOLS-16: --- Fixed in [r1388197|http://svn.apache.org/viewvc?view=revision&revision=1388197]. > NullPointerException when site URL is being generated > - > > Key: DOXIATOOLS-16 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-16 > Project: Maven Doxia Tools > Issue Type: Bug > Components: Doxia Integration Tools > Environment: environment independent >Reporter: Marc Claessens >Assignee: Dennis Lundberg > Fix For: doxia-integration-tools-1.5 > > > We have a parent POM where the site url is generated via the Maven Groovy > plugin, unless it is explicitly defined in the child POM > i.e. > >project-sites >Our project Nexus server Site > > > ... > >org.codehaus.groovy.maven >gmaven-plugin > > > pre-site > > execute > > > > > > > > > > } > This leads to a NullPointerException in DefaultSiteTool.java: > at java.io.File.(File.java:222) > at > org.apache.maven.doxia.tools.DefaultSiteTool.urlEncode(DefaultSiteTool.java:1478) > at > org.apache.maven.doxia.tools.DefaultSiteTool.getDistMgmntSiteUrl(DefaultSiteTool.java:1451) > The if statement in getDistMgntSiteUrl (for both methods) should test for > null on project.getDistributionManagement().getSite().getUrl() -- 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] (DOXIATOOLS-34) Separate inheritance and interpolation
[
https://jira.codehaus.org/browse/DOXIATOOLS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated DOXIATOOLS-34:
--
Fix Version/s: (was: doxia-integration-tools-1.5)
Removing this from the 1.5 release.
> Separate inheritance and interpolation
> ---
>
> Key: DOXIATOOLS-34
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-34
> Project: Maven Doxia Tools
> Issue Type: Improvement
> Components: Doxia Integration Tools
>Affects Versions: doxia-integration-tools-1.4
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>
> The implementation uses recursion to get an inherited model of the site.xml,
> but every step does the interpolation too.
> So if the parent site.xml contains something like ${project.name}, its value
> will be an ancestor project name, often an unexpected value.
> By moving the interpolation from the recursive method to the method-caller
> you will get the name of the active project.
--
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-162) Remove items marked "Issue:" from Maven Eclipse plugin guide
[ https://jira.codehaus.org/browse/MNGSITE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MECLIPSE-732 to MNGSITE-162: --- Component/s: (was: Plugin Documentation) Affects Version/s: (was: 2.9) Key: MNGSITE-162 (was: MECLIPSE-732) Project: Maven Project Web Site (was: Maven 2.x Eclipse Plugin) > Remove items marked "Issue:" from Maven Eclipse plugin guide > > > Key: MNGSITE-162 > URL: https://jira.codehaus.org/browse/MNGSITE-162 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Glen Mazza >Priority: Minor > > Hello, on this page: > http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Maven_2_repository, > there are several "Issue:" comments where people have added in things that > they would like to have changed with the Maven Eclipse Plugin. I think those > should be removed. If anyone finds a bug in or has enhancement suggestions > for the Maven Eclipse plugin, JIRAs should be entered instead. System > documentation shouldn't be used as a holder for JIRA items. > At the very least, I'd like the statement: "The command does not work." at > the top of this page (describing the mvn eclipse:add-maven-repo command) > removed. I just tested it with Eclipse Juno and JDK7 and it works fine--we > don't want to scare readers that commands don't work when they actually do. -- 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-162) Remove items marked "Issue:" from Maven Eclipse plugin guide
[
https://jira.codehaus.org/browse/MNGSITE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309305#comment-309305
]
Olivier Lamy commented on MNGSITE-162:
--
The file to patch is here:
http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/guides/mini/guide-ide-eclipse.apt
To test your patch :-)
{code}
svn co http://svn.apache.org/repos/asf/maven/site/trunk maven-site
cd maven-site
mvn clean site
{code}
generated site will be in target/site
> Remove items marked "Issue:" from Maven Eclipse plugin guide
>
>
> Key: MNGSITE-162
> URL: https://jira.codehaus.org/browse/MNGSITE-162
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Glen Mazza
>Priority: Minor
>
> Hello, on this page:
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Maven_2_repository,
> there are several "Issue:" comments where people have added in things that
> they would like to have changed with the Maven Eclipse Plugin. I think those
> should be removed. If anyone finds a bug in or has enhancement suggestions
> for the Maven Eclipse plugin, JIRAs should be entered instead. System
> documentation shouldn't be used as a holder for JIRA items.
> At the very least, I'd like the statement: "The command does not work." at
> the top of this page (describing the mvn eclipse:add-maven-repo command)
> removed. I just tested it with Eclipse Juno and JDK7 and it works fine--we
> don't want to scare readers that commands don't work when they actually do.
--
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-162) Remove items marked "Issue:" from Maven Eclipse plugin guide
[ https://jira.codehaus.org/browse/MNGSITE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309306#comment-309306 ] Glen Mazza commented on MNGSITE-162: OK, I'll submit a patch. > Remove items marked "Issue:" from Maven Eclipse plugin guide > > > Key: MNGSITE-162 > URL: https://jira.codehaus.org/browse/MNGSITE-162 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Glen Mazza >Priority: Minor > > Hello, on this page: > http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Maven_2_repository, > there are several "Issue:" comments where people have added in things that > they would like to have changed with the Maven Eclipse Plugin. I think those > should be removed. If anyone finds a bug in or has enhancement suggestions > for the Maven Eclipse plugin, JIRAs should be entered instead. System > documentation shouldn't be used as a holder for JIRA items. > At the very least, I'd like the statement: "The command does not work." at > the top of this page (describing the mvn eclipse:add-maven-repo command) > removed. I just tested it with Eclipse Juno and JDK7 and it works fine--we > don't want to scare readers that commands don't work when they actually do. -- 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-352) Subpackages in the config should handle multilined values
Peter Major created MJAVADOC-352: Summary: Subpackages in the config should handle multilined values Key: MJAVADOC-352 URL: https://jira.codehaus.org/browse/MJAVADOC-352 Project: Maven 2.x Javadoc Plugin Issue Type: Wish Reporter: Peter Major Currently having multilined value for the subpackages is not advised, because in the end the options file will contain the values in multiple lines as well (as opposed to separating them by ':') A sample setting would be: com.mycompany: org.mycompany.demo Currently you have to: com.mycompany:org.mycompany.demo Please note that sometimes JavaDoc _seems_ to handle the multilined config, but not always, and also strangely enough the order of the packages could matter as well - so it is possible that one order gives you full javadoc, while a different one will result in "No source found in package" warning messages. -- 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=309310#comment-309310 ] Herve Boutemy commented on MJAVADOC-318: yes, please create this demo project: either this will prove there is no problem any more, either it will be useful for me to change it into an integration test to work on a fix and we'll even be able to test with every m-javadoc-p version, then determine precisely when it didn't work > 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] (MJAVADOC-353) CLONE - Subpackages in the config should handle multilined values
aungtunooato created MJAVADOC-353: - Summary: CLONE - Subpackages in the config should handle multilined values Key: MJAVADOC-353 URL: https://jira.codehaus.org/browse/MJAVADOC-353 Project: Maven 2.x Javadoc Plugin Issue Type: Wish Reporter: aungtunooato Currently having multilined value for the subpackages is not advised, because in the end the options file will contain the values in multiple lines as well (as opposed to separating them by ':') A sample setting would be: com.mycompany: org.mycompany.demo Currently you have to: com.mycompany:org.mycompany.demo Please note that sometimes JavaDoc _seems_ to handle the multilined config, but not always, and also strangely enough the order of the packages could matter as well - so it is possible that one order gives you full javadoc, while a different one will result in "No source found in package" warning messages. -- 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-352) Subpackages in the config should handle multilined values
[ https://jira.codehaus.org/browse/MJAVADOC-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309316#comment-309316 ] osdfnxnb commented on MJAVADOC-352: --- ONLINE STORE : http://ppt.cc/g9nI n2012 comes, in order to thank everyone, characteristic, novel style, varieties, low price and good quality, and the low sale price. Thank everyone free shipping competitive price any size available accept the paypal jordan shoes $32 nike shox $32 Christan Audigier bikini $23 Ed Hardy Bikini $23 Smful short_t-shirt_woman $15 ed hardy short_tank_woman $16 Sandal $32 christian louboutin $80 Sunglass $15 COACH_Necklace $27 handbag $33 AF tank woman $17 puma slipper woman $30 http://ppt.cc/g9nI > Subpackages in the config should handle multilined values > - > > Key: MJAVADOC-352 > URL: https://jira.codehaus.org/browse/MJAVADOC-352 > Project: Maven 2.x Javadoc Plugin > Issue Type: Wish >Reporter: Peter Major > > Currently having multilined value for the subpackages is not advised, because > in the end the options file will contain the values in multiple lines as well > (as opposed to separating them by ':') > A sample setting would be: > > com.mycompany: > org.mycompany.demo > > Currently you have to: > > com.mycompany:org.mycompany.demo > > Please note that sometimes JavaDoc _seems_ to handle the multilined config, > but not always, and also strangely enough the order of the packages could > matter as well - so it is possible that one order gives you full javadoc, > while a different one will result in "No source found in package" warning > messages. -- 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-353) CLONE - Subpackages in the config should handle multilined values
[ https://jira.codehaus.org/browse/MJAVADOC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309314#comment-309314 ] osdfnxnb commented on MJAVADOC-353: --- ONLINE STORE : http://ppt.cc/g9nI n2012 comes, in order to thank everyone, characteristic, novel style, varieties, low price and good quality, and the low sale price. Thank everyone free shipping competitive price any size available accept the paypal jordan shoes $32 nike shox $32 Christan Audigier bikini $23 Ed Hardy Bikini $23 Smful short_t-shirt_woman $15 ed hardy short_tank_woman $16 Sandal $32 christian louboutin $80 Sunglass $15 COACH_Necklace $27 handbag $33 AF tank woman $17 puma slipper woman $30 http://ppt.cc/g9nI > CLONE - Subpackages in the config should handle multilined values > - > > Key: MJAVADOC-353 > URL: https://jira.codehaus.org/browse/MJAVADOC-353 > Project: Maven 2.x Javadoc Plugin > Issue Type: Wish >Reporter: aungtunooato > > Currently having multilined value for the subpackages is not advised, because > in the end the options file will contain the values in multiple lines as well > (as opposed to separating them by ':') > A sample setting would be: > > com.mycompany: > org.mycompany.demo > > Currently you have to: > > com.mycompany:org.mycompany.demo > > Please note that sometimes JavaDoc _seems_ to handle the multilined config, > but not always, and also strangely enough the order of the packages could > matter as well - so it is possible that one order gives you full javadoc, > while a different one will result in "No source found in package" warning > messages. -- 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=309315#comment-309315 ] osdfnxnb commented on MJAVADOC-318: --- ONLINE STORE : http://ppt.cc/g9nI n2012 comes, in order to thank everyone, characteristic, novel style, varieties, low price and good quality, and the low sale price. Thank everyone free shipping competitive price any size available accept the paypal jordan shoes $32 nike shox $32 Christan Audigier bikini $23 Ed Hardy Bikini $23 Smful short_t-shirt_woman $15 ed hardy short_tank_woman $16 Sandal $32 christian louboutin $80 Sunglass $15 COACH_Necklace $27 handbag $33 AF tank woman $17 puma slipper woman $30 http://ppt.cc/g9nI > 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
