[jira] Commented: (MSITE-134) add breadcrumb
[ http://jira.codehaus.org/browse/MSITE-134?page=comments#action_73390 ] Dmitry Ulanov commented on MSITE-134: - I use the next snippet: > add breadcrumb > -- > > Key: MSITE-134 > URL: http://jira.codehaus.org/browse/MSITE-134 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Reporter: Jörg Hohwiller > > When you have a complex project with multiple sub-projects that may > themselves have sub-projects, the visitor of the site might get lost. > It would therefore be awesome if one could active a breadcrumb that is > automatically generated to the sites. > Some line like this: > You are here TOPLEVEL > SUBPROJ1 > > SUBSUB5 -- 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: (MAVENUPLOAD-1023) mstor 0.9.9 - Maven bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1023?page=comments#action_73389 ] Carlos Sanchez commented on MAVENUPLOAD-1023: - You have to fix this for next time junit junit 3.8.1 test > mstor 0.9.9 - Maven bundle > -- > > Key: MAVENUPLOAD-1023 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1023 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ben Fortuna > Assigned To: Carlos Sanchez > > http://mstor.sourceforge.net/maven/mstor-0.9.9-bundle.jar > http://mstor.sourceforge.net/ > http://sourceforge.net/users/fortuna > mstor is a JavaMail local store provider based on the mbox email storage > format. -- 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-1095) Cojen 2.0.0 bundle upload
Cojen 2.0.0 bundle upload - Key: MAVENUPLOAD-1095 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1095 Project: maven-upload-requests Issue Type: Task Reporter: Brian S O'Neill Cojen is a Java library which makes it easy to dynamically generate and inject Java bytecode. I am listed as lead developer "broneill" on the team-list page. http://cojen.sourceforge.net/team-list.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] Closed: (MRM-151) re-introduce index of developers and dependencies
[ http://jira.codehaus.org/browse/MRM-151?page=all ] Brett Porter closed MRM-151. Assignee: Brett Porter Resolution: Fixed > re-introduce index of developers and dependencies > - > > Key: MRM-151 > URL: http://jira.codehaus.org/browse/MRM-151 > Project: Archiva > Issue Type: Improvement > Components: indexing >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > it will be useful to identify which projects a developer are associated with, > and the dependency index will be needed to do the depended-on page on the > browse artifact 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: (MAVENUPLOAD-1094) jasperreports 1.2.5
jasperreports 1.2.5 --- Key: MAVENUPLOAD-1094 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1094 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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: (MCHANGELOG-45) All reports generated links point to the trunk of the svn module
[ http://jira.codehaus.org/browse/MCHANGELOG-45?page=comments#action_73383 ] Dennis Lundberg commented on MCHANGELOG-45: --- A new SNAPSHOT of the plugin has been published. Please test it and see f it solves this issue. > All reports generated links point to the trunk of the svn module > > > Key: MCHANGELOG-45 > URL: http://jira.codehaus.org/browse/MCHANGELOG-45 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Windows >Reporter: Rob MavenUser > Assigned To: Dennis Lundberg >Priority: Minor > > Hello, > *all* my generated links (changelog reports, 2.0-SNAPSHOT, Maven 2.0.4) point > to the trunk of my svn module. > For example, for mypage.jsp, the link should be : > http://my.svn.com:/rep/prj/modname/trunk/src/www/webmodname/jsp/mypage.jsp > > but it is : > http://my.svn.com:/rep/prj/modname/trunk/ > The same for all my files. > Is it a bug or do I miss anything in my configuration ? > Thanks in advance > Best Regards > Rob > Here my settings : > ... > > > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 90 > > > changelog > file-activity > dev-activity > > > > > > > > > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > http://my.svn.com:/rep/prj/modname/trunk/ > > > > src/java > > > src/www > > > -- 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-1092) asm:asm 2.2.2
asm:asm 2.2.2 - Key: MAVENUPLOAD-1092 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1092 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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-1093) asm:asm-commons 2.2.2
asm:asm-commons 2.2.2 - Key: MAVENUPLOAD-1093 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1093 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Dennis Lundberg updated MCHANGELOG-16: -- Priority: Minor (was: Major) > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood >Priority: Minor > Fix For: 2.0 > > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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] Reopened: (MCHANGELOG-16) when using svn, links are wrong
[ http://jira.codehaus.org/browse/MCHANGELOG-16?page=all ] Dennis Lundberg reopened MCHANGELOG-16: --- Assignee: (was: Edwin Punzalan) I have reverted the patch for this issue because it breaks the link creation for other svn web presentation systems, most notably viewcvs and viewvc. > when using svn, links are wrong > --- > > Key: MCHANGELOG-16 > URL: http://jira.codehaus.org/browse/MCHANGELOG-16 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: osx 10.4.5, java 1.4.2_09 >Reporter: Julian Wood > Fix For: 2.0 > > Attachments: MCHANGELOG-16.patch, test.zip > > > Here's my setup: > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > scm:svn:http://apollo.ucalgary.ca:8800/pmgt/trunk > > http://apollo.ucalgary.ca/websvncommons/listing.php?repname=pmgt&rev=0&sc=0&path=/trunk > > ... > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-beta-2-SNAPSHOT > > > changes > > > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&rev=0&sc=0&path= > range > 90 > > > changelog > file-activity > dev-activity > > > > > With that displayFileDetailUrl, I get links like this in the resultant > changelog in my site: > http://apollo.ucalgary.ca/websvncommons/filedetails.php/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp?repname=pmgt&sc=0&path= > but it should be like this: > link = > http://apollo.ucalgary.ca/websvncommons/filedetails.php?repname=pmgt&sc=0&rev=0&path=/trunk/pmgt-webapp/src/main/webapp/links/create_groups.jsp -- 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: (MCHANGELOG-45) All reports generated links point to the trunk of the svn module
[ http://jira.codehaus.org/browse/MCHANGELOG-45?page=comments#action_73381 ] Dennis Lundberg commented on MCHANGELOG-45: --- I have reverted the patch for MCHANGELOG-16 which broke the link creation for most svn web presentation systems. > All reports generated links point to the trunk of the svn module > > > Key: MCHANGELOG-45 > URL: http://jira.codehaus.org/browse/MCHANGELOG-45 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Windows >Reporter: Rob MavenUser > Assigned To: Dennis Lundberg >Priority: Minor > > Hello, > *all* my generated links (changelog reports, 2.0-SNAPSHOT, Maven 2.0.4) point > to the trunk of my svn module. > For example, for mypage.jsp, the link should be : > http://my.svn.com:/rep/prj/modname/trunk/src/www/webmodname/jsp/mypage.jsp > > but it is : > http://my.svn.com:/rep/prj/modname/trunk/ > The same for all my files. > Is it a bug or do I miss anything in my configuration ? > Thanks in advance > Best Regards > Rob > Here my settings : > ... > > > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 90 > > > changelog > file-activity > dev-activity > > > > > > > > > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > http://my.svn.com:/rep/prj/modname/trunk/ > > > > src/java > > > src/www > > > -- 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: (MPA-76) Process Shinobu Kawai
[ http://jira.codehaus.org/browse/MPA-76?page=comments#action_73379 ] Lukas Theussl commented on MPA-76: -- CLA received, a/c requested. > Process Shinobu Kawai > - > > Key: MPA-76 > URL: http://jira.codehaus.org/browse/MPA-76 > Project: Maven Project Administration > Issue Type: Task > Components: New Committers >Reporter: Lukas Theussl > Assigned To: Jason van Zyl > Fix For: 2006-q3 > > -- 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-176) AbstractSiteRenderingMojo causes a NPE if url of current project is not set
[ http://jira.codehaus.org/browse/MSITE-176?page=comments#action_73378 ] Vincent Siveton commented on MSITE-176: --- https://svn.sourceforge.net/svnroot/el4j/branches/el4j_1.1-alpha-m2/el4j is broken Thanks > AbstractSiteRenderingMojo causes a NPE if url of current project is not set > --- > > Key: MSITE-176 > URL: http://jira.codehaus.org/browse/MSITE-176 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: WinXP, Java5 >Reporter: Martin Zeltner >Priority: Blocker > Attachments: patch_maven-site-plugin.txt > > > AbstractSiteRenderingMojo causes a NullPointerException in > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler > if url of current project is not set. > $ mvn site:site > ... > [INFO] [site:site] > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.getParentPrefix > (DefaultDecorationModelInheritanceAssembler.java:340) > at > org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelIn > heritance(DefaultDecorationModelInheritanceAssembler.java:46) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:225 > ) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:217 > ) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:492 > ) > at > org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo. > java:431) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:108) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav > a:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:690) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:380) > 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) > This url is mostly not set, anyway not for each child module. To solve this > issue I did the following in method *getDecorationModel* of > *org.apache.maven.plugins.site.AbstractSiteRenderingMojo*: > If the parent model descriptor exists, the current and the parent model will > be assembled by using following url parameters: > If parent's url is null but child's not child's url will be used for parent. > If both urls are null the "url" "./" will be used for current and parent. > See appended patch. > Cheers, > Martin -- 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: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site
[ http://jira.codehaus.org/browse/MNG-2493?page=all ] Vincent Siveton closed MNG-2493. Resolution: Fixed I changed the repo id according: http://www.nabble.com/-m2--ids-of-repositories-are-inconsistently-used-in-poms-tf2107348.html#a5808879 Thanks! > Snapshot plugin repositories should be included for reference at the Maven > site > --- > > Key: MNG-2493 > URL: http://jira.codehaus.org/browse/MNG-2493 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Reporter: Baerrach bonDierne > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > Attachments: MNG-2493-patch-2.txt, MNG-2493-patch.txt > > > When developing a plugin (or patching an existing plugin), the plugin often > depends upon snapshot versions of plugins. > There is no reference material for where these snapshot plugin repositories > are located. > Luckily people respond on the list with this information, but it would help > to include it as part of the reference material on the web site. -- 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: (MCHANGELOG-46) Using the dateFormat option the generate changelog report shows a wrong date
[ http://jira.codehaus.org/browse/MCHANGELOG-46?page=comments#action_73376 ] Dennis Lundberg commented on MCHANGELOG-46: --- Are aware that the dateFormat parameter is not a presentation parameter? In the plugin documentation at http://maven.apache.org/plugins/maven-changelog-plugin/changelog-mojo.html#dateFormat it says: "Used to specify the date format of log entries to retrieve. This format will also be reflected in the reports." Digging into maven-scm, which is used to retrieve data from your SCM, I found this documentation in ScmProvider.java: "the date pattern use in changelog output returned by scm tool" So this is the format of the dates that come back from your subversion repository when you request a changelog from it. Try running this command in the root of your project: svn log pom.xml Look at the dates and see what format they have. If the have the format "-MM-dd" then you shouldn't be setting the dateFormat at all, since that is the default format. If they are in another format please report back with a snippet of the output from the svn command. > Using the dateFormat option the generate changelog report shows a wrong date > > --- > > Key: MCHANGELOG-46 > URL: http://jira.codehaus.org/browse/MCHANGELOG-46 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Giorgio Urto > Assigned To: Dennis Lundberg >Priority: Minor > > Using the dateFormat option in the generated changelog report a file that was > changed the 14 december 2005 at 11.48.50 is show using this timestamp > 0020-05-27 00:00:00. > Here is my configuration for the plugin: > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 365 > dd-MM- > > > changelog > file-activity > dev-activity > > > > > Without the dateFormat attribute set, the date in the report is ok. -- 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: (MCHANGELOG-46) Using the dateFormat option the generate changelog report shows a wrong date
[ http://jira.codehaus.org/browse/MCHANGELOG-46?page=comments#action_73375 ] Dennis Lundberg commented on MCHANGELOG-46: --- I confirm that the format of the dates are incorrect. I'll take a look at it and see if I can find out what's causing it. > Using the dateFormat option the generate changelog report shows a wrong date > > --- > > Key: MCHANGELOG-46 > URL: http://jira.codehaus.org/browse/MCHANGELOG-46 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Giorgio Urto >Priority: Minor > > Using the dateFormat option in the generated changelog report a file that was > changed the 14 december 2005 at 11.48.50 is show using this timestamp > 0020-05-27 00:00:00. > Here is my configuration for the plugin: > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 365 > dd-MM- > > > changelog > file-activity > dev-activity > > > > > Without the dateFormat attribute set, the date in the report is ok. -- 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: (MRM-145) identify skins and adjust type in index accordingly
[ http://jira.codehaus.org/browse/MRM-145?page=all ] Brett Porter closed MRM-145. Resolution: Fixed > identify skins and adjust type in index accordingly > --- > > Key: MRM-145 > URL: http://jira.codehaus.org/browse/MRM-145 > Project: Archiva > Issue Type: Improvement > Components: indexing >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 15 minutes > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > like we identify archetypes, attempt to identify skins and index them > accordingly. > It may be beneficial to introduce a proper packaging type for this in Maven > itself. > While it is not entirely deterministic (as a skin is simply a set of files > laid onto the site), the existence of one of css/maven-base.css and site.vm > would be a reliable predictor. -- 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: (MCHANGELOG-45) All reports generated links point to the trunk of the svn module
[ http://jira.codehaus.org/browse/MCHANGELOG-45?page=comments#action_73373 ] Dennis Lundberg commented on MCHANGELOG-45: --- I can confirm this behaviour. Will take a look and see if I can find the cause. > All reports generated links point to the trunk of the svn module > > > Key: MCHANGELOG-45 > URL: http://jira.codehaus.org/browse/MCHANGELOG-45 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Windows >Reporter: Rob MavenUser >Priority: Minor > > Hello, > *all* my generated links (changelog reports, 2.0-SNAPSHOT, Maven 2.0.4) point > to the trunk of my svn module. > For example, for mypage.jsp, the link should be : > http://my.svn.com:/rep/prj/modname/trunk/src/www/webmodname/jsp/mypage.jsp > > but it is : > http://my.svn.com:/rep/prj/modname/trunk/ > The same for all my files. > Is it a bug or do I miss anything in my configuration ? > Thanks in advance > Best Regards > Rob > Here my settings : > ... > > > > org.apache.maven.plugins > maven-changelog-plugin > 2.0-SNAPSHOT > > > dual-report > > range > 90 > > > changelog > file-activity > dev-activity > > > > > > > > > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > scm:svn:http://my.svn.com:/rep/prj/modname/trunk > > http://my.svn.com:/rep/prj/modname/trunk/ > > > > src/java > > > src/www > > > -- 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: (MRM-145) identify skins and adjust type in index accordingly
[ http://jira.codehaus.org/browse/MRM-145?page=all ] Brett Porter updated MRM-145: - Remaining Estimate: 15 minutes Original Estimate: 15 minutes > identify skins and adjust type in index accordingly > --- > > Key: MRM-145 > URL: http://jira.codehaus.org/browse/MRM-145 > Project: Archiva > Issue Type: Improvement > Components: indexing >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > like we identify archetypes, attempt to identify skins and index them > accordingly. > It may be beneficial to introduce a proper packaging type for this in Maven > itself. > While it is not entirely deterministic (as a skin is simply a set of files > laid onto the site), the existence of one of css/maven-base.css and site.vm > would be a reliable predictor. -- 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: (MRM-138) complete the proxy interface
[ http://jira.codehaus.org/browse/MRM-138?page=all ] Brett Porter closed MRM-138. Resolution: Fixed > complete the proxy interface > > > Key: MRM-138 > URL: http://jira.codehaus.org/browse/MRM-138 > Project: Archiva > Issue Type: New Feature > Components: remote proxy >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > Original Estimate: 16 hours > Time Spent: 1 day, 1 hour, 30 minutes > Remaining Estimate: 4 hours > > the current proxy interface is not well integrated and the tests are failing. > Complete this integration. -- 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: (MAVENUPLOAD-1078) subethasmtp 1.0.3 bundles
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1078?page=comments#action_73367 ] fabrizio giustina commented on MAVENUPLOAD-1078: bundle updated, snapshot version for retrotranslator-maven-plugin removed. > subethasmtp 1.0.3 bundles > - > > Key: MAVENUPLOAD-1078 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1078 > Project: maven-upload-requests > Issue Type: Task >Reporter: fabrizio giustina > > subethasmtp-smtp and subethasmtp-wiser bundles: contain jar, sources, javadoc > plus an additional artifact for the jdk14 compatible version with a "java14" > classifier > http://magnolia.sourceforge.net/bundles/subethasmtp-smtp-1.0.3-bundle.jar > http://magnolia.sourceforge.net/bundles/subethasmtp-wiser-1.0.3-bundle.jar > subethasmtp-parent: only contains the parent pom > http://magnolia.sourceforge.net/bundles/subethasmtp-parent-1.0.3-bundle.jar -- 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: (DOXIA-74) Added muse format to doxia-core
[ http://jira.codehaus.org/browse/DOXIA-74?page=comments#action_73364 ] Arnaud Bailly commented on DOXIA-74: Hello Vincent, Some comments on your comments: * No problem with the license issue, I will fix that asap * Follow our code style: The link does give configuration files for eclipse and idea, but does not explain the rules to follow in plain english. I am using emacs so a checkstyle or jalopy file would be better. Best would be an emacs mode :-) * Provide a minimalist documentation: mea culpa, mea maxima culpa * role-hint="doxia" needs to be renamed * role-hint="xhtml" is already used somewhere. I am not sure what he implication of duplicate role-hint names are. I thought this information was context dependent so that a name could be used for different usages. * Use logging API instead of System.err or throw Exception. Of course. I was looking for a specific API in doxia (as there is in maven but didn't find one). As a general comment about this patch, I should say that I don't expect it to be integrated in the main tree. I'd rather add a module as twiki or confluence and I provided this patch to get around the annoying issues about loading external modules that is named DOXIA-68. As I explained in the project's page, this is quick (and obviously dirty) fix that should not last, I then propose to leave that patch alone (after the requested modifications being made) and to file another issue with a real module. > Added muse format to doxia-core > --- > > Key: DOXIA-74 > URL: http://jira.codehaus.org/browse/DOXIA-74 > Project: doxia > Issue Type: New Feature > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Arnaud Bailly >Priority: Minor > Fix For: 1.0-alpha-8 > > Attachments: patch-doxia-1.0-alpha-8 > > > As a workaround to DOXIA-68 bug, I have m\ade a patch to > doxia-core-1.0-alpha-8 that include necessary code for generating maven sites > from muse syntax and add a dependency to muse-parser from doxia-core pom.xml. > This patch may be useful for people who wish to write their documentation > using Emacs muse 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
