Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.216.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <028a01ccd9d0$09a0a650$1ce1f2f0$@ardescosolutions.com>
References: <00e101ccd88f$d3c55670$7b500350$@ardescosolutions.com>
	<CAOGo0VYZ5mqU8GHn1RrH6RJRu85cyp+Ut3sjAgiPJniyYtkxbg@mail.gmail.com>
	<006201ccd932$b5d243f0$2176cbd0$@ardescosolutions.com>
	<CAOGo0VZPRA3vVb4VVhQjLvRreO8J7phWRTgLPiNscnYCin4vhw@mail.gmail.com>
	<CAOGo0Va7kf0QkfDdFCFsSiYTMNOf91T_CxhRLm4S8qPqkVLJ_A@mail.gmail.com>
	<00e201ccd999$a2828c30$e787a490$@ardescosolutions.com>
	<026d01ccd9c6$fcef1260$f6cd3720$@ardescosolutions.com>
	<CAOGo0Vb+_4o7cq45y3_D2b7-r7=ASFMQC25Db5=p=D-V3=kSDQ@mail.gmail.com>
	<028a01ccd9d0$09a0a650$1ce1f2f0$@ardescosolutions.com>
Date: Mon, 23 Jan 2012 13:45:32 +0000
Message-ID: 
 <CAOGo0VY90p7oAdrHys+_VdovOm2FcvC7jr5aToht4u=H3OdYow@mail.gmail.com>
Subject: Re: Properties files in mavenised artifacts
From: sebb <sebbaz@gmail.com>
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 23 January 2012 13:08, Mark Collin <mark@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 followi=
ng
> 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:sebbaz@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 <mark@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. =A0I think you will instead
>> need to have a new package that the parent depends on that pulls in thes=
e
> extra files.
>
> Currently, the parent is now a jar package which contains the configurati=
on
> 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:mark@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. =A0This 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:sebbaz@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 <sebbaz@gmail.com> wrote:
>>> On 22 January 2012 18:21, Mark Collin <mark@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. =A0Something like this should work:
>>>>
>>>> <resources>
>>>> =A0 =A0<resource>
>>>> =A0 =A0 =A0 =A0<directory>${basedir}/bin</directory>
>>>> =A0 =A0 =A0 =A0<includes>
>>>> =A0 =A0 =A0 =A0 =A0 =A0<include>**/*.properties</include>
>>>> =A0 =A0 =A0 =A0</includes>
>>>> =A0 =A0</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 t=
he individual named. If you are not the named addressee you should not diss=
eminate, distribute or copy this e-mail. Please notify the sender immediate=
ly 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 notifi=
ed 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 postmaster@ardesco=
solutions.com