[jira] Commented: (MECLIPSE-394) Commandline Arguments do NOT override settings from pom.xml
[
http://jira.codehaus.org/browse/MECLIPSE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148190#action_148190
]
Brad Szabo commented on MECLIPSE-394:
-
I believe this is related to
[MNG-2974|http://jira.codehaus.org/browse/MNG-2974], in that SNAPSHOT plugin
versions are not being resolved and downloaded from the command line, even with
correct configuration for the SNAPSHOT repository in the {{settings.xml}}.
> Commandline Arguments do NOT override settings from pom.xml
> ---
>
> Key: MECLIPSE-394
> URL: http://jira.codehaus.org/browse/MECLIPSE-394
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Martin Höller
>
> It [was
> reported|http://www.nabble.com/Maven-eclipse-plugin---SNAPSHOT-2.5-and-wtp-2.0-to15845593s177.html]
> on the maven-users mailinglist, that specifying various command line
> arguments like {{-DdownloadSources=false -Declipse.wtpmanifest=true
> -Declipse.wtpapplicationxml=true -Dwtpversion=2.0}} has no effect. It turned
> out, that specifying this in the {{pom.xml}} file worked as expected.
> However, commandline arguments should always override settings from the pom.
--
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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[
http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Szabo updated ARCHETYPE-191:
-
Attachment: ReplaceAnyContextPropertyEnhancement-v2.patch
Attached a second version of the patch
{{ReplaceAnyContextPropertyEnhancement-v2.patch}}. This one properly handles
undefined properties.
> Ability to filter filenames (rename files) during project generation
>
>
> Key: ARCHETYPE-191
> URL: http://jira.codehaus.org/browse/ARCHETYPE-191
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Generator
>Affects Versions: 2.0-alpha-3
>Reporter: Wendy Smoak
> Fix For: 2.0-alpha-4
>
> Attachments: ReplaceAnyContextPropertyEnhancement-v2.patch,
> ReplaceAnyContextPropertyEnhancement.patch
>
>
> When generating a new project from an archetype, I need to filter not only
> values within files, but the names of the files themselves.
> For example, in .NET projects, the project files (.sln, .csproj) match the
> name of the solution or project rather than having a fixed name like Maven's
> pom.xml does.
> Another user raised a similar issue on the mailing list, the ability to
> filter in the name of Java source code files.
> See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[
http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Szabo updated ARCHETYPE-191:
-
Attachment: ReplaceAnyContextPropertyEnhancement.patch
Here is a patch that improves upon the token replacement to work with any
available context properties (not just {{artifactId}} & {{rootArtifactId}}). It
includes a test.
With this patch, any properties that are set can be used.
Example Archetype file:
{noformat}
example-archetype/src/main/resources/archetype-resources/module1/src/main/resources/__my-property__.properties
{noformat}
Example Generated output (where -DartifactId=sample2 -Dmy-property=arbitrary):
{noformat}
sample2/module1/src/main/resources/arbitrary.properties
{noformat}
> Ability to filter filenames (rename files) during project generation
>
>
> Key: ARCHETYPE-191
> URL: http://jira.codehaus.org/browse/ARCHETYPE-191
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Generator
>Affects Versions: 2.0-alpha-3
>Reporter: Wendy Smoak
> Fix For: 2.0-alpha-4
>
> Attachments: ReplaceAnyContextPropertyEnhancement.patch
>
>
> When generating a new project from an archetype, I need to filter not only
> values within files, but the names of the files themselves.
> For example, in .NET projects, the project files (.sln, .csproj) match the
> name of the solution or project rather than having a fixed name like Maven's
> pom.xml does.
> Another user raised a similar issue on the mailing list, the ability to
> filter in the name of Java source code files.
> See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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] Issue Comment Edited: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[
http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147841#action_147841
]
bszabo edited comment on ARCHETYPE-191 at 9/12/08 5:09 PM:
---
Thanks for adding this valuable feature Raphaël!
I just wanted to give an example of how this works (since I could not find an
example anywhere else and it may help others).
Files & directories which contain \_\_artifactId\_\_ or
\_\_rootArtifactId\_\_ are replaced by the property values.
Example Archetype file:
{noformat}
example-archetype/src/main/resources/archetype-resources/module1/src/main/resources/__rootArtifactId__.properties
{noformat}
Example Generated output (where -DartifactId=sample):
{noformat}
sample/module1/src/main/resources/sample.properties
{noformat}
was (Author: bszabo):
Thanks for adding this valuable feature Raphaël!
I just wanted to give an example of how this works (since I could not find an
example anywhere else and it may help others).
Files & directories which contain __artifactId__ or __rootArtifactId__ are
replaced by the property values.
Example Archetype file:
example-archetype/src/main/resources/archetype-resources/module1/src/main/resources/__rootArtifactId__.properties
Example Generated output (where -DartifactId=sample):
sample/module1/src/main/resources/sample.properties
> Ability to filter filenames (rename files) during project generation
>
>
> Key: ARCHETYPE-191
> URL: http://jira.codehaus.org/browse/ARCHETYPE-191
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Generator
>Affects Versions: 2.0-alpha-3
>Reporter: Wendy Smoak
> Fix For: 2.0-alpha-4
>
>
> When generating a new project from an archetype, I need to filter not only
> values within files, but the names of the files themselves.
> For example, in .NET projects, the project files (.sln, .csproj) match the
> name of the solution or project rather than having a fixed name like Maven's
> pom.xml does.
> Another user raised a similar issue on the mailing list, the ability to
> filter in the name of Java source code files.
> See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
[ http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147841#action_147841 ] Brad Szabo commented on ARCHETYPE-191: -- Thanks for adding this valuable feature Raphaël! I just wanted to give an example of how this works (since I could not find an example anywhere else and it may help others). Files & directories which contain __artifactId__ or __rootArtifactId__ are replaced by the property values. Example Archetype file: example-archetype/src/main/resources/archetype-resources/module1/src/main/resources/__rootArtifactId__.properties Example Generated output (where -DartifactId=sample): sample/module1/src/main/resources/sample.properties > Ability to filter filenames (rename files) during project generation > > > Key: ARCHETYPE-191 > URL: http://jira.codehaus.org/browse/ARCHETYPE-191 > Project: Maven Archetype > Issue Type: New Feature > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Wendy Smoak > Fix For: 2.0-alpha-4 > > > When generating a new project from an archetype, I need to filter not only > values within files, but the names of the files themselves. > For example, in .NET projects, the project files (.sln, .csproj) match the > name of the solution or project rather than having a fixed name like Maven's > pom.xml does. > Another user raised a similar issue on the mailing list, the ability to > filter in the name of Java source code files. > See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.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: (MRESOURCES-48) Failed to copy full contents from
[
http://jira.codehaus.org/browse/MRESOURCES-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123794
]
Brad Szabo commented on MRESOURCES-48:
--
I spoke too soon. It looks like an environment issue. After posting, I renamed
the local repository (mv ~/.m2/repository ~/.m2/repository.bkup) to run a
completely clean test and then started getting errors like this:
Downloading:
http://internal.repo.com/maven2/releases/package/name/project-parent/3/project-parent-3.pom
15K downloaded
[DEBUG] Artifact resolved
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0
POM. for project package.name:project-parent at
/home/builduser/.m2/repository/package/name/project-parent/3/project-parent-3.pom
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1405)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1377)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:528)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1255)
When I checked the downloaded parent POM file it turned out to be empty, so I
tried to simply copy a file and found out the real cause of the problem:
-bash$ cp pom.xml ~/.m2/test
cp: closing `/home/builduser/.m2/test': Disk quota exceeded
In my case /home/builduser is a mounted drive and I had not been aware of its
quota.
> Failed to copy full contents from
> -
>
> Key: MRESOURCES-48
> URL: http://jira.codehaus.org/browse/MRESOURCES-48
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Thomas Hart
>Priority: Blocker
> Attachments: error.log
>
>
> Every time i execute a maven i get the message: 'Failed to copy full
> contents'. I check the code from the class FileUtils and there is a simle
> File#length() compare.
> {code}
> if( source.length() != destination.length() )
> {
> final String message = "Failed to copy full contents from " + source +
> " to " + destination;
> throw new IOException( message );
> }
> {code}
> mvn -version
> Maven version: 2.0.7
> Java version: 1.5.0_04
> OS name: "windows xp" version: "5.1" arch: "x86"
--
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] Issue Comment Edited: (MRESOURCES-48) Failed to copy full contents from
[
http://jira.codehaus.org/browse/MRESOURCES-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123787
]
bszabo edited comment on MRESOURCES-48 at 2/15/08 8:30 AM:
---
I have this issue appearing consistently on a build using Maven 2.0.8,
Resources plugin version 2.2, and JDK 1.6.0_04 all running on RHEL 4. The JDK
bug referenced above I don't think applies to this issue, and obviously not to
my environment, but just for reference, the path length causing the problem is
only 146 characters.
was (Author: bszabo):
I have this issue appearing consistently on a build using Maven 2.0.8,
Resources plugin version 2.2, and JDK 1.6.0_04 all running on RHEL 4. The JDK
bug referenced above obviously does not apply to this environment, but just for
reference, the path length causing the problem is only 146 characters.
> Failed to copy full contents from
> -
>
> Key: MRESOURCES-48
> URL: http://jira.codehaus.org/browse/MRESOURCES-48
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Thomas Hart
>Priority: Blocker
> Attachments: error.log
>
>
> Every time i execute a maven i get the message: 'Failed to copy full
> contents'. I check the code from the class FileUtils and there is a simle
> File#length() compare.
> {code}
> if( source.length() != destination.length() )
> {
> final String message = "Failed to copy full contents from " + source +
> " to " + destination;
> throw new IOException( message );
> }
> {code}
> mvn -version
> Maven version: 2.0.7
> Java version: 1.5.0_04
> OS name: "windows xp" version: "5.1" arch: "x86"
--
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: (MRESOURCES-48) Failed to copy full contents from
[
http://jira.codehaus.org/browse/MRESOURCES-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123787
]
Brad Szabo commented on MRESOURCES-48:
--
I have this issue appearing consistently on a build using Maven 2.0.8,
Resources plugin version 2.2, and JDK 1.6.0_04 all running on RHEL 4. The JDK
bug referenced above obviously does not apply to this environment, but just for
reference, the path length causing the problem is only 146 characters.
> Failed to copy full contents from
> -
>
> Key: MRESOURCES-48
> URL: http://jira.codehaus.org/browse/MRESOURCES-48
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Thomas Hart
>Priority: Blocker
> Attachments: error.log
>
>
> Every time i execute a maven i get the message: 'Failed to copy full
> contents'. I check the code from the class FileUtils and there is a simle
> File#length() compare.
> {code}
> if( source.length() != destination.length() )
> {
> final String message = "Failed to copy full contents from " + source +
> " to " + destination;
> throw new IOException( message );
> }
> {code}
> mvn -version
> Maven version: 2.0.7
> Java version: 1.5.0_04
> OS name: "windows xp" version: "5.1" arch: "x86"
--
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-2972) Ignores version of plugin dependency specified in my pom
[ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97137 ] Brad Szabo commented on MNG-2972: - I also ran into this issue a couple months back. See my post on the Users list http://www.nabble.com/-Maven2--xmlbeans-maven-plugin-IssueStAX-transitive-dependencies-t3359711s177.html One issue that I discovered which is related to the overriding behavior in question is that if I added a few more dependencies to the POM, all of a sudden the dependency version that I specified in my plugin declaration DID successfully override the plugin version. I could consistently get the plugin override to work after adding 5 or 6 more seemingly random jars to my dependency list. > Ignores version of plugin dependency specified in my pom > > > Key: MNG-2972 > URL: http://jira.codehaus.org/browse/MNG-2972 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 > Environment: maven 2.0.6, java version "1.5.0_07" >Reporter: Derek Alexander >Priority: Critical > > xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0 > I want to use xmlbeans-2.2.0 > So in my pom I put: > > org.codehaus.mojo > xmlbeans-maven-plugin > > > > xmlbeans > > > > > ... > > > > xmlbeans > xbean > 2.2.0 > > >But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it > is using as it doesn't seem to output stuff like that. Couldn't see a verbose > or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0. > Seems like I'm not the first to experience this: > http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092 > Apparently this should be possible: http://maven.apache.org/pom.html#plugins > "dependencies: Dependencies are seen a lot within the POM, and are an element > under all plugins element blocks. The dependencies have the same structure > and function as under that base build. The major difference in this case is > that instead of applying as dependencies of the project, they now apply as > dependencies of the plugin that they are under. The power of this is to alter > the dependency list of a plugin, perhaps by removing an unused runtime > dependency via exclusions, or by altering the version of a required > dpendency. See above under Dependencies for more information." -- 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-2969) Unable to exclude a dependency from a needed plugin
[ http://jira.codehaus.org/browse/MNG-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97135 ] Brad Szabo commented on MNG-2969: - The reason I have been interested in excluding/overriding a plugin dependency stems from the issue described in MOJO-687. The short explanation is that the xmlbeans-maven-plugin v2.0.0 has a transitive dependency (xmlbeans-jsr173-api) which does not exist anywhere. This makes the plugin unusable without local modification to the plugin POM. So in that case, one could argue that the plugin writer unfortunately did not know better :( It would be nice to quickly work around this by being able to exclude the non-existent transitive dependency. > Unable to exclude a dependency from a needed plugin > --- > > Key: MNG-2969 > URL: http://jira.codehaus.org/browse/MNG-2969 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Stefano Bagnara > > When we add a "standard" dependency we can tune its dependency list using the > exclusions directive. > THis is not possible with plugins. > Let's say I add javacc-maven-plugin to my build/plugins section and the > plugin declared in its pom: > > org.codehaus.plexus > plexus-utils > 1.0.4 > > And I know that this dependency is a compile dependency and I won't need it, > how can I tune my plugin inclusion so to not download plexus-utils? > in I can add new dependencies to plugin (WHY is this > needed?) but I cannot exclude existing dependencies: isn't this a bug? > I can add a new dependency to the plugin and add exclusions for this new > dependency but I cannot add an exclusion for the top-level dependencies. > Am I missing something? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[ http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90178 ] Brad Szabo commented on SUREFIRE-300: - I should clarify, this NPE occurs if you do not have a dependency on either 'junit' or 'testng' declared in your project. > NPE in SurefirePlugin.constructSurefireBooter() > --- > > Key: SUREFIRE-300 > URL: http://jira.codehaus.org/browse/SUREFIRE-300 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Niklas Gustavsson > Assigned To: Jason van Zyl > Fix For: 2.3.1 > > Attachments: npe.log > > > SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are > present in the project. The log attached is from building FtpServer admin-gui > using the 2.3 version of maven-surefire-plugin: > http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-300) NPE in SurefirePlugin.constructSurefireBooter()
[ http://jira.codehaus.org/browse/SUREFIRE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90170 ] Brad Szabo commented on SUREFIRE-300: - This appears to happen if you do not have a dependency on junit declared in your project. > NPE in SurefirePlugin.constructSurefireBooter() > --- > > Key: SUREFIRE-300 > URL: http://jira.codehaus.org/browse/SUREFIRE-300 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Niklas Gustavsson > Assigned To: Jason van Zyl > Fix For: 2.3.1 > > Attachments: npe.log > > > SurefirePlugin.constructSurefireBooter() throws NPE when no testcases are > present in the project. The log attached is from building FtpServer admin-gui > using the 2.3 version of maven-surefire-plugin: > http://svn.apache.org/repos/asf/incubator/ftpserver/trunk/admin-gui/ -- 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-2842) Developers and Contributors information is not being inherited
Developers and Contributors information is not being inherited -- Key: MNG-2842 URL: http://jira.codehaus.org/browse/MNG-2842 Project: Maven 2 Issue Type: Bug Components: Documentation: Guides, Inheritance and Interpolation Affects Versions: 2.0.5, 2.0.4 Environment: Linux (Fedora Core 6) JDK 1.5.0_10 Reporter: Brad Szabo The developers and contributors information is not being merged into the effective POM of child projects. According to the Project Inheritance section of the following two POM references, this info should be merged. http://maven.apache.org/guides/introduction/introduction-to-the-pom.html http://maven.apache.org/pom.html#Inheritance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-47) Cannot find .cvspass file. Documentation not up-to-date.
[ http://jira.codehaus.org/browse/MCHANGELOG-47?page=comments#action_74935 ] Brad Szabo commented on MCHANGELOG-47: -- I take that back, you cannot just create an empty .cvspass file in your home directory to gain anonymous access, but if you actually connect to that CVS server and login, it will create an anonymous entry that should enable the plugin to work. cvs -d :pserver:anonymous:@cvs.apache.org:/cvs/root:module login > Cannot find .cvspass file. Documentation not up-to-date. > - > > Key: MCHANGELOG-47 > URL: http://jira.codehaus.org/browse/MCHANGELOG-47 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Maven2 on Windows in Eclipse with CVS (anonymous pserver) > Maven2 on GenToo in CruiseControl with CVS (anonymous pserver) >Reporter: Paul R. Saxman > > I've run into a few issues while using this plugin, which are as follows: > - When I try to run the Maven 2 changelog plugin in Eclipse or using > CruiseControl, I get an error that the file .cvspass cannot be found. > - I've found a reference to the .cvspass file on the Maven 1 plugin > documentation, but not in the Maven 2 documentation. > - The Maven 2 documentation specifies to use the groupId > org.apache.maven.plugins for the plugin, which doesn't exist on ibiblio. The > plugin actually exists at org.codehaus.mojo; HOWEVER, it is not documented as > being part of Mojo at http://mojo.codehaus.org. > - When I follow the Maven 1 instructions to generate the .cvspass file, I get > the error "The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does > not exist or no valid version could be found". > - Passing in a password (which doesn't really exist since I'm using an > anonymous pserver) using the Maven 2 plugin "password" parameter has no > effect, which is consistent with the documentation. Is there any way to not > bother with a password or to specify an empty password? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-47) Cannot find .cvspass file. Documentation not up-to-date.
[ http://jira.codehaus.org/browse/MCHANGELOG-47?page=comments#action_74927 ] Brad Szabo commented on MCHANGELOG-47: -- I agree, this plugin needs some better documentation. You can create an empty .cvspass file in your home directory to gain anonymous access. The username must have a delimiter after it i.e. scm:cvs:pserver:anonymous:@cvs.apache.org:/cvs/root:module You can also add the Maven snapshot repository to your pom pluginRespositories to download the latest version. http://people.apache.org/maven-snapshot-repository The snapshot is located at http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-changelog-plugin/ > Cannot find .cvspass file. Documentation not up-to-date. > - > > Key: MCHANGELOG-47 > URL: http://jira.codehaus.org/browse/MCHANGELOG-47 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 > Environment: Maven2 on Windows in Eclipse with CVS (anonymous pserver) > Maven2 on GenToo in CruiseControl with CVS (anonymous pserver) >Reporter: Paul R. Saxman > > I've run into a few issues while using this plugin, which are as follows: > - When I try to run the Maven 2 changelog plugin in Eclipse or using > CruiseControl, I get an error that the file .cvspass cannot be found. > - I've found a reference to the .cvspass file on the Maven 1 plugin > documentation, but not in the Maven 2 documentation. > - The Maven 2 documentation specifies to use the groupId > org.apache.maven.plugins for the plugin, which doesn't exist on ibiblio. The > plugin actually exists at org.codehaus.mojo; HOWEVER, it is not documented as > being part of Mojo at http://mojo.codehaus.org. > - When I follow the Maven 1 instructions to generate the .cvspass file, I get > the error "The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does > not exist or no valid version could be found". > - Passing in a password (which doesn't really exist since I'm using an > anonymous pserver) using the Maven 2 plugin "password" parameter has no > effect, which is consistent with the documentation. Is there any way to not > bother with a password or to specify an empty password? -- 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
