[jira] Updated: (MDEP-164) dependency:copy-dependencies does not honour 'copyPom'
[
http://jira.codehaus.org/browse/MDEP-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MDEP-164:
---
Summary: dependency:copy-dependencies does not honour 'copyPom' (was:
dependency:copy-dependencies does honour 'copyPom')
Updated title.
> dependency:copy-dependencies does not honour 'copyPom'
> --
>
> Key: MDEP-164
> URL: http://jira.codehaus.org/browse/MDEP-164
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 2.0-alpha-4
>Reporter: James Walker
>Assignee: Brian Fox
>
> Configure the pom as follows:
> {quote}
>
> ...
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.0-alpha-4
>
> true
>
> false
> lib
>
>
>
>
> ...
> {quote}
> Running:
> {quote}
>mvn dependency:copy-dependencies
> {quote}
> will copy the dependent jars but not their pom files. Adding configuration
> to use the repository layout doesn't fix the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3551) MANIFEST.MF in commons-attributes-api has bad line breaks
[
http://jira.codehaus.org/browse/MNG-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132779#action_132779
]
Dennis Lundberg commented on MNG-3551:
--
The MANIFEST.MF file you mention is following the JAR file specification at
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files
{quote}
* Line length:
No line may be longer than 72 bytes (not characters), in its UTF8-encoded form.
If a value would make the initial line longer than this, it should be continued
on extra lines (each starting with a single SPACE).
{quote}
May I suggest that you file a bug for the software that is unable to read such
a manifest.
> MANIFEST.MF in commons-attributes-api has bad line breaks
> -
>
> Key: MNG-3551
> URL: http://jira.codehaus.org/browse/MNG-3551
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Reporter: Craig
>
> The MANIFEST.MF file in commons-attributes-api 2.2 has some bad line breaks
> that prevent applications that use it from working.
> From http://forum.springframework.org/showthread.php?t=31092 :
> There seems to be a malformed MANIFEST.MF in the
> commons-attributes-compiler.jar library. You should unpack the library (with
> winzip or whatever), repair the MANIFEST.MF file there, so that the lines
> that have been dropped to the second line and added an empty space to the
> beginning, are rejoined to the line above them, without the empty space, and
> then pack the jar file again (with winzip or whatever and rename as .jar, not
> .zip).
> The suggested fix does work - can you fix the copy in the repository? 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] Closed: (MNG-3551) MANIFEST.MF in commons-attributes-api has bad line breaks
[ http://jira.codehaus.org/browse/MNG-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-3551. Resolution: Won't Fix > MANIFEST.MF in commons-attributes-api has bad line breaks > - > > Key: MNG-3551 > URL: http://jira.codehaus.org/browse/MNG-3551 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Craig > > The MANIFEST.MF file in commons-attributes-api 2.2 has some bad line breaks > that prevent applications that use it from working. > From http://forum.springframework.org/showthread.php?t=31092 : > There seems to be a malformed MANIFEST.MF in the > commons-attributes-compiler.jar library. You should unpack the library (with > winzip or whatever), repair the MANIFEST.MF file there, so that the lines > that have been dropped to the second line and added an empty space to the > beginning, are rejoined to the line above them, without the empty space, and > then pack the jar file again (with winzip or whatever and rename as .jar, not > .zip). > The suggested fix does work - can you fix the copy in the repository? 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: (MSHARED-1) [maven-verifier] Allow handling custom typed artifacts
[ http://jira.codehaus.org/browse/MSHARED-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3143 to MSHARED-1: Affects Version/s: (was: Shared Components) Fix Version/s: (was: Shared Components) Component/s: (was: Shared) maven-verifier Key: MSHARED-1 (was: MNG-3143) Project: Maven Shared Components (was: Maven 2) > [maven-verifier] Allow handling custom typed artifacts > -- > > Key: MSHARED-1 > URL: http://jira.codehaus.org/browse/MSHARED-1 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-verifier >Reporter: Arnaud Bailly >Priority: Minor > Attachments: custom-type.patch > > > In the Verifier class, checking artifacts' presence/absence in the repository > does not handle custom types/extensions. The attached patch adds a > TypeHandler class (a ligthweight ArtifactHandler) and a addHandler method for > managing custom artifact types. -- 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: (MSHARED-3) [maven-downloader] Infinite-loop in DefaultDownloader.download
[ http://jira.codehaus.org/browse/MSHARED-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3015 to MSHARED-3: Fix Version/s: (was: Reviewed Pending Version Assignment) Component/s: (was: Shared) maven-downloader Key: MSHARED-3 (was: MNG-3015) Project: Maven Shared Components (was: Maven 2) > [maven-downloader] Infinite-loop in DefaultDownloader.download > -- > > Key: MSHARED-3 > URL: http://jira.codehaus.org/browse/MSHARED-3 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-downloader >Reporter: Mark Hobson > > org.apache.maven.shared.downloader.DefaultDownloader.download(String, String, > String, File, String[]) continuously invokes itself since it doesn't convert > localRepository from a File to an ArtifactRepository. -- 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: (MSHARED-2) [maven-dependency-tree] Managed information lost when artifact previously encountered
[
http://jira.codehaus.org/browse/MSHARED-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton moved MNG-3548 to MSHARED-2:
Affects Version/s: (was: Shared Components)
Component/s: (was: Shared)
maven-dependency-tree
Key: MSHARED-2 (was: MNG-3548)
Project: Maven Shared Components (was: Maven 2)
> [maven-dependency-tree] Managed information lost when artifact previously
> encountered
> -
>
> Key: MSHARED-2
> URL: http://jira.codehaus.org/browse/MSHARED-2
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Reporter: Mark Hobson
>
> The scenario:
> {noformat}
> (managed: g:c:t:2)
> g:p:t:1
> \- g:a:t:1
>+- g:b:t:1
>| \- g:c:t:1
>\- g:c:t:1{noformat}
> Should result in:
> {noformat}g:p:t:1
> \- g:a:t:1
>+- g:b:t:1
>| \- (g:c:t:2 - version managed from 1; omitted for duplicate)
>\- g:c:t:2 (version managed from 1){noformat}
> But becomes:
> {noformat}g:p:t:1
> \- g:a:t:1
>+- g:b:t:1
>| \- (g:c:t:2 - version managed from 1; omitted for duplicate)
>\- g:c:t:2{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSHARED-4) [maven-dependency-tree] DefaultDependencyTreeBuilder ignores artifact filter
[ http://jira.codehaus.org/browse/MSHARED-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3236 to MSHARED-4: Affects Version/s: (was: Shared Components) Fix Version/s: (was: Shared Components) Component/s: (was: Shared) maven-dependency-tree Key: MSHARED-4 (was: MNG-3236) Project: Maven Shared Components (was: Maven 2) > [maven-dependency-tree] DefaultDependencyTreeBuilder ignores artifact filter > > > Key: MSHARED-4 > URL: http://jira.codehaus.org/browse/MSHARED-4 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-dependency-tree >Reporter: Mark Hobson > -- 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: (MSHARED-5) [maven-dependency-tree] Track range events in dependency tree nodes
[ http://jira.codehaus.org/browse/MSHARED-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3093 to MSHARED-5: Fix Version/s: (was: Shared Components) Component/s: (was: Shared) maven-dependency-tree Key: MSHARED-5 (was: MNG-3093) Project: Maven Shared Components (was: Maven 2) > [maven-dependency-tree] Track range events in dependency tree nodes > --- > > Key: MSHARED-5 > URL: http://jira.codehaus.org/browse/MSHARED-5 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Reporter: Mark Hobson > > Need to track the following DependencyTreeResolutionListener events in nodes: > - selectVersionFromRange > - restrictRange -- 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: (MSHARED-6) v3 pom properties is already supported in v4 poms and should be converted accordingly
[ http://jira.codehaus.org/browse/MSHARED-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-2100 to MSHARED-6: Component/s: (was: Shared) maven-model-converter Key: MSHARED-6 (was: MNG-2100) Project: Maven Shared Components (was: Maven 2) > v3 pom properties is already supported in v4 poms and should be converted > accordingly > - > > Key: MSHARED-6 > URL: http://jira.codehaus.org/browse/MSHARED-6 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-model-converter >Reporter: Edwin Punzalan >Assignee: Edwin Punzalan > Attachments: MNG-2100-maven-model-converter.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] Moved: (MSHARED-7) Add stricter pattern filters to maven-common-artifact-filters
[ http://jira.codehaus.org/browse/MSHARED-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-2621 to MSHARED-7: Fix Version/s: (was: Shared Components) Component/s: (was: Shared) maven-common-artifact-filters Key: MSHARED-7 (was: MNG-2621) Project: Maven Shared Components (was: Maven 2) > Add stricter pattern filters to maven-common-artifact-filters > - > > Key: MSHARED-7 > URL: http://jira.codehaus.org/browse/MSHARED-7 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-common-artifact-filters >Reporter: Brian Topping >Assignee: Mark Hobson > Attachments: IncludesArtifactFilter.patch, MNG-2621.patch > > > There is a todo in > http://svn.apache.org/viewvc/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/IncludesArtifactFilter.java?view=markup > to add regex. I checked all the sources and could only find usages of this > code by maven-assembly-plugin, webstart-maven-plugin and exec-maven-plugin. > The latter two are in mojo. > If you look at > http://svn.palle.net/projects/hauskeeper/hauskeeper-server/src/assemblies/debian.xml, > Trygvis is assuming that wildcards work, when in fact they do not. Arguably, > this is a documentation bug that it does not work. > The attached patch fixes this problem. -- 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: (MPLUGINTESTING-2) maven-plugin-testing-harness: all collections in MavenProjectStub should return empty collections
[ http://jira.codehaus.org/browse/MPLUGINTESTING-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-2998 to MPLUGINTESTING-2: --- Affects Version/s: (was: 2.0.6) Fix Version/s: (was: 2.0.7) 1.1 Component/s: (was: Shared) plugin-testing-harness Key: MPLUGINTESTING-2 (was: MNG-2998) Project: Maven 2.x Plugin Testing (was: Maven 2) > maven-plugin-testing-harness: all collections in MavenProjectStub should > return empty collections > - > > Key: MPLUGINTESTING-2 > URL: http://jira.codehaus.org/browse/MPLUGINTESTING-2 > Project: Maven 2.x Plugin Testing > Issue Type: Bug > Components: plugin-testing-harness >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 1.1 > > > All collections should return Collections.EMPTY_LIST / EMPTY_SET / EMPTY_MAP > http://www.nabble.com/testing-harness-MavenProjectStub-tf2269298s177.html#a6298829 -- 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: (MSHARED-8) New maven-runtime shared component
[ http://jira.codehaus.org/browse/MSHARED-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3026 to MSHARED-8: Priority: Major Component/s: (was: Shared) maven-runtime Key: MSHARED-8 (was: MNG-3026) Project: Maven Shared Components (was: Maven 2) > New maven-runtime shared component > -- > > Key: MSHARED-8 > URL: http://jira.codehaus.org/browse/MSHARED-8 > Project: Maven Shared Components > Issue Type: New Feature > Components: maven-runtime >Reporter: Mark Hobson > Attachments: maven-runtime.zip > > > The attached shared component allows introspection of the current Maven > runtime environment. The MavenRuntime API provides access to all Maven > project metadata available within a specified class path, which can be useful > for diagnostic purposes. -- 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: (MPLUGINTESTING-3) [maven-plugin-testing-harness] Implement ArtifactStub.getDependencyConflictId
[ http://jira.codehaus.org/browse/MPLUGINTESTING-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3050 to MPLUGINTESTING-3: --- Fix Version/s: (was: Shared Components) 1.1 Component/s: (was: Shared) plugin-testing-harness Key: MPLUGINTESTING-3 (was: MNG-3050) Project: Maven 2.x Plugin Testing (was: Maven 2) > [maven-plugin-testing-harness] Implement ArtifactStub.getDependencyConflictId > - > > Key: MPLUGINTESTING-3 > URL: http://jira.codehaus.org/browse/MPLUGINTESTING-3 > Project: Maven 2.x Plugin Testing > Issue Type: Bug > Components: plugin-testing-harness >Reporter: Mark Hobson >Assignee: Mark Hobson > Fix For: 1.1 > > Attachments: patch.txt > > > Return a simple dependency conflict id in ArtifactStub since this is never > null in DefaultArtifact and can cause NPEs in tests. -- 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: (MSHARED-9) invoker doesn't properly handle paths with spaces
[
http://jira.codehaus.org/browse/MSHARED-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton moved MNG-3096 to MSHARED-9:
Affects Version/s: (was: 2.0.7)
(was: 2.0.6)
Fix Version/s: (was: Shared Components)
Component/s: (was: Shared)
maven-invoker
Key: MSHARED-9 (was: MNG-3096)
Project: Maven Shared Components (was: Maven 2)
> invoker doesn't properly handle paths with spaces
> -
>
> Key: MSHARED-9
> URL: http://jira.codehaus.org/browse/MSHARED-9
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-invoker
>Reporter: Brian Fox
>Assignee: Brian Fox
>
> In the case of a specified pom with a space in the path, the name isn't
> properly escaped. It is likely that other command line options have similar
> problems.
> if ( !"pom.xml".equals( pom.getName() ) )
> {
> logger
> .debug( "Specified POM file is not named \'pom.xml\'.
> Using the \'-f\' command-line option to accommodate non-standard filename..."
> );
> // FIXME: Handle quotes in localRepo directory path...
> cli.createArgument().setLine( "-f " + pom.getName() );
> }
--
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: (MPLUGINTESTING-4) maven-plugin-testing-tools causes bad version in deployed artifacts after tests are run
[ http://jira.codehaus.org/browse/MPLUGINTESTING-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3095 to MPLUGINTESTING-4: --- Affects Version/s: (was: 2.0.7) Fix Version/s: (was: 2.0.8) 1.1 Component/s: (was: Shared) plugin-testing-tools Key: MPLUGINTESTING-4 (was: MNG-3095) Project: Maven 2.x Plugin Testing (was: Maven 2) > maven-plugin-testing-tools causes bad version in deployed artifacts after > tests are run > --- > > Key: MPLUGINTESTING-4 > URL: http://jira.codehaus.org/browse/MPLUGINTESTING-4 > Project: Maven 2.x Plugin Testing > Issue Type: Bug > Components: plugin-testing-tools >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 1.1 > > > After running tests with the plugin testing tools, the actual jar artifact > contains /META-INF/maven/plugin.xml containing the test version instead of > the real version. In certain instances, this causes the plugin to fail at > runtime. -- 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: (MSHARED-10) [file-management] Add a parameter to throw or not IOException in delete( FileSet fileSet )
[ http://jira.codehaus.org/browse/MSHARED-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3294 to MSHARED-10: - Component/s: (was: Shared) file-management Key: MSHARED-10 (was: MNG-3294) Project: Maven Shared Components (was: Maven 2) > [file-management] Add a parameter to throw or not IOException in delete( > FileSet fileSet ) > -- > > Key: MSHARED-10 > URL: http://jira.codehaus.org/browse/MSHARED-10 > Project: Maven Shared Components > Issue Type: Improvement > Components: file-management >Reporter: Vincent Siveton >Assignee: Vincent Siveton > > Add a parameter in delete( FileSet fileSet ) to throw IOException when errors > have occurred by deleting files or directories. -- 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: (MSHARED-11) invoker MavenCommandLineBuilder#checkRequiredState() should not throw Exception if envvar M2_HOME exists
[ http://jira.codehaus.org/browse/MSHARED-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3298 to MSHARED-11: - Fix Version/s: (was: 2.0.8) Component/s: (was: Shared) maven-invoker Key: MSHARED-11 (was: MNG-3298) Project: Maven Shared Components (was: Maven 2) > invoker MavenCommandLineBuilder#checkRequiredState() should not throw > Exception if envvar M2_HOME exists > > > Key: MSHARED-11 > URL: http://jira.codehaus.org/browse/MSHARED-11 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-invoker >Reporter: Olivier Lamy >Assignee: Olivier Lamy > > currently MavenCommandLineBuilder#checkRequiredState() failed if > System.getProperty( "maven.home" ). > Whereas we can accept the envar M2_HOME. -- 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: (MSHARED-12) verifier doesn't close outputstreams
[ http://jira.codehaus.org/browse/MSHARED-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3465 to MSHARED-12: - Fix Version/s: (was: Shared Components) Component/s: (was: Shared) (was: integration tests) maven-verifier Key: MSHARED-12 (was: MNG-3465) Project: Maven Shared Components (was: Maven 2) > verifier doesn't close outputstreams > > > Key: MSHARED-12 > URL: http://jira.codehaus.org/browse/MSHARED-12 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-verifier >Reporter: Brian Fox >Assignee: Brian Fox > > The verifier isn't closing the output streams and on Windows, this causes ITs > to fail during the auto inserted clean:clean goal. -- 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: (MSHARED-13) [maven-reporting-impl] 2.0.4 uses old doxia-site-renderer with obsolete Renderer.createSink(..) call
[ http://jira.codehaus.org/browse/MSHARED-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MNG-3476 to MSHARED-13: - Component/s: (was: Shared) (was: Sites & Reporting) maven-reporting-impl Key: MSHARED-13 (was: MNG-3476) Project: Maven Shared Components (was: Maven 2) > [maven-reporting-impl] 2.0.4 uses old doxia-site-renderer with obsolete > Renderer.createSink(..) call > > > Key: MSHARED-13 > URL: http://jira.codehaus.org/browse/MSHARED-13 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-reporting-impl >Reporter: John Casey >Assignee: John Casey >Priority: Critical > > AbstractMavenReport calls Renderer.createSink(..) which is obsolete. The > doxia-site-renderer 1.0-alpha-10 release is newest, and Renderer interface in > that release doesn't contain this method...The site plugin avoids this > problem by creating its own Sink and side-stepping the call in > AbstractMavenReport, but this leaves plugin:report (for instance) to fail > when called on its own. > Since the 2.0.4 release of reporting-impl, many changes have been > incorporated, such that I cannot guarantee we won't see significant other > problems if we try to use it. (there are several abstract methods that seem > to have literally disappeared out of AbstractMavenReport, for example). I've > created a copy of the 2.0.4 tag for this project into: > https://svn.apache.org/repos/asf/maven/shared/branches/maven-reporting-impl-2.0.4.1-dev > to allow us to make a much smaller updated release without all the other > changes, just to help stabilize plugins like the maven-plugin-plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSHARED-14) Schedule and release maven-doxia-tools 1.0
[ http://jira.codehaus.org/browse/MSHARED-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MSITE-301 to MSHARED-14: -- Fix Version/s: (was: 2.0-beta-7) Component/s: (was: doxia integration) maven-doxia-tools Key: MSHARED-14 (was: MSITE-301) Project: Maven Shared Components (was: Maven 2.x Site Plugin) > Schedule and release maven-doxia-tools 1.0 > -- > > Key: MSHARED-14 > URL: http://jira.codehaus.org/browse/MSHARED-14 > Project: Maven Shared Components > Issue Type: Task > Components: maven-doxia-tools >Reporter: Lukas Theussl > -- 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: (MSHARED-15) DefaultSiteTools fails on paths with prefix "../"
[
http://jira.codehaus.org/browse/MSHARED-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton moved MSITE-319 to MSHARED-15:
--
Affects Version/s: (was: 2.0-beta-7)
Fix Version/s: (was: 2.0-beta-7)
Key: MSHARED-15 (was: MSITE-319)
Project: Maven Shared Components (was: Maven 2.x Site Plugin)
> DefaultSiteTools fails on paths with prefix "../"
> -
>
> Key: MSHARED-15
> URL: http://jira.codehaus.org/browse/MSHARED-15
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-doxia-tools
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>
> {noformat}
> [ERROR] NORMALIZE: ../../../../localhost/G/test/site
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1938)
> at org.codehaus.plexus.util.FileUtils.normalize(FileUtils.java:1101)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getNormalizedPath(DefaultSiteTool.java:199)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultSiteTool.java:246)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.appendMenuItem(DefaultSiteTool.java:1324)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenuItemsFromModels(DefaultSiteTool.java:1297)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.populateModules(DefaultSiteTool.java:927)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:551)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSHARED-15) DefaultSiteTools fails on paths with prefix "../"
[
http://jira.codehaus.org/browse/MSHARED-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MSHARED-15:
---
Component/s: maven-doxia-tools
> DefaultSiteTools fails on paths with prefix "../"
> -
>
> Key: MSHARED-15
> URL: http://jira.codehaus.org/browse/MSHARED-15
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-doxia-tools
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>
> {noformat}
> [ERROR] NORMALIZE: ../../../../localhost/G/test/site
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1938)
> at org.codehaus.plexus.util.FileUtils.normalize(FileUtils.java:1101)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getNormalizedPath(DefaultSiteTool.java:199)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultSiteTool.java:246)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.appendMenuItem(DefaultSiteTool.java:1324)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.populateModulesMenuItemsFromModels(DefaultSiteTool.java:1297)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.populateModules(DefaultSiteTool.java:927)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:551)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSHARED-16) stage dies at normalization of relative path
[ http://jira.codehaus.org/browse/MSHARED-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MSITE-315 to MSHARED-16: -- Affects Version/s: (was: 2.0-beta-7) Key: MSHARED-16 (was: MSITE-315) Project: Maven Shared Components (was: Maven 2.x Site Plugin) > stage dies at normalization of relative path > > > Key: MSHARED-16 > URL: http://jira.codehaus.org/browse/MSHARED-16 > Project: Maven Shared Components > Issue Type: Bug > Environment: Linux >Reporter: Martin von Gagern > Attachments: normalizeRelativePaths.patch, testcase.zip > > > Since r640091, DefaultSiteTool from maven-doxia-tools tries to normalize > paths, which fails, as the current plexus-utils don't handle normalization of > relative paths, and the stage mojo seems to use them quite extensively. > I have attached a small testcase, a parent project with a single child, and > site:stage as the default goal, so you can simply run "mvn" on the parent. > Debugging this shows that FileUtils.normalize is handed a path starting in > "../../". > I have also attached a patch to plexus-utils that makes FileUtils.normalize > handle relative paths, but I'm not sure if this would be intended, and I > can't test it, because I can't get maven use the latest snapshot of > plexus-utils, even if stated as an explicit dependency of the site plugin. > See also: > http://svn.apache.org/viewvc/maven/shared/trunk/maven-doxia-tools/src/main/java/org/apache/maven/doxia/tools/DefaultSiteTool.java?r1=637431&r2=640091&diff_format=h#l72 > http://fisheye.codehaus.org/browse/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java -- 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: (MSHARED-16) stage dies at normalization of relative path
[ http://jira.codehaus.org/browse/MSHARED-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MSHARED-16: --- Component/s: maven-doxia-tools > stage dies at normalization of relative path > > > Key: MSHARED-16 > URL: http://jira.codehaus.org/browse/MSHARED-16 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-doxia-tools > Environment: Linux >Reporter: Martin von Gagern > Attachments: normalizeRelativePaths.patch, testcase.zip > > > Since r640091, DefaultSiteTool from maven-doxia-tools tries to normalize > paths, which fails, as the current plexus-utils don't handle normalization of > relative paths, and the stage mojo seems to use them quite extensively. > I have attached a small testcase, a parent project with a single child, and > site:stage as the default goal, so you can simply run "mvn" on the parent. > Debugging this shows that FileUtils.normalize is handed a path starting in > "../../". > I have also attached a patch to plexus-utils that makes FileUtils.normalize > handle relative paths, but I'm not sure if this would be intended, and I > can't test it, because I can't get maven use the latest snapshot of > plexus-utils, even if stated as an explicit dependency of the site plugin. > See also: > http://svn.apache.org/viewvc/maven/shared/trunk/maven-doxia-tools/src/main/java/org/apache/maven/doxia/tools/DefaultSiteTool.java?r1=637431&r2=640091&diff_format=h#l72 > http://fisheye.codehaus.org/browse/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java -- 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: (MSHARED-19) getRelativePath fails on non-normalized inputs
[ http://jira.codehaus.org/browse/MSHARED-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MSITE-284 to MSHARED-19: -- Affects Version/s: (was: 2.0-beta-6) Fix Version/s: (was: 2.0-beta-7) Component/s: (was: relative links) maven-doxia-tools Key: MSHARED-19 (was: MSITE-284) Project: Maven Shared Components (was: Maven 2.x Site Plugin) > getRelativePath fails on non-normalized inputs > -- > > Key: MSHARED-19 > URL: http://jira.codehaus.org/browse/MSHARED-19 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-doxia-tools >Reporter: Benjamin Bentmann >Assignee: Dennis Lundberg >Priority: Minor > Attachments: normalized-paths.patch > > > The algo in AbstractSiteMojo.getRelativePath() assumes that its input paths > are both normalized and produces wrong output if it gets something like > "dir/../dir". Attached is a simple unit test and a fix for the method itself. > FYI, non-normalized path are easily created by Maven if one has a > non-Maven-like directory layout with > project/ > project-parent/ > project-module-1/ > where simple string/path concatenation produces a path like > "project/project-module-1/../project-parent" when referencing the parent POM > from the module POM. > Path/URL transformations like normalization/relativization/resolution are > quite ubiquitous in Maven. Isn't there a nice util class around that prevents > each and every plugin developer to reimplement those error-prone methods? -- 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: (MSHARED-17) Local Parent POM not found if specifies a directory
[
http://jira.codehaus.org/browse/MSHARED-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton moved MSITE-261 to MSHARED-17:
--
Affects Version/s: (was: 2.0-beta-5)
Fix Version/s: (was: 2.0-beta-7)
Component/s: (was: multi module)
maven-doxia-tools
Key: MSHARED-17 (was: MSITE-261)
Project: Maven Shared Components (was: Maven 2.x Site Plugin)
> Local Parent POM not found if specifies a directory
> --
>
> Key: MSHARED-17
> URL: http://jira.codehaus.org/browse/MSHARED-17
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-doxia-tools
> Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>Reporter: Benjamin Bentmann
>Assignee: Lukas Theussl
>Priority: Minor
> Attachments: site-parent-pom.patch, site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the element
> in a module POM to locate the parent POM, e.g.{code:xml}
> ...
> ../parent
> {code}will properly find the parent POM in "../parent/pom.xml".
> However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a
> different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is
> not already included somewhere in the Maven core (where is belongs IMHO).
--
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: (MSHARED-18) Inheritance of elements from site descriptor quite broken
[ http://jira.codehaus.org/browse/MSHARED-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton moved MSITE-279 to MSHARED-18: -- Affects Version/s: (was: 2.0-beta-6) Fix Version/s: (was: 2.0-beta-7) Component/s: (was: inheritance) maven-doxia-tools Key: MSHARED-18 (was: MSITE-279) Project: Maven Shared Components (was: Maven 2.x Site Plugin) > Inheritance of elements from site descriptor quite broken > - > > Key: MSHARED-18 > URL: http://jira.codehaus.org/browse/MSHARED-18 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-doxia-tools > Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP >Reporter: Benjamin Bentmann >Assignee: Vincent Siveton >Priority: Critical > Attachments: bug1.zip, bug2.zip, exception.txt, project.zip, > site-directory.patch, site-directory.patch > > > After updating to 2.0-beta-6, I never get proper site output for multi module > projects. I attached a simple dummy project that shall help to reproduce the > problem. > When I perform a reactor build of the site (i.e. "project-parent> mvn site"), > the pages of the sub module project-module-1 properly inherit most of the > decorator elements, except for the custom "overview" menu. That is, the site > of the sub module contains the menu configured for the parent project despite > the sub module specifying its own menu.- > In contrast, when I only build the site of the sub module (i.e. > "project-module-1> mvn site"), many decoration elements are not inherited > from the parent's site.xml like , , , . > However, now the sub module's site properly outputs its own menu items (i.e. > "Module-Item" instead of "Parent-Item" for the attached projects). > This issues might be a duplicate/relative of MSITE-256 but as I cannot safely > judge from its description, I opened a new issue. -- 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: (MEV-581) Impossible to use artifact in repo1 castor:xml-one-london
[ http://jira.codehaus.org/browse/MEV-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl moved MAVENREPOMAINT-3 to MEV-581: Workflow: jira (was: Maven New) Key: MEV-581 (was: MAVENREPOMAINT-3) Project: Maven Evangelism (was: Maven Repository Maintenance) > Impossible to use artifact in repo1 castor:xml-one-london > - > > Key: MEV-581 > URL: http://jira.codehaus.org/browse/MEV-581 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Joakim Erdfelt >Assignee: Carlos Sanchez > > The following artifact has a version number that is impossible to use ... > http://repo1.maven.org/maven2/castor/xml-one-london/ > Hint: There is a space at the end of the version number. -- 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: (MPA-114) Merge JIRA projects WAGONSSH, WAGONFTP and WAGONHTTP into the corresponding components over at WAGON
Merge JIRA projects WAGONSSH, WAGONFTP and WAGONHTTP into the corresponding components over at WAGON Key: MPA-114 URL: http://jira.codehaus.org/browse/MPA-114 Project: Maven Project Administration Issue Type: Task Components: Issue Management Reporter: Benjamin Bentmann Priority: Minor We currently have some duplicate spaces to go for wagon issues. There's WAGON which seems to be the primary project, having components for the various providers, and yet there are separate projects for WAGONSSH, WAGONFTP and WAGONHTTP. I guess the later ones should be moved into the components over at WAGON and then get removed. -- 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-114) Merge JIRA projects WAGONSSH, WAGONFTP and WAGONHTTP into the corresponding components over at WAGON
[ http://jira.codehaus.org/browse/MPA-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132798#action_132798 ] Brett Porter commented on MPA-114: -- +1, they are all being released on the same schedule anyway. I'd had this on my list - if there are no objections I'll go ahead in a couple of days > Merge JIRA projects WAGONSSH, WAGONFTP and WAGONHTTP into the corresponding > components over at WAGON > > > Key: MPA-114 > URL: http://jira.codehaus.org/browse/MPA-114 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Reporter: Benjamin Bentmann >Priority: Minor > > We currently have some duplicate spaces to go for wagon issues. There's WAGON > which seems to be the primary project, having components for the various > providers, and yet there are separate projects for WAGONSSH, WAGONFTP and > WAGONHTTP. I guess the later ones should be moved into the components over at > WAGON and then get removed. -- 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: (SCM-376) 'Username isn't defined.' when generating SCM report if CVS port number is specified in SCM URL
[ http://jira.codehaus.org/browse/SCM-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132803#action_132803 ] Geert Pante commented on SCM-376: - The password is not empty, I'm just using native CVS, with the password in ~/.cvspass. I'm using the third form from http://maven.apache.org/scm/cvs.html scm:cvspserver[username[[EMAIL PROTECTED]port]path_to_repositorymodule_name With the [password] left out, and [port] filled in. Maybe it's better to use an empty password for the continuum user, but we're not an open source company (yet) :-) > 'Username isn't defined.' when generating SCM report if CVS port number is > specified in SCM URL > --- > > Key: SCM-376 > URL: http://jira.codehaus.org/browse/SCM-376 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs, maven-scm-site >Affects Versions: 1.0 >Reporter: Geert Pante >Priority: Minor > > I have an CVS connection URL defined as follows: > scm:cvs:pserver:[EMAIL PROTECTED]:2401:/data01/cvsroot_bkh:VCG_BKH/uBaseBkh > When I try mvn site, the stage 'Generating "Source Repository" report.' fails > as shown below. > If I remove the :2401, it works OK. > [INFO] Generating "Source Repository" report. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Username isn't defined. > [INFO] > > [INFO] Trace > java.lang.IllegalArgumentException: Username isn't defined. > at > org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRootForCvsPass(CvsScmProviderRepository.java:105) > at > org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRoot(CvsScmProviderRepository.java:73) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.developerAccessCVS(ScmReport.java:479) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderDeveloperAccessSection(ScmReport.java:323) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:186) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:87) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) -- 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: (SCM-376) 'Username isn't defined.' when generating SCM report if CVS port number is specified in SCM URL
[ http://jira.codehaus.org/browse/SCM-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132804#action_132804 ] Dennis Lundberg commented on SCM-376: - Can you please try this URL instead: scm:cvs|pserver|[EMAIL PROTECTED]:2401|/data01/cvsroot_bkh|VCG_BKH/uBaseBkh > 'Username isn't defined.' when generating SCM report if CVS port number is > specified in SCM URL > --- > > Key: SCM-376 > URL: http://jira.codehaus.org/browse/SCM-376 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs, maven-scm-site >Affects Versions: 1.0 >Reporter: Geert Pante >Priority: Minor > > I have an CVS connection URL defined as follows: > scm:cvs:pserver:[EMAIL PROTECTED]:2401:/data01/cvsroot_bkh:VCG_BKH/uBaseBkh > When I try mvn site, the stage 'Generating "Source Repository" report.' fails > as shown below. > If I remove the :2401, it works OK. > [INFO] Generating "Source Repository" report. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Username isn't defined. > [INFO] > > [INFO] Trace > java.lang.IllegalArgumentException: Username isn't defined. > at > org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRootForCvsPass(CvsScmProviderRepository.java:105) > at > org.apache.maven.scm.provider.cvslib.repository.CvsScmProviderRepository.getCvsRoot(CvsScmProviderRepository.java:73) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.developerAccessCVS(ScmReport.java:479) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderDeveloperAccessSection(ScmReport.java:323) > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.renderBody(ScmReport.java:186) > at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65) > at > org.apache.maven.report.projectinfo.ScmReport.executeReport(ScmReport.java:87) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) -- 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: (MRELEASE-123) release plugin does not take commandline parameters into account
[ http://jira.codehaus.org/browse/MRELEASE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132806#action_132806 ] Benjamin Bentmann commented on MRELEASE-123: bq. but -N should definitely be copied to invoked command line I fully agree. That the Release Plugin is forking a Maven build is an implementation detail. A user shouldn't be bothered with pushing parameters down to this forked Maven invocation. By putting -N on the command line he stated his intention to perform a non-recursive build/release. What would be the rationale to repeat this intention? Are there use cases where the recursive flag would be different for the main build and the forked build? > release plugin does not take commandline parameters into account > > > Key: MRELEASE-123 > URL: http://jira.codehaus.org/browse/MRELEASE-123 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Jorg Heymans > > i would like to do a release of a top-level pom only : intuitively i do "mvn > -N release:prepare". During release preparation the -N parameter is left out > however and maven does a full integration on all child modules and > subsequently includes them in the release process. -- 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: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
Provide AspectJ 1.6 jars/poms/javadocs/sources -- Key: MEV-582 URL: http://jira.codehaus.org/browse/MEV-582 Project: Maven Evangelism Issue Type: Wish Reporter: David J. M. Karlsen Provide AspectJ 1.6 jars/poms/javadocs/sources -- 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: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjrt.tar Attached is a bundle - please check that it's OK. > Provide AspectJ 1.6 jars/poms/javadocs/sources > -- > > Key: MEV-582 > URL: http://jira.codehaus.org/browse/MEV-582 > Project: Maven Evangelism > Issue Type: Wish >Reporter: David J. M. Karlsen > Attachments: aspectjrt.tar > > > Provide AspectJ 1.6 jars/poms/javadocs/sources -- 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: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjtools.tar Bundle for tools - please check contents for potential errors. > Provide AspectJ 1.6 jars/poms/javadocs/sources > -- > > Key: MEV-582 > URL: http://jira.codehaus.org/browse/MEV-582 > Project: Maven Evangelism > Issue Type: Wish >Reporter: David J. M. Karlsen > Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar > > > Provide AspectJ 1.6 jars/poms/javadocs/sources -- 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: (MEV-582) Provide AspectJ 1.6 jars/poms/javadocs/sources
[ http://jira.codehaus.org/browse/MEV-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-582: Attachment: aspectjweaver.tar Bundle for weaver - please check contents for potential errors. > Provide AspectJ 1.6 jars/poms/javadocs/sources > -- > > Key: MEV-582 > URL: http://jira.codehaus.org/browse/MEV-582 > Project: Maven Evangelism > Issue Type: Wish >Reporter: David J. M. Karlsen > Attachments: aspectjrt.tar, aspectjtools.tar, aspectjweaver.tar > > > Provide AspectJ 1.6 jars/poms/javadocs/sources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3552) ProfileManager not available as a component
ProfileManager not available as a component
---
Key: MNG-3552
URL: http://jira.codehaus.org/browse/MNG-3552
Project: Maven 2
Issue Type: Improvement
Components: Profiles
Affects Versions: 2.0.9
Reporter: Kohsuke Kawaguchi
ProfileManager is currently not available as a component in plexus, so plugins
cannot get hold of it, unlike other components.
IOW, the following code won't work from Mojo.
{noformat}
/**
* @component
*/
private ProfileManager profileManager;
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2034) Please upload Concordion 1.3.0
Please upload Concordion 1.3.0 -- Key: MAVENUPLOAD-2034 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2034 Project: maven-upload-requests Issue Type: Wish Reporter: Jose M Beas http://concordion.googlecode.com/files/concordion-1.3.0-bundle.jar This is our first upload to the Maven Central Repository. I am one of the project members (please see http://code.google.com/p/concordion/ or ask David Peterson, the project owner) Thanks in advance, JMB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-184) Unable to differentiate JavaDoc reports when using multiple doclets
Unable to differentiate JavaDoc reports when using multiple doclets --- Key: MJAVADOC-184 URL: http://jira.codehaus.org/browse/MJAVADOC-184 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Anthony Whitford If you configure the javadoc plugin with a reportSet using 2 doclets (like the YDoc doclet, and the PDF doclet, for example), both reports appear on projects-reports.html with the same Document and Description. There is presently no way to differentiate them. I think a reasonable solution is to have the ability to overwrite the Document and Description for the generated reports page, so that I can label the PDF version as such. -- 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: (ARCHETYPE-163) Allow archetype to generate subprojects using a secondary archetype
Allow archetype to generate subprojects using a secondary archetype --- Key: ARCHETYPE-163 URL: http://jira.codehaus.org/browse/ARCHETYPE-163 Project: Maven Archetype Issue Type: New Feature Components: Archetypes Affects Versions: 2.0-alpha-2 Reporter: Gert Vanthienen Priority: Minor It would be nice to have the possibility to reuse another Maven archetype for generating a subproject in a multi-module archetype. Cfr. http://www.nabble.com/Developing-an-archetype%3A-delegation-access-to-parent--td16895144s177.html#a16895144 -- 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
