Re: What does this mean?
Hi, does your project have some other modules? 2009/1/19 David Jencks : > Results : > Tests run: 1837, Failures: 0, Errors: 0, Skipped: 0 In my opinion this info is only for the current module which was build. Check maven logs for the same (but with failures > 0) somewhere higher. You can also run maven with -X -e , then you should see some additional stack traces. Maven surefire plugin generates additional reports with test failure cause in target/maven-surefire-plugin of current module -- Greetings, Matthew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2.0.9 - internal repository - archetype plugin version help
I may be talking out a hole but check this out... The release version along with version range information comes from metadata... if you created your internal repository in a way other than using the deploy plugin then you won't have metadata. If you are copying your local repository aka the artifact cache then you don't have 'maven-metadata.xml' in the correct place. you have cache copies of the metadata named central-maven-metadata.xml... if you only used central to build your local cache then you could just rename centra-maven-metadata... or you could just use a repository manager given you seem to have the requirement for it. hope that helps.. On Mon, 19 Jan 2009 07:46:18 Ross B wrote: > > Hello, > > > I'm having difficulties getting the maven-archetype-plug-in to work with an > internal repository. The problem seems to be that it cannot locate the > RELEASE version of this plugin when given an internal repository. I've copied > the error I get to the end of this email together with my settings.xml file. > I have tried various configurations and workarounds. I have maven configured > to * which points to my internal repo and I have tried > combining this with a profile that uses this mirror for a > to no avail. The only workaround which works for me is to specify the fully > qualified archetype command which locks down the version of both the > archetype plugin and the archetype rather than using the metadata to > determine the RELEASE versions: > > e.g. > > mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:create > -DartifactId=new-proj -DgroupId=org.mycompany -DpackageId=org.mycompany > -DarchetypeVersion=1.0 > > This is executed in a directory that does not have a pom.xml file. I can get > the list of available archetypes from the generate goal if I execute mvn > archetype:generate in a directory that has a pom.xml, which defines the > plugin and its version as a build dependency, but then it bombs out when I > select an archetype because it cannot find the RELEASE version of that > archetype (even though it exists in the internal repo). > > Now, as far as I can see, the metadata in my internal repository matches the > metadata in central so I'm struggling to see what's going wrong. I should > note that my internal repository is generated by running the archetype and > other plugins in an environment with access to central and then I copy the > local repo from .m2 into another folder which acts as an internal repository. > Does this method not provide appropriate metadata, or is Maven for some > reason always going to Central to determine the release version of this > plugin? I should note that I have also tried the > -DremoteRepositories=file:// flag but this doesn't seem to > have much effect. > > This behavior is consistent in Maven 2.0.9/Archetype plugin 2.0-alpha-4 and > Maven 2.1.0-M1. I have read various FAQs and bug reports about this being > fixed but I'm still having difficulties so I'd be grateful for some > suggestions or a working configuration. > > Here's the config I've tried thus far: > > My settings.xml (I get the same failure case when the profile is switched off > or commented and have tried both direct/indirect urls in the profile > repository 's): > > mirrorId * Human > Readable Name for this Mirror. > file://C:/ > > > internal-repo > central-repo http://dummy-url > >true > > true > > > central-plugin-repo > http://dummy-url > true > > true > > > > Here's the error: > > -- > > [INFO] Scanning for projects...[INFO] Searching repository for plugin with > prefix: 'archetype'.[DEBUG] Loading plugin prefixes from group: > org.apache.maven.plugins[INFO] org.apache.maven.plugins: checking for updates > from central-plugin-repo[DEBUG] repository metadata for: > 'org.apache.maven.plugins' could not be found on repository: > central-plugin-repo[INFO] org.apache.maven.plugins: checking for updates from > central[DEBUG] repository metadata for: 'org.apache.maven.plugins' could not > be found on repository: central[DEBUG] Loading plugin prefixes from group: > org.codehaus.mojo[INFO] org.codehaus.mojo: checking for updates from > central-plugin-repo[DEBUG] repository metadata for: 'org.codehaus.mojo' could > not be found on repository: central-plugin-repo[INFO] org.codehaus.mojo: > checking for updates from central[DEBUG] repository metadata for: > 'org.codehaus.mojo' could not be found on repository: cen
Re: What does this mean?
Is this intermittent? Does running with -e -X give any additional hints? Do you have a MAVEN_OPTS set with -Xmx - could you be running out of heap (perhaps at around 512M)? Best Brett On Mon, Jan 19, 2009 at 5:05 PM, David Jencks wrote: > > Results : > Tests run: 1837, Failures: 0, Errors: 0, Skipped: 0 > > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 66 minutes 20 seconds > [INFO] Finished at: Sun Jan 18 19:05:55 PST 2009 > [INFO] Final Memory: 51M/508M > [INFO] > > > I think this has happened twice now. > > maven 2.0.9, I'm building activemq trunk. > > thanks > david jencks > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
What does this mean?
Results : Tests run: 1837, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 66 minutes 20 seconds [INFO] Finished at: Sun Jan 18 19:05:55 PST 2009 [INFO] Final Memory: 51M/508M [INFO] I think this has happened twice now. maven 2.0.9, I'm building activemq trunk. thanks david jencks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uploading files created by assembly to server
using a profile ofcourse -D On Sun, Jan 18, 2009 at 9:55 PM, Dan Tran wrote: > Use build-helper-maven-plugin to attached your specific files to > maven, so that they can be deploy with the rest of other built > artifacts > > However, if you want to upload your files to somewhere else rather > maven repo, then use wagin-maven-plugin at deploy phase > > > -D > > On Sat, Jan 17, 2009 at 6:56 AM, Michael Decker wrote: >>Hi, >> >> I want to modify my "release:perform" goal, so it will automatically upload >> my >> assemblies to sourceforge, so I can easily provide them on the sourceforge >> download page. >> >> Yet I can build the assemblies and upload the site on using "release:perform" >> by using this: >>--- SNIP --- >> >> maven-release-plugin >> >>https: >>true >>assembly:assembly site-deploy >> >> >> >> >>--- SNAP --- >> >> So I wonder, how I can perform uploading of four files. >> >> There is Maven Wagon without any documentation: >> http://maven.apache.org/wagon/index.html >> >> And I found Maven Upload Plugin, that can upload a whole directory, but I >> want >> only four files saved in target directory: >> http://docs.atlassian.com/maven-upload-plugin/1.1/usage.html >> >> Perhaps someone can me help me on this. >> >> Thanks a lot. >> >> With regards >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Uploading files created by assembly to server
Use build-helper-maven-plugin to attached your specific files to maven, so that they can be deploy with the rest of other built artifacts However, if you want to upload your files to somewhere else rather maven repo, then use wagin-maven-plugin at deploy phase -D On Sat, Jan 17, 2009 at 6:56 AM, Michael Decker wrote: >Hi, > > I want to modify my "release:perform" goal, so it will automatically upload my > assemblies to sourceforge, so I can easily provide them on the sourceforge > download page. > > Yet I can build the assemblies and upload the site on using "release:perform" > by using this: >--- SNIP --- > > maven-release-plugin > >https: >true >assembly:assembly site-deploy > > > > >--- SNAP --- > > So I wonder, how I can perform uploading of four files. > > There is Maven Wagon without any documentation: > http://maven.apache.org/wagon/index.html > > And I found Maven Upload Plugin, that can upload a whole directory, but I want > only four files saved in target directory: > http://docs.atlassian.com/maven-upload-plugin/1.1/usage.html > > Perhaps someone can me help me on this. > > Thanks a lot. > > With regards > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 2.0.9 - local repository - archetype plugin
Hello, I'm having difficulties getting the maven-archetype-plug-in to work with a local repository. The problem seems to be that it cannot locate the RELEASE version of this plugin when given a local repository. I've copied the error I get to the end of this email together with my settings.xml file. I have tried various configurations and workarounds. I have maven configured to * which points to my local repo and I have tried combining this with a profile that uses this mirror for a to no avail. The only workaround which works for me is to specify the fully qualified archetype command which locks down the version of both the archetype plugin and the archetype rather than using the metadata to determine the RELEASE versions: e.g. mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:create -DartifactId=new-proj -DgroupId=org.mycompany -DpackageId=org.mycompany -DarchetypeVersion=1.0 This is executed in a directory that does not have a pom.xml file. I can get the list of available archetypes from the generate goal if I execute mvn archetype:generate in a directory that has a pom.xml, which defines the plugin and its version as a build dependency, but then it bombs out when I select an archetype because it cannot find the RELEASE version of that archetype (even though it exists in the local repo). Now, as far as I can see, the metadata in my internal repository matches the metadata in central so I'm struggling to see what's going wrong. I should note that my internal repository is generated by running the archetype and other plugins in an environment with access to central and then I copy the local repo from .m2 into another folder which acts as an internal repository. Does this method not provide appropriate metadata or is Maven for some reason always going to Central to determine the release version of this plugin? I should note that I have also tried the -DremoteRepositories=file:// flag but this doesn't seem to have much effect. This behavior is consistent in Maven 2.0.9/Archetype plugin 2.0-alpha-4 and Maven 2.1.0-M1. I have read various FAQs and bug reports about this being fixed but I'm still having difficulties so I'd be grateful for some suggestions or a working configuration. Here's the config I've tried thus far: My settings.xml (I get the same failure case when the profile is switched off or commented and have tried both direct/indirect urls in the profile repository 's): mirrorId * Human Readable Name for this Mirror. file://C:/ internal-repo central-repo http://dummy-url true true central-plugin-repo http://dummy-url true true Here's the error: -- [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central-plugin-repo [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: central-plugin-repo [INFO] org.apache.maven.plugins: checking for updates from central [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: central [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [INFO] org.codehaus.mojo: checking for updates from central-plugin-repo [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: central-plugin-repo [INFO] org.codehaus.mojo: checking for updates from central [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: central [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central-plugin-repo [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-archetype-plugin' could not be found on repository: central-plugin-repo [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-archetype-plugin' could not be found on repository: central [DEBUG] maven-archetype-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-archetype-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-archetype-plugin:pom:LATEST [DEBUG] maven-archetype-plugin: using locally installed snapshot [DEBUG]
Maven 2.0.9 - internal repository - archetype plugin version help
Hello, I'm having difficulties getting the maven-archetype-plug-in to work with an internal repository. The problem seems to be that it cannot locate the RELEASE version of this plugin when given an internal repository. I've copied the error I get to the end of this email together with my settings.xml file. I have tried various configurations and workarounds. I have maven configured to * which points to my internal repo and I have tried combining this with a profile that uses this mirror for a to no avail. The only workaround which works for me is to specify the fully qualified archetype command which locks down the version of both the archetype plugin and the archetype rather than using the metadata to determine the RELEASE versions: e.g. mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:create -DartifactId=new-proj -DgroupId=org.mycompany -DpackageId=org.mycompany -DarchetypeVersion=1.0 This is executed in a directory that does not have a pom.xml file. I can get the list of available archetypes from the generate goal if I execute mvn archetype:generate in a directory that has a pom.xml, which defines the plugin and its version as a build dependency, but then it bombs out when I select an archetype because it cannot find the RELEASE version of that archetype (even though it exists in the internal repo). Now, as far as I can see, the metadata in my internal repository matches the metadata in central so I'm struggling to see what's going wrong. I should note that my internal repository is generated by running the archetype and other plugins in an environment with access to central and then I copy the local repo from .m2 into another folder which acts as an internal repository. Does this method not provide appropriate metadata, or is Maven for some reason always going to Central to determine the release version of this plugin? I should note that I have also tried the -DremoteRepositories=file:// flag but this doesn't seem to have much effect. This behavior is consistent in Maven 2.0.9/Archetype plugin 2.0-alpha-4 and Maven 2.1.0-M1. I have read various FAQs and bug reports about this being fixed but I'm still having difficulties so I'd be grateful for some suggestions or a working configuration. Here's the config I've tried thus far: My settings.xml (I get the same failure case when the profile is switched off or commented and have tried both direct/indirect urls in the profile repository 's): mirrorId * Human Readable Name for this Mirror. file://C:/ internal-repo central-repo http://dummy-url true true central-plugin-repo http://dummy-url true true Here's the error: -- [INFO] Scanning for projects...[INFO] Searching repository for plugin with prefix: 'archetype'.[DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins[INFO] org.apache.maven.plugins: checking for updates from central-plugin-repo[DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: central-plugin-repo[INFO] org.apache.maven.plugins: checking for updates from central[DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: central[DEBUG] Loading plugin prefixes from group: org.codehaus.mojo[INFO] org.codehaus.mojo: checking for updates from central-plugin-repo[DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: central-plugin-repo[INFO] org.codehaus.mojo: checking for updates from central[DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: central[INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central-plugin-repo[DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-archetype-plugin' could not be found on repository: central-plugin-repo[INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for updates from central[DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-archetype-plugin' could not be found on repository: central[DEBUG] maven-archetype-plugin: using locally installed snapshot[DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-archetype-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-archetype-plugin:pom:LATEST[DEBUG] maven-archetype-plugin: using locally installed snapshot[DEBUG]
Uploading files created by assembly to server
Hi, I want to modify my "release:perform" goal, so it will automatically upload my assemblies to sourceforge, so I can easily provide them on the sourceforge download page. Yet I can build the assemblies and upload the site on using "release:perform" by using this: --- SNIP --- maven-release-plugin https: true assembly:assembly site-deploy --- SNAP --- So I wonder, how I can perform uploading of four files. There is Maven Wagon without any documentation: http://maven.apache.org/wagon/index.html And I found Maven Upload Plugin, that can upload a whole directory, but I want only four files saved in target directory: http://docs.atlassian.com/maven-upload-plugin/1.1/usage.html Perhaps someone can me help me on this. Thanks a lot. With regards signature.asc Description: This is a digitally signed message part.
Re: Uploading files created by assembly to server (on release:perform)
Hi,
I try to use wagon-maven-plugin to solve my problem:
http://mojo.codehaus.org/wagon-maven-plugin/
But I do something wrong. I call the goal release:perform, but nothing
happens.
Here my add to pom.xml:
--- SNIP ---
org.codehaus.mojo
wagon-maven-plugin
1.0-beta-1
upload-to-sourceforge-releasing
release:perform
upload
target/
*.zip,*.jar,*.tar.gz,*.tar.bz2
sftp://${sfUsername}:${sfpasswo...@frs.sourceforge.net/
uploads/
--- SNAP ---
What is my failure?
Tanks a lot.
On Thursday 15 January 2009 23:30:49 News Assi wrote:
> Hi,
>
> I want to modify my "release:perform" goal, so it will automatically upload
> my assemblies to sourceforge, so I can easily provide them on the
> sourceforge download page.
>
> Yet I can build the assemblies and upload the site on using
> "release:perform" by using this:
> --- SNIP ---
>
> maven-release-plugin
>
> https:
> true
> assembly:assembly site-deploy
>
>
>
>
> --- SNAP ---
>
> So I wonder, how I can perform uploading of four files.
>
> There is Maven Wagon without any documentation:
> http://maven.apache.org/wagon/index.html
>
> And I found Maven Upload Plugin, that can upload a whole directory, but I
> want only four files saved in target directory:
> http://docs.atlassian.com/maven-upload-plugin/1.1/usage.html
>
> Perhaps someone can me help me on this.
>
> Thanks a lot.
>
> With regards
signature.asc
Description: This is a digitally signed message part.
Re: [SOLVED] Re: exclude jars during filtering
ok I overlooked the plugin version. nonFilteredFileExtensions works only with version 2.3 and in my build 2.2 version of the resources plugin was being picked up. Thanks for the pointer :) Olivier Lamy wrote: > > Yes please because nonFilteredFileExtensions feature was added to > prevent such extra pom configuration. > Have you forced the maven-resources-plugin version in your pom ? > Is it a reactor builds ? In this case is the version in the pluginMngt > section of your root pom ? > > -- > Olivier > > 2009/1/18 Mark Struberg : >>> Still I did not get to resolve why >>> nonFilteredFileExtensions did not work. >> >> Can you create a really lightweight test case and attach it to a Jira? >> >> LieGrue, >> strub >> >> --- ksangani schrieb am So, 18.1.2009: >> >>> Von: ksangani >>> Betreff: [SOLVED] Re: exclude jars during filtering >>> An: users@maven.apache.org >>> Datum: Sonntag, 18. Januar 2009, 11:05 >>> I solved by following >>> http://blog.xebia.com/2008/11/02/watch-out-when-filtering-resources-with-maven/ >>> this approach. Declared two elements, one >>> to copy unfiltered >>> resources and other to copy filtered resources. >>> >>> Still I did not get to resolve why >>> nonFilteredFileExtensions did not work. >>> >>> >>> Wayne Fay wrote: >>> > >>> >> I have some jar files under src/test/resources >>> folder. I have enabled >>> >> filter for the test resources. Now during >>> filtering jar files get >>> >> corrupted. I have tried the following >>> configuration but does not seem >>> > >>> > Many people use /src/main/resources/filtered and >>> > /src/main/resources/unfiltered for this very reason >>> (or /src/test). >>> > >>> > You will, of course, have to configure the resources >>> directories >>> > manually in the pom as a result of this, as the >>> default configuration >>> > (convention) will no longer apply. >>> > >>> > Wayne >>> > >>> > >>> - >>> > To unsubscribe, e-mail: >>> users-unsubscr...@maven.apache.org >>> > For additional commands, e-mail: >>> users-h...@maven.apache.org >>> > >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/exclude-jars-during-filtering-tp21492939p21525970.html >>> Sent from the Maven - Users mailing list archive at >>> Nabble.com. >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: >>> users-h...@maven.apache.org >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/exclude-jars-during-filtering-tp21492939p21530114.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [SOLVED] Re: exclude jars during filtering
Yes please because nonFilteredFileExtensions feature was added to prevent such extra pom configuration. Have you forced the maven-resources-plugin version in your pom ? Is it a reactor builds ? In this case is the version in the pluginMngt section of your root pom ? -- Olivier 2009/1/18 Mark Struberg : >> Still I did not get to resolve why >> nonFilteredFileExtensions did not work. > > Can you create a really lightweight test case and attach it to a Jira? > > LieGrue, > strub > > --- ksangani schrieb am So, 18.1.2009: > >> Von: ksangani >> Betreff: [SOLVED] Re: exclude jars during filtering >> An: users@maven.apache.org >> Datum: Sonntag, 18. Januar 2009, 11:05 >> I solved by following >> http://blog.xebia.com/2008/11/02/watch-out-when-filtering-resources-with-maven/ >> this approach. Declared two elements, one >> to copy unfiltered >> resources and other to copy filtered resources. >> >> Still I did not get to resolve why >> nonFilteredFileExtensions did not work. >> >> >> Wayne Fay wrote: >> > >> >> I have some jar files under src/test/resources >> folder. I have enabled >> >> filter for the test resources. Now during >> filtering jar files get >> >> corrupted. I have tried the following >> configuration but does not seem >> > >> > Many people use /src/main/resources/filtered and >> > /src/main/resources/unfiltered for this very reason >> (or /src/test). >> > >> > You will, of course, have to configure the resources >> directories >> > manually in the pom as a result of this, as the >> default configuration >> > (convention) will no longer apply. >> > >> > Wayne >> > >> > >> - >> > To unsubscribe, e-mail: >> users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: >> users-h...@maven.apache.org >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/exclude-jars-during-filtering-tp21492939p21525970.html >> Sent from the Maven - Users mailing list archive at >> Nabble.com. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: >> users-h...@maven.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven EAR Plugin ContextRoot
On Wed, Jan 14, 2009 at 11:39 PM, Stephen Duncan Jr wrote: > I'm following the instructions here to set the context-root for my web > modules as specified here: > http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-context-root.html > > It seems to have no effect on the generated application.xml, the > context-root still has the default values. I couldn't find any mention of > this problem. Can anyone else indicate if this works or not in the current > release of the maven-ear-pluging (2.3.1)? It is working with both 2.3.1 and the trunk. I've just tried on a stupid project that I have for testing and it worked. Can you maybe post your pom.xml file? maven-ear-plugin 2.3.1 root.project.servlets servlet /foobar > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: [SOLVED] Re: exclude jars during filtering
> Still I did not get to resolve why > nonFilteredFileExtensions did not work. Can you create a really lightweight test case and attach it to a Jira? LieGrue, strub --- ksangani schrieb am So, 18.1.2009: > Von: ksangani > Betreff: [SOLVED] Re: exclude jars during filtering > An: users@maven.apache.org > Datum: Sonntag, 18. Januar 2009, 11:05 > I solved by following > http://blog.xebia.com/2008/11/02/watch-out-when-filtering-resources-with-maven/ > this approach. Declared two elements, one > to copy unfiltered > resources and other to copy filtered resources. > > Still I did not get to resolve why > nonFilteredFileExtensions did not work. > > > Wayne Fay wrote: > > > >> I have some jar files under src/test/resources > folder. I have enabled > >> filter for the test resources. Now during > filtering jar files get > >> corrupted. I have tried the following > configuration but does not seem > > > > Many people use /src/main/resources/filtered and > > /src/main/resources/unfiltered for this very reason > (or /src/test). > > > > You will, of course, have to configure the resources > directories > > manually in the pom as a result of this, as the > default configuration > > (convention) will no longer apply. > > > > Wayne > > > > > - > > To unsubscribe, e-mail: > users-unsubscr...@maven.apache.org > > For additional commands, e-mail: > users-h...@maven.apache.org > > > > > > > > -- > View this message in context: > http://www.nabble.com/exclude-jars-during-filtering-tp21492939p21525970.html > Sent from the Maven - Users mailing list archive at > Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: > users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[SOLVED] Re: exclude jars during filtering
I solved by following http://blog.xebia.com/2008/11/02/watch-out-when-filtering-resources-with-maven/ this approach. Declared two elements, one to copy unfiltered resources and other to copy filtered resources. Still I did not get to resolve why nonFilteredFileExtensions did not work. Wayne Fay wrote: > >> I have some jar files under src/test/resources folder. I have enabled >> filter for the test resources. Now during filtering jar files get >> corrupted. I have tried the following configuration but does not seem > > Many people use /src/main/resources/filtered and > /src/main/resources/unfiltered for this very reason (or /src/test). > > You will, of course, have to configure the resources directories > manually in the pom as a result of this, as the default configuration > (convention) will no longer apply. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/exclude-jars-during-filtering-tp21492939p21525970.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: project artifacts returns empty collection
@requiresDependencyResolution fixed the problem. I needed to put the
annotation at class level and I was putting at field level. Thanks.
struberg wrote:
>
> @requiresDependencyResolution compile
> is also a good bet in combination with project.getArtifacts() ...
>
> hth
>
> --- Mark Struberg schrieb am So, 18.1.2009:
>
>> Von: Mark Struberg
>> Betreff: Re: AW: project artifacts returns empty collection
>> An: "Maven Users List"
>> Datum: Sonntag, 18. Januar 2009, 1:27
>> oops, sorry it's really late.
>> you may look at MavenProject
>> /**
>> * POM
>> *
>> * @parameter expression="${project}"
>> * @readonly
>> * @required
>> */
>> protected MavenProject project;
>>
>> lg,
>> strub
>>
>> --- Mark Struberg schrieb am So,
>> 18.1.2009:
>>
>> > Von: Mark Struberg
>> > Betreff: Re: AW: project artifacts returns empty
>> collection
>> > An: "Maven Users List"
>>
>> > Datum: Sonntag, 18. Januar 2009, 1:04
>> > What does your pom look like?
>> > Which scope do the dependencies have?
>> > In which lifecycle is your mojo being executed?
>> standard?
>> >
>> > LieGrue,
>> > strub
>> >
>> >
>> > --- Kamlesh Sangani
>> schrieb am
>> > So, 18.1.2009:
>> >
>> > > Von: Kamlesh Sangani
>> > > Betreff: Re: AW: project artifacts returns empty
>> > collection
>> > > An: "Maven Users List"
>> >
>> > > Datum: Sonntag, 18. Januar 2009, 0:45
>> > > I tried the sample code. But now for the
>> collection
>> > injected
>> > > for the expression
>> ${project.compileClasspathElements}
>> > only
>> > > has classes folder for the project. It does not
>> > include any
>> > > other dependency module jars. Any idea?
>> > >
>> > > Other thing is third party jar that I am calling
>> uses
>> > > getClass().getClassLoader().getResource(). In
>> such
>> > case
>> > > changing thread context classloader does not
>> help. Any
>> > work
>> > > around for this use case?
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > From: Mark Struberg
>> > > To: Maven Users List
>>
>> > > Sent: Saturday, January 17, 2009 3:10:38 PM
>> > > Subject: AW: project artifacts returns empty
>> > collection
>> > >
>> > > you may look at the openjpa-maven-plugin:
>> > >
>> > >
>> >
>> https://svn.codehaus.org/mojo/trunk/mojo/openjpa-maven-plugin/
>> > >
>> > > latest version is in my git at
>> > http://ns1.backwork.net/git
>> > >
>> > > the interesting code is in
>> > >
>> >
>> https://svn.codehaus.org/mojo/trunk/mojo/openjpa-maven-plugin/src/main/java/org/codehaus/mojo/openjpa/AbstractOpenJpaMojo.java
>> > >
>> > > protected void extendRealmClasspath()
>> > >
>> > > hth
>> > > LieGrue,
>> > > strub
>> > >
>> > > --- Kamlesh Sangani
>> > schrieb am
>> > > So, 18.1.2009:
>> > >
>> > > > Von: Kamlesh Sangani
>>
>> > > > Betreff: project artifacts returns empty
>> > collection
>> > > > An: users@maven.apache.org
>> > > > Datum: Sonntag, 18. Januar 2009, 0:02
>> > > > I have a mojo which is bound to
>> generated-sources
>> > > phase. In
>> > > > the mojo I am calling some third party code
>> which
>> > > expects
>> > > > project's dependecies in the classpath.
>> These
>> > > > dependencies are decalred in the project
>> which is
>> > > calling my
>> > > > mojo. So before calling the third party code
>> I
>> > need to
>> > > add
>> > > > these dependecies to the classpath. Is there
>> a
>> > > standard
>> > > > solution to this problem?
>> > > >
>> > > > I have looked at the mailing list and there
>> are
>> > some
>> > > > suggestions of using ${project.artifacts} to
>> get
>> > > project
>> > > > dependecies and then change context
>> classloader.
>> > I
>> > > tried to
>> > > > decalre the following configuration but
>> artifacts
>> > is
>> > > always
>> > > > empty set.
>> > > >
>> > > >/**
>> > > > * The set of artifact artifacts
>> > > > *
>> > > > * @parameter expression =
>> > > > "${project.artifacts}"
>> > > > * @readonly
>> > > > * @requiresDependencyResolution runtime
>> > > > */
>> > > > private Collection artifacts;
>> > > >
>> > > > Do I need to have some other configuration
>> in
>> > > > project/plugin pom to make this work? Any
>> help is
>> > > > appreciated.
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> -
>> > > To unsubscribe, e-mail:
>> > users-unsubscr...@maven.apache.org
>> > > For additional commands, e-mail:
>> > > users-h...@maven.apache.org
>> >
>> >
>> >
>> >
>> >
>> -
>> > To unsubscribe, e-mail:
>> users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail:
>> > users-h...@maven.apache.org
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail:
>> users-h...@maven.apache.org
>
>
>
>
>
