Re: Default location of config files -> Maven Standard Directroy Layo ut?
This thread is old, but it appears to be the closest to a definitive answer that I can find. Martin Höller wrote: > > On 26-03-2007 11:15 Doyle D.G. (Duncan) wrote: > >> Furthermore, where should one put configuration files which are needed >> for testing? There is no 'src/test/config' listed in the Maven Standard >> Directory Layout. > > Put it in src/test/resources. > Martin, I don't think this is the answer Duncan is looking for. If I understand him correctly (and he is asking the same question that I have), he is referring to configuration files that are *not* needed on the test classpath, such as a testng.xml file for configuring TestNG execution. This is not a file that belongs on any classpath. It is simply used during build execution to control test execution. As Doyle suggests, it seems that the place to put such test configuration files would be src/test/config, but this directory is not identified in Maven's standard directory layout. Only src/main/config is specified, and since the purpose of that directory is not clearly described or understood, we can only guess as to its purpose. Under the assumption that src/main/config is the "right" place for files such as checkstyle.xml, it seems that a similar directory for test configuration files (src/test/config) would be the "right" place to put files such as testng.xml, but again, nobody seems to have definitively answered this long-standing question. Anyone care to add to this, or point me to a more recent discussion/solution for this? -- View this message in context: http://maven.40175.n5.nabble.com/Default-location-of-config-files-Maven-Standard-Directroy-Layo-ut-tp84421p4470992.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: Question on poms
The first warning that is being generated is because you haven't specified a version for maven-compiler-plugin so Maven is only guessing which one to use. This is undesirable because once a new version is released Maven might (will?) choose that one and it may be incompatible with the version you used before. Are you configuring the plugin like this: org.apache.maven.plugins maven-compiler-plugin 2.3.2 ? Or are you configuring it at all? I had seen the second error message before when I used a local repository, that had been created by Maven 2, with Maven 3. What happens if you delete the artifacts in question (the entire folder) and re-download them? Lenni On Wed, Jun 8, 2011 at 10:20 PM, Refr Bruhl wrote: > I will try this > > Thank you! > > --Refr inn gra > > > "Wars are to be won with swords and spears, > not with rice and salt." -- Uesugi Kenshin > > > > - Original Message > From: Wendy Smoak > To: Maven Users List > Sent: Wed, June 8, 2011 1:30:10 PM > Subject: Re: Question on poms > > On Wed, Jun 8, 2011 at 2:25 PM, Refr Bruhl wrote: > > I used the instructions at > > http://maven.apache.org/guides/MavenQuickReferenceCard.pdf for adding > 3rd > party > > libraries to my repository. > > Interesting... haven't seen that before! > > So you used mvn install:install-file? > > Odd.. > http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html > says generatePom defaults to true. > > Try re-doing mvn install:install-file and adding -DgeneratePom=true . > > -- > Wendy > > - > 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: Question on poms
I will try this Thank you! --Refr inn gra "Wars are to be won with swords and spears, not with rice and salt." -- Uesugi Kenshin - Original Message From: Wendy Smoak To: Maven Users List Sent: Wed, June 8, 2011 1:30:10 PM Subject: Re: Question on poms On Wed, Jun 8, 2011 at 2:25 PM, Refr Bruhl wrote: > I used the instructions at > http://maven.apache.org/guides/MavenQuickReferenceCard.pdf for adding 3rd party > libraries to my repository. Interesting... haven't seen that before! So you used mvn install:install-file? Odd.. http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html says generatePom defaults to true. Try re-doing mvn install:install-file and adding -DgeneratePom=true . -- Wendy - 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: Question on poms
On Wed, Jun 8, 2011 at 2:25 PM, Refr Bruhl wrote: > I used the instructions at > http://maven.apache.org/guides/MavenQuickReferenceCard.pdf for adding 3rd > party > libraries to my repository. Interesting... haven't seen that before! So you used mvn install:install-file? Odd.. http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html says generatePom defaults to true. Try re-doing mvn install:install-file and adding -DgeneratePom=true . -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Question on poms
Greetings I used the instructions at http://maven.apache.org/guides/MavenQuickReferenceCard.pdf for adding 3rd party libraries to my repository. I see instructions there for creating a minimal pom... however I am not sure what should go into it. We are an aix shop. While the company has plans to get the type of manager you describe it hasn't been acted upon yet. Most open source stuff has issues compiling on aix 6.1 nowadays As for commons-io, no I am not sure. This was downloaded manually from the apache site. --Refr inn gra "Wars are to be won with swords and spears, not with rice and salt." -- Uesugi Kenshin - Original Message From: Wendy Smoak To: Maven Users List Sent: Wed, June 8, 2011 12:52:01 PM Subject: Re: Question on poms On Wed, Jun 8, 2011 at 1:45 PM, Refr Bruhl wrote: > I get the following warnings in my builds. I've had to add jars manually to my > local repository. How did you do that? > What steps do I need to to do to create these poms sine they didn't arrive with > the original vendor? Depending on how they got there... the install:install-file goal has an option to generate a minimal pom. However, looking at the list of things it's complaining about, are you sure there's no pom in central for commons-io ? It's best to run a repository manager and put the artifacts there, so you don't have to re-do this if you blow away your local repo for any reason. -- Wendy - 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: Question on poms
On Wed, Jun 8, 2011 at 1:45 PM, Refr Bruhl wrote: > I get the following warnings in my builds. I've had to add jars manually to my > local repository. How did you do that? > What steps do I need to to do to create these poms sine they didn't arrive > with > the original vendor? Depending on how they got there... the install:install-file goal has an option to generate a minimal pom. However, looking at the list of things it's complaining about, are you sure there's no pom in central for commons-io ? It's best to run a repository manager and put the artifacts there, so you don't have to re-do this if you blow away your local repo for any reason. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Question on poms
Team I get the following warnings in my builds. I've had to add jars manually to my local repository. Near as I can tell the only thing that really generates the "future version of Maven" message is missing poms. What steps do I need to to do to create these poms sine they didn't arrive with the original vendor? Am I correct in thinking the missing poms are causing the warning message of "For this reason, future Maven versions might no longer support building such malformed projects." ? My other projects that have poms from the vendors do not generate warning. I am using maven 2 # mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0 Java home: /usr/java6_64/jre Default locale: en_US, platform encoding: ISO8859-1 OS name: "aix" version: "6.1" arch: "ppc64" Family: "unix" Thanks in advance -Rob [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 66, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] The POM for com.ibm.db2.jcc:db2jcc:jar:3.53.70 is missing, no dependency information available [WARNING] The POM for org.apache.commons:commons-io:jar:2.0.1 is missing, no dependency information available [WARNING] The POM for ch.ethz:ssh2:jar:build251beta is missing, no dependency information available --Refr inn gra "Wars are to be won with swords and spears, not with rice and salt." -- Uesugi Kenshin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to convert from Ant project to maven project?
> Sorry for my entry-level question. Is it possible for me to convert from an > Ant project to A Maven project from within NetBeans IDE? This is a question for the Netbeans User list. > Or, is there any method to convert from an Ant project to a Maven project > using some command line method? Not that I am aware of. > Or, any standard method to do so? As Stephen already told you, the easiest option is probably to create an empty Maven project structure and then move your source code and resources to the proper directories. But this assumes that you have a fairly simple project. If you are doing anything "special" then this will most likely not work either. Your best bet is to start reading about Maven using one of the free ebooks that are available and linked to from the http://maven.apache.org website, create some sample projects as outlined in those books, begin to understand the tool and how it works, and then attempt to convert an Ant build. You can't skip all that learning and expect to be successful in this endeavor. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: assemble and compile for a specific version
I finally solved using filter resources instead of assemblies.
2011/6/7 Fernando Wermus
> Hi all,
> I have the following pom.xml that only assambles in a certein profile:
>
>
>
> qa-tomcat5x
>
>
>
> maven-assembly-plugin
> 2.2-beta-5
>
>
> qa-tomcat5x
>
> single
>
>
>
> ${project.basedir}/src/assemble/filter.properties
>
>
> ${project.basedir}/src/assemble/descriptor.xml
>
>
> package
>
>
>
>
>
>
>
>
> But I also need that the generated jar has all the compiled classes as well
> as all the resources. The only thing that this jar contains is just the file
> that participates in assembly. How can I change that in my profile?
>
> thanks in advance
>
>
Re: How to convert from Ant project to maven project?
1. Maven is not ANT. I assume you have read the Maven books and have tried some projects using Maven. If you are somebody who is used to ANT it will take a while to de-ANT you, so switching an ANT based project over to Maven is a really bad way to learn Maven... OTOH 2. If you have a fairly simple project structure (ie you just are building a jar or a war and not doing fancy stuff) the best bet is to create an empty Maven project structure (one module for each jar and one module for each web app... if you have more than one module create a parent project to hold them all) Then just move the .java files into (module)/src/main/java/ and all the resources into (module)/src/main/resources/ keeping the existing package directory structure... Then repeat the same for any tests you have, .java files into (module)/src/test/java/ and all the resources into (module)/src/test/resources/ All the webapp files go into (module)/src/main/webapp in the layout as for the war, so e.g. the web.xml goes to (module)/src/main/webapp/WEB-INF/web.xml Next you add all the dependencies to the poms, and cross your fingers and do "mvn verify" if that works you are done with ANT and on to Maven. 3. If you have a complex project try to do a migration along the lines of #1 first. On 8 June 2011 09:06, jiapei100 wrote: > > Hi, all: > > Sorry for my entry-level question. Is it possible for me to convert from an > Ant project to A Maven project from within NetBeans IDE? > > Or, is there any method to convert from an Ant project to a Maven project > using some command line method? Or, any standard method to do so? > > Best Regards > Pei > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-convert-from-Ant-project-to-maven-project-tp4468638p4468638.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
How to convert from Ant project to maven project?
Hi, all: Sorry for my entry-level question. Is it possible for me to convert from an Ant project to A Maven project from within NetBeans IDE? Or, is there any method to convert from an Ant project to a Maven project using some command line method? Or, any standard method to do so? Best Regards Pei -- View this message in context: http://maven.40175.n5.nabble.com/How-to-convert-from-Ant-project-to-maven-project-tp4468638p4468638.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
