Re: Properties files in mavenised artifacts

[sebb]

On 21 January 2012 22:55, Mark Collin  wrote:
> I've been hunting through the mavenised artifacts available at:
>
>
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/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
>
>
>
>   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

RE: Properties files in mavenised artifacts

[Mark Collin]

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:



${basedir}/bin

**/*.properties




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.

-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  wrote:
> I've been hunting through the mavenised artifacts available at:
>
>
>
> https://repository.apache.org/content/repositories/snapshots/org/apach
> 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

Re: Properties files in mavenised artifacts

[sebb]

On 22 January 2012 18:21, Mark Collin  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:
>
> 
>    
>        ${basedir}/bin
>        
>            **/*.properties
>        
>    
> 

OK, thanks, I'll try that.

> 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.

> -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  wrote:
>> I've been hunting through the mavenised artifacts available at:
>>
>>
>>
>> https://repository.apache.org/content/repositories/snapshots/org/apach
>> 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

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 01:03, sebb  wrote:
> On 22 January 2012 18:21, Mark Collin  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:
>>
>> 
>>    
>>        ${basedir}/bin
>>        
>>            **/*.properties
>>        
>>    
>> 
>
> 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  wrote:
>>> I've been hunting through the mavenised artifacts available at:
>>>
>>>
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apach
>>> 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

RE: Properties files in mavenised artifacts

[Mark Collin]

The mvn deploy command should also build the package if the  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  wrote:
> On 22 January 2012 18:21, Mark Collin  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:
>>
>> 
>>    
>>        ${basedir}/bin
>>        
>>            **/*.properties
>>        
>>    
>> 
>
> 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  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 disclos

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 06:38, Mark Collin  wrote:
> The mvn deploy command should also build the package if the  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).

Ant build is currently only using deploy-file, which does not build anything.

The problem with deploy (as used when testing this previously) is that
it wants to build (and test) everything, which means that it
regenerates the jars.
Apart from being quite slow and unnecessary, the deployed jars would
then be different from the binary archive.

> 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.

That's what I have done for now; however I've put it in a maven-only task.

> -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  wrote:
>> On 22 January 2012 18:21, Mark Collin  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:
>>>
>>> 
>>>    
>>>        ${basedir}/bin
>>>        
>>>            **/*.properties
>>>        
>>>    
>>> 
>>
>> 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  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

RE: Properties files in mavenised artifacts

[Mark Collin]

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.

-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  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  wrote:
> On 22 January 2012 18:21, Mark Collin  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:
>>
>> 
>>    
>>        ${basedir}/bin
>>        
>>            **/*.properties
>>        
>>    
>> 
>
> 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  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
>>>
>>>
>>

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 12:03, Mark Collin  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  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  wrote:
>> On 22 January 2012 18:21, Mark Collin  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:
>>>
>>> 
>>>    
>>>        ${basedir}/bin
>>>        
>>>            **/*.properties
>>>        
>>>    
>>> 
>>
>> 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  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?
>>>
>>

RE: Properties files in mavenised artifacts

[Mark Collin]

Yes parent really does have to be a POM package.

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:

[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  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  
> 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  wrote:
>> On 22 January 2012 18:21, Mark Collin  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:
>>>
>>> 
>>>    
>>>        ${basedir}/bin
>>>        
>>>            **/*.properties
>>>        
>>>    
>>> 
>>
>> 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

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 13:08, Mark Collin  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  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 
>> 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  wrote:
>>> On 22 January 2012 18:21, Mark Collin  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:
>>>>
>>>> 
>>>>    
>>>>        ${basedir}/bin
>>>>        
>>>>            **/*.properties
>>>>        
>>>>    
>>>> 
>>>
>>> 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.
>>
>

RE: Properties files in mavenised artifacts

[Mark Collin]

Unfortunately that's what it looks like :(

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 13:46
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 13:08, Mark Collin  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.ht
> ml
>
> 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  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  
>> 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  wrote:
>>> On 22 January 2012 18:21, Mark Collin  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:
>>>>
>>>> 
>>>>    
>>>>        ${basedir}/bin
>>>>        
>>>>            **/*.properties
>>>>        
>>>>    
>>>> 
>>>
>>> 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. 

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 14:14, Mark Collin  wrote:
> Unfortunately that's what it looks like :(

I've uploaded another version which creates a _config jar.

Can you try that?

Also, how are you testing it?

It might speed turnround if I could test the deployed jars myself.

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 13:46
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 13:08, Mark Collin  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.ht
>> ml
>>
>> 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  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 
>>> 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  wrote:
>>>> On 22 January 2012 18:21, Mark Collin  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:
>>>>>
>>>>> 
>>>>>    
>>>>> 

RE: Properties files in mavenised artifacts

[Mark Collin]

I'm able to pull the artifacts in and use them again, but I can't see any
properties files in the ApacheJMeter_config jar.

I'm testing it by building this:

https://github.com/Ronnie76er/jmeter-maven-plugin

If that builds and successfully creates the package I'm using it to run a
couple of JMeter tests.

The above currently has copies of the properties files to enable it to run
until they are available in maven artifacts.

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 14:23
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 14:14, Mark Collin  wrote:
> Unfortunately that's what it looks like :(

I've uploaded another version which creates a _config jar.

Can you try that?

Also, how are you testing it?

It might speed turnround if I could test the deployed jars myself.

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 13:46
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 13:08, Mark Collin  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.h
>> t
>> ml
>>
>> 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  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  
>>> 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]
>>> Se

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 14:46, Mark Collin  wrote:
> I'm able to pull the artifacts in and use them again, but I can't see any
> properties files in the ApacheJMeter_config jar.

Just downloaded it, and I get:

$ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
 0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
 11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
 0 Mon Jan 23 01:39:32 GMT 2012 bin/
  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml

> I'm testing it by building this:
>
> https://github.com/Ronnie76er/jmeter-maven-plugin

OK, thanks, if that is not too time-consuming to set up I'll try it out.

> If that builds and successfully creates the package I'm using it to run a
> couple of JMeter tests.
>
> The above currently has copies of the properties files to enable it to run
> until they are available in maven artifacts.
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 14:23
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 14:14, Mark Collin  wrote:
>> Unfortunately that's what it looks like :(
>
> I've uploaded another version which creates a _config jar.
>
> Can you try that?
>
> Also, how are you testing it?
>
> It might speed turnround if I could test the deployed jars myself.
>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 13:46
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 13:08, Mark Collin  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.h
>>> t
>>> ml
>>>
>>> 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  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.
>>>
>>> Currentl

RE: Properties files in mavenised artifacts

[Mark Collin]

That's what I am seeing, I was also expecting the following:

saveservice.properties
upgrade.properties
system.properties
jmeter.properties
user.properties

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 14:57
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 14:46, Mark Collin  wrote:
> I'm able to pull the artifacts in and use them again, but I can't see 
> any properties files in the ApacheJMeter_config jar.

Just downloaded it, and I get:

$ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
 0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
 11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
 0 Mon Jan 23 01:39:32 GMT 2012 bin/
  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml

> I'm testing it by building this:
>
> https://github.com/Ronnie76er/jmeter-maven-plugin

OK, thanks, if that is not too time-consuming to set up I'll try it out.

> If that builds and successfully creates the package I'm using it to 
> run a couple of JMeter tests.
>
> The above currently has copies of the properties files to enable it to 
> run until they are available in maven artifacts.
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 14:23
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 14:14, Mark Collin  wrote:
>> Unfortunately that's what it looks like :(
>
> I've uploaded another version which creates a _config jar.
>
> Can you try that?
>
> Also, how are you testing it?
>
> It might speed turnround if I could test the deployed jars myself.
>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 13:46
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 13:08, Mark Collin  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.
>>> h
>>> t
>>> ml
>>>
>>> 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  wrote:
>>>> Thinking

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 15:05, Mark Collin  wrote:
> That's what I am seeing, I was also expecting the following:
>
> saveservice.properties
> upgrade.properties
> system.properties
> jmeter.properties
> user.properties

Oops, should be fixed now.

Tried the JMeter Maven plugin, and it requires quite a lot of
additional set up (creating work dirs etc.).

Not easy to use compared with JMeter scripts or the JMeter Ant task
(see extras/build.xml)

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 14:57
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 14:46, Mark Collin  wrote:
>> I'm able to pull the artifacts in and use them again, but I can't see
>> any properties files in the ApacheJMeter_config jar.
>
> Just downloaded it, and I get:
>
> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>
>> I'm testing it by building this:
>>
>> https://github.com/Ronnie76er/jmeter-maven-plugin
>
> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>
>> If that builds and successfully creates the package I'm using it to
>> run a couple of JMeter tests.
>>
>> The above currently has copies of the properties files to enable it to
>> run until they are available in maven artifacts.
>>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:23
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:14, Mark Collin  wrote:
>>> Unfortunately that's what it looks like :(
>>
>> I've uploaded another version which creates a _config jar.
>>
>> Can you try that?
>>
>> Also, how are you testing it?
>>
>> It might speed turnround if I could test the deployed jars myself.
>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 13:46
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 13:08, Mark Collin  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.
>>>> h
>>>> t
>>>> ml
>>>>
>>>> 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

RE: Properties files in mavenised artifacts

[Mark Collin]

I'm in the process of simplifying it right now.

The plan is that the only thing you will need to supply in the future is
test files (obviously in a mavenised directory structure).

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 15:35
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 15:05, Mark Collin  wrote:
> That's what I am seeing, I was also expecting the following:
>
> saveservice.properties
> upgrade.properties
> system.properties
> jmeter.properties
> user.properties

Oops, should be fixed now.

Tried the JMeter Maven plugin, and it requires quite a lot of additional set
up (creating work dirs etc.).

Not easy to use compared with JMeter scripts or the JMeter Ant task (see
extras/build.xml)

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 14:57
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 14:46, Mark Collin  wrote:
>> I'm able to pull the artifacts in and use them again, but I can't see 
>> any properties files in the ApacheJMeter_config jar.
>
> Just downloaded it, and I get:
>
> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>
>> I'm testing it by building this:
>>
>> https://github.com/Ronnie76er/jmeter-maven-plugin
>
> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>
>> If that builds and successfully creates the package I'm using it to 
>> run a couple of JMeter tests.
>>
>> The above currently has copies of the properties files to enable it 
>> to run until they are available in maven artifacts.
>>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:23
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:14, Mark Collin  wrote:
>>> Unfortunately that's what it looks like :(
>>
>> I've uploaded another version which creates a _config jar.
>>
>> Can you try that?
>>
>> Also, how are you testing it?
>>
>> It might speed turnround if I could test the deployed jars myself.
>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 13:46
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 13:08, Mark Collin  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.
>>>> h
>>>> t
>>>> ml
>>>>
>>>> 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.jme

Re: Properties files in mavenised artifacts

[sebb]

On 23 January 2012 16:29, Mark Collin  wrote:
> I'm in the process of simplifying it right now.
>
> The plan is that the only thing you will need to supply in the future is
> test files (obviously in a mavenised directory structure).

With the stand-alone (and Ant) installation, it's easy for users to
update the properties files if they need to.
Will that be possible with the plugin?

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 15:35
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 15:05, Mark Collin  wrote:
>> That's what I am seeing, I was also expecting the following:
>>
>> saveservice.properties
>> upgrade.properties
>> system.properties
>> jmeter.properties
>> user.properties
>
> Oops, should be fixed now.
>
> Tried the JMeter Maven plugin, and it requires quite a lot of additional set
> up (creating work dirs etc.).
>
> Not easy to use compared with JMeter scripts or the JMeter Ant task (see
> extras/build.xml)
>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:57
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:46, Mark Collin  wrote:
>>> I'm able to pull the artifacts in and use them again, but I can't see
>>> any properties files in the ApacheJMeter_config jar.
>>
>> Just downloaded it, and I get:
>>
>> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>>
>>> I'm testing it by building this:
>>>
>>> https://github.com/Ronnie76er/jmeter-maven-plugin
>>
>> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>>
>>> If that builds and successfully creates the package I'm using it to
>>> run a couple of JMeter tests.
>>>
>>> The above currently has copies of the properties files to enable it
>>> to run until they are available in maven artifacts.
>>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 14:23
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 14:14, Mark Collin  wrote:
>>>> Unfortunately that's what it looks like :(
>>>
>>> I've uploaded another version which creates a _config jar.
>>>
>>> Can you try that?
>>>
>>> Also, how are you testing it?
>>>
>>> It might speed turnround if I could test the deployed jars myself.
>>>
>>>> -Original Message-
>>>> From: sebb [mailto:seb...@gmail.com]
>>>> Sent: 23 January 2012 13:46
>>>> To: dev@jmeter.apache.org
>>>> Subject: Re: Properties files in mavenised artifacts
>>>>
>>>> On 23 January 2012 13:08, Mark Collin  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.
>>>>> h
>>>>> t
>>>>> ml
>>>>>
>>>>> I've just tried using the latest 2.6-SNAPSHOT and I'm getting the
>>>>> following
>>>>> error:
>>>>
>>>> How are you using it?
>>>>
>>>>> [INFO]
>>>>> --

RE: Properties files in mavenised artifacts

[Mark Collin]

The plan is to allow you to provide your own property file, or if you don't
drop back to the default offered by JMeter.

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 16:43
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 16:29, Mark Collin  wrote:
> I'm in the process of simplifying it right now.
>
> The plan is that the only thing you will need to supply in the future 
> is test files (obviously in a mavenised directory structure).

With the stand-alone (and Ant) installation, it's easy for users to update
the properties files if they need to.
Will that be possible with the plugin?

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 15:35
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 15:05, Mark Collin  wrote:
>> That's what I am seeing, I was also expecting the following:
>>
>> saveservice.properties
>> upgrade.properties
>> system.properties
>> jmeter.properties
>> user.properties
>
> Oops, should be fixed now.
>
> Tried the JMeter Maven plugin, and it requires quite a lot of 
> additional set up (creating work dirs etc.).
>
> Not easy to use compared with JMeter scripts or the JMeter Ant task 
> (see
> extras/build.xml)
>
>> -Original Message-----
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:57
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:46, Mark Collin  wrote:
>>> I'm able to pull the artifacts in and use them again, but I can't 
>>> see any properties files in the ApacheJMeter_config jar.
>>
>> Just downloaded it, and I get:
>>
>> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>>
>>> I'm testing it by building this:
>>>
>>> https://github.com/Ronnie76er/jmeter-maven-plugin
>>
>> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>>
>>> If that builds and successfully creates the package I'm using it to 
>>> run a couple of JMeter tests.
>>>
>>> The above currently has copies of the properties files to enable it 
>>> to run until they are available in maven artifacts.
>>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 14:23
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 14:14, Mark Collin  wrote:
>>>> Unfortunately that's what it looks like :(
>>>
>>> I've uploaded another version which creates a _config jar.
>>>
>>> Can you try that?
>>>
>>> Also, how are you testing it?
>>>
>>> It might speed turnround if I could test the deployed jars myself.
>>>
>>>> -Original Message-
>>>> From: sebb [mailto:seb...@gmail.com]
>>>> Sent: 23 January 2012 13:46
>>>> To: dev@jmeter.apache.org
>>>> Subject: Re: Properties files in mavenised artifacts
>>>>
>>>> On 23 January 2012 13:08, Mark Collin 
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.
>>>>> h
>>>>> t
>>>>> ml
>>>>>
>>>>> I'

RE: Properties files in mavenised artifacts

[Mark Collin]

I think I've found one more thing that's missing, the JUnit Test.jar

-Original Message-
From: Mark Collin [mailto:m...@ardescosolutions.com] 
Sent: 23 January 2012 16:29
To: dev@jmeter.apache.org
Subject: RE: Properties files in mavenised artifacts

I'm in the process of simplifying it right now.

The plan is that the only thing you will need to supply in the future is
test files (obviously in a mavenised directory structure).

-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: 23 January 2012 15:35
To: dev@jmeter.apache.org
Subject: Re: Properties files in mavenised artifacts

On 23 January 2012 15:05, Mark Collin  wrote:
> That's what I am seeing, I was also expecting the following:
>
> saveservice.properties
> upgrade.properties
> system.properties
> jmeter.properties
> user.properties

Oops, should be fixed now.

Tried the JMeter Maven plugin, and it requires quite a lot of additional set
up (creating work dirs etc.).

Not easy to use compared with JMeter scripts or the JMeter Ant task (see
extras/build.xml)

> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 14:57
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 14:46, Mark Collin  wrote:
>> I'm able to pull the artifacts in and use them again, but I can't see 
>> any properties files in the ApacheJMeter_config jar.
>
> Just downloaded it, and I get:
>
> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>
>> I'm testing it by building this:
>>
>> https://github.com/Ronnie76er/jmeter-maven-plugin
>
> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>
>> If that builds and successfully creates the package I'm using it to 
>> run a couple of JMeter tests.
>>
>> The above currently has copies of the properties files to enable it 
>> to run until they are available in maven artifacts.
>>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:23
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:14, Mark Collin  wrote:
>>> Unfortunately that's what it looks like :(
>>
>> I've uploaded another version which creates a _config jar.
>>
>> Can you try that?
>>
>> Also, how are you testing it?
>>
>> It might speed turnround if I could test the deployed jars myself.
>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 13:46
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 13:08, Mark Collin  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.
>>>> h
>>>> t
>>>> ml
>>>>
>>>> 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 

Re: Properties files in mavenised artifacts

[sebb]

On 24 January 2012 12:09, Mark Collin  wrote:
> I think I've found one more thing that's missing, the JUnit Test.jar

Ah, yes, it's in a different place - lib/junit

It's not actually needed for running JMeter - it only contains some
trivial examples.

But it could be included anyway.

> -Original Message-
> From: Mark Collin [mailto:m...@ardescosolutions.com]
> Sent: 23 January 2012 16:29
> To: dev@jmeter.apache.org
> Subject: RE: Properties files in mavenised artifacts
>
> I'm in the process of simplifying it right now.
>
> The plan is that the only thing you will need to supply in the future is
> test files (obviously in a mavenised directory structure).
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 23 January 2012 15:35
> To: dev@jmeter.apache.org
> Subject: Re: Properties files in mavenised artifacts
>
> On 23 January 2012 15:05, Mark Collin  wrote:
>> That's what I am seeing, I was also expecting the following:
>>
>> saveservice.properties
>> upgrade.properties
>> system.properties
>> jmeter.properties
>> user.properties
>
> Oops, should be fixed now.
>
> Tried the JMeter Maven plugin, and it requires quite a lot of additional set
> up (creating work dirs etc.).
>
> Not easy to use compared with JMeter scripts or the JMeter Ant task (see
> extras/build.xml)
>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 14:57
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 14:46, Mark Collin  wrote:
>>> I'm able to pull the artifacts in and use them again, but I can't see
>>> any properties files in the ApacheJMeter_config jar.
>>
>> Just downloaded it, and I get:
>>
>> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>>
>>> I'm testing it by building this:
>>>
>>> https://github.com/Ronnie76er/jmeter-maven-plugin
>>
>> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>>
>>> If that builds and successfully creates the package I'm using it to
>>> run a couple of JMeter tests.
>>>
>>> The above currently has copies of the properties files to enable it
>>> to run until they are available in maven artifacts.
>>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 14:23
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 14:14, Mark Collin  wrote:
>>>> Unfortunately that's what it looks like :(
>>>
>>> I've uploaded another version which creates a _config jar.
>>>
>>> Can you try that?
>>>
>>> Also, how are you testing it?
>>>
>>> It might speed turnround if I could test the deployed jars myself.
>>>
>>>> -Original Message-
>>>> From: sebb [mailto:seb...@gmail.com]
>>>> Sent: 23 January 2012 13:46
>>>> To: dev@jmeter.apache.org
>>>> Subject: Re: Properties files in mavenised artifacts
>>>>
>>>> On 23 January 2012 13:08, Mark Collin  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.
>>>>> 

Re: Properties files in mavenised artifacts

[sebb]

On 24 January 2012 14:48, sebb  wrote:
> On 24 January 2012 12:09, Mark Collin  wrote:
>> I think I've found one more thing that's missing, the JUnit Test.jar
>
> Ah, yes, it's in a different place - lib/junit
>
> It's not actually needed for running JMeter - it only contains some
> trivial examples.
>
> But it could be included anyway.

Should now be available as ApacheJMeter_junit-test.jar

>> -Original Message-
>> From: Mark Collin [mailto:m...@ardescosolutions.com]
>> Sent: 23 January 2012 16:29
>> To: dev@jmeter.apache.org
>> Subject: RE: Properties files in mavenised artifacts
>>
>> I'm in the process of simplifying it right now.
>>
>> The plan is that the only thing you will need to supply in the future is
>> test files (obviously in a mavenised directory structure).
>>
>> -Original Message-
>> From: sebb [mailto:seb...@gmail.com]
>> Sent: 23 January 2012 15:35
>> To: dev@jmeter.apache.org
>> Subject: Re: Properties files in mavenised artifacts
>>
>> On 23 January 2012 15:05, Mark Collin  wrote:
>>> That's what I am seeing, I was also expecting the following:
>>>
>>> saveservice.properties
>>> upgrade.properties
>>> system.properties
>>> jmeter.properties
>>> user.properties
>>
>> Oops, should be fixed now.
>>
>> Tried the JMeter Maven plugin, and it requires quite a lot of additional set
>> up (creating work dirs etc.).
>>
>> Not easy to use compared with JMeter scripts or the JMeter Ant task (see
>> extras/build.xml)
>>
>>> -Original Message-
>>> From: sebb [mailto:seb...@gmail.com]
>>> Sent: 23 January 2012 14:57
>>> To: dev@jmeter.apache.org
>>> Subject: Re: Properties files in mavenised artifacts
>>>
>>> On 23 January 2012 14:46, Mark Collin  wrote:
>>>> I'm able to pull the artifacts in and use them again, but I can't see
>>>> any properties files in the ApacheJMeter_config jar.
>>>
>>> Just downloaded it, and I get:
>>>
>>> $ jar -tvf ApacheJMeter_config-2.6-20120123.135339-1.jar
>>>     0 Mon Jan 23 13:50:32 GMT 2012 META-INF/
>>>   373 Mon Jan 23 13:50:30 GMT 2012 META-INF/MANIFEST.MF
>>>   172 Sat Jan 21 17:08:48 GMT 2012 META-INF/NOTICE
>>>  11560 Sat Jan 21 17:08:48 GMT 2012 META-INF/LICENSE
>>>     0 Mon Jan 23 01:39:32 GMT 2012 bin/
>>>  1435 Sat Apr 05 02:49:46 BST 2008 bin/BeanShellAssertion.bshrc
>>>  2079 Fri Apr 17 11:29:10 BST 2009 bin/BeanShellFunction.bshrc
>>>  1232 Sat Apr 05 02:50:08 BST 2008 bin/BeanShellListeners.bshrc
>>>  2105 Sat Sep 17 16:40:04 BST 2011 bin/BeanShellSampler.bshrc
>>>  1406 Tue Dec 14 17:33:02 GMT 2010 bin/hc.parameters
>>>  1563 Fri Dec 10 02:29:52 GMT 2010 bin/httpclient.parameters
>>>  1801 Fri Jan 28 15:04:14 GMT 2011 bin/log4j.conf
>>>  5781 Fri Dec 16 10:57:22 GMT 2011 bin/logkit.xml
>>>  1324 Wed Aug 05 23:42:30 BST 2009 bin/proxyserver.jks
>>>  1022 Tue Apr 08 12:36:12 BST 2008 bin/users.dtd
>>>  2365 Tue Apr 08 12:36:14 BST 2008 bin/users.xml
>>>
>>>> I'm testing it by building this:
>>>>
>>>> https://github.com/Ronnie76er/jmeter-maven-plugin
>>>
>>> OK, thanks, if that is not too time-consuming to set up I'll try it out.
>>>
>>>> If that builds and successfully creates the package I'm using it to
>>>> run a couple of JMeter tests.
>>>>
>>>> The above currently has copies of the properties files to enable it
>>>> to run until they are available in maven artifacts.
>>>>
>>>> -Original Message-
>>>> From: sebb [mailto:seb...@gmail.com]
>>>> Sent: 23 January 2012 14:23
>>>> To: dev@jmeter.apache.org
>>>> Subject: Re: Properties files in mavenised artifacts
>>>>
>>>> On 23 January 2012 14:14, Mark Collin  wrote:
>>>>> Unfortunately that's what it looks like :(
>>>>
>>>> I've uploaded another version which creates a _config jar.
>>>>
>>>> Can you try that?
>>>>
>>>> Also, how are you testing it?
>>>>
>>>> It might speed turnround if I could test the deployed jars myself.
>>>>
>>>>> -Original Message-
>>>>> From: sebb [mailto:seb...@gmail.com]
>>>>> Sent: 23 January 2012 13:46
>>>>> To: dev@jmeter.apache.org
>>>>