Re: [ANN] Maven 2.1.0-M1 Released
Where is this new make-like reactor documented? Is it part of 2.1.0-M1? I also could not find a tag for 2.1.0-M1 in Subversion, so verifying what is actually part of 2.1.0-M1 is a bit difficult. Asgeir On Fri, Sep 19, 2008 at 10:33, Brett Porter [EMAIL PROTECTED] wrote: Well that isn't too surprising since it's not in the download area at all (!) I've copied it across form the deployed repository and it should be syncing shortly... - Brett 2008/9/19 Mark Derricutt [EMAIL PROTECTED]: I just tried downloading it by non of the mirrors I tried seemed to have it - I gave up after about 10 mirrors - will try downloading again in a few hours, probably just taking its time to propagate.. On Fri, Sep 19, 2008 at 8:13 PM, Brett Porter [EMAIL PROTECTED] wrote: However I did notice a problem with the site since it was deployed, will update it again now. -- It is easier to optimize correct code than to correct optimized code. -- Bill Harlan -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to disable a plugin?
In the submodule where you don't want the plugin to run, add a plugin element with the following elements within: executions execution idsome-id/id phasenone/phase /execution /executions On Fri, Sep 5, 2008 at 08:40, youhaodeyi [EMAIL PROTECTED] wrote: In the parent pom, it includes copy-dependency plugin which I want to disable in the child pom. I use this configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId inheritedfalse/inherited /plugin But every time running 'mvn package', it will copy all the dependencies to the child module. How can I disable this? -- View this message in context: http://www.nabble.com/How-to-disable-a-plugin--tp19325716p19325716.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: from workaround to workaround 1
Wolfgang, For test resources you should use the testResources element, not the resources element. The documentation is a bit shallow on this matter. Asgeir On Fri, Sep 5, 2008 at 08:46, [EMAIL PROTECTED] wrote: Hi, here is a small story about working with Maven. In my experience of 6 months now this happened very often like this. Maven is very hard to manage, not intuitive and error messages are incomprehensible or misleading. The problem: We have 5 Maven projects with sub projects. For test classes, the database connection should be defined only once, we put it into the user's settings.xml. Now, how accessing the db-properties in test classes? First idea: Filtering! I created properties file in the test/resources directories and tried to filter db properties from the settings properties with resources resource directorysrc/test/resources/directory filteringtrue/filtering /resource /resources Nothing happens. Filtering seems to be possible only in main/resources. Then I ask myself why have I to define a directory when only one value is working? You could hard-code it. This is not intuitive! Freundliche Grüße / Kind regards Wolfgang Winter System Analyst
Re: Memory issues in 2.0.9
Do you think this is related to MCOMPILER-64 in any way? We've started experiencing a number of PermGen errors in our build. Most of the time setting PermSize to 128m helps, but not always. Asgeir On Thu, May 15, 2008 at 3:28 PM, Ryan Moquin [EMAIL PROTECTED] wrote: Hello, I'm not sure what all to submit informationwise about this issue, but I switched to Maven 2.0.9 and now my builds fail with PermGen errors and on my other build, it complains about being out of heapspace. When I switch back to 2.0.8, I do not get this memory errors during a full build Are there any known memory issues with 2.0.9? Or should I just be increasing my memory settings? It appears to me to be a bug, but I wanted to run it past you all. Has anyone else seen this problem? Thanks, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
