On 23 January 2012 13:08, Mark Collin <m...@ardescosolutions.com> wrote: > Yes parent really does have to be a POM package.
Bother. So we need another jar and another pom. > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > > I've just tried using the latest 2.6-SNAPSHOT and I'm getting the following > error: How are you using it? > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Error building POM (may not be this project's POM). > > > Project ID: org.apache.jmeter:ApacheJMeter_core > > Reason: Parent: org.apache.jmeter:ApacheJMeter_parent:jar:2.6-SNAPSHOT of > project: org.apache.jmeter:ApacheJMeter_core has > wrong packaging: jar. Must be 'pom'. for project > org.apache.jmeter:ApacheJMeter_core > > > [INFO] > ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 12 seconds > [INFO] Finished at: Mon Jan 23 13:03:50 GMT 2012 > [INFO] Final Memory: 13M/107M > [INFO] > ------------------------------------------------------------------------ > > -----Original Message----- > From: sebb [mailto:seb...@gmail.com] > Sent: 23 January 2012 12:15 > To: dev@jmeter.apache.org > Subject: Re: Properties files in mavenised artifacts > > On 23 January 2012 12:03, Mark Collin <m...@ardescosolutions.com> wrote: >> Thinking about it, I think I'm talking a degree of rubbish here. >> >> A parent needs to be packaged as a pom and not a jar so even if you >> add a build section it's not going to work. I think you will instead >> need to have a new package that the parent depends on that pulls in these > extra files. > > Currently, the parent is now a jar package which contains the configuration > files. > > The poms are basically just being used as jar descriptors and dependency > declarations currently. > > Does the parent really have to be a pom package? > > Has anyone tried using one of the latest snapshots (i.e. one with > ApacheJMeter_parent.jar as well as .pom)? > >> -----Original Message----- >> From: Mark Collin [mailto:m...@ardescosolutions.com] >> Sent: 23 January 2012 06:39 >> To: dev@jmeter.apache.org >> Subject: RE: Properties files in mavenised artifacts >> >> The mvn deploy command should also build the package if the <build> >> section exists in the POM so you could have a build section for the >> parent POM that only pulls in resources that are required (this would >> muddy the waters slightly but seems like the pragmatic approach). >> >> Of course you could also tweak your ant script to build all of the >> dependencies into a jar and then deploy that as well for the mavenised >> build. This sounds worse IMHO because you are modifying your existing >> build process to create something that your normal ant build doesn't > require. >> >> -----Original Message----- >> From: sebb [mailto:seb...@gmail.com] >> Sent: 23 January 2012 01:50 >> To: dev@jmeter.apache.org >> Subject: Re: Properties files in mavenised artifacts >> >> On 23 January 2012 01:03, sebb <seb...@gmail.com> wrote: >>> On 22 January 2012 18:21, Mark Collin <m...@ardescosolutions.com> wrote: >>>> Parent sounds like a good place. >>>> >>>> Normally it would pick up things in src/main/resources, but as you >>>> don't have a maven directory structure I think you'll need to define >>>> a resource dir in the parent POM. Something like this should work: >>>> >>>> <resources> >>>> <resource> >>>> <directory>${basedir}/bin</directory> >>>> <includes> >>>> <include>**/*.properties</include> >>>> </includes> >>>> </resource> >>>> </resources> >>> >>> OK, thanks, I'll try that. >> >> Just realised that won't work for creating the files to be uploaded, >> as we don't use Maven to create the artifacts. >> >>>> I'm not sure exactly where you would need to place it in the >>>> artifact, I guess that depends on where you expect them to be when >>>> you >> read them in. >>> >>> JMeter expects to find them in the bin/ directory, i.e. where it >>> finds ApacheJMeter.jar. >>> >>> However, I've no idea how any JMeter Maven launch plugins are >>> intended to work so that may not be appropriate. >> >> Sorry, but I've no idea how to make this work. >> >> All I can suggest is creating a jar containing the missing properties >> files (there are also some other missing files) which can be uploaded as > parent > > -- > This message contains confidential information and is intended only for the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and delete > this e-mail from your system. If you are not the intended recipient you are > notified that disclosing, copying, distributing or taking any action in > reliance on the contents of this information is strictly prohibited. > > If you have received this email in error please notify > postmas...@ardescosolutions.com
