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. > > Whether that will be usable, I've no idea. > >>> -----Original Message----- >>> From: sebb [mailto:seb...@gmail.com] >>> Sent: 22 January 2012 11:42 >>> To: dev@jmeter.apache.org >>> Subject: Re: Properties files in mavenised artifacts >>> >>> On 21 January 2012 22:55, Mark Collin <m...@ardescosolutions.com> wrote: >>>> I've been hunting through the mavenised artifacts available at: >>>> >>>> >>>> >>>> https://repository.apache.org/content/repositories/snapshots/org/apa >>>> ch >>>> e/jmet >>>> er/ >>>> >>>> >>>> >>>> However I cannot find the following in any package: >>>> >>>> >>>> >>>> saveservice.properties >>>> >>>> upgrade.properties >>>> >>>> system.properties >>>> >>>> jmeter.properties >>>> >>>> user.properties >>>> >>>> >>>> >>>> If I'm being blind please point me in the right direction, if I'm >>>> not being blind can we get these added to an artefact, or another >>>> artefact added that contains these. >>>> >>> >>> You're right, those files are normally provided as part of the full >>> binary archive, which contains quite a few files in addition to the jars. >>> >>> Adding them to an existing jar may cause issues for non-Maven users, >>> so they need to be in a new artifact. >>> Possibly change parent to be a jar? >>> >>> But having them in a jar would be a bit of a pain. >>> How do Maven applications manage configuration files normally? >>> >>>> >>>> >>>> ------------------------------------------ >>>> >>>> Mark Collin >>>> >>>> Managing Director >>>> >>>> Ardesco Solutions Ltd >>>> >>>> >>>> >>>> <mailto:m...@ardescosolutions.com> m...@ardescosolutions.com >>>> >>>> >>>> >>>> Registered Office: >>>> >>>> The Coachhouse >>>> >>>> Greys Green Business Centre >>>> >>>> Henley-on-Thames >>>> >>>> Oxon >>>> >>>> RG9 4QG >>>> >>>> >>>> >>>> REGISTERED IN ENGLAND NO. 4837759 >>>> >>>> >>>> >>>> >>>> -- >>>> 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 >>> >>> -- >>> 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 > > -- > 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 > -- > 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 > > -- > 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
