[jira] Commented: (MDEP-145) Outputting dependency resolution/tree in a well known _machine readable_ output format
[
http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165754#action_165754
]
Pi Song commented on MDEP-145:
--
I branched from the latest trunk and applied the patch.
http://svn.apache.org/repos/asf/maven/sandbox/branches/MDEP-145/
> Outputting dependency resolution/tree in a well known _machine readable_
> output format
> --
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
>Affects Versions: 2.0
>Reporter: Samuel Le Berrigaud
>Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file.
> However the file output doesn't follow any specific format, except from being
> the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could
> leverage the dependency resolution/tree. I am thinking for example of
> continuous integration tools that could report on added/removed/updated
> dependencies on modules.
> The format could be xml, json or something else. I've been playing with the
> current output to make it so that:
> * the first line describes the current module for which dependency resolution
> is done, formatted as such: {{:::}}
> * every following line is a dependency (indented by 2 or more spaces),
> formatted as such: {{}}
> This already is easy to parse.
> What do you think?
--
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: (MIDEA-118) Generate JAVA_MODULE instead of J2EE_*_MODULE
Generate JAVA_MODULE instead of J2EE_*_MODULE - Key: MIDEA-118 URL: http://jira.codehaus.org/browse/MIDEA-118 Project: Maven 2.x IDEA Plugin Issue Type: Task Affects Versions: 2.2 Reporter: Michal Ropka IDEA 8 does not recognize any more modules with type J2EE_*_MODULE (e.g. J2EE_WEB_MODULE) - gives error message when opening such a project and cannot auto detect appropriate facets. The module "type" should be simple JAVA_MODULE now. -- 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: (MAVENUPLOAD-2359) bndlib 0.0.311
bndlib 0.0.311 -- Key: MAVENUPLOAD-2359 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2359 Project: Maven Upload Requests Issue Type: Task Reporter: Stuart McCulloch Stable version of the Bnd Tool library, contains fixes for various inconsistencies when calculating versions. -- 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-226) Add a new goal to fix Javadoc tags
Add a new goal to fix Javadoc tags -- Key: MJAVADOC-226 URL: http://jira.codehaus.org/browse/MJAVADOC-226 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Vincent Siveton This new goal will fix Javadoc tags for the Java source ie adding missing tags for class and methods and update existing tags. It will be available only in interactive mode. -- 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-226) Add a new goal to fix Javadoc tags
[ http://jira.codehaus.org/browse/MJAVADOC-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165768#action_165768 ] Vincent Siveton commented on MJAVADOC-226: -- Also, it could use Clirr to dynamically add the correct version of @since > Add a new goal to fix Javadoc tags > -- > > Key: MJAVADOC-226 > URL: http://jira.codehaus.org/browse/MJAVADOC-226 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Vincent Siveton > > This new goal will fix Javadoc tags for the Java source ie adding missing > tags for class and methods and update existing tags. > It will be available only in interactive mode. -- 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-383) Problem using "super pom" as parent in multi module project
[ http://jira.codehaus.org/browse/MSITE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165772#action_165772 ] Per Lindfors commented on MSITE-383: Yes. > Problem using "super pom" as parent in multi module project > --- > > Key: MSITE-383 > URL: http://jira.codehaus.org/browse/MSITE-383 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-7 > Environment: Windows XP SP_2 > JDK 1.5 > Maven 2.0.9 >Reporter: Per Lindfors > Attachments: MyProj.zip, super-poms.zip > > > I'm trying to generate a site for my multimodule project with mvn site-deploy > and with the following layout: > MyProj >| >- myproj-bl >| >- myproj-pl >| >- myproj-ear > In the case where each module refere to MyProj as , everything works > fine, the module-links are listed in the index page for MyProj. But when I > use the desired layout, where each module refere to a "super pom" as > , the resulting site structure is different and the links to the > modules are missing. > To me this is a bug when I dont find information saying that a module can > have parent not beeing the "multimodule project" > To reproduce, use attched projects. > 1. Unpack and build super-poms to your local repo. > 2. Unpack and build myproj with mvn install site-deploy. The site will be > deployed at c:/arkiv/proj/maven-site se root/pom.xml in super poms -- 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: (JXR-69) fails to create cross links in multi-module project
fails to create cross links in multi-module project --- Key: JXR-69 URL: http://jira.codehaus.org/browse/JXR-69 Project: Maven JXR Issue Type: Bug Components: maven2 jxr plugin Affects Versions: 2.1 Reporter: Giovanni Azua My build pulls jxr 2.1. Although I set the aggregate parameter to true, I still don't get linked cross module references say e.g. Module A Interface X Module B (depends on A) Class Y implements X In the aggregate reports Class Y will not link to X. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIASITETOOLS-16) NullPointerException
NullPointerException Key: DOXIASITETOOLS-16 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-16 Project: Maven Doxia Sitetools Issue Type: Bug Environment: Maven version: 2.0.9 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" Reporter: Valerio Schiavoni I get this stacktrace: [INFO] [INFO] [site:site] [INFO] [INFO] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] [INFO] [INFO] null [INFO] [INFO] [INFO] [INFO] Trace [INFO] java.lang.NullPointerException [INFO] at org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192) [INFO] at org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) [INFO] at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:253) [INFO] at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:527) [INFO] at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:466) [INFO] at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) [INFO] at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [INFO] at java.lang.reflect.Method.invoke(Method.java:585) [INFO] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [INFO] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [INFO] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [INFO] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) I'm using the latest released maven site 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] Commented: (DOXIASITETOOLS-16) NullPointerException
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165782#action_165782 ] Valerio Schiavoni commented on DOXIASITETOOLS-16: - The stacktrace is a result of the command: mvn release:perform -e -DconnectionUrl=scm:svn:svn+ssh://svn.forge.objectweb.org/svnroot/fractal/tags/FRACTAL_BF_0_5 The pom files causing the stacktrace are freely accessible by browsing the SVN: http://svn.forge.objectweb.org/cgi-bin/viewcvs.cgi/fractal/tags/FRACTAL_BF_0_5/ and the module that it causing the failire is: http://svn.forge.objectweb.org/cgi-bin/viewcvs.cgi/fractal/tags/FRACTAL_BF_0_5/core/pom.xml?rev=9145&view=markup > NullPointerException > > > Key: DOXIASITETOOLS-16 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-16 > Project: Maven Doxia Sitetools > Issue Type: Bug > Environment: Maven version: 2.0.9 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Valerio Schiavoni > > I get this stacktrace: > [INFO] [INFO] [site:site] > [INFO] [INFO] > > [INFO] [ERROR] FATAL ERROR > [INFO] [INFO] > > [INFO] [INFO] null > [INFO] [INFO] > > [INFO] [INFO] Trace > [INFO] java.lang.NullPointerException > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:253) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:527) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:466) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > [INFO]at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > [INFO]at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > [INFO]at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > [INFO]at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > [INFO]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [INFO]at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [INFO]at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [INFO]at java.lang.reflect.Method.invoke(Method.java:585) > [INFO]at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [INFO]at org.codehaus.classworlds.Launcher.launch(Launcher.
[jira] Commented: (DOXIASITETOOLS-16) NullPointerException
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165786#action_165786 ] Valerio Schiavoni commented on DOXIASITETOOLS-16: - Reading a run with -X option, more informations are discovered: Configuring mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site' [INFO] [DEBUG] (f) siteDirectory = /Users/veleno/workspace/fractal-bf-parent/target/checkout/core/src/site [INFO] [DEBUG] (f) templateDirectory = /Users/veleno/workspace/fractal-bf-parent/target/checkout/core/src/site [INFO] [DEBUG] (f) xdocDirectory = /Users/veleno/workspace/fractal-bf-parent/target/checkout/core/xdocs [INFO] [DEBUG] -- end configuration -- [INFO] [INFO] [site:site] [INFO] [DEBUG] Mapped url: /Users/veleno/workspace/fractal-bf-parent/target/checkout/core/src/site to relative path: src/site [INFO] [DEBUG] Reading site descriptor from src/site/site.xml [INFO] [DEBUG] Parent project loaded ... [INFO] [DEBUG] Mapped url: /Users/veleno/workspace/fractal-bf-parent/target/checkout/core/src/site to relative path: core/src/site [INFO] [DEBUG] Reading site descriptor from core/src/site/site.xml [INFO] [INFO] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] [INFO] [INFO] null hopefully this helps debugging the problem somehow.. > NullPointerException > > > Key: DOXIASITETOOLS-16 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-16 > Project: Maven Doxia Sitetools > Issue Type: Bug > Environment: Maven version: 2.0.9 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Valerio Schiavoni > > I get this stacktrace: > [INFO] [INFO] [site:site] > [INFO] [INFO] > > [INFO] [ERROR] FATAL ERROR > [INFO] [INFO] > > [INFO] [INFO] null > [INFO] [INFO] > > [INFO] [INFO] Trace > [INFO] java.lang.NullPointerException > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:253) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:527) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:466) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > [INFO]at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor
[jira] Commented: (DOXIASITETOOLS-16) NullPointerException
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165789#action_165789 ] Valerio Schiavoni commented on DOXIASITETOOLS-16: - For what it matters, it's using: maven-release-plugin 2.0-beta-8 > NullPointerException > > > Key: DOXIASITETOOLS-16 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-16 > Project: Maven Doxia Sitetools > Issue Type: Bug > Environment: Maven version: 2.0.9 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Valerio Schiavoni > > I get this stacktrace: > [INFO] [INFO] [site:site] > [INFO] [INFO] > > [INFO] [ERROR] FATAL ERROR > [INFO] [INFO] > > [INFO] [INFO] null > [INFO] [INFO] > > [INFO] [INFO] Trace > [INFO] java.lang.NullPointerException > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192) > [INFO]at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:253) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:527) > [INFO]at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:466) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) > [INFO]at > org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > [INFO]at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > [INFO]at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > [INFO]at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > [INFO]at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > [INFO]at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > [INFO]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [INFO]at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [INFO]at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [INFO]at java.lang.reflect.Method.invoke(Method.java:585) > [INFO]at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > [INFO]at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > [INFO]at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > [INFO]at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > I'm using the latest released maven site 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 mo
[jira] Commented: (MDEP-145) Outputting dependency resolution/tree in a well known _machine readable_ output format
[
http://jira.codehaus.org/browse/MDEP-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165791#action_165791
]
Brian Fox commented on MDEP-145:
branch merged and snapshot deployed (to new snapshot repo:
http://repository.apache.org/snapshots/)
The ticket needs to stay open until the site docs are updated.
> Outputting dependency resolution/tree in a well known _machine readable_
> output format
> --
>
> Key: MDEP-145
> URL: http://jira.codehaus.org/browse/MDEP-145
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: resolve, tree
>Affects Versions: 2.0
>Reporter: Samuel Le Berrigaud
>Assignee: Brian Fox
> Fix For: 2.2
>
> Attachments: MDEP-145.zip, treegraph.patch
>
>
> Currently (at least on trunk) one can output the dependencies in a file.
> However the file output doesn't follow any specific format, except from being
> the exact same output than on the console.
> I would be nice to have an easily parse-able, format so that tools could
> leverage the dependency resolution/tree. I am thinking for example of
> continuous integration tools that could report on added/removed/updated
> dependencies on modules.
> The format could be xml, json or something else. I've been playing with the
> current output to make it so that:
> * the first line describes the current module for which dependency resolution
> is done, formatted as such: {{:::}}
> * every following line is a dependency (indented by 2 or more spaces),
> formatted as such: {{}}
> This already is easy to parse.
> What do you think?
--
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: (MECLIPSE-526) MyEclipse : Bad generation of .metadata file for an EAR project
MyEclipse : Bad generation of .metadata file for an EAR project
---
Key: MECLIPSE-526
URL: http://jira.codehaus.org/browse/MECLIPSE-526
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: MyEclipse support
Affects Versions: 2.5.1
Environment: WinXP, Sun JVM 1.5.0_14, Eclipse 3.3.x, MyEclipse 6.0.x
Reporter: Guillaume Darmont
Attachments: MyEclipseMetadataWriter.java
The file .metadata of an EAR project does not contains reference to WAR and/or
EJB modules.
I attached a patched "MyEclipseMetadataWriter.java" file that takes care of the
maven-ear-plugin part of an EAR pom.xml to generate a working .metadata file.
The following pom.xml
{code:xml}
...
ear
[${packaging}] ${artifactId}
maven-ear-plugin
MyApp
${groupId}
my-webapp2
/mywebapp
${groupId}
my-webapp2
/mywebapp
...
{code}
now generates
{code:xml}
{code}
Hope this help.
--
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: (MAVENUPLOAD-2360) Request to upload the new Orbroker project version
Request to upload the new Orbroker project version -- Key: MAVENUPLOAD-2360 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2360 Project: Maven Upload Requests Issue Type: Improvement Reporter: Gilberto Caetano de Andrade Attachments: orbroker-2.0.4-bundle.jar http://orbroker.sourceforge.net/downloads/orbroker-2.0.4-bundle.jar http://orbroker.sourceforge.net/ http://orbroker.sourceforge.net/team-list.html O/R Broker is a framework for applications that use JDBC. It allows you to externalize dynamic SQL statements in individual files, improving readability, and it allows declarative mapping from queries to arbitrary domain objects, not just JavaBeans. Please upload! -- 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: (MINVOKER-77) Add a invoker report mojo which display invoker its result
[ http://jira.codehaus.org/browse/MINVOKER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165827#action_165827 ] Olivier Lamy commented on MINVOKER-77: -- no problem we have just to document this :-). Don't close the issue I have too add french bundle. > Add a invoker report mojo which display invoker its result > --- > > Key: MINVOKER-77 > URL: http://jira.codehaus.org/browse/MINVOKER-77 > Project: Maven 2.x Invoker Plugin > Issue Type: New Feature >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.4 > > > The result will displayed by parsing the result generated with new feature > from MINVOKER-76 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-288) Support for DITA input format
Support for DITA input format - Key: DOXIA-288 URL: http://jira.codehaus.org/browse/DOXIA-288 Project: Maven Doxia Issue Type: Wish Components: Modules Affects Versions: 1.0 Reporter: Markus KARG The DITA input format gets quite popular these days and is often told to be the successor of DocBook, so I'd be happy to see DITA support for DOXIA. :-) DITA is an OASIS standard (http://docs.oasis-open.org/dita/v1.1/OS/overview/overview.html) and has support from IBM and other stakeholders. -- 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: (SUREFIRE-536) Plugin cannot handle "java" in a path name
[ http://jira.codehaus.org/browse/SUREFIRE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165858#action_165858 ] SebbASF commented on SUREFIRE-536: -- This appears to be due to the following code in AbstractDirectoryTestSuite.processIncludesExcludes(List list): incs[i] = StringUtils.replace( (String) list.get( i ), "java", "class" ); Changing this to incs[i] = StringUtils.replace( (String) list.get( i ), ".java", ".class" ); would be better than nothing, however that would still fail on a directory name that contains ".java" (perhaps not very likely). What is really needed is to only replace the ".java" if it appears at the end of the string. > Plugin cannot handle "java" in a path name > -- > > Key: SUREFIRE-536 > URL: http://jira.codehaus.org/browse/SUREFIRE-536 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.4.3 >Reporter: SebbASF > > Commons SCXML has the following include: > org/apache/commons/scxml/env/javascript/EnvJavaScriptTestSuite.java > However, the suite was not being found and executed. > A bit of experimentation shows that the problem is the string "java" in the > pathname. > A work-round is to use: > org/apache/commons/scxml/env/j*avascript/EnvJavaScriptTestSuite.java > or > org/apache/commons/scxml/env/jav*ascript/EnvJavaScriptTestSuite.java > or > org/apache/commons/scxml/env/*/EnvJavaScriptTestSuite.java > etc. -- 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: (MASSEMBLY-391) Sharing a default assembly descriptor across sub modules does not work if invoked from parent project
Sharing a default assembly descriptor across sub modules does not work if invoked from parent project - Key: MASSEMBLY-391 URL: http://jira.codehaus.org/browse/MASSEMBLY-391 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Affects Versions: 2.0.1 Reporter: Stephen Evanchik Assignee: John Casey Fix For: 2.2-beta-2 I have a multi-project folders setup like one shown below, root |_ sub-folder1 |_ sub-folder2 |_ sub-folder3 |_ etc Have a root pom.xml at the root folder level and in that I have defined maven-assembly-plugin src/main/assembly/descriptor.xml Above descriptor works fine only if I have defined a descriptor file on the src/main/assembly folder for each sub-folder1, sub-folder2, etc. It would be great if maven supports me in defining a common assembly descriptor and can be shared by all the sub modules from a common location. -- 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: (MASSEMBLY-391) Sharing a default assembly descriptor across sub modules does not work if invoked from parent project
[ http://jira.codehaus.org/browse/MASSEMBLY-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Evanchik updated MASSEMBLY-391: --- Attachment: test.error File showing the error > Sharing a default assembly descriptor across sub modules does not work if > invoked from parent project > - > > Key: MASSEMBLY-391 > URL: http://jira.codehaus.org/browse/MASSEMBLY-391 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Stephen Evanchik >Assignee: John Casey > Fix For: 2.2-beta-2 > > Attachments: test.error > > > I have a multi-project folders setup like one shown below, > > root > |_ sub-folder1 > |_ sub-folder2 > |_ sub-folder3 > |_ etc > > Have a root pom.xml at the root folder level and in that I have defined > > maven-assembly-plugin > > > src/main/assembly/descriptor.xml > > > > > > Above descriptor works fine only if I have defined a descriptor file on the > src/main/assembly folder for each sub-folder1, sub-folder2, etc. > It would be great if maven supports me in defining a common assembly > descriptor and can be shared by all the sub modules from a common location. -- 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: (MASSEMBLY-391) Sharing a default assembly descriptor across sub modules does not work if invoked from parent project
[ http://jira.codehaus.org/browse/MASSEMBLY-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165872#action_165872 ] Stephen Evanchik commented on MASSEMBLY-391: Summary: maven-assembly-plugin dependencies are only resolved in superpom's pluginManagement section OR in the declaring POM. Details: My issue is that I started with a project structure of: root -> sub-project -> sub-module I have created a shared-project-assembly and installed it in the repository. I configure the assembly plugin like so: maven-assembly-plugin 2.2-beta-2 my-group shared-project-assembly 0.0.1 . just like in the FAQ . If I place that assembly configuration in a leaf project such as: root -> sub-project -> sub-module-distribution It only works if I invoke mvn package from sub-module-distribution. If I invoke it from sub-project I receive the attached error. However, if I place the plugin configuration in my superpom's pluginManagement section it works just fine. If I make a mistake in the dependency section of the assembly configuration, such as: NOT_THE_RIGHT_GROUP shared-project-assembly 0.0.1 and execute mvn package from sub-project nothing happens, there is no error indicating that Maven is unable to resolve artifact. If I move in to sub-module-distribution and execute mvn package I receive the error indicating that the artifact cannot be resolved. > Sharing a default assembly descriptor across sub modules does not work if > invoked from parent project > - > > Key: MASSEMBLY-391 > URL: http://jira.codehaus.org/browse/MASSEMBLY-391 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Stephen Evanchik >Assignee: John Casey > Fix For: 2.2-beta-2 > > Attachments: test.error > > > I have a multi-project folders setup like one shown below, > > root > |_ sub-folder1 > |_ sub-folder2 > |_ sub-folder3 > |_ etc > > Have a root pom.xml at the root folder level and in that I have defined > > maven-assembly-plugin > > > src/main/assembly/descriptor.xml > > > > > > Above descriptor works fine only if I have defined a descriptor file on the > src/main/assembly folder for each sub-folder1, sub-folder2, etc. > It would be great if maven supports me in defining a common assembly > descriptor and can be shared by all the sub modules from a common location. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-385) Create anchor automatically from headings
Create anchor automatically from headings
-
Key: MSITE-385
URL: http://jira.codehaus.org/browse/MSITE-385
Project: Maven 2.x Site Plugin
Issue Type: New Feature
Reporter: Barrie Treloar
When writing the apt pages you often want to cross reference pages and link to
headings.
Instead of manually placing the headings in an anchor block {} the site
generation should do this automatically.
It would also be nice to validate that the cross reference is valid as spaces
will get replaced with underscores and typos are easy to make.
--
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
