[jira] Commented: (MRELEASE-146) Release tag with SVN under Cygwin fails when sending the svn command a bad absolute path
[ http://jira.codehaus.org/browse/MRELEASE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91650 ] Samuel Kerrien commented on MRELEASE-146: - I have had the same problem and making sure that Windows' subversion was upstream of cygwin in the PATH did the trick. Hope that helps ;) > Release tag with SVN under Cygwin fails when sending the svn command a bad > absolute path > > > Key: MRELEASE-146 > URL: http://jira.codehaus.org/browse/MRELEASE-146 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: scm >Affects Versions: 2.0-beta-4 > Environment: Windows XP >Reporter: Christian Gruber > > When release:prepare is invoked, on a cygwin system using svn provided with > cygwin, the following error occurs. > [INFO] Checking in modified POMs... > [INFO] Executing: svn --non-interactive commit --file > E:\DOCUME~1\CGRUBE~1.DJI\LOCALS~1\Temp\maven-scm-1141263545.commit > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml > [INFO] Working directory: E:\projects\israfil-fw\net.israfil.foundation-JDK1.4 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: > '/projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4' > is not a working copy > ... > SVN on cygwin interprets > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4/pom.xml to be > /projects/israfil-fw/net.israfil.foundation-JDK1.4/E:/projects/israfil-fw/net.israfil.foundation-JDK1.4, > essentially appending the absolute path on the current working driectory as > if it were a relative path. > This is very odd, since "svn > E:/projects/israfil-fw/net.israfil.foundation-JDK1.4" works like a charm. I > tried it with E: and e: to no avail. > Proposed solution: Use relative paths > Alternative - really really bad alternative: detect the presence of cygwin > and re-structure the file path to use /cygdrive/e/blah/blah format. > Ultimate remedy: Figure out why SVN is interpreting this way and fix in svn. > -Christian. -- 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: (MAVENUPLOAD-1453) Upload of rmock 2.0.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Brolund closed MAVENUPLOAD-1453. --- Resolution: Duplicate > Upload of rmock 2.0.0 > - > > Key: MAVENUPLOAD-1453 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1453 > Project: maven-upload-requests > Issue Type: Task >Reporter: Daniel Brolund > Assigned To: Carlos Sanchez > > rMock 2.0.0 is a Java mock object framework to use with jUnit. > rMock has support for a setup-modify-run-verify workflow when writing jUnit > tests. > It integrates better with IDE refactoring support and allows designing classes > and interfaces in a true test-first fashion. rMock has the flexibility and > power of jMock, while the recording of mock calls is influenced by EasyMock. -- 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-1453) Upload of rmock 2.0.0
Upload of rmock 2.0.0 - Key: MAVENUPLOAD-1453 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1453 Project: maven-upload-requests Issue Type: Task Reporter: Daniel Brolund Assigned To: Carlos Sanchez rMock 2.0.0 is a Java mock object framework to use with jUnit. rMock has support for a setup-modify-run-verify workflow when writing jUnit tests. It integrates better with IDE refactoring support and allows designing classes and interfaces in a true test-first fashion. rMock has the flexibility and power of jMock, while the recording of mock calls is influenced by EasyMock. -- 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-1454) Upload of rmock 2.0.0. Group already exists.
Upload of rmock 2.0.0. Group already exists. Key: MAVENUPLOAD-1454 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1454 Project: maven-upload-requests Issue Type: Task Reporter: Daniel Brolund RMock 2.0.0 is a Java mock object framework to use with jUnit. RMock has support for a setup-modify-run-verify workflow when writing jUnit tests. It integrates better with IDE refactoring support and allows designing classes and interfaces in a true test-first fashion. -- 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: (JXR-26) NPE when source code contains quoted strings "package" or "import"
[
http://jira.codehaus.org/browse/JXR-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated JXR-26:
---
Assignee: Dennis Lundberg
Affects Version/s: (was: 1.1)
1.0
Fix Version/s: 1.1
> NPE when source code contains quoted strings "package" or "import"
> --
>
> Key: JXR-26
> URL: http://jira.codehaus.org/browse/JXR-26
> Project: Maven JXR
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Géraud Dugé
> Assigned To: Dennis Lundberg
> Fix For: 1.1
>
>
> Here is a sample code:
> {code}
> package fr.test;
> public class SimpleTest
> {
> public void test()
> {
> //String varTest = "import";
> String varTest = "package";
> }
> }
> {code}
> When I run mvn jxr:jxr, the following NPE happens:
> {quote}
> ...
> [DEBUG] parsing... fr\test\SimpleTest.java
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.jxr.pacman.JavaFileImpl.parse(JavaFileImpl.java:95)
> at
> org.apache.maven.jxr.pacman.JavaFileImpl.(JavaFileImpl.java:64)
> at
> org.apache.maven.jxr.pacman.FileManager.getFile(FileManager.java:68)
> ...
> {quote}
--
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: (JXR-26) NPE when source code contains quoted strings "package" or "import"
[
http://jira.codehaus.org/browse/JXR-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed JXR-26.
--
Resolution: Fixed
This was fixed in r516976.
> NPE when source code contains quoted strings "package" or "import"
> --
>
> Key: JXR-26
> URL: http://jira.codehaus.org/browse/JXR-26
> Project: Maven JXR
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Géraud Dugé
> Assigned To: Dennis Lundberg
> Fix For: 1.1
>
>
> Here is a sample code:
> {code}
> package fr.test;
> public class SimpleTest
> {
> public void test()
> {
> //String varTest = "import";
> String varTest = "package";
> }
> }
> {code}
> When I run mvn jxr:jxr, the following NPE happens:
> {quote}
> ...
> [DEBUG] parsing... fr\test\SimpleTest.java
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.jxr.pacman.JavaFileImpl.parse(JavaFileImpl.java:95)
> at
> org.apache.maven.jxr.pacman.JavaFileImpl.(JavaFileImpl.java:64)
> at
> org.apache.maven.jxr.pacman.FileManager.getFile(FileManager.java:68)
> ...
> {quote}
--
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: (MJXR-22) Upgrade to maven-jxr-1.1
[ http://jira.codehaus.org/browse/MJXR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MJXR-22. --- Assignee: Dennis Lundberg Resolution: Fixed This was achieved by combining jxr and maven-jxr-plugin into the same directory in in svn, and also by using a unified release cycle like in surefire. > Upgrade to maven-jxr-1.1 > > > Key: MJXR-22 > URL: http://jira.codehaus.org/browse/MJXR-22 > Project: Maven 2.x JXR Plugin > Issue Type: Task >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > Fix For: 2.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] Moved: (JXR-27) If inceptionYear is not set in the pom then "{inceptionYear}-" is printed in the footer
[
http://jira.codehaus.org/browse/JXR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MJXR-23 to JXR-27:
Affects Version/s: (was: 2.0)
Fix Version/s: (was: 2.1)
Key: JXR-27 (was: MJXR-23)
Project: Maven JXR (was: Maven 2.x JXR Plugin)
> If inceptionYear is not set in the pom then "{inceptionYear}-" is printed in
> the footer
> ---
>
> Key: JXR-27
> URL: http://jira.codehaus.org/browse/JXR-27
> Project: Maven JXR
> Issue Type: Bug
>Reporter: Dennis Lundberg
> Assigned To: Dennis Lundberg
>Priority: Minor
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-28) If the pom does not have an organization/name then "null" is shown in the footer
[ http://jira.codehaus.org/browse/JXR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-25 to JXR-28: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.1) Key: JXR-28 (was: MJXR-25) Project: Maven JXR (was: Maven 2.x JXR Plugin) > If the pom does not have an organization/name then "null" is shown in the > footer > > > Key: JXR-28 > URL: http://jira.codehaus.org/browse/JXR-28 > Project: Maven JXR > Issue Type: Bug >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-31) empty index.html when site is staged.
[ http://jira.codehaus.org/browse/JXR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-20 to JXR-31: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.1) Key: JXR-31 (was: MJXR-20) Project: Maven JXR (was: Maven 2.x JXR Plugin) > empty index.html when site is staged. > - > > Key: JXR-31 > URL: http://jira.codehaus.org/browse/JXR-31 > Project: Maven JXR > Issue Type: Bug >Reporter: Jörg Hohwiller > Assigned To: Dennis Lundberg > > The JXR report works fine with "mvn site" but fails for "mvn site:stage" > (empty index.html). > Could you please evaluate MSITE-138 and MSITE-120. > Thank you very much. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-32) JXR does not handle empty (completely commented) java-files...
[
http://jira.codehaus.org/browse/JXR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MJXR-26 to JXR-32:
Affects Version/s: (was: 2.0)
Fix Version/s: (was: 2.1)
Key: JXR-32 (was: MJXR-26)
Project: Maven JXR (was: Maven 2.x JXR Plugin)
> JXR does not handle empty (completely commented) java-files...
> --
>
> Key: JXR-32
> URL: http://jira.codehaus.org/browse/JXR-32
> Project: Maven JXR
> Issue Type: Bug
> Environment: Maven 2.0.5 (Windows 2003 Srv/Windows XP)
>Reporter: Jan Palmquist
> Assigned To: Dennis Lundberg
>Priority: Minor
>
> I have detected that the jxr-plugin (or sub components) does not handle
> java-files being completely commented away e.g.
> //package my.demopackage;
> //public class MyClass {
> //}
> This is not a big issue, however it is quite annoying to have to notify
> developers that this not only is bad coding style but also breaks site
> generation.
> My stack trace:
> INFO] Generate "Test Source Xref" report.
> Unable to processPath
> C:\CC\projects\MyProject\src\test\java\my\demopackage\MyClass.java =>
> c:\CC\projects\MyProject\target/site/xref-test\my\demopackage\MyClass.html
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.jxr.JavaCodeTransform.getHeader(JavaCodeTransform.java:651)
> at
> org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.java:716)
> at
> org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.java:787)
> at org.apache.maven.jxr.JXR.transform(JXR.java:195)
> at org.apache.maven.jxr.JXR.processPath(JXR.java:114)
> at org.apache.maven.jxr.JXR.xref(JXR.java:335)
> at
> org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrReport.java:226)
> at
> org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:352)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
> 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:330)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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)
> [INFO]
>
> [INFO] Total time: 9 minutes 24 seconds
> [INFO] Finished at: Thu Mar 22 07:26:14 CET 2007
> [INFO] Final Memory: 73M/200M
> [INFO]
>
--
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.atlassia
[jira] Moved: (JXR-34) Upgrade to maven-jxr-1.1
[ http://jira.codehaus.org/browse/JXR-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-22 to JXR-34: Fix Version/s: (was: 2.1) Key: JXR-34 (was: MJXR-22) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Upgrade to maven-jxr-1.1 > > > Key: JXR-34 > URL: http://jira.codehaus.org/browse/JXR-34 > Project: Maven JXR > Issue Type: Task >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-30) NPE creating jxr report
[ http://jira.codehaus.org/browse/JXR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-17 to JXR-30: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.1) Key: JXR-30 (was: MJXR-17) Project: Maven JXR (was: Maven 2.x JXR Plugin) > NPE creating jxr report > --- > > Key: JXR-30 > URL: http://jira.codehaus.org/browse/JXR-30 > Project: Maven JXR > Issue Type: Bug >Reporter: Brian Fox > Assigned To: Vincent Siveton > > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.jxr.JavaCodeTransform.getHeader(JavaCodeTransform.ja > va:651) > at > org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.ja > va:716) > at > org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.ja > va:787) > at org.apache.maven.jxr.JXR.transform(JXR.java:195) > at org.apache.maven.jxr.JXR.processPath(JXR.java:114) > at org.apache.maven.jxr.JXR.xref(JXR.java:335) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrR > eport.java:226) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJ > xrReport.java:352) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven > Report.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(R > eportDocumentRenderer.java:67) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( > DefaultSiteRenderer.java:239) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul > tSiteRenderer.java:115) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124 > ) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-29) JXR Plugin ignores the reporting output directory when generating cross reference
[ http://jira.codehaus.org/browse/JXR-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-19 to JXR-29: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.1) Key: JXR-29 (was: MJXR-19) Project: Maven JXR (was: Maven 2.x JXR Plugin) > JXR Plugin ignores the reporting output directory when generating cross > reference > - > > Key: JXR-29 > URL: http://jira.codehaus.org/browse/JXR-29 > Project: Maven JXR > Issue Type: Bug >Reporter: Eric Helfrich > Assigned To: Dennis Lundberg > Attachments: module.zip > > > The JXR Plugin ignores the reporting outputDirectory when generating the > cross reference and puts it in target/site instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-36) Parameter sourcePaths like it exists in Javadoc plugin added
[ http://jira.codehaus.org/browse/JXR-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-15 to JXR-36: Affects Version/s: (was: 2.1) Fix Version/s: (was: 2.1) Key: JXR-36 (was: MJXR-15) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Parameter sourcePaths like it exists in Javadoc plugin added > > > Key: JXR-36 > URL: http://jira.codehaus.org/browse/JXR-36 > Project: Maven JXR > Issue Type: Improvement > Environment: WinXp >Reporter: Martin Zeltner > Assigned To: Stephane Nicoll > Attachments: patch_maven-jxr-plugin_parameter-sourcePaths-added.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > I've added the parameter "sourcePaths". If this parameter is set the jxr > plugin will take the java sources from the given paths instead of the root > source path. If it is not set the plugin will work as before. This is very > useful to define own sets of jxr report pages. > 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] Moved: (JXR-35) Review and revise plugin documentation
[ http://jira.codehaus.org/browse/JXR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-14 to JXR-35: Fix Version/s: (was: 2.1) Key: JXR-35 (was: MJXR-14) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Review and revise plugin documentation > -- > > Key: JXR-35 > URL: http://jira.codehaus.org/browse/JXR-35 > Project: Maven JXR > Issue Type: Task >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Original Estimate: 12 hours > Time Spent: 10 hours, 15 minutes > Remaining Estimate: 1 hour, 45 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-33) Add the ability to include/exclude source files
[ http://jira.codehaus.org/browse/JXR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-24 to JXR-33: Affects Version/s: (was: 2.0) Fix Version/s: (was: 2.1) Key: JXR-33 (was: MJXR-24) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Add the ability to include/exclude source files > --- > > Key: JXR-33 > URL: http://jira.codehaus.org/browse/JXR-33 > Project: Maven JXR > Issue Type: New Feature >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > -- 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: (JXR-37) Jxr plugin fails if xdoclet executed without sources generation
[ http://jira.codehaus.org/browse/JXR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated JXR-37: --- Component/s: maven2 jxr plugin > Jxr plugin fails if xdoclet executed without sources generation > --- > > Key: JXR-37 > URL: http://jira.codehaus.org/browse/JXR-37 > Project: Maven JXR > Issue Type: Bug > Components: maven2 jxr plugin >Reporter: Fernando Lindner >Priority: Critical > Attachments: MJXR-21.zip > > > JXR plugin always tries to find directory "target/generated-sources/xdoclet" > if a xdoclet execution is set. For instance, if a webdoclet task is used, no > "target/generated-sources/xdoclet" directory should be created, resulting in > a build error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-37) Jxr plugin fails if xdoclet executed without sources generation
[ http://jira.codehaus.org/browse/JXR-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MJXR-21 to JXR-37: Key: JXR-37 (was: MJXR-21) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Jxr plugin fails if xdoclet executed without sources generation > --- > > Key: JXR-37 > URL: http://jira.codehaus.org/browse/JXR-37 > Project: Maven JXR > Issue Type: Bug > Components: maven2 jxr plugin >Reporter: Fernando Lindner >Priority: Critical > Attachments: MJXR-21.zip > > > JXR plugin always tries to find directory "target/generated-sources/xdoclet" > if a xdoclet execution is set. For instance, if a webdoclet task is used, no > "target/generated-sources/xdoclet" directory should be created, resulting in > a build error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-38) View Javadoc link invalid
[
http://jira.codehaus.org/browse/JXR-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg moved MJXR-13 to JXR-38:
Affects Version/s: (was: 2.1)
2.0
Key: JXR-38 (was: MJXR-13)
Project: Maven JXR (was: Maven 2.x JXR Plugin)
> View Javadoc link invalid
> -
>
> Key: JXR-38
> URL: http://jira.codehaus.org/browse/JXR-38
> Project: Maven JXR
> Issue Type: Bug
>Affects Versions: 2.0
> Environment: 2.0.4
>Reporter: John Allen
> Assigned To: Fabrice BELLINGARD
>
> JXR View JavaDoc link is invalid
> JXR page URL:
> http://foo.com/projects/snapshots/examples/utils/xml/xref/index.html
> JXR page HTML:
> {noformat}
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
>
> />App xref
>
>
>
> href="../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.html">View
> Javadoc
> 1 package
> com.aelitis.common.utils.xml;
> 2
> [snip]
>
> {noformat}
> The JavaDoc URL used is:
> href="../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.html">View
> Javadoc
> However that takes us all the way back to the server root, mapping to the URL:
> http://foo.com/apidocs/com/aelitis/common/utils/xml/App.html
> When it should be the URL:
> http://foo.com/projects/snapshots/examples/utils/xml/apidocs/index.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] Updated: (JXR-38) View Javadoc link invalid
[
http://jira.codehaus.org/browse/JXR-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated JXR-38:
---
Fix Version/s: 2.1
Component/s: maven2 jxr plugin
> View Javadoc link invalid
> -
>
> Key: JXR-38
> URL: http://jira.codehaus.org/browse/JXR-38
> Project: Maven JXR
> Issue Type: Bug
> Components: maven2 jxr plugin
>Affects Versions: 2.0
> Environment: 2.0.4
>Reporter: John Allen
> Assigned To: Fabrice BELLINGARD
> Fix For: 2.1
>
>
> JXR View JavaDoc link is invalid
> JXR page URL:
> http://foo.com/projects/snapshots/examples/utils/xml/xref/index.html
> JXR page HTML:
> {noformat}
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
>
> />App xref
>
>
>
> href="../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.html">View
> Javadoc
> 1 package
> com.aelitis.common.utils.xml;
> 2
> [snip]
>
> {noformat}
> The JavaDoc URL used is:
> href="../../../../../../../../../../../../apidocs/com/aelitis/common/utils/xml/App.html">View
> Javadoc
> However that takes us all the way back to the server root, mapping to the URL:
> http://foo.com/apidocs/com/aelitis/common/utils/xml/App.html
> When it should be the URL:
> http://foo.com/projects/snapshots/examples/utils/xml/apidocs/index.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MONE-7) Add the ability to convert a pom from M1 to M2
Add the ability to convert a pom from M1 to M2 -- Key: MONE-7 URL: http://jira.codehaus.org/browse/MONE-7 Project: Maven 2.x M1 Plugin Issue Type: New Feature Affects Versions: 1.0 Reporter: Dennis Lundberg 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] Updated: (MONE-4) Review Plugin Documentation
[ http://jira.codehaus.org/browse/MONE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MONE-4: --- Affects Version/s: 1.0 Fix Version/s: 1.1 > Review Plugin Documentation > --- > > Key: MONE-4 > URL: http://jira.codehaus.org/browse/MONE-4 > Project: Maven 2.x M1 Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > 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] Closed: (MONE-7) Add the ability to convert a pom from M1 to M2
[ http://jira.codehaus.org/browse/MONE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MONE-7. -- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 1.1 > Add the ability to convert a pom from M1 to M2 > -- > > Key: MONE-7 > URL: http://jira.codehaus.org/browse/MONE-7 > Project: Maven 2.x M1 Plugin > Issue Type: New Feature >Affects Versions: 1.0 >Reporter: Dennis Lundberg > Assigned To: Dennis Lundberg > 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] Updated: (MRRESOURCES-21) Supplement the data model used by Velocity
[
http://jira.codehaus.org/browse/MRRESOURCES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliot Metsger updated MRRESOURCES-21:
--
Attachment: MRRP-21.patch
Attached is a patch for this issue. I'm not in love with the names. Instead
of "supplemental model" perhaps "stub model" is better/more accurate
terminology.
It allows a new element, . By default
${appendedResourceDirectory}/supplemental-models.xml is looked for, but can be
overridden:
path/to/supplemental-models.xml
org.apache:apache-jar-resource-bundle:1.2
The supplemental model file looks like this:
The patch includes a Modello model for the supplemental-model.xml file.
> Supplement the data model used by Velocity
> --
>
> Key: MRRESOURCES-21
> URL: http://jira.codehaus.org/browse/MRRESOURCES-21
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Improvement
>Affects Versions: 1.0-alpha-4
> Environment:
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-remote-resources-plugin
> r523911.
>Reporter: Elliot Metsger
>Priority: Minor
> Attachments: MRRP-21.patch
>
>
> Related to MRRESOURCES-2, I'd like to be able to deal with artifacts that
> have incomplete POM's, because incomplete NOTICE files are generated.
> But instead of having the MRRP append to a locally managed NOTICE file like
> MRRESOURCES-2, I'd like to augment the data model used by Velocity.
> The idea is that MRR plugin will take a parameter to a file which contains
> POM XML snippits. The ModelInheritanceAssembler merges the POM XML snippits
> with the actual artifact POM. Thoughts? I'll plan on submitting a patch.
--
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: (WAGON-71) Wagon nukes the permission bits of uploaded files.
[ http://jira.codehaus.org/browse/WAGON-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91683 ] Henning Schmiedehausen commented on WAGON-71: - Any news on this issue? This is now open for two months. > Wagon nukes the permission bits of uploaded files. > -- > > Key: WAGON-71 > URL: http://jira.codehaus.org/browse/WAGON-71 > Project: wagon > Issue Type: Bug >Reporter: Henning Schmiedehausen > > Uploading a site using wagon might nuke permission bits of e.g. CGI scripts > thus making these unavailable. > For Apache webserver, a CGI script can have the permission bit set and is > then executed. This is e.g. used for the "download.cgi" script on many Apache > project sites. > The wagon uploader (at least ssh and ssh-external) unconditionally change the > permissions of all files to be 664. Which kills the execution bits. Which is > bad (TM). -- 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: (MCLOVER-37) clover does not work with site:run
[ http://jira.codehaus.org/browse/MCLOVER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91684 ] Julien HENRY commented on MCLOVER-37: - Can you please give me the link to the related maven-site-plugin issue? I still have the problem with site:stage. > clover does not work with site:run > -- > > Key: MCLOVER-37 > URL: http://jira.codehaus.org/browse/MCLOVER-37 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: John Allen > Assigned To: Vincent Massol >Priority: Minor > > Don't know if this is by design or a known issue and it's probably a big ask > but i thought i'd mention it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-40) maven 2 jxr plugin puts wrong javadoc link
[
http://jira.codehaus.org/browse/JXR-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MJXR-4 to JXR-40:
Key: JXR-40 (was: MJXR-4)
Project: Maven JXR (was: Maven 2.x JXR Plugin)
> maven 2 jxr plugin puts wrong javadoc link
> --
>
> Key: JXR-40
> URL: http://jira.codehaus.org/browse/JXR-40
> Project: Maven JXR
> Issue Type: Bug
>Reporter: Lee Meador
> Assigned To: Brett Porter
>Priority: Minor
>
> There are too many '../'s in the link to the javadocs that is generated at
> the top of each page of java class source code. I have moved the javadocs to
> ${project.build.directory}/site/javadoc/ (which is given to the javadoc
> plugin and then told the jxr plugin that they were at
> ${project.build.directory}/site/javadoc/apidocs/ which takes into account how
> the javadocs are built. The link has way too many .. parts to the path and
> backs up all the way to the top of my web site instead of just to the folder
> equivalent to "site"
> The xml is:
>
>
>
> org.codehaus.mojo
> jxr-maven-plugin
>
>
> ${project.build.directory}/site/javadoc/apidocs/
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
> ${project.build.directory}/site/javadoc/
>
>
> ...
> Sorry to put this issue here. It needs moving but there is no MNGJXR and
> MPJXR seemed to be the maven1 jxr plugin. I assume it will be moved to the
> right place. (and thanks)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-41) Relative link to Xref not determined reliably
[ http://jira.codehaus.org/browse/JXR-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-5 to JXR-41: Key: JXR-41 (was: MJXR-5) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Relative link to Xref not determined reliably > - > > Key: JXR-41 > URL: http://jira.codehaus.org/browse/JXR-41 > Project: Maven JXR > Issue Type: Bug >Reporter: Nick Giles > Assigned To: Brett Porter > Attachments: MOJO-jxr.patch > > > Using the HEAD revision of the JXR plugin, I find that with certain of my > projects determining the relative link between the xref and the jxr.html page > can both crash and provide incorrect results. The problem is basically this > line: > String relativPath = des.getAbsolutePath().substring( > out.getAbsolutePath().length() + 1 ); > It does no content checking, and thus when for instance the output directory > contains some '..' elements, it doesn't consider how that affects the length. > A slight improvement is: > String relativPath = des.getCanonicalPath().substring( > out.getCanonicalPath().length() + 1 ); > which will at least be better so long as the locations point to similar > filesystem locations (see attached patch). > What is really needed is to do a filesystem based compare of the two > locations and determine what the link should be - or just add a parameter to > let the link be defined as a parameter, and reduce the cases that are > guaranteed to work automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-42) Jxr breaks in projects with generated-sources directories
[ http://jira.codehaus.org/browse/JXR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-6 to JXR-42: Fix Version/s: (was: 2.0) Key: JXR-42 (was: MJXR-6) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Jxr breaks in projects with generated-sources directories > - > > Key: JXR-42 > URL: http://jira.codehaus.org/browse/JXR-42 > Project: Maven JXR > Issue Type: Bug >Reporter: Mike Perham > Assigned To: Brett Porter > Attachments: jxr.txt > > > Jxr breaks when reporting on a project using the xdoclet plugin because the > target/generated-sources/xdoclet directory is added to the project's sources > but is deleted before the site is generated. This patch removes any source > directories from the list to be xref'd so they do not cause an error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-43) long/complex destination directories for site cause a "String index out of range" error
[
http://jira.codehaus.org/browse/JXR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MJXR-11 to JXR-43:
-
Fix Version/s: (was: 2.0)
Key: JXR-43 (was: MJXR-11)
Project: Maven JXR (was: Maven 2.x JXR Plugin)
> long/complex destination directories for site cause a "String index out of
> range" error
> ---
>
> Key: JXR-43
> URL: http://jira.codehaus.org/browse/JXR-43
> Project: Maven JXR
> Issue Type: Bug
> Environment: windows xp
>Reporter: rudi grasmuck
> Assigned To: Jesse McConnell
>
> If I setup the plugin as follows
>
> org.codehaus.mojo
>jxr-maven-plugin
>
>${workspace.dir}/site/${project.artifactId}/xref
>
>
> where the destDir variables resolve to
> "C:\projects\FNBTestAgain3\site\rasonlineswift\xref"
> I get
> Embedded error: Error while generating the HTML source code of the projet.
> String index out of range: -3
> If i use relative indicators
> ../../site/${project.artifactId}/xref which in effect
> points to the same directory it works fine
> full exception below:
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during report
> gene
> ration
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
> report g
> eneration
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.reporting.MavenReportException: Error while
> generati
> ng the HTML source code of the projet.
> at
> org.apache.maven.plugin.jxr.JxrReport.generateXrefForSources(JxrRepor
> t.java:202)
> at
> org.apache.maven.plugin.jxr.JxrReport.executeReport(JxrReport.java:16
> 5)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven
> Report.java:117)
> at
> org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.
> java:802)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> ... 18 more
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range:
> -3
> at java.lang.String.substring(String.java:1444)
> at java.lang.String.substring(String.java:1411)
> at
> org.apache.maven.plugin.jxr.JxrReport.generateXrefForSources(JxrRepor
> t.java:195)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-39) [JXR] botton doesn't include current year for license text
[ http://jira.codehaus.org/browse/JXR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-3 to JXR-39: Fix Version/s: (was: 2.0) Key: JXR-39 (was: MJXR-3) Project: Maven JXR (was: Maven 2.x JXR Plugin) > [JXR] botton doesn't include current year for license text > -- > > Key: JXR-39 > URL: http://jira.codehaus.org/browse/JXR-39 > Project: Maven JXR > Issue Type: Bug >Reporter: Carlos Sanchez > Assigned To: Brett Porter >Priority: Minor > > We need to extract the bottom code from the javadoc plugin and use it here too > sample: http://maven.apache.org/ref/current/maven-settings/xref/index.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] Moved: (JXR-46) add an option
[ http://jira.codehaus.org/browse/JXR-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-1 to JXR-46: Fix Version/s: (was: 2.0) Key: JXR-46 (was: MJXR-1) Project: Maven JXR (was: Maven 2.x JXR Plugin) > add an option > - > > Key: JXR-46 > URL: http://jira.codehaus.org/browse/JXR-46 > Project: Maven JXR > Issue Type: New Feature >Reporter: Brett Porter > Assigned To: Brett Porter > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-50) JXR Plugin Documentation and How to use APT doc
[ http://jira.codehaus.org/browse/JXR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-9 to JXR-50: Fix Version/s: (was: 2.0) Key: JXR-50 (was: MJXR-9) Project: Maven JXR (was: Maven 2.x JXR Plugin) > JXR Plugin Documentation and How to use APT doc > --- > > Key: JXR-50 > URL: http://jira.codehaus.org/browse/JXR-50 > Project: Maven JXR > Issue Type: Improvement >Reporter: Johnny R. Ruiz III > Assigned To: Fabrice BELLINGARD >Priority: Minor > > Document Plugin (Javadoc) and create a brief How to use APT Document. > Add sample report. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-44) Jxr plugin failes build if no source directory is found
[ http://jira.codehaus.org/browse/JXR-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-16 to JXR-44: - Key: JXR-44 (was: MJXR-16) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Jxr plugin failes build if no source directory is found > --- > > Key: JXR-44 > URL: http://jira.codehaus.org/browse/JXR-44 > Project: Maven JXR > Issue Type: Bug >Reporter: Kaare Nilsen > Assigned To: Dennis Lundberg >Priority: Critical > > When the jxr plugin does not find a source directory e.g. "src/main/java" it > failes the build. This creates some serious side effects. For my project it > ment that the release of our software failed, because we have several > artifacts with no src/main/java dirs. eg. xmlbeans artifacts, and aspect > libraries. The plugin should just log to debug that no sources was found for > processing, and then continue the build -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-49) don't generated summary page and include both reports in menu like m1
[ http://jira.codehaus.org/browse/JXR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-2 to JXR-49: Fix Version/s: (was: 2.0) Key: JXR-49 (was: MJXR-2) Project: Maven JXR (was: Maven 2.x JXR Plugin) > don't generated summary page and include both reports in menu like m1 > - > > Key: JXR-49 > URL: http://jira.codehaus.org/browse/JXR-49 > Project: Maven JXR > Issue Type: Improvement >Reporter: Brett Porter > Assigned To: Brett Porter > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-45) NPE if .java file contains only comments
[ http://jira.codehaus.org/browse/JXR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-27 to JXR-45: - Affects Version/s: (was: 2.0) Key: JXR-45 (was: MJXR-27) Project: Maven JXR (was: Maven 2.x JXR Plugin) > NPE if .java file contains only comments > > > Key: JXR-45 > URL: http://jira.codehaus.org/browse/JXR-45 > Project: Maven JXR > Issue Type: Bug >Reporter: Wendy Smoak >Priority: Minor > Attachments: jxr-test.zip > > > If a .java file contains only comments, the JXR plugin fails with the > following error. > To reproduce, use the quickstart archetype, edit App.java to contain only > comments, and add the jxr plugin in the reporting section of the pom. Sample > project attached > $mvn site > ... > Unable to processPath C:\temp\jxr-test\src\main\java\net\wsmoak\App.java => > c:\temp\jxr-test\target/site/xref\net\wsmoak\App.html > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.jxr.JavaCodeTransform.getHeader(JavaCodeTransform.java:651) > at > org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.java:716) > at > org.apache.maven.jxr.JavaCodeTransform.transform(JavaCodeTransform.java:787) > at org.apache.maven.jxr.JXR.transform(JXR.java:195) > at org.apache.maven.jxr.JXR.processPath(JXR.java:114) > at org.apache.maven.jxr.JXR.xref(JXR.java:335) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.createXref(AbstractJxrReport.java:226) > at > org.apache.maven.plugin.jxr.AbstractJxrReport.executeReport(AbstractJxrReport.java:352) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > 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:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > 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) > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Tue Mar 27 20:30:55 MST 2007 > [INFO] Final Memory: 14M/26M > [INFO] > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-48) Create test for jxr plugin
[ http://jira.codehaus.org/browse/JXR-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-10 to JXR-48: - Fix Version/s: (was: 2.0) Key: JXR-48 (was: MJXR-10) Project: Maven JXR (was: Maven 2.x JXR Plugin) > Create test for jxr plugin > -- > > Key: JXR-48 > URL: http://jira.codehaus.org/browse/JXR-48 > Project: Maven JXR > Issue Type: Task >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (JXR-47) add option to disable test Xref
[ http://jira.codehaus.org/browse/JXR-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MJXR-8 to JXR-47: Key: JXR-47 (was: MJXR-8) Project: Maven JXR (was: Maven 2.x JXR Plugin) > add option to disable test Xref > --- > > Key: JXR-47 > URL: http://jira.codehaus.org/browse/JXR-47 > Project: Maven JXR > Issue Type: New Feature >Reporter: Brett Porter > Assigned To: Brett Porter > Attachments: mjxr-8.patch > > -- 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: (JXR-47) add option to disable test Xref
[ http://jira.codehaus.org/browse/JXR-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-47: Fix Version/s: 2.0 > add option to disable test Xref > --- > > Key: JXR-47 > URL: http://jira.codehaus.org/browse/JXR-47 > Project: Maven JXR > Issue Type: New Feature >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0 > > Attachments: mjxr-8.patch > > -- 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: (JXR-42) Jxr breaks in projects with generated-sources directories
[ http://jira.codehaus.org/browse/JXR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-42: Fix Version/s: 2.0 > Jxr breaks in projects with generated-sources directories > - > > Key: JXR-42 > URL: http://jira.codehaus.org/browse/JXR-42 > Project: Maven JXR > Issue Type: Bug >Reporter: Mike Perham > Assigned To: Brett Porter > Fix For: 2.0 > > Attachments: jxr.txt > > > Jxr breaks when reporting on a project using the xdoclet plugin because the > target/generated-sources/xdoclet directory is added to the project's sources > but is deleted before the site is generated. This patch removes any source > directories from the list to be xref'd so they do not cause an error. -- 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: (JXR-46) add an option
[ http://jira.codehaus.org/browse/JXR-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-46: Fix Version/s: 2.0 > add an option > - > > Key: JXR-46 > URL: http://jira.codehaus.org/browse/JXR-46 > Project: Maven JXR > Issue Type: New Feature >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.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] Updated: (JXR-49) don't generated summary page and include both reports in menu like m1
[ http://jira.codehaus.org/browse/JXR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-49: Fix Version/s: 2.0 > don't generated summary page and include both reports in menu like m1 > - > > Key: JXR-49 > URL: http://jira.codehaus.org/browse/JXR-49 > Project: Maven JXR > Issue Type: Improvement >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.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] Updated: (JXR-48) Create test for jxr plugin
[ http://jira.codehaus.org/browse/JXR-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-48: Fix Version/s: 2.0 > Create test for jxr plugin > -- > > Key: JXR-48 > URL: http://jira.codehaus.org/browse/JXR-48 > Project: Maven JXR > Issue Type: Task >Reporter: Maria Odea Ching > Assigned To: Maria Odea Ching > Fix For: 2.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] Updated: (JXR-39) [JXR] botton doesn't include current year for license text
[ http://jira.codehaus.org/browse/JXR-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-39: Fix Version/s: 2.0 > [JXR] botton doesn't include current year for license text > -- > > Key: JXR-39 > URL: http://jira.codehaus.org/browse/JXR-39 > Project: Maven JXR > Issue Type: Bug >Reporter: Carlos Sanchez > Assigned To: Brett Porter >Priority: Minor > Fix For: 2.0 > > > We need to extract the bottom code from the javadoc plugin and use it here too > sample: http://maven.apache.org/ref/current/maven-settings/xref/index.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] Updated: (JXR-43) long/complex destination directories for site cause a "String index out of range" error
[
http://jira.codehaus.org/browse/JXR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated JXR-43:
Fix Version/s: 2.0
> long/complex destination directories for site cause a "String index out of
> range" error
> ---
>
> Key: JXR-43
> URL: http://jira.codehaus.org/browse/JXR-43
> Project: Maven JXR
> Issue Type: Bug
> Environment: windows xp
>Reporter: rudi grasmuck
> Assigned To: Jesse McConnell
> Fix For: 2.0
>
>
> If I setup the plugin as follows
>
> org.codehaus.mojo
>jxr-maven-plugin
>
>${workspace.dir}/site/${project.artifactId}/xref
>
>
> where the destDir variables resolve to
> "C:\projects\FNBTestAgain3\site\rasonlineswift\xref"
> I get
> Embedded error: Error while generating the HTML source code of the projet.
> String index out of range: -3
> If i use relative indicators
> ../../site/${project.artifactId}/xref which in effect
> points to the same directory it works fine
> full exception below:
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during report
> gene
> ration
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
> report g
> eneration
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:389)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.reporting.MavenReportException: Error while
> generati
> ng the HTML source code of the projet.
> at
> org.apache.maven.plugin.jxr.JxrReport.generateXrefForSources(JxrRepor
> t.java:202)
> at
> org.apache.maven.plugin.jxr.JxrReport.executeReport(JxrReport.java:16
> 5)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMaven
> Report.java:117)
> at
> org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.
> java:802)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
> ... 18 more
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range:
> -3
> at java.lang.String.substring(String.java:1444)
> at java.lang.String.substring(String.java:1411)
> at
> org.apache.maven.plugin.jxr.JxrReport.generateXrefForSources(JxrRepor
> t.java:195)
--
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: (JXR-50) JXR Plugin Documentation and How to use APT doc
[ http://jira.codehaus.org/browse/JXR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated JXR-50: Fix Version/s: 2.0 > JXR Plugin Documentation and How to use APT doc > --- > > Key: JXR-50 > URL: http://jira.codehaus.org/browse/JXR-50 > Project: Maven JXR > Issue Type: Improvement >Reporter: Johnny R. Ruiz III > Assigned To: Fabrice BELLINGARD >Priority: Minor > Fix For: 2.0 > > > Document Plugin (Javadoc) and create a brief How to use APT Document. > Add sample report. -- 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: (MRRESOURCES-21) Supplement the data model used by Velocity
[ http://jira.codehaus.org/browse/MRRESOURCES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliot Metsger updated MRRESOURCES-21: -- Attachment: MRRP-21.patch Updating patch, forgot to include the mdo. > Supplement the data model used by Velocity > -- > > Key: MRRESOURCES-21 > URL: http://jira.codehaus.org/browse/MRRESOURCES-21 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-4 > Environment: > https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-remote-resources-plugin > r523911. >Reporter: Elliot Metsger >Priority: Minor > Attachments: MRRP-21.patch, MRRP-21.patch > > > Related to MRRESOURCES-2, I'd like to be able to deal with artifacts that > have incomplete POM's, because incomplete NOTICE files are generated. > But instead of having the MRRP append to a locally managed NOTICE file like > MRRESOURCES-2, I'd like to augment the data model used by Velocity. > The idea is that MRR plugin will take a parameter to a file which contains > POM XML snippits. The ModelInheritanceAssembler merges the POM XML snippits > with the actual artifact POM. Thoughts? I'll plan on submitting a patch. -- 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: (MCHECKSTYLE-64) Allow inclusion of javadoc source path in check
[
http://jira.codehaus.org/browse/MCHECKSTYLE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91697
]
Gregory Kick commented on MCHECKSTYLE-64:
-
I've looked into this and it's actually an issue with the {{PackageHtmlCheck}}.
Rather than checking the fileset to see that it includes a corresponding
{{package.html}}, it creates a {{File}} for {{package.html}} in the same
directory as the java file and uses the {{exists()}} method. In order for this
issue to be resolved, it would require either a fix in checkstyle or a new
check implemented specifically for maven. In the end, I like to do things the
_maven way_, but in this particular case, I'm not entirely sure that putting
{{package.html}} files in a different directory even makes sense anyway. Why
put just a small fraction of the javadocs in a different folder? It is a
little odd to put resources like images there, but the {{package.html}} files
just might be better off in {{src/main/java}}.
> Allow inclusion of javadoc source path in check
> ---
>
> Key: MCHECKSTYLE-64
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-64
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Johan Vanbockryck
>Priority: Minor
>
> According to the documentation of the maven-javadoc-plugin, the Javadoc
> resources (like package.html) should be placed in src/main/javadoc. This will
> cause a checkstyle error for missing package.html files however when enabling
> the PackageHtml module, since this directory is not included in the
> checkstyle source path.
> See also: http://maven.apache.org/plugins/maven-javadoc-plugin/faq.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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91698 ] Dennis Lundberg commented on MIDEA-39: -- Is there nobody out there who can confirm or deny that this is working in 2.1-SNAPSHOT? > In a multi-module project, idea plugin should generate module dependencies > instead of creating libs with references to the repository > - > > Key: MIDEA-39 > URL: http://jira.codehaus.org/browse/MIDEA-39 > Project: Maven 2.x Idea Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 >Reporter: Vikash Ramanlal > Assigned To: Brett Porter >Priority: Minor > Attachments: module-dependencies.patch > > > When I generate my idea files using "mvn idea:idea", all works fine. > However if I have module a and module b (both jar packaging) and b depends on > a, then I expected the idea plugin to generate the project files such that > for module b, a is a dependent module. However what I get is a library entry > for a that points to a jar in the local repository. > Maven 1.0.2 idea plugin did not work this way. I created the module > dependencies in correctly in the idea 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] Updated: (MIDEA-80) Transitive dependencies in a of a module in a multiproject should be exported
[ http://jira.codehaus.org/browse/MIDEA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MIDEA-80: - Affects Version/s: (was: 2.1) 2.0 > Transitive dependencies in a of a module in a multiproject should be exported > - > > Key: MIDEA-80 > URL: http://jira.codehaus.org/browse/MIDEA-80 > Project: Maven 2.x Idea Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Michael Mekaail >Priority: Critical > Attachments: MIDEA-80-maven-idea-plugin.patch, > MIDEA-80-maven-idea-plugin.patch > > > Currently the maven-idea-plugin treats all dependencies the same in that it > just adds all of them to each module > But what I would like is that if I have dependencies that are transative as a > result of it depending upon another module in my multimodule project then I > would like the module to be dependent only upon its upper module and this > upper module to export all its dependencies. > This stops cluttering of alot of dependencies being put in for each module > when they can all just be exported from the top level dependency. -- 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: (MCHECKSTYLE-65) regression in checkstyle 2.2: config locations seen as null
[ http://jira.codehaus.org/browse/MCHECKSTYLE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91699 ] Dennis Lundberg commented on MCHECKSTYLE-65: Brett, I think that Dan fixed this in http://svn.apache.org/viewvc?view=rev&revision=518817 Can you verify that? > regression in checkstyle 2.2: config locations seen as null > --- > > Key: MCHECKSTYLE-65 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-65 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Brett Porter > Fix For: 2.2 > > > I was just looking at the test Jason added from Brian about the extensions > (utilising checkstyle), and I've found an additional problem occurs under > Checkstyle 2.2 that works with 2.1. > With Maven 2.0.4, change it0111 to use checkstyle 2.2-SNAPSHOT and run mvn > -Dtest=MavenIT0111PluginsThatRequireAResourceFromAnExtensionTest test > Caused by: org.apache.maven.reporting.MavenReportException: Unable to process > null config location. > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.getConfigFile(CheckstyleReport.java:969) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:504) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > at > org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73) > ... 18 more -- 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: (MCHECKSTYLE-66) How to configure maven-checkstyle-plugin with external ImportControl file in your checkstyle configuration ?
[ http://jira.codehaus.org/browse/MCHECKSTYLE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHECKSTYLE-66: --- Priority: Major (was: Blocker) > How to configure maven-checkstyle-plugin with external ImportControl file in > your checkstyle configuration ? > > > Key: MCHECKSTYLE-66 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-66 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Maven 2.0.4 > Windows 200 Pro (command line), Linux Mandrake Server 3.0 (Continuum 1.0.3) >Reporter: Cyril MOREAU > > How to configure maven-checkstyle-plugin with external ImportControl file > in your checkstyle configuration ? > My checstyles configuration is available in > "http://www.xxx.com/repository/rdc";. This > address contains this files : > my_checstyleconfiguration.xml > import-control.xml > In the "my_checstyleconfiguration.xml", the importcontrol is define : > > value="Utilisation d'un package non autoris??"/> > > value="http://www.xxx.com/repository/rdc/import-control.xml"/> > > But when I run maven, build failure because maven doesn't localize > import-control.xml : "http://www.xxx.com/repository/rdc/import-control.xml > (syntaxe de nom de fichier, de répertoire ou de volume incorrect) -- 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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91703 ] Arik Kfir commented on MIDEA-39: This is definitly working for me in 2.1-SNAPSHOT. Caveat is to run "mvn idea:idea" in the multi-module root; if you run it inside one of the modules, inter-module dependencies indeed do not work (as they are not in the reactor I believe). > In a multi-module project, idea plugin should generate module dependencies > instead of creating libs with references to the repository > - > > Key: MIDEA-39 > URL: http://jira.codehaus.org/browse/MIDEA-39 > Project: Maven 2.x Idea Plugin > Issue Type: Improvement >Affects Versions: 2.0 > Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 >Reporter: Vikash Ramanlal > Assigned To: Brett Porter >Priority: Minor > Attachments: module-dependencies.patch > > > When I generate my idea files using "mvn idea:idea", all works fine. > However if I have module a and module b (both jar packaging) and b depends on > a, then I expected the idea plugin to generate the project files such that > for module b, a is a dependent module. However what I get is a library entry > for a that points to a jar in the local repository. > Maven 1.0.2 idea plugin did not work this way. I created the module > dependencies in correctly in the idea 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: (MGROOVY-24) When maven.test.skip=true skip groovy:testCompile
When maven.test.skip=true skip groovy:testCompile
-
Key: MGROOVY-24
URL: http://jira.codehaus.org/browse/MGROOVY-24
Project: Maven 2.x Groovy Plugin
Issue Type: Improvement
Reporter: Jason Dillon
Assigned To: Jason Dillon
This is the same behavior as the compiler plugin, it will skip execution when
{{maven.test.skip}} == {{true}}.
--
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: (MGROOVY-24) When maven.test.skip=true skip groovy:testCompile
[
http://jira.codehaus.org/browse/MGROOVY-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed MGROOVY-24.
---
Resolution: Fixed
Fix Version/s: 1.0-alpha-3
> When maven.test.skip=true skip groovy:testCompile
> -
>
> Key: MGROOVY-24
> URL: http://jira.codehaus.org/browse/MGROOVY-24
> Project: Maven 2.x Groovy Plugin
> Issue Type: Improvement
>Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 1.0-alpha-3
>
>
> This is the same behavior as the compiler plugin, it will skip execution when
> {{maven.test.skip}} == {{true}}.
--
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
