[jira] Created: (MNGSITE-135) Faq should include information about project.reporting.outputEncoding
Faq should include information about project.reporting.outputEncoding
-
Key: MNGSITE-135
URL: http://jira.codehaus.org/browse/MNGSITE-135
Project: Maven Project Web Site
Issue Type: Improvement
Reporter: Paul Nyheim
Attachments: faqissue.patch
Failsafe plugin reports a WARNING if
{code:xml}
UTF-8
{code}
is not set. The FAQ only suggests to set the
{code:xml}
UTF-8
{code}
ref:
http://stackoverflow.com/questions/3017695/how-to-configure-encoding-in-maven
Suggested patch attached
--
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-717) Remove old site file still available on-line
Remove old site file still available on-line Key: SUREFIRE-717 URL: http://jira.codehaus.org/browse/SUREFIRE-717 Project: Maven Surefire Issue Type: Task Components: documentation Environment: n/a Reporter: Anders Hammar While googling for surefire and forking, I found this old example page still available: http://maven.apache.org/plugins/maven-surefire-plugin/examples/forking.html Please remove it! -- 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: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261815#action_261815
]
KP commented on MRESOURCES-99:
--
I would close this issue, as it has been fixed, as [~olamy] has shown. I have
confirmed that {{${maven.build.timestamp}}} works.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
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] Issue Comment Edited: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261815#action_261815
]
KP edited comment on MRESOURCES-99 at 3/29/11 7:52 AM:
---
I would close this issue, as it has been fixed, as [~olamy] has shown. I have
confirmed that {{$\{maven.build.timestamp\}}} works.
was (Author: thealchemist):
I would close this issue, as it has been fixed, as [~olamy] has shown. I
have confirmed that {{${maven.build.timestamp}}} works.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
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: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261816#action_261816
]
Evgeny Mandrikov commented on MRESOURCES-99:
I'm not sure that issue should be closed, because definition of a new property
- it's just a workaround for original problem.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
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: (MNG-3952) Create Deprecation Mechanism for Maven Artifacts
[ http://jira.codehaus.org/browse/MNG-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261832#action_261832 ] Victor Dolirio Ferreira Barbosa commented on MNG-3952: -- We have this problem too. Our component repository is in a constant update and sometimes we change groupId and/or artifactId. Somtimes we just want to sign an artifact as deprecated because these turned deprecated. Therefore developers who are using these components sometimes get confused with artifacts that is supposed to not be used. This mechanism will be very usefull. []s > Create Deprecation Mechanism for Maven Artifacts > > > Key: MNG-3952 > URL: http://jira.codehaus.org/browse/MNG-3952 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Artifacts and Repositories, General >Affects Versions: 2.0.9 > Environment: All >Reporter: Immo Huneke > Fix For: Issues to be reviewed for 3.x > > > An example of the sort of problem that developers currently encounter can be > seen at > http://blog.jonasbandi.net/2008/12/using-jpa-and-hibernate-with-maven.html. I > have encountered similar problems in the past, e.g. trying to decide which > version of a plugin is the current one or being unaware that an artifact I > was using in a build had been superseded by another with a different groupId > and artifactId. > I feel that Maven lacks a deprecation mechanism that would make it obvious to > everyone that they're using something out of date. The problem is that once > an artifact (other than a snapshot) has been published, it is never supposed > to change thereafter. But it shouldn't be impossible to devise a mechanism > for adding deprecation and redirection to the associated metadata. It would > then be possible for the dependency resolver to display a warning whenever a > deprecated artifact was used in a build, either as a plugin or as a library. -- 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: (ARCHETYPE-359) fail on mvn install with a archetype created from create-from-project command having required property in archetype-metadata.xml
[
http://jira.codehaus.org/browse/ARCHETYPE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laird Nelson updated ARCHETYPE-359:
---
Attachment: archetype359.tar.gz
Oh for goodness' sake. Here's a small project that reproduces (trivially) the
problem.
I assembled the project by doing this:
mvn clean archetype:create-from-project
(edited
target/generated-sources/archetype/src/main/resources/META-INF/maven/archetype-metadata.xml;
added required properties section)
To reproduce the issue, go into target/generated-sources/archetype and do mvn
install.
> fail on mvn install with a archetype created from create-from-project command
> having required property in archetype-metadata.xml
>
>
> Key: ARCHETYPE-359
> URL: http://jira.codehaus.org/browse/ARCHETYPE-359
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.0
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530)
> Java version: 1.6.0_21
> Java home: C:\Program Files\Java\jdk1.6.0_18\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Abhishek Sharma
>Priority: Blocker
> Attachments: archetype359.tar.gz, output.txt
>
>
> mvn install fails when archetype-metadata.xml having required property entry.
> {noformat}[INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building quipoz-qte-project-archetype-archetype
> [INFO]task-segment: [install]
> [INFO]
>
> [INFO] [resources:resources {execution: default-resources}]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 25 resources
> [INFO] [resources:testResources {execution: default-testResources}]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 2 resources
> [INFO] [archetype:jar {execution: default-jar}]
> [INFO] [archetype:add-archetype-metadata {execution:
> default-add-archetype-metadata}]
> [INFO] [archetype:integration-test {execution: default-integration-test}]
> [ERROR] Archetype
> quipoz-qte-project-archetype:quipoz-qte-project-archetype-archetype:0.0.1-SNAPSHOT
> is not configured
> Property check is missing.
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype
> quipoz-qte-project-archetype:quipoz-qte-project-archetype-archetype:0.0.1-SNAPSHOT
> is not configured
> Property check is missing.
> at
> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:128)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.processIntegrationTest(IntegrationTestMojo.java:237)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:108)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> a
[jira] Commented: (DOXIASITETOOLS-50) Add a footer element
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261850#action_261850 ] Dennis Lundberg commented on DOXIASITETOOLS-50: --- Technically you probably can put HTML code inside a site.xml file, but it is not recommended you do so. The site.xml file might be used for other output formats besides (X)HTML, like PDF. Using HTML code in the site.xml would not look pretty in the PDF. There is another request to modify the copyright text in a simple way, see DOXIASITETOOLS-56. I feel that having ways to specify both a copyright *and* a footer will be confusing to users, as one currently contains the other. > 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 >Assignee: Dennis Lundberg > 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
[jira] Created: (MCHANGES-229) Incorrect documentation for changes-check goal -- references "release phase"
Incorrect documentation for changes-check goal -- references "release phase" Key: MCHANGES-229 URL: http://jira.codehaus.org/browse/MCHANGES-229 Project: Maven 2.x Changes Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Philip Maher Priority: Trivial The documentation for the changes-check goal [1] mentions attaching the goal to the "release phase". According to all the maven lifecycle documentation I've been able to dig up, I can't find any mention of a "release phase". I also found a question over on stackoverflow about a "release phase" and the answer was that it did not exist. Is this an error in the documentation of the plugin that needs corrected? [1] http://maven.apache.org/plugins/maven-changes-plugin/examples/check-changes-file.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] Created: (DOXIASITETOOLS-57) update to Java 5
update to Java 5 Key: DOXIASITETOOLS-57 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-57 Project: Maven Doxia Sitetools Issue Type: Improvement Components: Decoration model, Doc renderer, Site renderer Affects Versions: 1.1.4 Reporter: Herve Boutemy this will allow generics and will be consistent with Maven 2.2+ -- 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-57) update to Java 5
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated DOXIASITETOOLS-57: Fix Version/s: 1.2 > update to Java 5 > > > Key: DOXIASITETOOLS-57 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-57 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Decoration model, Doc renderer, Site renderer >Affects Versions: 1.1.4 >Reporter: Herve Boutemy > Fix For: 1.2 > > > this will allow generics and will be consistent with Maven 2.2+ -- 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-57) update to Java 5
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated DOXIASITETOOLS-57: Description: this will allow generics and will be consistent with Maven 2.2+ it would be useful for site descriptor or other parts of the API, that makes use of Collection API was:this will allow generics and will be consistent with Maven 2.2+ > update to Java 5 > > > Key: DOXIASITETOOLS-57 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-57 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Decoration model, Doc renderer, Site renderer >Affects Versions: 1.1.4 >Reporter: Herve Boutemy > Fix For: 1.2 > > > this will allow generics and will be consistent with Maven 2.2+ > it would be useful for site descriptor or other parts of the API, that makes > use of Collection API -- 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: (DOXIA-424) update to Java 5
update to Java 5 Key: DOXIA-424 URL: http://jira.codehaus.org/browse/DOXIA-424 Project: Maven Doxia Issue Type: Improvement Affects Versions: 1.1.4 Reporter: Herve Boutemy nothing much expected from such a move, since the most interesting thing IMHO is generics, but I didn't notice any part of the public API that makes use of Collection API so the rationale is more for consistency with Doxia Site Tools: see DOXIASITETOOLS-57 -- 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: (DOXIA-424) update to Java 5
[ http://jira.codehaus.org/browse/DOXIA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated DOXIA-424: Fix Version/s: 1.2 > update to Java 5 > > > Key: DOXIA-424 > URL: http://jira.codehaus.org/browse/DOXIA-424 > Project: Maven Doxia > Issue Type: Improvement >Affects Versions: 1.1.4 >Reporter: Herve Boutemy > Fix For: 1.2 > > > nothing much expected from such a move, since the most interesting thing IMHO > is generics, but I didn't notice any part of the public API that makes use of > Collection API > so the rationale is more for consistency with Doxia Site Tools: see > DOXIASITETOOLS-57 -- 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] Deleted: (DOXIA-424) update to Java 5
[ http://jira.codehaus.org/browse/DOXIA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy deleted DOXIA-424: > update to Java 5 > > > Key: DOXIA-424 > URL: http://jira.codehaus.org/browse/DOXIA-424 > Project: Maven Doxia > Issue Type: Improvement >Reporter: Herve Boutemy > > nothing much expected from such a move, since the most interesting thing IMHO > is generics, but I didn't notice any part of the public API that makes use of > Collection API > so the rationale is more for consistency with Doxia Site Tools: see > DOXIASITETOOLS-57 -- 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] Issue Comment Edited: (DOXIA-422) upgrade to Java 5
[ http://jira.codehaus.org/browse/DOXIA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261892#action_261892 ] Herve Boutemy edited comment on DOXIA-422 at 3/29/11 8:45 PM: -- nothing much expected from such a move, since the most interesting thing IMHO is generics, but I didn't notice any part of the public API that makes use of Collection API so the rationale is more for consistency with Doxia Site Tools: see DOXIASITETOOLS-57, where generics would be a real improvement was (Author: hboutemy): nothing much expected from such a move, since the most interesting thing IMHO is generics, but I didn't notice any part of the public API that makes use of Collection API so the rationale is more for consistency with Doxia Site Tools: see DOXIASITETOOLS-57 > upgrade to Java 5 > - > > Key: DOXIA-422 > URL: http://jira.codehaus.org/browse/DOXIA-422 > Project: Maven Doxia > Issue Type: Task > Components: Core, Decoration Model, Doxia Tools, Module - Apt, > Module - Confluence, Module - Docbook Simple, Module - Fml, Module - FO, > Module - Itext, Module - Latex, Module - Rtf, Module - Twiki, Module - Xdoc, > Module - Xhtml, Modules, Sink API, Site Renderer >Affects Versions: 1.1.5 >Reporter: Herve Boutemy > Fix For: 1.2 > > > using generics will ease maintenance -- 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] Moved: (DOXIASITETOOLS-58) Add logo and banner size in the decoration model
[
http://jira.codehaus.org/browse/DOXIASITETOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy moved DOXIA-335 to DOXIASITETOOLS-58:
---
Component/s: (was: Decoration Model)
Decoration model
Affects Version/s: (was: 1.1)
1.1
Key: DOXIASITETOOLS-58 (was: DOXIA-335)
Project: Maven Doxia Sitetools (was: Maven Doxia)
> Add logo and banner size in the decoration model
>
>
> Key: DOXIASITETOOLS-58
> URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-58
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Decoration model
>Affects Versions: 1.1
>Reporter: Vincent Siveton
>
> The decoration model should be improved for logo banner to include some image
> informations like size.
> {noformat}
>
>
>
>
>
>
> {noformat}
> Also, it will be better to use the XHTML notation for image ie
> {noformat}
>
> {noformat}
--
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: (MCHANGES-230) Add ability for changes-check to validate that the changes.xml release date is the day of the release
Add ability for changes-check to validate that the changes.xml release date is the day of the release - Key: MCHANGES-230 URL: http://jira.codehaus.org/browse/MCHANGES-230 Project: Maven 2.x Changes Plugin Issue Type: New Feature Affects Versions: 2.4 Reporter: Philip Maher I like the functionality included in the changes-check in MCHANGES-140. It would be nice, in addition to checking the format of the date, if an option could be added to have it check to see if the date of the release in the changes.xml is the current date when the goal is run. I would like to be able to have release:prepare or release:perform fail if the changes.xml did not have the right day. This definitely should be an option that is off by default. -- 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: (DOXIA-422) upgrade to Java 5
[ http://jira.codehaus.org/browse/DOXIA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated DOXIA-422: Component/s: (was: Decoration Model) Maven plugin Logging API > upgrade to Java 5 > - > > Key: DOXIA-422 > URL: http://jira.codehaus.org/browse/DOXIA-422 > Project: Maven Doxia > Issue Type: Task > Components: Core, Doxia Tools, Logging API, Maven plugin, Module - > Apt, Module - Confluence, Module - Docbook Simple, Module - Fml, Module - FO, > Module - Itext, Module - Latex, Module - Rtf, Module - Twiki, Module - Xdoc, > Module - Xhtml, Modules, Sink API, Site Renderer >Affects Versions: 1.1.5 >Reporter: Herve Boutemy > Fix For: 1.2 > > > using generics will ease maintenance -- 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: (MJAVADOC-314) failOnWarnings option is required
failOnWarnings option is required - Key: MJAVADOC-314 URL: http://jira.codehaus.org/browse/MJAVADOC-314 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Reporter: Yegor Bugayenko Would be nice to have failOnWarnings option. -- 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: (MCOMPILER-151) failOnWarning option is required
failOnWarning option is required Key: MCOMPILER-151 URL: http://jira.codehaus.org/browse/MCOMPILER-151 Project: Maven 2.x Compiler Plugin Issue Type: Improvement Reporter: Yegor Bugayenko Would be nice to have failOnWarning option -- 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
