[jira] (MJAVADOC-205) Review output directory for Javadoc reports (main and test) and jar (main and test)
[ https://jira.codehaus.org/browse/MJAVADOC-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308562#comment-308562 ] Vincent Siveton commented on MJAVADOC-205: -- Nothing right now. Review output directory for Javadoc reports (main and test) and jar (main and test) --- Key: MJAVADOC-205 URL: https://jira.codehaus.org/browse/MJAVADOC-205 Project: Maven 2.x Javadoc Plugin Issue Type: Task Affects Versions: 2.4 Reporter: Vincent Siveton Actually, plugin report used: * ouputDirectory * reportOutputDirectory * destDir in JavadocReport and TestJavadocReport The configuration is not easy to change ouput directory -- 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] Closed: (DOXIATOOLS-15) snippet macro with file reference cause editor failure
[
https://jira.codehaus.org/browse/DOXIATOOLS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIATOOLS-15.
-
Resolution: Fixed
Assignee: Vincent Siveton
Fixed in r1176346
you need to add ${project.basedir}/src... or ${basedir}/src...
snippet macro with file reference cause editor failure
--
Key: DOXIATOOLS-15
URL: https://jira.codehaus.org/browse/DOXIATOOLS-15
Project: Maven Doxia Tools
Issue Type: Bug
Components: Doxia Eclipse Editor
Reporter: Herve Boutemy
Assignee: Vincent Siveton
Priority: Minor
if you open following APT file:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/site/apt/lifecycles.apt?revision=1169931view=markup
you'll see the editing error marker.
And it is not possible to View the rendering: Doxia Converter Exception:
ParseException: Unable to execute macro in the APT document
It seems that relative path calculation is not done the same way in the
editor than when run with mvn CLI
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-15) snippet macro with file reference cause editor failure
[ https://jira.codehaus.org/browse/DOXIATOOLS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=278597#comment-278597 ] Vincent Siveton commented on DOXIATOOLS-15: --- apt editor doesn't handle correctly snippet snippet macro with file reference cause editor failure -- Key: DOXIATOOLS-15 URL: https://jira.codehaus.org/browse/DOXIATOOLS-15 Project: Maven Doxia Tools Issue Type: Bug Components: Doxia Eclipse Editor Reporter: Herve Boutemy Priority: Minor if you open following APT file: http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/site/apt/lifecycles.apt?revision=1169931view=markup you'll see the editing error marker. And it is not possible to View the rendering: Doxia Converter Exception: ParseException: Unable to execute macro in the APT document It seems that relative path calculation is not done the same way in the editor than when run with mvn CLI -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIATOOLS-14) remove doxia-converter-1.2-jar-with-dependencies.jar from svn
[ https://jira.codehaus.org/browse/DOXIATOOLS-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIATOOLS-14. - Resolution: Fixed Assignee: Vincent Siveton Removed useless lib remove doxia-converter-1.2-jar-with-dependencies.jar from svn - Key: DOXIATOOLS-14 URL: https://jira.codehaus.org/browse/DOXIATOOLS-14 Project: Maven Doxia Tools Issue Type: Improvement Components: Doxia Eclipse Editor Reporter: Herve Boutemy Assignee: Vincent Siveton this jar is actually in svn: http://svn.apache.org/viewvc/maven/sandbox/trunk/doxia/doxia-ide/eclipse/eclipse-plugins/plugins/org.apache.maven.doxia.ide.eclipse.common.ui/lib/ it should eventually be downloaded by Maven and put here, but not stored in svn -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277830#comment-277830 ] Vincent Siveton commented on DOXIATOOLS-11: --- You need to build doxia-osgi firstly and plugins secondly add Doxia Eclipse Editor to Apache CI server Key: DOXIATOOLS-11 URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 Project: Maven Doxia Tools Issue Type: New Feature Components: Doxia Eclipse Editor Reporter: Herve Boutemy Attachments: typescript latest builds should be downloadable from https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JXR-54) Discuss about Forrestdoc and JXR
[ https://jira.codehaus.org/browse/JXR-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274114#comment-274114 ] Vincent Siveton commented on JXR-54: No specials addons during the last year. If every body are happy with this, we could release 3.0 version as alpha or beta. Discuss about Forrestdoc and JXR Key: JXR-54 URL: https://jira.codehaus.org/browse/JXR-54 Project: Maven JXR Issue Type: Improvement Components: jxr Reporter: Vincent Siveton http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (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:comment-tabpanelfocusedCommentId=265219#action_265219
]
Vincent Siveton commented on DOXIASITETOOLS-58:
---
title/ is missing
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}
bannerLeft
name/
src/
width/
height/
/bannerLeft
{noformat}
Also, it will be better to use the XHTML notation for image ie
{noformat}
bannerLeft src= alt= name= border= width= height= title=/
{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] Closed: (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
]
Vincent Siveton closed DOXIASITETOOLS-58.
-
Resolution: Fixed
Fix Version/s: 1.2
Assignee: Vincent Siveton
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
Assignee: Vincent Siveton
Fix For: 1.2
The decoration model should be improved for logo banner to include some image
informations like size.
{noformat}
bannerLeft
name/
src/
width/
height/
/bannerLeft
{noformat}
Also, it will be better to use the XHTML notation for image ie
{noformat}
bannerLeft src= alt= name= border= width= height= title=/
{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] Commented: (MPDF-46) Remove [WARNING] Deprecated API called
[ http://jira.codehaus.org/browse/MPDF-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=255947#action_255947 ] Vincent Siveton commented on MPDF-46: - No warn using mvn 3+ only in mvn 2 Remove [WARNING] Deprecated API called -- Key: MPDF-46 URL: http://jira.codehaus.org/browse/MPDF-46 Project: Maven 2.x PDF Plugin Issue Type: Task Affects Versions: 1.1 Reporter: Lukas Theussl Assignee: Herve Boutemy Fix For: 1.2 Happens when including reports in the pdf. -- 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: (MSITE-41) Add a list of available language in site plugin
[ http://jira.codehaus.org/browse/MSITE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=255408#action_255408 ] Vincent Siveton commented on MSITE-41: -- http://sandbox.curre.net/mvn-site/2 or http://sandbox.curre.net/mvn-site/4/ could be the default IMHO. I will review it and commit soon. Add a list of available language in site plugin --- Key: MSITE-41 URL: http://jira.codehaus.org/browse/MSITE-41 Project: Maven 2.x and 3.x Site Plugin Issue Type: New Feature Components: internationalization Reporter: Vincent Siveton Fix For: 2.3 Attachments: language_menu.jpg, language_menu.jpg, language_menu.jpg, language_menu_as_select.jpg, MSITE-41-doxia-sitetools.patch, MSITE-41-maven-site-plugin.patch Please see the attached screenshots This preference menu could be a list of links or a select/ tag. The site descriptor needs to be updated: * for select/, by adding asSelect attribute in the menu element. * for links list, by adding nostrong attribute in the menu element (to not display as strong the current language and the current page) -- 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: (MDOAP-35) Fetch file-release url
Fetch file-release url -- Key: MDOAP-35 URL: http://jira.codehaus.org/browse/MDOAP-35 Project: Maven 2.x DOAP Plugin Issue Type: New Feature Reporter: Vincent Siveton -- 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: (MDOAP-35) Fetch file-release url
[ http://jira.codehaus.org/browse/MDOAP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-35. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1055397 Fetch file-release url -- Key: MDOAP-35 URL: http://jira.codehaus.org/browse/MDOAP-35 Project: Maven 2.x DOAP Plugin Issue Type: New Feature Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 -- 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: (MPIR-216) Report on dependency-management throws Exceptions using version range for dependency
[
http://jira.codehaus.org/browse/MPIR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=250506#action_250506
]
Vincent Siveton commented on MPIR-216:
--
It seems to come from aether, fill an issue to
https://issues.sonatype.org/browse/AETHER
Report on dependency-management throws Exceptions using version range for
dependency
Key: MPIR-216
URL: http://jira.codehaus.org/browse/MPIR-216
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependency-management
Affects Versions: 2.3.1
Environment: Maven 3.0.1, Java 6u23
Reporter: André Fügenschuh
Given the following simple project:
{code}
?xml version=1.0 encoding=UTF-8?
project xmlns=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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdfoo/groupId
artifactIdapp/artifactId
version3.0-SNAPSHOT/version
nameApp/name
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
version3.0-beta-3/version
configuration
reportPlugins
reportPlugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-project-info-reports-plugin/artifactId
version2.3.1/version
reportSets
reportSet
reports
!--reportindex/report
reportsummary/report--
reportdependency-management/report
!--reportdependencies/report--
/reports
/reportSet
/reportSets
/reportPlugin
/reportPlugins
/configuration
/plugin
/plugins
/pluginManagement
/build
dependencyManagement
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version[4.8,)/version
scopetest/scope
/dependency
/dependencies
/dependencyManagement
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
/dependency
/dependencies
/project
{code}
{{mvn site}} throws an exception (although site is generated):
{code}
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building App 3.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-3:site (default-site) @ app ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.3.1
[WARNING] No URL defined for the project - decoration links will not be
resolved
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Generating Dependency Management report---
maven-project-info-reports-plugin:2.3.1
[WARNING] Unable to create Maven project from repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find junit:junit:pom:[4.
8,) in http://uk.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the updat
e interval of UK has elapsed or updates are forced for project
junit:junit:pom:[4.8,)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:260)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:237)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:252)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtil
s.java:332)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(Depen
dencyManagementRenderer.java:219)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForS
cope(DependencyManagementRenderer.java:198)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForA
llScopes(DependencyManagementRenderer.java:149)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDe
pendencies(DependencyManagementRenderer.java:140)
at
[jira] Closed: (MDOAP-34) Add a way to add dynamically namespace
[ http://jira.codehaus.org/browse/MDOAP-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-34. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1055064, snapshot deployed Add a way to add dynamically namespace -- Key: MDOAP-34 URL: http://jira.codehaus.org/browse/MDOAP-34 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 Take http://labs.apache.org/doapizer.html We need to find a way to add for example xmlns:labs=http://labs.apache.org/doap-ext/1.0; -- 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: (MSITE-41) Add a list of available language in site plugin
[ http://jira.codehaus.org/browse/MSITE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248965#action_248965 ] Vincent Siveton commented on MSITE-41: -- Under the Project Documentation and before the built by logo. Add a list of available language in site plugin --- Key: MSITE-41 URL: http://jira.codehaus.org/browse/MSITE-41 Project: Maven 2.x and 3.x Site Plugin Issue Type: New Feature Components: internationalization Reporter: Vincent Siveton Attachments: language_menu.jpg, language_menu.jpg, language_menu.jpg, language_menu_as_select.jpg Please see the attached screenshots This preference menu could be a list of links or a select/ tag. The site descriptor needs to be updated: * for select/, by adding asSelect attribute in the menu element. * for links list, by adding nostrong attribute in the menu element (to not display as strong the current language and the current page) -- 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: (MDOAP-34) Add a way to add dynamically namespace
Add a way to add dynamically namespace -- Key: MDOAP-34 URL: http://jira.codehaus.org/browse/MDOAP-34 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton Take http://labs.apache.org/doapizer.html We need to find a way to add for example xmlns:labs=http://labs.apache.org/doap-ext/1.0; -- 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: (MDOAP-32) Generate a DOAP file for another Maven Project
[ http://jira.codehaus.org/browse/MDOAP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-32. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1050381, snapshot deployed Generate a DOAP file for another Maven Project -- Key: MDOAP-32 URL: http://jira.codehaus.org/browse/MDOAP-32 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 If the Maven project is a site project, it could be great to generate file DOAP in this Maven project but for another Maven project. -- 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: (MDOAP-33) Add more DOAP options like blog, audience, plateform...
[ http://jira.codehaus.org/browse/MDOAP-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-33. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1045054, snapshot deployed. Add more DOAP options like blog, audience, plateform... --- Key: MDOAP-33 URL: http://jira.codehaus.org/browse/MDOAP-33 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 DOAP has new fields, we need to add them as options. -- 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: (MDOAP-29) Detect Apache projects
Detect Apache projects -- Key: MDOAP-29 URL: http://jira.codehaus.org/browse/MDOAP-29 Project: Maven 2.x DOAP Plugin Issue Type: New Feature Affects Versions: 1.1 Reporter: Vincent Siveton Actually, asfextoptions/included parameter is always set to true, we need to detect ASF project to include or not extension -- 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: (MDOAP-29) Detect Apache projects
[ http://jira.codehaus.org/browse/MDOAP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-29. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1044800, snapshot deployed Detect Apache projects -- Key: MDOAP-29 URL: http://jira.codehaus.org/browse/MDOAP-29 Project: Maven 2.x DOAP Plugin Issue Type: New Feature Affects Versions: 1.1 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 Actually, asfextoptions/included parameter is always set to true, we need to detect ASF project to include or not extension -- 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: (MDOAP-30) Update requirement to Maven 2.2 and Java 5
Update requirement to Maven 2.2 and Java 5 -- Key: MDOAP-30 URL: http://jira.codehaus.org/browse/MDOAP-30 Project: Maven 2.x DOAP Plugin Issue Type: Task Affects Versions: 1.0 Reporter: Vincent Siveton -- 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: (MDOAP-30) Update requirement to Maven 2.2 and Java 5
[ http://jira.codehaus.org/browse/MDOAP-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-30. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1044930, snapshot deployed Update requirement to Maven 2.2 and Java 5 -- Key: MDOAP-30 URL: http://jira.codehaus.org/browse/MDOAP-30 Project: Maven 2.x DOAP Plugin Issue Type: Task Affects Versions: 1.0 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 -- 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: (MDOAP-31) Generated DOAP Mailing lists are too stricts
Generated DOAP Mailing lists are too stricts Key: MDOAP-31 URL: http://jira.codehaus.org/browse/MDOAP-31 Project: Maven 2.x DOAP Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Vincent Siveton The generated DOAP mailing-lists lists all Maven ML archive and other ML archives. We need to add a doapOptions for ML to set a single ML web page. -- 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: (MDOAP-31) Generated DOAP Mailing lists are too stricts
[ http://jira.codehaus.org/browse/MDOAP-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-31. Resolution: Fixed Fix Version/s: 1.1 o fixed in r1044941, snapshot deployed Generated DOAP Mailing lists are too stricts Key: MDOAP-31 URL: http://jira.codehaus.org/browse/MDOAP-31 Project: Maven 2.x DOAP Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Vincent Siveton Fix For: 1.1 The generated DOAP mailing-lists lists all Maven ML archive and other ML archives. We need to add a doapOptions for ML to set a single ML web page. -- 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: (MDOAP-32) Generate a DOAP file for another Maven Project
Generate a DOAP file for another Maven Project -- Key: MDOAP-32 URL: http://jira.codehaus.org/browse/MDOAP-32 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton If the Maven project is a site project, it could be great to generate file DOAP in this Maven project but for another Maven project. -- 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: (MDOAP-33) Add more DOAP options like blog, audience, plateform...
Add more DOAP options like blog, audience, plateform... --- Key: MDOAP-33 URL: http://jira.codehaus.org/browse/MDOAP-33 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Vincent Siveton DOAP has new fields, we need to add them as options. -- 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: (MDOAP-24) programing-language, os and name properties should be an RDF literals, not a RDF resources.
[ http://jira.codehaus.org/browse/MDOAP-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-24. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1044153, snapshot will be deployed programing-language, os and name properties should be an RDF literals, not a RDF resources. --- Key: MDOAP-24 URL: http://jira.codehaus.org/browse/MDOAP-24 Project: Maven 2.x DOAP Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Any Reporter: Tim Fliss Assignee: Vincent Siveton Priority: Minor Fix For: 1.1 Attachments: doap-language-bugreport.tgz, maven-doap-plugin.diff Summary The programming-language, os, and name properties are literals, not URIs. They should not be written as rdf:resources in the RDF output. The Problem While the resulting RDF will validate, what happens is that an RDF parser will interpret programming-language rdf:resource=java / as a URI fragment. (see the attached incorrect doap-language-bugreport.tgz:/target/site/doap_doap-language.rdf) Since there is no explicit xml:base in the DoaP file generated by the plugin, the resulting URL is based on the default supplied by the RDF parser. For example using the W3C RDF Validator yields: http://www.w3.org/RDF/Validator/run/java rather than simply java XML Base for RDF is specified at: see http://www.w3.org/TR/2003/PR-rdf-syntax-grammar-20031215/#section-Syntax-ID-xml-base Also note that the Apache Doap instructions correctly do not have rdf:resource for the programming language element: http://projects.apache.org/languages.html The Fix Instead of programming-language rdf:resource=java /, the plugin should generate programming-languagejava/programming-language. Similar changes apply to the os and name properties. Validation I am attaching diffs that include changes to the unit tests. Also, the RDF validator at http://www.w3.org/RDF/Validator/direct may be used to demonstrate that the progamming language, etc. elements are getting resolved to: http://www.w3.org/RDF/Validator/run/java rather than simply java. Simply java is what it should be. -- 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: (MDOAP-27) Generated files aren't useable with Jena
[ http://jira.codehaus.org/browse/MDOAP-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-27. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton MDOAP-24 fixed this issue and I added a validate parameter to validate the generated doap file using jena. Snapshot deployed. Generated files aren't useable with Jena Key: MDOAP-27 URL: http://jira.codehaus.org/browse/MDOAP-27 Project: Maven 2.x DOAP Plugin Issue Type: Bug Reporter: Christian Mahnke Assignee: Vincent Siveton Fix For: 1.1 I'm generating a DOAP file for deployment, the resulting file isn't parseable by Jena, here the exception: Caused by: com.hp.hpl.jena.rdf.model.LiteralRequiredException: Apache UGH metadata library at com.hp.hpl.jena.rdf.model.impl.StatementImpl.getLiteral(StatementImpl.java:101) at com.hp.hpl.jena.rdf.model.impl.StatementBase.getString(StatementBase.java:127) at uk.ac.osswatch.simal.model.jena.Resource.getLiteralValue(Resource.java:198) at uk.ac.osswatch.simal.model.jena.DoapResource.getName(DoapResource.java:77) at uk.ac.osswatch.simal.wicket.panel.ProjectSummaryPanel.populatePage(ProjectSummaryPanel.java:83) at uk.ac.osswatch.simal.wicket.panel.ProjectSummaryPanel.init(ProjectSummaryPanel.java:65) at uk.ac.osswatch.simal.wicket.UserHomePage.init(UserHomePage.java:32) ... 32 more The offending fragment of the DOAP file: !-- == -- !-- A name of something. -- !-- == -- name rdf:resource=Apache UGH metadata library/ Note the spaces in the rdf:resource attribute. The Plugin should probably do a sanity check. -- 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: (MDOAP-28) Remove developers/contributors having role 'emeritus'
[ http://jira.codehaus.org/browse/MDOAP-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-28. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton fixed in r1044279, snapshot deployed Remove developers/contributors having role 'emeritus' -- Key: MDOAP-28 URL: http://jira.codehaus.org/browse/MDOAP-28 Project: Maven 2.x DOAP Plugin Issue Type: Improvement Affects Versions: 1.1 Environment: All Reporter: Felix Knecht Assignee: Vincent Siveton Fix For: 1.1 Attachments: emeritus.patch, emeritus_test.patch In various Apache projects it's common to leave developers who are no longer active in the project still the developers section of the pom.xml but set the role to 'Emeritus'. Such developers shouldn't be listed in the DOAP file as maintainer. Patch doesn't adds this developers (and contributors) as maintainer. -- 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: (MDOAP-25) foaf:Organization usage doesn't comply with DoaP/FoaF specs.
[ http://jira.codehaus.org/browse/MDOAP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MDOAP-25. Resolution: Fixed Fix Version/s: 1.1 Assignee: Vincent Siveton Fixed in r1044321, snapshot deployed foaf:Organization usage doesn't comply with DoaP/FoaF specs. Key: MDOAP-25 URL: http://jira.codehaus.org/browse/MDOAP-25 Project: Maven 2.x DOAP Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Any Reporter: Tim Fliss Assignee: Vincent Siveton Priority: Minor Fix For: 1.1 Attachments: doap-organization-bugreport.tgz, MDOAP-25.patch Summary The foaf:Organization node is misplaced inside the foaf:Person node. It is not compliant with the FoaF or Doap specs. The Problem This is an instance of the issue described here: http://lists.foaf-project.org/pipermail/foaf-dev/2009-January/009452.html foaf:Organization like foaf:Group is a foaf:Agent (see http://xmlns.com/foaf/spec/#term_Agent), so the issue is the same. The recommended syntax from the DoaP project examples is to use the foaf:member property between the foaf:Organization node and the foaf:Person node. Unfortunately, per the FoaF spec, the relation only goes in that direction (Organization-member-Person) with no convenient inverse property. The Fix The best fix I can currently find is to use blank nodes and a separate Organization element that is not nested in the person element. Unfortunately, because the DoaP plugin isn't using native RDF tools internally, this will require a little more bookkeeping. rdf:RDF doap:Project maintainer rdf:nodeID=jdoe/ founder rdf:nodeID=jdoe/ /doap:Project Person nodeID=jdoe nameJohn Doe/name mbox rdf:resource=mailto:j...@example.org; / /Person doap:Organization doap:homepage rdf:resource=http://www.example.org; / doap:member rdf:nodeID=jdoe / /doap:Organization /rdf:RDF Additional Info Info about rdf:nodeID is available at: http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-blank-nodes -- 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: (MPIR-80) Add Java requirements to the Dependency Report
[ http://jira.codehaus.org/browse/MPIR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-80. --- Resolution: Fixed This feature is implemented only for java projects. For other requirements, please create a new issue. Add Java requirements to the Dependency Report -- Key: MPIR-80 URL: http://jira.codehaus.org/browse/MPIR-80 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Components: dependencies, summary Affects Versions: 2.0.1 Reporter: Niall Pemberton Fix For: 2.3 Attachments: maven-projectinfo-dependency-java-v3.patch, maven-projectinfo-dependency-java.patch, maven-projectinfo-summary-java.patch It would be nice to add a section to the dependency report showing the java version requirements. Attaching a patch which discovers the java version and compiler options from the java-compiler-plugin configuration and outputs a Java Version section. Has an option to configure whether or not this section is shown (default to false). -- 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: (DOXIASITETOOLS-40) List of site locales should be available in the rendering context.
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=245789#action_245789 ] Vincent Siveton commented on DOXIASITETOOLS-40: --- sounds good List of site locales should be available in the rendering context. -- Key: DOXIASITETOOLS-40 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-40 Project: Maven Doxia Sitetools Issue Type: Improvement Components: Site renderer Affects Versions: 1.1.4 Reporter: Yevgeny Nyden Attachments: siteLocalesChange-sitetools.diff Attached is a small improvement that adds a list of available site locales to the site rendering context. This would make a site template be aware of other locales available for the site and make it possible to implement a locale switching 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: (MPIR-208) Reduce the size of Repository locations for each of the Dependencies.
Reduce the size of Repository locations for each of the Dependencies. - Key: MPIR-208 URL: http://jira.codehaus.org/browse/MPIR-208 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: dependencies Affects Versions: 2.2 Reporter: Vincent Siveton If no artefacts in column repo, this column should be not listed for increase the reading. -- 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: (MPIR-180) Repositories which require authentication get blacklisted
[ http://jira.codehaus.org/browse/MPIR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-180. Resolution: Fixed Fix Version/s: 2.3 Assignee: Vincent Siveton refactored code to take care of auth defined in your settings.xml in r1040071, snapshot deployed. Repositories which require authentication get blacklisted - Key: MPIR-180 URL: http://jira.codehaus.org/browse/MPIR-180 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.1.2 Environment: maven 2.2.1 maven-site-plugin 2.1 Reporter: Stevo Slavic Assignee: Vincent Siveton Fix For: 2.3 Dependencies report when rendering dependency repository locations wrongfully blacklists repositories which require authentication. Bug is in DependenciesRenderer, void blacklistRepositoryMap( Map repos, List repoUrlBlackListed ) method, ProjectInfoReportUtils.getInputStream( repoUrl, settings ) call throws IOException (java.io.IOException: Server returned HTTP response code: 401 for URL: ...) if repoUrl is URL of a repository which requires authentication. -- 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: (MPIR-181) Dependency reporting plugin overwrites other project's artifact file
[
http://jira.codehaus.org/browse/MPIR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-181.
Resolution: Fixed
should be fixed with MPIR-158
Dependency reporting plugin overwrites other project's artifact file
Key: MPIR-181
URL: http://jira.codehaus.org/browse/MPIR-181
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Environment: Linux
Reporter: blaabloo
Projectmap is map of artifacts with groupid:artifactid being the key. When
project has multiple artifacts only one of them is put to the map. Dependency
node contains information about artifact and file information is the same
reference as used DefaultLifecycleExecutor. Every dependency's file is set
from this map and when building multimodule projects the latter projects may
fail because project's default artifact file is set to one of its attached
artifacts.
In org.apache.maven.report.projectinfo.dependencies.Dependencies
private void mapArtifactFiles( DependencyNode node, Map projectMap )
{
List childs = node.getChildren();
if ( ( childs == null ) || childs.isEmpty() )
{
return;
}
Iterator it = childs.iterator();
while ( it.hasNext() )
{
DependencyNode anode = (DependencyNode) it.next();
String key = ArtifactUtils.versionlessKey( anode.getArtifact() );
Artifact projartifact = (Artifact) projectMap.get( key );
if ( projartifact != null )
{
anode.getArtifact().setFile( projartifact.getFile() );
}
mapArtifactFiles( anode, projectMap );
}
}
--
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: (MNG-4921) Improve POM model
Improve POM model - Key: MNG-4921 URL: http://jira.codehaus.org/browse/MNG-4921 Project: Maven 2 3 Issue Type: New Feature Components: POM Affects Versions: 3.0.1 Reporter: Vincent Siveton The POM model was not enhanced in m3 for backward compatible reasons. Some users ask to add qualityMangement section (MPIR-149) and javadoc link (MJAVADOC-32). We need to have a plan to include them. -- 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: (MPIR-147) Dependencies report hangs while accessing SSL site. Connection never closes
[ http://jira.codehaus.org/browse/MPIR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=245657#action_245657 ] Vincent Siveton commented on MPIR-147: -- I bumped to latest wagon r1040075 (snap deployed). Confirm if it solves the pb. Dependencies report hangs while accessing SSL site. Connection never closes --- Key: MPIR-147 URL: http://jira.codehaus.org/browse/MPIR-147 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.1 Reporter: Jerome Lacoste mvn site hangs while generating the reports (dump below). This is 100% reproducible. This happens while contacting maven-repository.dev.java.net. The connection is opened and never closed. The connection to this external repository was done successfully several time in the same build. Notes: * a timeout would be useful: at org.apache.maven.wagon.providers.http.LightweightHttpWagon.resourceExists(LightweightHttpWagon.java:312) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.dependencyExistsInRepo(RepositoryUtils.java:219) * for some reason, the site report bypass our corporate repository (nexus). Cf MPIR-137 * workaround is to enable dependencyLocationsEnabledfalse/dependencyLocationsEnabled dependencyDetailsEnabledfalse/dependencyDetailsEnabled as done in MPIR-137 Full thread dump Java HotSpot(TM) Client VM (1.5.0_16-133 mixed mode): AWT-AppKit daemon prio=5 tid=0x01038530 nid=0xa0110fa0 runnable [0x..0xbfffe818] Low Memory Detector daemon prio=5 tid=0x01009030 nid=0x805800 runnable [0x..0x] CompilerThread0 daemon prio=9 tid=0x01008580 nid=0x812c00 waiting on condition [0x..0xb0b077d8] Signal Dispatcher daemon prio=9 tid=0x01008130 nid=0x811e00 waiting on condition [0x..0x] Finalizer daemon prio=8 tid=0x01007860 nid=0x819200 in Object.wait() [0xb0a05000..0xb0a05d90] at java.lang.Object.wait(Native Method) - waiting on 0x0a440228 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:120) - locked 0x0a440228 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:136) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x01007480 nid=0x817800 in Object.wait() [0xb0984000..0xb0984d90] at java.lang.Object.wait(Native Method) - waiting on 0x0a4402b0 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:474) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked 0x0a4402b0 (a java.lang.ref.Reference$Lock) main prio=5 tid=0x01001570 nid=0xb0801000 runnable [0xb07fe000..0xb0800148] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) - locked 0x05a4ba78 (a java.lang.Object) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:680) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) - locked 0x05a4bb28 (a com.sun.net.ssl.internal.ssl.AppInputStream) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at java.io.BufferedInputStream.read(BufferedInputStream.java:313) - locked 0x06b58100 (a java.io.BufferedInputStream) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:681) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:626) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:957) - locked 0x06b56708 (a sun.net.www.protocol.https.DelegateHttpsURLConnection) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) at org.apache.maven.wagon.providers.http.LightweightHttpWagon.resourceExists(LightweightHttpWagon.java:312) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.dependencyExistsInRepo(RepositoryUtils.java:219) at
[jira] Closed: (MPIR-194) [WARNING] Deprecated API called
[
http://jira.codehaus.org/browse/MPIR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-194.
Resolution: Not A Bug
Fix Version/s: 2.3
Should be fixed in latest maven-site-plugin (2.2)
[WARNING] Deprecated API called
---
Key: MPIR-194
URL: http://jira.codehaus.org/browse/MPIR-194
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Affects Versions: 2.2
Reporter: Lukas Theussl
Priority: Minor
Fix For: 2.3
Version 2.2 spits out a warning for each generated page:
{noformat}
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
{noformat}
The warning can be ignored AFAICT but it is annoying and confusing for users.
--
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: (MPIR-163) Invalid url fragment with local license file
[
http://jira.codehaus.org/browse/MPIR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=244574#action_244574
]
Vincent Siveton commented on MPIR-163:
--
Yes it is a known limitation of the basedir... you could define a trunk.dir
property in your parent and override it in your modules i.e.
{code}
|trunk.dir
|_LICENSE.TXT
|_ pom.xml (parent)
|_ module\
|_ pom.xml
{code}
Parent pom.xml:
{code}
properties
trunk.dir${basedir}/trunk.dir
/properties
licenses
license
nameXXX/name
url${trunk.dir}/LICENSE.TXT/ur
/license
/licenses
{code}
Module pom.xml:
{code}
properties
trunk.dir${basedir}/../trunk.dir
/properties
{code}
You could make your LICENSE.TXT on a webserver or on a public svn.
Invalid url fragment with local license file
Key: MPIR-163
URL: http://jira.codehaus.org/browse/MPIR-163
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.1.1
Environment: mvn 2.0.10, xp sp2
Reporter: Michael Osipov
Attachments: local-license.patch
I've set a local license file from my basedir in my pom. The dependencies
tree report lists the license but links to /dependencies.html#LICENSE.txt
which is incorrect. See
[here|http://java.fckeditor.net/java-demo/dependencies.html] for
net.fckeditor:java-core:jar:2.5-beta-1 for the failing testcase.
I have patched 2.1.1 which works well, see attachment.
--
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: (MPIR-163) Invalid url fragment with local license file
[ http://jira.codehaus.org/browse/MPIR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-163. Resolution: Won't Fix License url should be a valid url (file://...) Invalid url fragment with local license file Key: MPIR-163 URL: http://jira.codehaus.org/browse/MPIR-163 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.1.1 Environment: mvn 2.0.10, xp sp2 Reporter: Michael Osipov Attachments: local-license.patch I've set a local license file from my basedir in my pom. The dependencies tree report lists the license but links to /dependencies.html#LICENSE.txt which is incorrect. See [here|http://java.fckeditor.net/java-demo/dependencies.html] for net.fckeditor:java-core:jar:2.5-beta-1 for the failing testcase. I have patched 2.1.1 which works well, see attachment. -- 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: (MPIR-158) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-158. Resolution: Fixed Fix Version/s: 2.3 Assignee: Vincent Siveton fixed in r1036825, snapshot deployed Artifact ## has no file error. -- Key: MPIR-158 URL: http://jira.codehaus.org/browse/MPIR-158 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependencies Affects Versions: 2.1.1 Environment: Windows xp, tomcat 5.5 server Reporter: Damian Sinczak Assignee: Vincent Siveton Priority: Minor Fix For: 2.3 During 'mvn site' command on project i receive some strange errors. Their are no critical, but they are still errors. Console dump: [ERROR] Artifact: org.apache.abdera:abdera-core:jar:0.4.0-incubating has no file . [ERROR] Artifact: org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating has no file. [ERROR] Artifact: org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating has no file. [ERROR] Artifact: org.apache.abdera:abdera-i18n:jar:0.4.0-incubating has no file . [ERROR] Artifact: org.apache.abdera:abdera-parser:jar:0.4.0-incubating has no fi le. [ERROR] Artifact: org.apache.cxf:cxf-api:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-common-schemas:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-common-utilities:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-soap:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-xml:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-core:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-frontend-simple:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-rt-ws-addr:jar:2.2 has no file. [ERROR] Artifact: org.apache.cxf:cxf-tools-common:jar:2.2 has no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0 .2 has no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 .1 has no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.5 h as no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0 has no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.2 ha s no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 has no file. [ERROR] Artifact: org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1. 1.2 has no file. [ERROR] Artifact: org.apache.neethi:neethi:jar:2.0.4 has no file. [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 has no file. [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 has no file. [ERROR] Artifact: org.apache.ws.commons.schema:XmlSchema:jar:1.4.4 has no file. [ERROR] Artifact: org.apache.xmlbeans:xmlbeans:jar:2.3.0 has no file. [ERROR] Artifact: org.codehaus.jettison:jettison:jar:1.0.1 has no file. [ERROR] Artifact: org.codehaus.woodstox:wstx-asl:jar:3.2.6 has no file. [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.1.GA has no file. [ERROR] Artifact: org.hibernate:hibernate-commons-annotations:jar:3.0.0.ga has n o file. [ERROR] Artifact: org.mortbay.jetty:jetty:jar:6.1.15 has no file. [ERROR] Artifact: org.mortbay.jetty:jetty-util:jar:6.1.15 has no file. [ERROR] Artifact: org.slf4j:slf4j-api:jar:1.3.1 has no file. [ERROR] Artifact: org.slf4j:slf4j-jdk14:jar:1.3.1 has no file. [ERROR] Artifact: org.springframework:spring-beans:jar:2.5.5 has no file. [ERROR] Artifact: org.springframework:spring-context:jar:2.5.5 has no file. [ERROR] Artifact: org.springframework:spring-core:jar:2.5.5 has no file. [ERROR] Artifact: org.springframework:spring-web:jar:2.5.5 has no file. [ERROR] Artifact: wsdl4j:wsdl4j:jar:1.6.2 has no file. [ERROR] Artifact: xalan:xalan:jar:2.6.0 has no file. [ERROR] Artifact: xerces:xercesImpl:jar:2.6.2 has no file. [ERROR] Artifact: xerces:xmlParserAPIs:jar:2.6.2 has no file. [ERROR] Artifact: xml-apis:xml-apis:jar:1.3.02 has no file. [ERROR] Artifact: xml-resolver:xml-resolver:jar:1.2 has no file. [ERROR] Artifact: xom:xom:jar:1.0 has no file. [INFO] Generating Project Team report. [INFO] Generating Project License report. [INFO] Generating Project Plugins report. [INFO] Generating Maven Surefire Report report. [INFO] Generating FindBugs Report report. [INFO] Using source root: [INFO] C:\edys_workspace\edystok\target\classes [INFO] Using test source root: [INFO] C:\edys_workspace\edystok\target\test-classes [INFO] No effort provided, using default effort. [INFO] Adding Source Directory:
[jira] Moved: (MJAVADOC-303) Project reports label for JavaDocs contains pom property name instead.
[ http://jira.codehaus.org/browse/MJAVADOC-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MPIR-192 to MJAVADOC-303: --- Affects Version/s: (was: 2.1.2) 2.7 Key: MJAVADOC-303 (was: MPIR-192) Project: Maven 2.x Javadoc Plugin (was: Maven 2.x Project Info Reports Plugin) Project reports label for JavaDocs contains pom property name instead. -- Key: MJAVADOC-303 URL: http://jira.codehaus.org/browse/MJAVADOC-303 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.7 Environment: Windows XPSP2, Maven 2.2.1, Java 1.6u18 Reporter: David Biesack Priority: Minor Attachments: pom.xml When a pom.xml defines a property, such as properties namejava.language.version/namevalue1.6/value /properties then the project info reports uses the property name for the 'Document' label of the Javadoc report in site/project-reports.html i.e. the generated HTML is file:///U:/dev/maven-bugs/MPIR-javadoc/target/site/apidocs/index.html tr class=btda href=apidocs/index.htmljava.language.version/a/td tdJavaDoc API documentation./td See attached pom.xml -- 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: (MPIR-199) ProjectInfoReportUtils.java : Avoid using blocking call [ url.openStream() ] while opening stream from an URL
[
http://jira.codehaus.org/browse/MPIR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-199.
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Vincent Siveton
fixed in r1036439, snapshot deployed
ProjectInfoReportUtils.java : Avoid using blocking call [ url.openStream() ]
while opening stream from an URL
-
Key: MPIR-199
URL: http://jira.codehaus.org/browse/MPIR-199
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.1.1, 2.1.2, 2.2
Environment: any, with no internet connectivity [=~ intranet , behind
proxy etc.. ]
Reporter: Prashant Bhate
Assignee: Vincent Siveton
Fix For: 2.3
This issue is related to http://jira.codehaus.org/browse/MPIR-150
it would be nice if {{url.openStream();}}
from
{code:title=ProjectInfoReportUtils.java|borderStyle=solid}
InputStream in =null;
try
{
in = url.openStream();
{code}
can be replaced with
{code}
//Define constant TIMEOUT with pre set timeout
InputStream in =null;
try
{
URLConnection conn = url.openConnection();
conn.setConnectTimeout(TIMEOUT);
conn.setReadTimeout(TIMEOUT);
in = conn.getInputStream();
{code}
{{url.openStream();}} is a blocking call that makes caller wait forever and
eventually timeouts at the end
--
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: (MPIR-132) Dependency report fails on system-scope dependencies
[
http://jira.codehaus.org/browse/MPIR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-132.
Resolution: Cannot Reproduce
Unable to reproduce it
Dependency report fails on system-scope dependencies
Key: MPIR-132
URL: http://jira.codehaus.org/browse/MPIR-132
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies
Affects Versions: 2.1
Reporter: Kohsuke Kawaguchi
Attachments: MPIR-132-test.patch
If a project includes a dependency to the system-scope artifact (such as
tools.jar), the dependency report generation fails with NPE.
MPIR-37 is probably the same issue, but I couldn't reopen it.
{noformat}
java.lang.NullPointerException
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:526)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:234)
at
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:316)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.java:623)
at
org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:274)
at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:239)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The essence of the problem is as follows.
DependenciesRenderer has the following code to build POM out of all
dependencies, so that it can generate transitive dependency tree:
{noformat}
populateRepositoryMap( repoMap,
repoUtils.getRemoteArtifactRepositories() );
for ( Iterator it = alldeps.iterator(); it.hasNext(); )
{
Artifact artifact = (Artifact) it.next();
try
{
[jira] Updated: (MPIR-206) Generalize configuration for text reports
[ http://jira.codehaus.org/browse/MPIR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-206: - Component/s: summary scm project-team plugin-management license issue-tracking index dependency-management dependency-convergence dependencies cim Summary: Generalize configuration for text reports (was: Improve configuration of mailing list header text.) Generalize configuration for text reports - Key: MPIR-206 URL: http://jira.codehaus.org/browse/MPIR-206 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: cim, dependencies, dependency-convergence, dependency-management, index, issue-tracking, license, mailing-list, plugin-management, project-team, scm, summary Reporter: Olivier Lamy Fix For: 2.2 Attachments: MPIR-206.txt The generated mailing list report has a header which provides basic info on the page. However, in some cases this information is not enough. For example, some lists may not allow posting; it would be useful to be able to explain why. In the case of Apache Commons, the lists are shared, so users need to add a prefix to the subject line. There are no doubt other use cases. It would be useful to be able to override the introduction. -- 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: (MPIR-206) Generalize configuration for text reports
[ http://jira.codehaus.org/browse/MPIR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-206. Resolution: Fixed Fix Version/s: (was: 2.2) 2.3 Assignee: Vincent Siveton fixed in r1035985, snapshot deployed Generalize configuration for text reports - Key: MPIR-206 URL: http://jira.codehaus.org/browse/MPIR-206 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: cim, dependencies, dependency-convergence, dependency-management, index, issue-tracking, license, mailing-list, plugin-management, project-team, scm, summary Reporter: Olivier Lamy Assignee: Vincent Siveton Fix For: 2.3 Attachments: MPIR-206.txt The generated mailing list report has a header which provides basic info on the page. However, in some cases this information is not enough. For example, some lists may not allow posting; it would be useful to be able to explain why. In the case of Apache Commons, the lists are shared, so users need to add a prefix to the subject line. There are no doubt other use cases. It would be useful to be able to override the introduction. -- 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: (MPIR-207) Add a distribution management report
Add a distribution management report Key: MPIR-207 URL: http://jira.codehaus.org/browse/MPIR-207 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Reporter: Vincent Siveton -- 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: (MPIR-207) Add a distribution management report
[ http://jira.codehaus.org/browse/MPIR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-207. Resolution: Fixed Fix Version/s: 2.3 Assignee: Vincent Siveton fixed in r1036268, snapshot deployed. Add a distribution management report Key: MPIR-207 URL: http://jira.codehaus.org/browse/MPIR-207 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 2.3 -- 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: (MPIR-198) introduction does not allow HTML markup
[ http://jira.codehaus.org/browse/MPIR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-198. Resolution: Fixed Fix Version/s: 2.3 should be fixed with MPIR-206 introduction does not allow HTML markup --- Key: MPIR-198 URL: http://jira.codehaus.org/browse/MPIR-198 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: mailing-list Affects Versions: 2.2 Reporter: SebbASF Fix For: 2.3 Further to http://jira.codehaus.org/browse/MPIR-189 the property does not seem to allow any markup. This is very limiting. HTML markup ought to be allowed, e.g. to allow a link to a page describing the e-mail etiquette etc. In particular for ASF projects there really needs to be a link to the Forum Archive Policy http://www.apache.org/foundation/public-archives.html The string can be specified with embedded markup if one uses the ![CDATA[ tag. But something in the code then escapes theso they appear as text in the generated page. -- 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: (MPIR-128) Add a link to a repository location in Project Summary
[ http://jira.codehaus.org/browse/MPIR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-128. Resolution: Fixed Fix Version/s: 2.3 Assignee: Vincent Siveton fixed in r1036275, snapshot deployed Add a link to a repository location in Project Summary -- Key: MPIR-128 URL: http://jira.codehaus.org/browse/MPIR-128 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: summary Affects Versions: 2.1 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 2.3 Similar to the dependencies report but for the current project. -- 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: (MPIR-196) Add a DateBuilt field to the Build Information section of the Project Summary page
[ http://jira.codehaus.org/browse/MPIR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-196. Resolution: Won't Fix The date is display using the site plugin (see the Last Published info), yes we could duplicate this information in the summary report but I don't think it is a necessary requirement. Add a DateBuilt field to the Build Information section of the Project Summary page -- Key: MPIR-196 URL: http://jira.codehaus.org/browse/MPIR-196 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: William Ferguson One of the biggest problems (IMHO) when looking at project documentation is the inability to readily determine the age of a component or the age age of the documentation. Such information is often sued to make a decision on how relevant a new component might be. The Project Summary page generated by the Site plugin contains a Build Information section. This section identifies the GroupId, ArtifactId, Version, and Type. If it also published the DateTime at which a component was built then it solve the problem above. -- 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: (MPIR-203) Missing info leads to ArrayIndexOutOfBounds
[ http://jira.codehaus.org/browse/MPIR-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-203. Resolution: Cannot Reproduce using the latest MPIR I cannot reproduce it. Missing info leads to ArrayIndexOutOfBounds --- Key: MPIR-203 URL: http://jira.codehaus.org/browse/MPIR-203 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Environment: Apache Maven 2.2.1 (rdebian-1) Java version: 1.6.0_20 Java home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre Default locale: en_GB, platform encoding: UTF-8 OS name: linux version: 2.6.32-24-generic arch: amd64 Family: unix Reporter: Tim Pizey [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 1 [INFO] [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777) at org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267) at org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDependenciesForScope(DependenciesRenderer.java:787) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderDependenciesForAllScopes(DependenciesRenderer.java:452) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencies(DependenciesRenderer.java:436) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:253) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:215) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) 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) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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:
[jira] Commented: (MSITE-522) Update to Doxia 1.1.4
[ http://jira.codehaus.org/browse/MSITE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242663#action_242663 ] Vincent Siveton commented on MSITE-522: --- Probably we need to do it for the m3 core too, but we have a JVZ's comment to use 1.0-alpha-9 Update to Doxia 1.1.4 - Key: MSITE-522 URL: http://jira.codehaus.org/browse/MSITE-522 Project: Maven 2.x Site Plugin Issue Type: Task Components: doxia integration Affects Versions: 2.1.1, 3.0-beta-3 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 2.2, 3.0-beta-4 -- 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: (MLINKCHECK-10) Upgrade to Doxia 1.1
[
http://jira.codehaus.org/browse/MLINKCHECK-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242086#action_242086
]
Vincent Siveton commented on MLINKCHECK-10:
---
agree
Upgrade to Doxia 1.1
Key: MLINKCHECK-10
URL: http://jira.codehaus.org/browse/MLINKCHECK-10
Project: Maven 2.x Linkcheck Plugin
Issue Type: Task
Affects Versions: 1.0
Reporter: Lukas Theussl
Attachments: MLINKCHECK-10.patch
There are a couple of Doxia 1.0 specific quirks in the report-generation
code, in particular several calls to {{sink.rawText()}}, which makes the
plugin unusable with different sinks (cf the pdf plugin).
--
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: (MPIR-171) support TimeZones as a timezone
[
http://jira.codehaus.org/browse/MPIR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-171.
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Vincent Siveton
I fixed the M3 POM description and updated the code in r1029846, snapshot
deployed.
support TimeZones as a timezone
-
Key: MPIR-171
URL: http://jira.codehaus.org/browse/MPIR-171
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Affects Versions: 2.1.2
Reporter: James Nord
Assignee: Vincent Siveton
Priority: Trivial
Fix For: 2.3
The POM XSD defiens the TimeZone as an xs:string (although the descriptions
says an integer between -11 and 12)
If the desctription is enforced you can not be in a timezone that is not a
multiple of 1 hour away from UTC (e.g. certain parts of india)
So the description is wrong and it's just a String.
So why not support a full formatted timezone such as Europe/London, then the
mpir can use funky javascript to show your actual time including any daylight
saving offset. (as opposed to a fixed offset from GMT ignoring DST changes)
e.g. support
{code:xml}developers
developer
idbob/id
nameBob Hacker/name
emailb...@example.com/email
timezoneEurope/London/timezone
roles
roledeveloper/role
/roles
/developer
/developers{code}
Currently the site shows NaN for the Current time.
--
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: (MPIR-206) Improve configuration of mailing list header text.
[ http://jira.codehaus.org/browse/MPIR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-206: - Attachment: MPIR-206.txt A patch to include custom bundle and a custom i18n class. Improve configuration of mailing list header text. -- Key: MPIR-206 URL: http://jira.codehaus.org/browse/MPIR-206 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: mailing-list Reporter: Olivier Lamy Fix For: 2.2 Attachments: MPIR-206.txt The generated mailing list report has a header which provides basic info on the page. However, in some cases this information is not enough. For example, some lists may not allow posting; it would be useful to be able to explain why. In the case of Apache Commons, the lists are shared, so users need to add a prefix to the subject line. There are no doubt other use cases. It would be useful to be able to override the introduction. -- 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: (MPIR-205) Add the license information for each dependency
[ http://jira.codehaus.org/browse/MPIR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241287#action_241287 ] Vincent Siveton commented on MPIR-205: -- Also added similar stuffs for the dependency-management report in r1028260, snapshot deployed Add the license information for each dependency --- Key: MPIR-205 URL: http://jira.codehaus.org/browse/MPIR-205 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Matthew Smith Assignee: Vincent Siveton Fix For: 2.3 Attachments: patch The current Dependency report includes tables for the dependencies that include GroupId,ArtifactId, Version, Classifier,Type. This patch will include a License column to the tables. The License will also be a link making it easier to relate licenses to atrifacts. The License section of the document is affected. -- 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: (MPIR-204) License report should not try to include pdf content as plain text
[
http://jira.codehaus.org/browse/MPIR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPIR-204.
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Vincent Siveton
Patch applied in r1028267 with this change: linkOnly param is always true in
offline mode
License report should not try to include pdf content as plain text
--
Key: MPIR-204
URL: http://jira.codehaus.org/browse/MPIR-204
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: license
Affects Versions: 2.2
Reporter: Grégory Joseph
Assignee: Vincent Siveton
Fix For: 2.3
Attachments: MPIR-204.patch
The LicenseReport class has a relevant TODO: {{we should check for a
text/html mime type instead, and possibly use a html parser to do this a bit
more cleanly/reliably.}}. That, and/or there could be a configuration item so
that one could configure the report to simply render links to the license
documents rather than attempt to include them verbatim in the generated 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] Commented: (MPIR-204) License report should not try to include pdf content as plain text
[
http://jira.codehaus.org/browse/MPIR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241291#action_241291
]
Vincent Siveton commented on MPIR-204:
--
soon probably in November or for Xmas
License report should not try to include pdf content as plain text
--
Key: MPIR-204
URL: http://jira.codehaus.org/browse/MPIR-204
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: license
Affects Versions: 2.2
Reporter: Grégory Joseph
Assignee: Vincent Siveton
Fix For: 2.3
Attachments: MPIR-204.patch
The LicenseReport class has a relevant TODO: {{we should check for a
text/html mime type instead, and possibly use a html parser to do this a bit
more cleanly/reliably.}}. That, and/or there could be a configuration item so
that one could configure the report to simply render links to the license
documents rather than attempt to include them verbatim in the generated 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] Commented: (MJAVADOC-297) NullPointerException in AbstractFixJavadocMojo.writeParamTag()
[
http://jira.codehaus.org/browse/MJAVADOC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241149#action_241149
]
Vincent Siveton commented on MJAVADOC-297:
--
It seems that a given javadoc param has no type. Could you isolate your error
and give us a sample?
NullPointerException in AbstractFixJavadocMojo.writeParamTag()
--
Key: MJAVADOC-297
URL: http://jira.codehaus.org/browse/MJAVADOC-297
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.7
Environment: graham-leggetts-macbook-pro-3:patricia-db-trunk minfrin$
mvn --version
Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.5.8 arch: x86_64 Family: mac
Reporter: Graham Leggett
While attempting to run the javadoc:fix goal against source code, v2.7 of the
javadoc plugin crashed as follows:
{noformat}[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.writeParamTag(AbstractFixJavadocMojo.java:1958)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1842)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1747)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocComment(AbstractFixJavadocMojo.java:1658)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateEntityComment(AbstractFixJavadocMojo.java:1527)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.fixMethodComment(AbstractFixJavadocMojo.java:1391)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.processFix(AbstractFixJavadocMojo.java:993)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.execute(AbstractFixJavadocMojo.java:405)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{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] Commented: (MJAVADOC-298) java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc when building a javadoc-jar
[
http://jira.codehaus.org/browse/MJAVADOC-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241150#action_241150
]
Vincent Siveton commented on MJAVADOC-298:
--
mvn clean install from your test case works for me. My env:
{noformat}
$ mvn -version
Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
Java version: 1.6.0_22
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: fr_FR, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
{noformat}
What is your env?
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be
cast to com.sun.javadoc.AnnotationTypeDoc when building a javadoc-jar
Key: MJAVADOC-298
URL: http://jira.codehaus.org/browse/MJAVADOC-298
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.7
Reporter: Marius Kruger
Attachments: test-javadoc.zip
I'm trying to build java-doc jar, but I get the stack trace below if I run
`mvn install` in the attached maven project.
I tried the workarounds in the following, but could not get them to work for
building a javadoc-jar:
http://jira.codehaus.org/browse/MJAVADOC-214
http://maven.40175.n5.nabble.com/JavaDoc-Report-crashes-with-TestNG-td106262.html
[ERROR] MavenReportException: Error while creating archive:
Exit code: 1 -
/stf/prj/arch_prototypes/maven/test-javadoc/src/main/java/com/google/common/collect/UnFinalHashMultimap.java:49:
warning - Tag @link: reference not found:
com.google.common.collect.HashMultimaps
/stf/prj/arch_prototypes/maven/test-javadoc/src/main/java/com/google/common/collect/UnFinalHashMultimap.java:49:
warning - Tag @link: reference not found: http
://code.google.com/p/guava-libraries/issues/detail?id=338
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be
cast to com.sun.javadoc.AnnotationTypeDoc
at
com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
at
com.sun.tools.doclets.formats.html.HtmlDocletWriter.getAnnotations(HtmlDocletWriter.java:1739)
at
com.sun.tools.doclets.formats.html.HtmlDocletWriter.writeAnnotationInfo(HtmlDocletWriter.java:1713)
at
com.sun.tools.doclets.formats.html.HtmlDocletWriter.writeAnnotationInfo(HtmlDocletWriter.java:1692)
at
com.sun.tools.doclets.formats.html.AbstractExecutableMemberWriter.writeParameters(AbstractExecutableMemberWriter.java:117)
at
com.sun.tools.doclets.formats.html.AbstractExecutableMemberWriter.writeParameters(AbstractExecutableMemberWriter.java:100)
at
com.sun.tools.doclets.formats.html.MethodWriterImpl.writeSignature(MethodWriterImpl.java:154)
at
com.sun.tools.doclets.internal.toolkit.builders.MethodBuilder.buildSignature(MethodBuilder.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[jira] Closed: (MPIR-205) Add the license information for each dependency
[ http://jira.codehaus.org/browse/MPIR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-205. Resolution: Fixed Fix Version/s: 2.3 Assignee: Vincent Siveton Fixed in r1027937 with minor modifications, snapshot deployed. Add the license information for each dependency --- Key: MPIR-205 URL: http://jira.codehaus.org/browse/MPIR-205 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Matthew Smith Assignee: Vincent Siveton Fix For: 2.3 Attachments: patch The current Dependency report includes tables for the dependencies that include GroupId,ArtifactId, Version, Classifier,Type. This patch will include a License column to the tables. The License will also be a link making it easier to relate licenses to atrifacts. The License section of the document is affected. -- 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: (MANTRUN-133) maven-antrun-plugin with the ejbgen ant task
[ http://jira.codehaus.org/browse/MANTRUN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANTRUN-133. --- Resolution: Duplicate maven-antrun-plugin with the ejbgen ant task - Key: MANTRUN-133 URL: http://jira.codehaus.org/browse/MANTRUN-133 Project: Maven 2.x Antrun Plugin Issue Type: Bug Environment: Dev environment Reporter: polireddy Attachments: ejbgen-build-maven.xml, pom.xml When i am calling ant build.xml from maven to run ejbgen task, getting the following issue. [null] Exception in thread main java.lang.NoClassDefFoundError: com/sun/j avadoc/Type [null] at com.bea.util.jam.provider.JamServiceFactoryImpl.createSourceB uilder(JamServiceFactoryImpl.java:205) [null] at com.bea.util.jam.provider.JamServiceFactoryImpl.createBuilder (JamServiceFactoryImpl.java:158) [null] at com.bea.util.jam.provider.JamServiceFactoryImpl.createClassLo ader(JamServiceFactoryImpl.java:137) [null] at com.bea.util.jam.provider.JamServiceFactoryImpl.createService (JamServiceFactoryImpl.java:78) [null] at com.bea.sgen.loader.JClassLoaderImpl.load(JClassLoaderImpl.ja va:107) [null] at com.bea.sgen.SGen.run(SGen.java:190) [null] at com.bea.wls.ejbgen.EJBGen.main(EJBGen.java:212) [null] at com.bea.wls.ejbgen.EJBGen.main(EJBGen.java:238) [ejbgen] Java returned: 1 [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: The following error occurred while exe cuting this line: C:\apps-maven\sasejb\sasejb-ear\ejbgen-build-maven.xml:32: Java returned: 1 If i run ant build.xml from command prompt, not getting any issue. it's working fine. Issue is comming if i do from Maven. Would you please me to fix this issue. it's very urgent for me -- 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: (MANTRUN-127) provide more tracking info when a task fails
[ http://jira.codehaus.org/browse/MANTRUN-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANTRUN-127. --- Resolution: Fixed Fix Version/s: 1.7 Assignee: Vincent Siveton fixed in r1027516 Add in the MojoExecutionException the following message: around Ant part ...Ant XML part... @ lineNumber:columnNumber from target/antrun/build-main.xml provide more tracking info when a task fails Key: MANTRUN-127 URL: http://jira.codehaus.org/browse/MANTRUN-127 Project: Maven 2.x Antrun Plugin Issue Type: Improvement Reporter: Petr Kozelka Assignee: Vincent Siveton Priority: Minor Fix For: 1.7 - task name - pom line number - or at least, line number in the tasks part This might make finding out a problem much faster -- 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: (MANTRUN-129) Please add as 'skip' parameter
[ http://jira.codehaus.org/browse/MANTRUN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANTRUN-129. --- Resolution: Fixed Fix Version/s: 1.7 Assignee: Vincent Siveton fixed in r1025502 Please add as 'skip' parameter -- Key: MANTRUN-129 URL: http://jira.codehaus.org/browse/MANTRUN-129 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.3 Reporter: Benson Margulies Assignee: Vincent Siveton Fix For: 1.7 In some structures involving parent poms, it is very helpful when plugin have a 'skip' parameter, so that an execution which is inherited through an entire forest of projects can be selectively turned on and off. Other plugins have this. -- 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: (MANTRUN-158) Add a new parameter to export Ant properties to Maven properties
Add a new parameter to export Ant properties to Maven properties Key: MANTRUN-158 URL: http://jira.codehaus.org/browse/MANTRUN-158 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.6 Reporter: Vincent Siveton In some case, it will be great to propagate Ant properties from target/ to the Maven properties. -- 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: (MANTRUN-158) Add a new parameter to export Ant properties to Maven properties
[ http://jira.codehaus.org/browse/MANTRUN-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MANTRUN-158. --- Resolution: Fixed Fix Version/s: 1.7 Assignee: Vincent Siveton Fixed in r1025558 Add a new parameter to export Ant properties to Maven properties Key: MANTRUN-158 URL: http://jira.codehaus.org/browse/MANTRUN-158 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.6 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.7 In some case, it will be great to propagate Ant properties from target/ to the Maven properties. -- 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: (MSKINS-8) Merge Doxia 1.1.2 changes
Merge Doxia 1.1.2 changes - Key: MSKINS-8 URL: http://jira.codehaus.org/browse/MSKINS-8 Project: Maven Skins Issue Type: Task Components: Stylus Skin Affects Versions: stylus-1.1.1 Reporter: Vincent Siveton -- 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: (MSKINS-8) Merge Doxia 1.1.2 changes
[ http://jira.codehaus.org/browse/MSKINS-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MSKINS-8. Resolution: Fixed Fix Version/s: stylus-1.1.1 Assignee: Vincent Siveton fixed in [r888366|http://svn.apache.org/viewvc?rev=888366view=rev] Merge Doxia 1.1.2 changes - Key: MSKINS-8 URL: http://jira.codehaus.org/browse/MSKINS-8 Project: Maven Skins Issue Type: Task Components: Stylus Skin Affects Versions: stylus-1.1.1 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: stylus-1.1.1 -- 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: (DOXIASITETOOLS-32) Deployed decoration-1.0.1.xsd
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIASITETOOLS-32. - Resolution: Fixed Fix Version/s: (was: 1.2) 1.1.2 Assignee: Vincent Siveton need to sync Deployed decoration-1.0.1.xsd - Key: DOXIASITETOOLS-32 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-32 Project: Maven Doxia Sitetools Issue Type: Task Components: Decoration model Affects Versions: 1.1.2 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1.2 Due to DOXIASITETOOLS-31, we need to deployed a new version of decoration-1.0.1.xsd -- 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-32) Deployed decoration-1.0.1.xsd
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIASITETOOLS-32: -- Fix Version/s: (was: 1.1.2) 1.2 Deployed decoration-1.0.1.xsd - Key: DOXIASITETOOLS-32 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-32 Project: Maven Doxia Sitetools Issue Type: Task Components: Decoration model Affects Versions: 1.1.2 Reporter: Vincent Siveton Fix For: 1.2 Due to DOXIASITETOOLS-31, we need to deployed a new version of decoration-1.0.1.xsd -- 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: (MJAVADOC-266) META-INF directory copied from resource artifacts
[ http://jira.codehaus.org/browse/MJAVADOC-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-266. Resolution: Fixed Fix Version/s: 2.6.1 Assignee: Vincent Siveton fixed in [r828711|http://svn.apache.org/viewvc?rev=828711view=rev], snapshot deployed META-INF directory copied from resource artifacts - Key: MJAVADOC-266 URL: http://jira.codehaus.org/browse/MJAVADOC-266 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Reporter: Daniel Spilker Assignee: Vincent Siveton Priority: Minor Fix For: 2.6.1 When using a resource artifacts the META-INF directory from the artifact JAR should not be copied into the output directory. -- 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: (MJAVADOC-268) performance problem in AbstractJavadocMojo.getModulesLinks()
[ http://jira.codehaus.org/browse/MJAVADOC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-268. Resolution: Fixed Fix Version/s: 2.6.1 Assignee: Vincent Siveton Patch applied in [r827951|http://svn.apache.org/viewvc?rev=827951view=rev], snapshot deployed. performance problem in AbstractJavadocMojo.getModulesLinks() Key: MJAVADOC-268 URL: http://jira.codehaus.org/browse/MJAVADOC-268 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200) Java version: 1.6.0_13 Java home: /home/mkleint/javatools/jdk1.6.0_13/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.29.6-desktop-2mnb arch: i386 Family: unix Reporter: Milos Kleint Assignee: Vincent Siveton Priority: Critical Fix For: 2.6.1 Attachments: javadoc.patch The getModulesLinks() method is unacceptably slow under certain conditions: 1. project's url is defined 2. one or more projects in reactor do not have any java sources and are not of pom packaging. For such projects the apidocs/ output folder is never created resulting in repeated invokation of a forked javadoc goal. It's more severe with high number of modules in reactor and high number of modules without any java sources. as an example checkout hg clone https://hg.kenai.com/hg/forceten~src; The immediate problem is in the apidocsFile.exists() condition that re-triggers the forked invokation. The attached patch fixes that. However it looks suspicitions that the method is being called repeatedly for each module at all. Maybe the aborting condition at the start of the method body is wrong (I was not able to decypher that) workaround is to use 2.5 or not to specify the url in pom.xml or set the detectOfflineLinks parameter to false. -- 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: (MJAVADOC-252) javadoc link : nonproxyhosts not used
[ http://jira.codehaus.org/browse/MJAVADOC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=195227#action_195227 ] Vincent Siveton commented on MJAVADOC-252: -- @Martijn, the patch doesn't affect NTLM proxy. You could use additionalJOption/ for this proxy, feel free to try it and create a new issue if it doesn't work javadoc link : nonproxyhosts not used - Key: MJAVADOC-252 URL: http://jira.codehaus.org/browse/MJAVADOC-252 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: maven-2.0.10 jdk 1.6_014 Reporter: Maxime Gréau Assignee: Vincent Siveton Priority: Minor Fix For: 2.6.1 Attachments: link_nonproxy_2.0.10.patch, link_nonproxy_2.2.0.patch - Prerequisite : - web access via http proxy - javadoc-plugin configuration with detectLinkstrue/detectLinks - $MVN_HOME/conf/settings.xml with configuration above ( internal-host is host to access the internal javadoc web sites ) proxies proxy activetrue/active protocolhttp/protocol hostmyproxyhost/host portmyproxyport/port nonProxyHostsinternal-host/nonProxyHosts /proxy /proxies Launch the mvn site-deploy command. If you have a dependency with an internal javadoc web site, the plugin tried to link this javadoc with the http proxy and logged: Error fetching link: http://internal-host//apidocs/package-list. Ignored it. This is a bug because this javadoc isn't accessible via http proxy. So I attached 2 patches : - the first one (link_nonproxy_2.0.10.patch) is compatible (and tested) with mvn 2.0.9 and 2.0.10 but included a method directly copied from ProxyUtils.java (wagon-provider-api-1.0-beta-6.jar) - the second (link_nonproxy_2.2.0.patch) used 2 classes from wagon-provider-api-1.0-beta-6.jar dependency so it requires mvn 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] Closed: (MJAVADOC-267) Allow changing the reportOutputDirectory from the commandline
[ http://jira.codehaus.org/browse/MJAVADOC-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-267. Resolution: Fixed Fix Version/s: 2.6.1 Assignee: Vincent Siveton fixed in [r824995|http://svn.apache.org/viewvc?rev=824995view=rev] snapshot deployed Allow changing the reportOutputDirectory from the commandline - Key: MJAVADOC-267 URL: http://jira.codehaus.org/browse/MJAVADOC-267 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.6 Reporter: Dirk Olmes Assignee: Vincent Siveton Fix For: 2.6.1 Attachments: reportOutputDirectory.patch We run the javadoc:aggregate task from the CI server to publish javadocs for a certain release. It's not possible now to specifiy the reportOutputDirectory from the commandline by running mvn -DreportOutputDirectory=/dest/dir javadoc:aggregate Instead, you have to put this config in a profile/property which exposes too much environment specific info in the pom. The attached simple patch allows for specifying the reportOutputDirectory on the cmdline while preserving existing behaviour. -- 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: (MJAVADOC-265) Generate a combined javadoc using all dependency source jars.
[ http://jira.codehaus.org/browse/MJAVADOC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=192375#action_192375 ] Vincent Siveton commented on MJAVADOC-265: -- Using linksource/? Could you detail? Generate a combined javadoc using all dependency source jars. - Key: MJAVADOC-265 URL: http://jira.codehaus.org/browse/MJAVADOC-265 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Reporter: Paul Gier I would like to be able to create a javadoc API that combines not only the sources from my project modules, but also downloads available dependency source files and includes these when generating the javadocs. -- 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: (MJAVADOC-252) javadoc link : nonproxyhosts not used
[ http://jira.codehaus.org/browse/MJAVADOC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-252. Resolution: Fixed Maxime confirmed me the resolution in private javadoc link : nonproxyhosts not used - Key: MJAVADOC-252 URL: http://jira.codehaus.org/browse/MJAVADOC-252 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: maven-2.0.10 jdk 1.6_014 Reporter: Maxime Gréau Assignee: Vincent Siveton Priority: Minor Fix For: 2.6.1 Attachments: link_nonproxy_2.0.10.patch, link_nonproxy_2.2.0.patch - Prerequisite : - web access via http proxy - javadoc-plugin configuration with detectLinkstrue/detectLinks - $MVN_HOME/conf/settings.xml with configuration above ( internal-host is host to access the internal javadoc web sites ) proxies proxy activetrue/active protocolhttp/protocol hostmyproxyhost/host portmyproxyport/port nonProxyHostsinternal-host/nonProxyHosts /proxy /proxies Launch the mvn site-deploy command. If you have a dependency with an internal javadoc web site, the plugin tried to link this javadoc with the http proxy and logged: Error fetching link: http://internal-host//apidocs/package-list. Ignored it. This is a bug because this javadoc isn't accessible via http proxy. So I attached 2 patches : - the first one (link_nonproxy_2.0.10.patch) is compatible (and tested) with mvn 2.0.9 and 2.0.10 but included a method directly copied from ProxyUtils.java (wagon-provider-api-1.0-beta-6.jar) - the second (link_nonproxy_2.2.0.patch) used 2 classes from wagon-provider-api-1.0-beta-6.jar dependency so it requires mvn 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] Commented: (MJAVADOC-253) Http proxy does not work any more
[ http://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191429#action_191429 ] Vincent Siveton commented on MJAVADOC-253: -- I bet that you are using an isaproxy which asks for NTLM authentication. IIRC httpclient supports NTLMv1, not NTLMv2. Since I have no proxy there, could you please try to provide a patch? Http proxy does not work any more - Key: MJAVADOC-253 URL: http://jira.codehaus.org/browse/MJAVADOC-253 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Maven 2.0.9 JDK5 (Sun) Reporter: Mohan K Priority: Critical It appears the update of Wagon Provider in 2.6 is not compatible with Maven 2.0.x. Here is the email snippet as posted to maven users group (no responses) I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the links configured in my plugin config. Now all resolution of external links fail (we are behind a proxy *not* NTLM) with this: Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: ntlm authentication scheme selected Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector authenticate The wagon provider appears to have been upgraded to 1.0-beta-6 in the maven-javadoc-plugin 2.6 (as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is wrong) that wagon 1.0-beta-6 requires Maven 2.1.x and above? If that is the case, I don't understand how the plugin was released with prerequisite of 2.0.9? Is there a workaround to disable the default ntlm auth scheme via a magical system property? TIA -- 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: (MJAVADOC-253) Http proxy does not work any more
[
http://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191430#action_191430
]
Vincent Siveton commented on MJAVADOC-253:
--
Also, a workaround could be to use additionalJOption, ie
{noformat}
configuration
additionalJOption-J-Dhttp.proxySet=true
-J-Dhttp.proxyHost=proxy.somewhere.com -J-Dhttp.proxyPort=3128
-J-Dhttp.nonProxyHosts=java.sun.com|*.somewhere.com \
-J-Dhttp.proxyUser=foo -J-Dhttp.proxyPassword=bar /additionalJOption
...
/configuration
{noformat}
Http proxy does not work any more
-
Key: MJAVADOC-253
URL: http://jira.codehaus.org/browse/MJAVADOC-253
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: Maven 2.0.9
JDK5 (Sun)
Reporter: Mohan K
Priority: Critical
It appears the update of Wagon Provider in 2.6 is not compatible with Maven
2.0.x. Here is the
email snippet as posted to maven users group (no responses)
I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the links
configured in my
plugin config. Now all resolution of external links fail (we are behind a
proxy *not* NTLM)
with this:
Aug 12, 2009 12:02:31 AM
org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
INFO: ntlm authentication scheme selected
Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector
authenticate
The wagon provider appears to have been upgraded to 1.0-beta-6 in the
maven-javadoc-plugin 2.6
(as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is
wrong) that wagon 1.0-beta-6
requires Maven 2.1.x and above? If that is the case, I don't understand how
the plugin was released with
prerequisite of 2.0.9?
Is there a workaround to disable the default ntlm auth scheme via a magical
system property? TIA
--
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: (MJAVADOC-264) mvn clean install site doesn't work
[
http://jira.codehaus.org/browse/MJAVADOC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-264.
Resolution: Duplicate
Maven issue, see MJAVADOC-116
mvn clean install site doesn't work
---
Key: MJAVADOC-264
URL: http://jira.codehaus.org/browse/MJAVADOC-264
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.5, 2.6
Reporter: Arnaud Brunet
Attachments: build.log, myTest.zip
Hi,
I tried to generate a maven site for a projet with multiple modules using
maven-javadoc-plugin in version 2.6. But i got this error :
{quote}
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) mygroup:myartifact:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=mygroup -DartifactId=myartifact
-Dversion=1.0-SNAPSHOT -Dpa
ckaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=mygroup -DartifactId=myartifact
-Dversion=1.0-SNAPSHOT -Dpack
aging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) mygroup:moduleA:jar:1.0-SNAPSHOT
2) mygroup:myartifact:jar:1.0-SNAPSHOT
{quote}
I tried downgrade to 2.5 but I had always the error. With the 2.4 version, it
works.
I attach a test projet. Before each build, you must delete mygroup directory
in your maven repository.
--
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: (MJAVADOC-252) javadoc link : nonproxyhosts not used
[
http://jira.codehaus.org/browse/MJAVADOC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191328#action_191328
]
Vincent Siveton commented on MJAVADOC-252:
--
Fixed in [r816155|http://svn.apache.org/viewvc?rev=816155view=rev], snapshot
deployed. Please review it so I could close it. Thanks!
@Martijn For NTLM, I guess you need to add Joption param, ie
{noformat}
configuration
additionalJOption-J-Dhttp.auth.ntlm.domain=MYDOMAIN/additionalJOption
...
/configuration
{noformat}
javadoc link : nonproxyhosts not used
-
Key: MJAVADOC-252
URL: http://jira.codehaus.org/browse/MJAVADOC-252
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: maven-2.0.10
jdk 1.6_014
Reporter: Maxime Gréau
Priority: Minor
Fix For: 2.6.1
Attachments: link_nonproxy_2.0.10.patch, link_nonproxy_2.2.0.patch
- Prerequisite :
- web access via http proxy
- javadoc-plugin configuration with detectLinkstrue/detectLinks
- $MVN_HOME/conf/settings.xml with configuration above ( internal-host is
host to access the internal javadoc web sites )
proxies
proxy
activetrue/active
protocolhttp/protocol
hostmyproxyhost/host
portmyproxyport/port
nonProxyHostsinternal-host/nonProxyHosts
/proxy
/proxies
Launch the mvn site-deploy command.
If you have a dependency with an internal javadoc web site, the plugin tried
to link this javadoc with the http proxy and logged:
Error fetching link: http://internal-host//apidocs/package-list. Ignored
it.
This is a bug because this javadoc isn't accessible via http proxy.
So I attached 2 patches :
- the first one (link_nonproxy_2.0.10.patch) is compatible (and tested) with
mvn 2.0.9 and 2.0.10 but included a method directly copied from
ProxyUtils.java (wagon-provider-api-1.0-beta-6.jar)
- the second (link_nonproxy_2.2.0.patch) used 2 classes from
wagon-provider-api-1.0-beta-6.jar dependency so it requires mvn 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: (MJAVADOC-252) javadoc link : nonproxyhosts not used
[ http://jira.codehaus.org/browse/MJAVADOC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-252: - Assignee: Vincent Siveton Fix Version/s: 2.6.1 javadoc link : nonproxyhosts not used - Key: MJAVADOC-252 URL: http://jira.codehaus.org/browse/MJAVADOC-252 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: maven-2.0.10 jdk 1.6_014 Reporter: Maxime Gréau Assignee: Vincent Siveton Priority: Minor Fix For: 2.6.1 Attachments: link_nonproxy_2.0.10.patch, link_nonproxy_2.2.0.patch - Prerequisite : - web access via http proxy - javadoc-plugin configuration with detectLinkstrue/detectLinks - $MVN_HOME/conf/settings.xml with configuration above ( internal-host is host to access the internal javadoc web sites ) proxies proxy activetrue/active protocolhttp/protocol hostmyproxyhost/host portmyproxyport/port nonProxyHostsinternal-host/nonProxyHosts /proxy /proxies Launch the mvn site-deploy command. If you have a dependency with an internal javadoc web site, the plugin tried to link this javadoc with the http proxy and logged: Error fetching link: http://internal-host//apidocs/package-list. Ignored it. This is a bug because this javadoc isn't accessible via http proxy. So I attached 2 patches : - the first one (link_nonproxy_2.0.10.patch) is compatible (and tested) with mvn 2.0.9 and 2.0.10 but included a method directly copied from ProxyUtils.java (wagon-provider-api-1.0-beta-6.jar) - the second (link_nonproxy_2.2.0.patch) used 2 classes from wagon-provider-api-1.0-beta-6.jar dependency so it requires mvn 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] Commented: (MJAVADOC-253) Http proxy does not work any more
[
http://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191330#action_191330
]
Vincent Siveton commented on MJAVADOC-253:
--
In 2.6, the implementation uses HttpClient and not wagon.
For NTLM, I guess you need to add Joption param, ie
{noformat}
configuration
additionalJOption-J-Dhttp.auth.ntlm.domain=MYDOMAIN/additionalJOption
...
/configuration
{noformat}
Http proxy does not work any more
-
Key: MJAVADOC-253
URL: http://jira.codehaus.org/browse/MJAVADOC-253
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: Maven 2.0.9
JDK5 (Sun)
Reporter: Mohan K
Priority: Critical
It appears the update of Wagon Provider in 2.6 is not compatible with Maven
2.0.x. Here is the
email snippet as posted to maven users group (no responses)
I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the links
configured in my
plugin config. Now all resolution of external links fail (we are behind a
proxy *not* NTLM)
with this:
Aug 12, 2009 12:02:31 AM
org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
INFO: ntlm authentication scheme selected
Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector
authenticate
The wagon provider appears to have been upgraded to 1.0-beta-6 in the
maven-javadoc-plugin 2.6
(as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is
wrong) that wagon 1.0-beta-6
requires Maven 2.1.x and above? If that is the case, I don't understand how
the plugin was released with
prerequisite of 2.0.9?
Is there a workaround to disable the default ntlm auth scheme via a magical
system property? TIA
--
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: (MJAVADOC-263) No respect for JAVA_HOME or PATH in locating javadoc executable
[
http://jira.codehaus.org/browse/MJAVADOC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=191332#action_191332
]
Vincent Siveton commented on MJAVADOC-263:
--
As described in [1], you could always specify the javadoc tool using the
javadocExecutable param, ie
{noformat}
configuration
javadocExecutableC:\jdk1.6.0\bin\javadoc.exe/javadocExecutable
...
/configuration
{noformat}
For other people's machines, just use env variables, ie:
{noformat}
javadocExecutable${env.JAVA_1.6_HOME}/bin/javadoc/javadocExecutable
{noformat}
Does it help you?
[1]
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/alternate-javadoc-tool.apt.vm
No respect for JAVA_HOME or PATH in locating javadoc executable
---
Key: MJAVADOC-263
URL: http://jira.codehaus.org/browse/MJAVADOC-263
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Benson Margulies
I have code that runs into a java 1.6 bug in javadoc, so I'm trying to be
sure to use the 1.5 version of javadoc.
In my .mavenrc, I set JAVA_HOME to point to 1.5. I set PATH to find a 1.5
version of javadoc. I set my PATH in my shell to find the 1.5 version of
Javadoc. Still, somehow, the maven-javadoc-plugin finds and runs the 1.6.0
version.
Command line
was:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/javadoc
@options @packages
I cannot embed a shared pathname in the POM which won't work on other
people's machines.
--
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: (MJAVADOC-246) ExceptionInInitializerError with maven-site-plugin:2.1-SNAPSHOT and mvn 2.1
[
http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MJAVADOC-246:
-
Description:
This bug only happens if I have maven-javadoc-plugin enabled. If I comment it
out site generation works. The POM is not specifying a particular version so I
am not sure which one it is using.
These bugs seem to report the same problem against other plugins:
http://jira.codehaus.org/browse/MOJO-1118
http://jira.codehaus.org/browse/MOJO-1101
Based on the error message, I checked the repository after successfully
building without JavaDoc and it shows these versions of commons-logging were
used:
1.0
1.0.3
1.0.4
1.1
The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get
around site generation bugs). I am using the -U during building.
{noformat}
# mvn site
...
[INFO] Generating JavaDocs report.
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage
error (java.lang.ExceptionInInitializerError) and may be out-of-date. Check the
realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
urls[0] =
file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
urls[1] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
urls[3] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
urls[4] =
file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
urls[7] =
file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
urls[11] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
urls[12] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
urls[13] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
urls[14] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar
urls[15] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
urls[17] =
file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar
urls[21] =
file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/opt/apache-maven-2.1.0/lib/maven-2.1.0-uber.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Invalid class loader hierarchy. You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.
[INFO]
[INFO] Trace
java.lang.ExceptionInInitializerError
at
org.apache.maven.plugin.javadoc.JavadocUtil.fetchURL(JavadocUtil.java:730)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.isValidJavadocLink(AbstractJavadocMojo.java:4680)
at
[jira] Updated: (MJAVADOC-246) ExceptionInInitializerError with maven-site-plugin:2.1-SNAPSHOT and mvn 2.1
[
http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MJAVADOC-246:
-
Description:
This bug only happens if I have maven-javadoc-plugin enabled. If I comment it
out site generation works. The POM is not specifying a particular version so I
am not sure which one it is using.
These bugs seem to report the same problem against other plugins:
http://jira.codehaus.org/browse/MOJO-1118
http://jira.codehaus.org/browse/MOJO-1101
Based on the error message, I checked the repository after successfully
building without JavaDoc and it shows these versions of commons-logging were
used:
1.0
1.0.3
1.0.4
1.1
The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get
around site generation bugs). I am using the -U during building.
{noformat}
# mvn site
...
[INFO] Generating JavaDocs report.
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage
error (java.lang.ExceptionInInitializerError) and may be out-of-date. Check the
realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
urls[0] =
file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
urls[1] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
urls[3] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
urls[4] =
file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
urls[7] =
file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
urls[11] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
urls[12] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
urls[13] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
urls[14] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar
urls[15] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
urls[17] =
file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar
urls[21] =
file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/opt/apache-maven-2.1.0/lib/maven-2.1.0-uber.jar
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
Invalid class loader hierarchy. You have more than one version of
'org.apache.commons.logging.Log' visible, which is not allowed.
[INFO]
[INFO] Trace
java.lang.ExceptionInInitializerError
at
org.apache.maven.plugin.javadoc.JavadocUtil.fetchURL(JavadocUtil.java:730)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.isValidJavadocLink(AbstractJavadocMojo.java:4680)
at
[jira] Closed: (MJAVADOC-246) ExceptionInInitializerError with maven-site-plugin:2.1-SNAPSHOT and mvn 2.1
[
http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-246.
Assignee: Vincent Siveton
Resolution: Fixed
Fixed in [r814574|http://svn.apache.org/viewvc?rev=814574view=rev], snapshot
deployed
ExceptionInInitializerError with maven-site-plugin:2.1-SNAPSHOT and mvn 2.1
-
Key: MJAVADOC-246
URL: http://jira.codehaus.org/browse/MJAVADOC-246
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: Hudson or command-line
Maven 2.1.0 or 2.2.0
JDK 1.6 or JDK 1.7
maven-site-plugin:2.1-SNAPSHOT
OpenSolaris
Reporter: Malachi de AElfweald
Assignee: Vincent Siveton
Priority: Blocker
Fix For: 2.6.1
This bug only happens if I have maven-javadoc-plugin enabled. If I comment it
out site generation works. The POM is not specifying a particular version so
I am not sure which one it is using.
These bugs seem to report the same problem against other plugins:
http://jira.codehaus.org/browse/MOJO-1118
http://jira.codehaus.org/browse/MOJO-1101
Based on the error message, I checked the repository after successfully
building without JavaDoc and it shows these versions of commons-logging were
used:
1.0
1.0.3
1.0.4
1.1
The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get
around site generation bugs). I am using the -U during building.
{noformat}
# mvn site
...
[INFO] Generating JavaDocs report.
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a
linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date.
Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT]
urls[0] =
file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar
urls[1] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
urls[2] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar
urls[3] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar
urls[4] =
file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] =
file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
urls[7] =
file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar
urls[11] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar
urls[12] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar
urls[13] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar
urls[14] =
file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar
urls[15] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[16] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
urls[17] =
file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[18] =
file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[20] =
file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar
urls[21] =
file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[22] =
file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[23] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar
urls[24] =
file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar
urls[25] =
[jira] Closed: (MJAVADOC-245) Aggregate does not work
[ http://jira.codehaus.org/browse/MJAVADOC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-245. Resolution: Not A Bug Seems to work for you so I close it. You could always create a new issue. Aggregate does not work --- Key: MJAVADOC-245 URL: http://jira.codehaus.org/browse/MJAVADOC-245 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.5, 2.6 Reporter: Jörg Hohwiller Attachments: MJAVADOC-245.zip I want to have an aggregated javadoc for the entire project as well as per module. Therefore I followed instructions at: http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html When I do mvn site:stage I get no aggregated javadoc but just per module. This does not even change if I only do reportSets reportSet reports reportaggregate/report /reports /reportSet /reportSets So to me this looks as if reportSets is magically ignored here. I have tested 2.5 as well as 2.6 from https://repository.apache.org/content/repositories/maven-staging-027/org/apache/maven/plugins/maven-javadoc-plugin/2.6/ -- 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: (MJAVADOC-134) Support aggregated reports at each level in the multi-module hierarchy
[ http://jira.codehaus.org/browse/MJAVADOC-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=190853#action_190853 ] Vincent Siveton commented on MJAVADOC-134: -- Martin, FYI MJAVADOC-257 should fix your problem Support aggregated reports at each level in the multi-module hierarchy -- Key: MJAVADOC-134 URL: http://jira.codehaus.org/browse/MJAVADOC-134 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: John Allen The current system makes the assumption that if one wants aggregated reports one does not want further javadoc reports (aggregated ones) down the hierarchy. We do require this functionality and in fact do the same for all our reports (PMD, Checkstyle, Clover, JXR, Surefire, etc): A-B-C-D1 (JAR) A-B-C-D2 (JAR) A-B-E(JAR) A-F (JAR) A - javadoc for D1,D2,E,F B - javadoc for D1,D2,E C - javadoc for D1,D2 D1 - javadoc for D1 D2 - javadoc for D2 E - javadoc for E F - javadoc for F This way there is the required info at the appropriate level throughout the hierarchy. And nope we dont care about space or generation times:) -- 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: (MJAVADOC-258) Grouping example could show multiple packages per group
[ http://jira.codehaus.org/browse/MJAVADOC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-258. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6.1 added more samples for groups and other options in [r|http://svn.apache.org/viewvc?rev=814309view=rev] Grouping example could show multiple packages per group --- Key: MJAVADOC-258 URL: http://jira.codehaus.org/browse/MJAVADOC-258 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.6 Reporter: Paul Benedict Assignee: Vincent Siveton Priority: Trivial Fix For: 2.6.1 One thing that I learned the hard way was grouping multiple packages together. The example (http://maven.apache.org/plugins/maven-javadoc-plugin/examples/group-configuration.html) only shows one package per group, but this could be enhanced. Could you please show the asterisk notation (subpackages) and the separator (colon or semicolon)? By the way, I erroneously tried to use multiple packages -- which seemed a natural expectation -- but it didn't work and was silently ignored. A note to this effect may be useful. -- 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-262) Parameters like sourcepath depend on system path separator (colon/semicolon)
Parameters like sourcepath depend on system path separator (colon/semicolon)
Key: MJAVADOC-262
URL: http://jira.codehaus.org/browse/MJAVADOC-262
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Vincent Siveton
Using the following conf on Windows box doesnt generate javadoc
{noformat}
sourcepath${basedir}/src/main/java:${basedir}/src/main/javadoc/sourcepath
{noformat}
It is due to the colon separator (solaris) instead of the semi-colon (windows)
Other path options (docletPath, extdirs, sourcepath, tagletpath, bootclasspath)
are also plateform dependant.
--
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: (MJAVADOC-262) Parameters like sourcepath depend on system path separator (colon/semicolon)
[
http://jira.codehaus.org/browse/MJAVADOC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-262.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.6.1
fixed in [r814171|http://svn.apache.org/viewvc?rev=814171view=rev], snap
deployed
Parameters like sourcepath depend on system path separator (colon/semicolon)
Key: MJAVADOC-262
URL: http://jira.codehaus.org/browse/MJAVADOC-262
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Vincent Siveton
Assignee: Vincent Siveton
Fix For: 2.6.1
Using the following conf on Windows box doesnt generate javadoc
{noformat}
sourcepath${basedir}/src/main/java:${basedir}/src/main/javadoc/sourcepath
{noformat}
It is due to the colon separator (solaris) instead of the semi-colon (windows)
Other path options (docletPath, extdirs, sourcepath, tagletpath,
bootclasspath) are also plateform dependant.
--
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: (MJAVADOC-260) Javadoc report not generated for multi-module project if run from parent level - error resolving dependencies
[ http://jira.codehaus.org/browse/MJAVADOC-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-260. Resolution: Duplicate It is a Maven issue and not a Javadoc plugin issue, see MNG-3685 Javadoc report not generated for multi-module project if run from parent level - error resolving dependencies - Key: MJAVADOC-260 URL: http://jira.codehaus.org/browse/MJAVADOC-260 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Windows XP, JDK 1.6.0_12 Reporter: Tom Forwood Attachments: tstmvn.zip Similar perhaps to bug http://jira.codehaus.org/browse/MJAVADOC-181 reported as fixed in version 2.6 Javadoc plugin fails to correctly compute dependencies between modules attached project structure will generate error when mvn site:site is run ... [INFO] Building subproject2 [INFO] [INFO] No goals needed for project - skipping [INFO] Preparing javadoc:javadoc [INFO] No goals needed for project - skipping [INFO] Preparing javadoc:test-aggregate [INFO] [INFO] Building tstmvn [INFO] [INFO] No goals needed for project - skipping [INFO] [INFO] Building subproject1 [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [INFO] Building subproject2 [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] snapshot tst.tstmvn:subproject1:0.0-SNAPSHOT: checking for updates from digital-sales-maven2 Downloading: http://digital-sales-tech/maven2/tst/tstmvn/subproject1/0.0-SNAPSHOT/subproject1-0.0-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) tst.tstmvn:subproject1:jar:0.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=tst.tstmvn -DartifactId=subproject1 -Dversion=0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=tst.tstmvn -DartifactId=subproject1 -Dversion=0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) tst.tstmvn:subproject2:jar:0.0-SNAPSHOT 2) tst.tstmvn:subproject1:jar:0.0-SNAPSHOT -- 1 required artifact is missing. for artifact: tst.tstmvn:subproject2:jar:0.0-SNAPSHOT from the specified remote repositories: digital-sales-maven2 (http://digital-sales-tech/maven2), central (http://repo1.maven.org/maven2) -- 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: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
[
http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-257.
Resolution: Fixed
maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
--
Key: MJAVADOC-257
URL: http://jira.codehaus.org/browse/MJAVADOC-257
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.5, 2.6
Environment: Apache Maven 2.2.0
Java version: 1.6.0_11
Reporter: jcrouvi
Assignee: Vincent Siveton
Fix For: 2.6.1
Attachments: MJAVADOC-257.diff
Using maven-javadoc-plugin Version 2.5 or 2.6 for a project of type
*packagingmaven-plugin/packaging* leads to the following error message,
even if the aggregation is not set:
{{Error extracting plugin descriptor: 'Goal: ... already exists in the plugin
descriptor ...}}
*Using maven-javadoc-plugin Version 2.2 solves this problem.*
Structure of the project:
{code:none}
[INFO] Reactor build order:
[INFO] Service
[INFO] Service: Common Dependencies
[INFO] Service: API
[INFO] Service: Test Fixture
[INFO] Service: Implementation
[INFO] Service: DI
[INFO] Service: auth-maven-plugin
[INFO] Service: Config
[INFO] Service: Interceptors
[INFO] Service: Client Module
[INFO] Service: Web Components
[INFO] Service: Example
{code}
Configuration in {{service/pom.xml}}
{code:xml}
profile
idfull-site/id
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
reportSets
reportSet
reports
reportanalyze-report/report
/reports
/reportSet
/reportSets
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
quiettrue/quiet
showprotected/show
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
/configuration
/plugin
...
{code}
Also see: [http://jira.codehaus.org/browse/MJAVADOC-224]
--
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: (MJAVADOC-259) Resource copying from javadoc dir is incomplete
[ http://jira.codehaus.org/browse/MJAVADOC-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-259. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6.1 fixed in [r813404|http://svn.apache.org/viewvc?rev=813404view=rev], snapshot deployed Resource copying from javadoc dir is incomplete --- Key: MJAVADOC-259 URL: http://jira.codehaus.org/browse/MJAVADOC-259 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Mac OS X 10.5.7 Reporter: Ken Arnold Assignee: Vincent Siveton Fix For: 2.6.1 Attachments: jd.zip The plugin is ignoring my directory src/main/javadoc/resources I want to put in background images for my stylesheet to use, and I want to overwite inherit.gif (to one with a transparent background, a Java problem since I started with Java back before 1.0, sigh). So I put a bg.gif and a new inherit.gif in src/main/javadoc/resources. It is not copied. I do have docfilessubdirs set to true. I have attached a subset of my project that demonstrates the problem. Unzip and then run mvn javadoc:javadoc. If you look at target/site/apidocs/resources, the file contains only one file, while src/main/javadoc/resources contains three. -- 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: (MJAVADOC-255) Cannot suppress reports
[
http://jira.codehaus.org/browse/MJAVADOC-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-255.
Resolution: Not A Bug
To exclude all reports you need to use:
{noformat}
reportSets
reportSet
reports/
/reportSet
/reportSets
{noformat}
Cannot suppress reports
---
Key: MJAVADOC-255
URL: http://jira.codehaus.org/browse/MJAVADOC-255
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Benson Margulies
I wanted to suppress javadoc aggregation for mvn site:site.
So, I tried
reportSets/reportSets
No effect. it goes ahead and runs the aggregate report. help:effectivePom
does not show the empty reportSets element.
--
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: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
[
http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-257.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.6.1
I created an IT and fixed the pb as discuss here in
[r811825|http://svn.apache.org/viewvc?rev=811825view=rev], snap deployed.
maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
--
Key: MJAVADOC-257
URL: http://jira.codehaus.org/browse/MJAVADOC-257
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.5, 2.6
Environment: Apache Maven 2.2.0
Java version: 1.6.0_11
Reporter: jcrouvi
Assignee: Vincent Siveton
Fix For: 2.6.1
Attachments: MJAVADOC-257.diff
Using maven-javadoc-plugin Version 2.5 or 2.6 for a project of type
*packagingmaven-plugin/packaging* leads to the following error message,
even if the aggregation is not set:
{{Error extracting plugin descriptor: 'Goal: ... already exists in the plugin
descriptor ...}}
*Using maven-javadoc-plugin Version 2.2 solves this problem.*
Structure of the project:
{code:none}
[INFO] Reactor build order:
[INFO] Service
[INFO] Service: Common Dependencies
[INFO] Service: API
[INFO] Service: Test Fixture
[INFO] Service: Implementation
[INFO] Service: DI
[INFO] Service: auth-maven-plugin
[INFO] Service: Config
[INFO] Service: Interceptors
[INFO] Service: Client Module
[INFO] Service: Web Components
[INFO] Service: Example
{code}
Configuration in {{service/pom.xml}}
{code:xml}
profile
idfull-site/id
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
reportSets
reportSet
reports
reportanalyze-report/report
/reports
/reportSet
/reportSets
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
quiettrue/quiet
showprotected/show
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
/configuration
/plugin
...
{code}
Also see: [http://jira.codehaus.org/browse/MJAVADOC-224]
--
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: (MPDF-31) LinkageError using JDK6
[
http://jira.codehaus.org/browse/MPDF-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPDF-31.
---
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 1.1
Fixed in [r811614|http://svn.apache.org/viewvc?rev=811614view=rev], snap
deployed
LinkageError using JDK6
---
Key: MPDF-31
URL: http://jira.codehaus.org/browse/MPDF-31
Project: Maven 2.x PDF Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: mvn 2.1 or later, jdk 6
Reporter: Vincent Siveton
Assignee: Vincent Siveton
Fix For: 1.1
Attachments: myapp.zip
{noformat}
#mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_15
Java home: jdk1.6.0_15\jre
Default locale: fr_CA, platform encoding: Cp1252
OS name: windows xp version: 5.2 arch: x86 Family: windows
{noformat}
{noformat}
#mvn site
...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] loader constraint violation in interface itable initialization: when
resolving method o
rg.apache.maven.doxia.sink.AbstractSink.enableLogging(Lorg/apache/maven/doxia/logging/Log;)V
t
he class loader (instance of org/codehaus/classworlds/RealmClassLoader) of
the current class, o
rg/apache/maven/plugins/pdf/PdfMojo$PdfSink, and the class loader (instance
of org/codehaus/cla
ssworlds/RealmClassLoader) for interface
org/apache/maven/doxia/logging/LogEnabled have differe
nt Class objects for the type org/apache/maven/doxia/logging/Log used in the
signature
[INFO]
...
{noformat}
BUT using JDK 1.5 no error when running mvn site:
{noformat}
#mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.5.0_18
Java home: dk1.5.0_18\jre
Default locale: fr_CA, platform encoding: Cp1252
OS name: windows xp version: 5.2 arch: x86 Family: windows
{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] Commented: (DOXIASITETOOLS-33) Add an option to include or not the TOC
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189952#action_189952 ] Vincent Siveton commented on DOXIASITETOOLS-33: --- applied suggestion in [r811653|http://svn.apache.org/viewvc?rev=811653view=rev] Add an option to include or not the TOC --- Key: DOXIASITETOOLS-33 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-33 Project: Maven Doxia Sitetools Issue Type: Improvement Affects Versions: 1.1.1 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1.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] Commented: (MPDF-30) Add a parameter to include or not the TOC
[ http://jira.codehaus.org/browse/MPDF-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189954#action_189954 ] Vincent Siveton commented on MPDF-30: - applied in [r811654|http://svn.apache.org/viewvc?rev=811654view=rev], snap deployed Add a parameter to include or not the TOC - Key: MPDF-30 URL: http://jira.codehaus.org/browse/MPDF-30 Project: Maven 2.x PDF Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: Vincent Siveton Assignee: Vincent Siveton Fix For: 1.1 See DOXIASITETOOLS-33 -- 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
