[jira] Commented: (MRESOURCES-43) resources:resources overwrites destination files when filtering is on, not when filtering is off
[ http://jira.codehaus.org/browse/MRESOURCES-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148834#action_148834 ] Olivier Lamy commented on MRESOURCES-43: Can you provide a simple test case ? I think MRESOURCES-21 should fix that. Can you check with trunk or 2.3-SNAPSHOT ? Thanks > resources:resources overwrites destination files when filtering is on, not > when filtering is off > > > Key: MRESOURCES-43 > URL: http://jira.codehaus.org/browse/MRESOURCES-43 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: Linux >Reporter: Roar Lauritzsen >Assignee: Olivier Lamy > Fix For: 2.3 > > > It is not possible to specify that resources:resources should overwrite > destination files or not if they already exist. > However, the behavior should at the very least be predictable so that one can > achieve the desired result through phase ordering or ant scripts. > As it is today, when filtering is turned on, destination files are > overwritten. When filtering is off, destination files are not overwritten. > If not selectable, the most practical solution would be to always overwrite > (I believe). -- 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-24) Force overwrite resources defined in profiles
[ http://jira.codehaus.org/browse/MRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148833#action_148833 ] Olivier Lamy commented on MRESOURCES-24: Can you provide a simple test case ? I think MRESOURCES-21 should fix that. Can you check with trunk or 2.3-SNAPSHOT ? Thanks > Force overwrite resources defined in profiles > - > > Key: MRESOURCES-24 > URL: http://jira.codehaus.org/browse/MRESOURCES-24 > Project: Maven 2.x Resources Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Kees de Kooter >Assignee: Olivier Lamy > Fix For: 2.3 > > > I am using profiles to package for different environments. The profile > typically defines a couple of properties files with db and log settings. > The resource plugin only overwrites files that are changed, so the profile > specific resources with the same name are ignored and the wrong resources are > packaged. > I could do a clean first, but that seems a bit of a crude approach. > I would prefer to have a property like "overwrite=true" on a resource. -- 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: (MRESOURCES-58) Filter not working on src/test/resources
[ http://jira.codehaus.org/browse/MRESOURCES-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRESOURCES-58. -- Resolution: Not A Bug Fix Version/s: (was: 2.3) I don't where is the issue here ? If you have more details, please reopen the issue. > Filter not working on src/test/resources > > > Key: MRESOURCES-58 > URL: http://jira.codehaus.org/browse/MRESOURCES-58 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: OS: Linux (Ubuntu gutsy) 2.6.22-14-generic. > Maven: 2.0.8 >Reporter: Lorand Somogyi >Assignee: Olivier Lamy > Attachments: test.zip > > > Filter does not work for test-resources. > I tried: > 1. No definition in pom.xml > 2. Defining the resource in pom.xml > In the attached really basic case the property comes from pom.xml property, > but it does fail for filter file too. And even for default pom.xml variables > too... -- 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-58) Filter not working on src/test/resources
[
http://jira.codehaus.org/browse/MRESOURCES-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148831#action_148831
]
Olivier Lamy commented on MRESOURCES-58:
As in your pom there is
{code:xml}
src/test/resources
true
{code}
The filtered result is in in target/classes and a non filtered file is in
target/test-classes.
You have to use
{code:xml}
src/test/resources
true
{code}
> Filter not working on src/test/resources
>
>
> Key: MRESOURCES-58
> URL: http://jira.codehaus.org/browse/MRESOURCES-58
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: OS: Linux (Ubuntu gutsy) 2.6.22-14-generic.
> Maven: 2.0.8
>Reporter: Lorand Somogyi
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: test.zip
>
>
> Filter does not work for test-resources.
> I tried:
> 1. No definition in pom.xml
> 2. Defining the resource in pom.xml
> In the attached really basic case the property comes from pom.xml property,
> but it does fail for filter file too. And even for default pom.xml variables
> too...
--
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: (MRESOURCES-74) configuring file extension to not filtering
[ http://jira.codehaus.org/browse/MRESOURCES-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRESOURCES-74. -- Resolution: Fixed fixed in rev [698374|http://svn.apache.org/viewvc?rev=698374&view=rev] > configuring file extension to not filtering > --- > > Key: MRESOURCES-74 > URL: http://jira.codehaus.org/browse/MRESOURCES-74 > Project: Maven 2.x Resources Plugin > Issue Type: New Feature >Affects Versions: 2.1, 2.2, 2.3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.3 > > > Currently if filtered directories contains some binaries files they will be > filtered. > The maven-filtering has some default extensions (jpg, jpeg, gif, bmp, png) to > not apply filters but users must be able to add some. > Note : users can do it but they need to add some extra includes excludes > configuration elements. -- 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-3763) Site / Dependency / Classifier Issue
Site / Dependency / Classifier Issue Key: MNG-3763 URL: http://jira.codehaus.org/browse/MNG-3763 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.1.0-M1, 2.0.9 Environment: Maven 2.0.9, Maven 2.1.0-M1, Windows, CentOS Reporter: Geoffrey Wiseman Attachments: dependency-site-bug.zip When the attached project is run with "mvn clean install" it's successful. When "mvn clean install site" is run, the build fails to compile. Seems like it's a bug, not sure where the bug lies. -- 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: (MINVOKER-66) Reduce log level for install goal output to debug
[
http://jira.codehaus.org/browse/MINVOKER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-66.
-
Resolution: Won't Fix
Fix Version/s: (was: 1.3)
Reverted in [r698334|http://svn.apache.org/viewvc?view=rev&revision=698334].
The artifact installer can potentially be used by multiple threads so we cannot
safely hack its logger without affecting its other clients.
> Reduce log level for install goal output to debug
> -
>
> Key: MINVOKER-66
> URL: http://jira.codehaus.org/browse/MINVOKER-66
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.2.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
>
> The staging of artifacts to the test repo is currently logged with one
> message per file at info level. With the support for staging of all
> dependencies (MINVOKER-64) this heavily floods the console. We should try to
> grab the logger for the {{ArtifactInstaller}} and have it output its original
> INFO messages at DEBUG level to reduce the noise.
--
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: (MREACTOR-5) Can't resume a make build
[ http://jira.codehaus.org/browse/MREACTOR-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed MREACTOR-5. --- Resolution: Fixed Fix Version/s: 1.0 Fixed revision 698326 > Can't resume a make build > - > > Key: MREACTOR-5 > URL: http://jira.codehaus.org/browse/MREACTOR-5 > Project: Maven 2.x Reactor Plugin > Issue Type: New Feature >Reporter: Dan Fabulich > Fix For: 1.0 > > > If you run reactor:make, it will launch mvn with -r, using a specific set of > include files. If you want to resume a reactor:make from the middle, you > can't, even with -Dmake.goals=reactor:resume, because that would just run > reactor:resume on every sub-project. > Instead, reactor:make should accept -Dfrom and -DfromArtifact just like > reactor:resume. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MINVOKER-66) Reduce log level for install goal output to debug
[
http://jira.codehaus.org/browse/MINVOKER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann reopened MINVOKER-66:
---
The implementation as is also suppresses logging of the artifact installer in
other plugins: I erroneously assumed the [instantiation
strategy|http://plexus.codehaus.org/ref/component-configuration.html] would be
per-lookup but is usually singleton. Even if the default weren't like this,
relying on such an assumption is a bad idea.
Either come up with up reliable/safe solution of revert it.
> Reduce log level for install goal output to debug
> -
>
> Key: MINVOKER-66
> URL: http://jira.codehaus.org/browse/MINVOKER-66
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.2.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.3
>
>
> The staging of artifacts to the test repo is currently logged with one
> message per file at info level. With the support for staging of all
> dependencies (MINVOKER-64) this heavily floods the console. We should try to
> grab the logger for the {{ArtifactInstaller}} and have it output its original
> INFO messages at DEBUG level to reduce the noise.
--
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: (MREACTOR-5) Can't resume a make build
Can't resume a make build - Key: MREACTOR-5 URL: http://jira.codehaus.org/browse/MREACTOR-5 Project: Maven 2.x Reactor Plugin Issue Type: New Feature Reporter: Dan Fabulich If you run reactor:make, it will launch mvn with -r, using a specific set of include files. If you want to resume a reactor:make from the middle, you can't, even with -Dmake.goals=reactor:resume, because that would just run reactor:resume on every sub-project. Instead, reactor:make should accept -Dfrom and -DfromArtifact just like reactor:resume. -- 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: (MCHECKSTYLE-103) Error in site whith 2 Regexp checks
Error in site whith 2 Regexp checks --- Key: MCHECKSTYLE-103 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-103 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Windows, Maven 1.7, Java 5 Reporter: Benjamin Pochat Attachments: checkstyle-result.xml, screenshot.JPG I have 2 different Regexp checks with 2 different regular expressions as described above. In the site, in the "Rules" part, I have 2 lines for the 2 checks. This is ok. The issue is that the 2 lines have the same number of violations, wherease the second regexp is never matched over the whole project (cf the screenshot and the xml result provided as an attachment). -- 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-2208) Upload request for mvn-gwt-plugin
Upload request for mvn-gwt-plugin - Key: MAVENUPLOAD-2208 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2208 Project: Maven Upload Requests Issue Type: Wish Reporter: Roald Bankras Attachments: mvn-gwt-plugin-1.0.4-bundle.jar http://mvn-gwt-plugin.googlecode.com/files/mvn-gwt-plugin-1.0.4-bundle.jar http://code.google.com/p/mvn-gwt-plugin/ I'm the project owner and my brother is owner of bankras.net. You can reach me by email through [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MIDEA-115) Allow the user to provide IDEA project file (.ipr, .iml, .iws) templates (project.xml, module.xml, workspace.xml)
Allow the user to provide IDEA project file (.ipr, .iml, .iws) templates (project.xml, module.xml, workspace.xml) - Key: MIDEA-115 URL: http://jira.codehaus.org/browse/MIDEA-115 Project: Maven 2.x IDEA Plugin Issue Type: New Feature Affects Versions: 2.3 Reporter: Raul Igrisan It would be simple to implement it by adding config parameters and very helpful if the user wants to add unsupported options to the generated files (e.g. compiler arguments). -- 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: (MINVOKER-67) Create interpolated settings file in cloneProjectsTo directory and keep it after execution
[
http://jira.codehaus.org/browse/MINVOKER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-67.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.3
Done in [r698174|http://svn.apache.org/viewvc?view=rev&revision=698174].
> Create interpolated settings file in cloneProjectsTo directory and keep it
> after execution
> --
>
> Key: MINVOKER-67
> URL: http://jira.codehaus.org/browse/MINVOKER-67
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.2.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.3
>
>
> When the IT projects are cloned via {{cloneProjectsTo}}, we should also save
> the interpolated settings file in there. This eliminates the requirement to
> delete the interpolated settings, allowing the user to inspect its effective
> contents after plugin execution.
--
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: (MINVOKER-67) Create interpolated settings file in cloneProjectsTo directory and keep it after execution
Create interpolated settings file in cloneProjectsTo directory and keep it
after execution
--
Key: MINVOKER-67
URL: http://jira.codehaus.org/browse/MINVOKER-67
Project: Maven 2.x Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.2.1
Reporter: Benjamin Bentmann
Priority: Minor
When the IT projects are cloned via {{cloneProjectsTo}}, we should also save
the interpolated settings file in there. This eliminates the requirement to
delete the interpolated settings, allowing the user to inspect its effective
contents after plugin execution.
--
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: (MCHECKSTYLE-102) errors in site for regexp checks with "message" property
errors in site for regexp checks with "message" property
Key: MCHECKSTYLE-102
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-102
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Windows, JDK1.5, Maven 1.7
Reporter: Benjamin Pochat
Attachments: screenshot.JPG
Hi,
It seems that the site built by the CheckStyle plugin is wrong if we use regexp
check containing the "message" property.
The error is in the total of violations by rule ("Rules" part). The number of
violation is always null for such checks, even if checkstyle shows such
violations in the "Details" part.
For instance, i tried this check :
A screen shot of the site is given as an attachment.
If I remove the message property in the check definition, the site is correct.
--
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=148792#action_148792 ] Geir Pettersen commented on ARCHETYPE-191: -- This is exactly what I am looking for. I notice that 2.0-alpha-4-SNAPSHOT plugin already exists in the snapshot repositories and I assume that this fix should be included there as the issue has been marked as "fixed" , right? If so, how do i tell Maven to use 2.0-alpha-4-SNAPSHOT instead of 2.0-alpha-3 ? I tried running "mvn -U archetype:generate .." but it still uses 2.0-alpha-3. Thank you very much! > 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] Closed: (MINVOKER-66) Reduce log level for install goal output to debug
[
http://jira.codehaus.org/browse/MINVOKER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-66.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.3
Done in [r698131|http://svn.apache.org/viewvc?view=rev&revision=698131].
> Reduce log level for install goal output to debug
> -
>
> Key: MINVOKER-66
> URL: http://jira.codehaus.org/browse/MINVOKER-66
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.2.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.3
>
>
> The staging of artifacts to the test repo is currently logged with one
> message per file at info level. With the support for staging of all
> dependencies (MINVOKER-64) this heavily floods the console. We should try to
> grab the logger for the {{ArtifactInstaller}} and have it output its original
> INFO messages at DEBUG level to reduce the noise.
--
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: (MCOMPILER-80) Change default source level to 1.5
Change default source level to 1.5 -- Key: MCOMPILER-80 URL: http://jira.codehaus.org/browse/MCOMPILER-80 Project: Maven 2.x Compiler Plugin Issue Type: Improvement Reporter: Grzegorz Borkowski Priority: Minor Deafult source level setting for Maven compiler plugin is 1.3, as far as I remember. This makes no sense. 1.3 is used at this moment only in legacy applications. Probability of porting such legacy application to Maven 2 is very small. I was working with such applications - none of them used Maven. In fact, I don't know any application using Maven, which requires level 1.3. On the other hand, Maven is used exensively in new applications. Most of them use Java 5 features (annotations, generics...). All new applications I create use Maven 2 and Java 5. Every time I setup such application it makes me crazy that I get errors on my generics and annoations, and I have to setup manually the source level to 1.5. Come on, we have year 2008, not 2000! Java 5 is here for several years already. So why Maven compiler plugin does not use the most reasonable default approach, instead it still assumes we are in 2000 year? If someone wants to use old java version, than he can change the source level. By default should be 1.5. The default setting can be changed in never wersion of maven compiler 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] Created: (MIDEA-114) Wrong regex for splitting paths in Library (classes, sources and javadocs) -- Breaks paths containing whitespaces, doesn't obbey system path separator
Wrong regex for splitting paths in Library (classes, sources and javadocs) -- Breaks paths containing whitespaces, doesn't obbey system path separator -- Key: MIDEA-114 URL: http://jira.codehaus.org/browse/MIDEA-114 Project: Maven 2.x IDEA Plugin Issue Type: Bug Affects Versions: 2.2, 2.3 Reporter: Raul Igrisan Attachments: maven-idea-plugin.MIDEA-paths_split.patch org.apache.maven.plugin.idea.Library should use "[" + File.pathSeparatorChar + "]+" instead of "[,\\s]+" also needed refactoring (extract method) since the code is duplicated 3 times I have attached my patch (needs whitespace formatting) -- 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=148784#action_148784 ] Mickaël Leduque commented on ARCHETYPE-191: --- Is the "any property" feature merged in? The artifactId version seems far too limited... > 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] Created: (SCM-413) scm:bootstrap example needs updating or a warning associated with it
scm:bootstrap example needs updating or a warning associated with it Key: SCM-413 URL: http://jira.codehaus.org/browse/SCM-413 Project: Maven SCM Issue Type: Improvement Components: documentation Affects Versions: 1.1 Environment: Documentation Reporter: Andy Stocks Priority: Minor The scm:bootstrap example ( http://maven.apache.org/scm/plugins/examples/bootstrapping-with-pom.html ) shows how to use a pom file and maven to set up a project from scratch, pulling source code from a repository. What it doesn't mention is a situation that can occur once the code is checked out and the operation has finished. The bootstrap pom file remains - should you accidentally run an mvn clean with this pom (as the example shows) it will remove all the source code that has been checked out via the scm:bootstrap command. Unfortunately, this may be done by accident after many local changes have been made to the checked out source - losing all the changes not checked in. I think *it should be made very clear* in the example of this issue (or the example should be modified to either recommend removal of the bootstrap pom, or if it's possible include some mark-up to disable the clean operation (is this possible?)). This has made the case for using Maven more difficult to annoyed team members, in one case losing several days of work. -- 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-472) Add support for view by groups in the surefire report
[ http://jira.codehaus.org/browse/SUREFIRE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148783#action_148783 ] Erik Drolshammer commented on SUREFIRE-472: --- It would be nice of they at least where attached, yes. > Add support for view by groups in the surefire report > -- > > Key: SUREFIRE-472 > URL: http://jira.codehaus.org/browse/SUREFIRE-472 > Project: Maven Surefire > Issue Type: Improvement > Components: TestNG support >Affects Versions: 2.4.2 > Environment: Linux, java 1.6 >Reporter: Erik Drolshammer > Fix For: Future > > > The group annotation in testng is really useful. It would be even more useful > if Maven had a report that could show these groups. See mail thread on the > testng list for details: > http://forums.opensymphony.com/thread.jspa?messageID=334370&tstart=0 > I.e., something like the report in http://testng.org/test-output/index.html > cannot be found in > http://maven.apache.org/plugins/maven-surefire-report-plugin/surefire-report.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: (MINVOKER-66) Reduce log level for install goal output to debug
Reduce log level for install goal output to debug
-
Key: MINVOKER-66
URL: http://jira.codehaus.org/browse/MINVOKER-66
Project: Maven 2.x Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.2.1
Reporter: Benjamin Bentmann
Priority: Minor
The staging of artifacts to the test repo is currently logged with one message
per file at info level. With the support for staging of all dependencies
(MINVOKER-64) this heavily floods the console. We should try to grab the logger
for the {{ArtifactInstaller}} and have it output its original INFO messages at
DEBUG level to reduce the noise.
--
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
