Re: maven-plugin-testing-harness

[Olivier Lamy]

Hi
IMHO using the maven invoker plugin is a better way as you can easily test
your plugin with different core versions.
but it's only my POV :-)

On 23 August 2017 at 18:03, ahardy42  wrote:

> After a concentrated stint of experimentation, I have setup my tests using
> the maven-plugin-testing-harness so that the tests run with a live remote
> repository and have all the resources provided in the target/test-classes
> directory.
>
> The solution is here:
> https://stackoverflow.com/questions/45241317/hard-time-
> mojo-testing-with-maven-plugin-testing-harness/45833419#answer-45833419
>
> Sorry if the question title betrays my frustration. The limited feedback I
> got here on this user list was also surprising. Obviously with no feedback
> to speak of, I have no idea why no-one from the maven community wanted to
> communicate on this subject. I would of course be grateful now to get some
> feedback of any kind. I'm not asking for anyone to spend more than a minute
> to write a reply - I have essentially finished my work with the testing
> harness.
>
> Why was it so difficult? Are the inner workings all in the process of
> re-development for maven 4?
>
>
>
> --
> View this message in context: http://maven.40175.n5.nabble.
> com/maven-plugin-testing-harness-tp5911556p5912964.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: How to up date a property in a POM to a specific value

[Sandra Parsick]

Thanks for your answers.

Passing the property value from command line don't meet my condition,
because the new value has to be stored in the POM.

I found out that a new mojo called "set-property" was implemented in the
current master branch of versions maven plugin. This mojo would meet my
use cases.

Does it exist a target date for the next release of version maven plugin?

Best regards,

Sandra


Am 22.08.2017 um 11:07 schrieb Anders Hammar:
> Specifying property values from command line when doing a release could be
> bad practice, as the pom deployed would not contain the value from command
> line. It all depends on what the property is used for.
> 
> /Anders
> 
> On Tue, Aug 22, 2017 at 10:34 AM, John Patrick 
> wrote:
> 
>> I think I do similar and I simply use
>> -DpropertyName=newValueForProperty on the command line when executing
>> the maven command, or via a profile and then activate the required
>> profile.
>>
>> Just checking the property is already defined in a pom e.g.
>> ..oldValueForProperty> propertyName>
>>
>> At build time I would simply change the command line I'm using to
>> build. I do this type of thing all the line when testing new
>> dependencies, different external systems, loading different
>> properties/config via a different dependency.
>>
>> John
>>
>>
>> On 21 August 2017 at 08:50,   wrote:
>>> Hello mailing,
>>>
>>> I use property values, defined in a POM, during resource filtering. I'd
>> like to change this properties during my release process. I know that the
>> Maven Version Plugin has a goal named update-properties. But it requires
>> that the properties are used in the dependency definition. I search for
>> something like 'set-property -Dname=propertyName
>> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports this
>> use case?
>>>
>>> Thank you and best regards,
>>>
>>> Sandra Parsick
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> 



signature.asc
Description: OpenPGP digital signature

[ANN] Animal Sniffer Maven Plugin 1.16 Released

[Robert Scholte]

Hi,

The Mojo team is pleased to announce the release of the Animal Sniffer  
Maven Plugin version 1.16.


Animal Sniffer provides tools to assist verifying that classes compiled  
with a newer JDK/API are compatible with an older JDK/API.


http://www.mojohaus.org/animal-sniffer/

To get this update, simply specify the version in your project's plugin  
configuration:



org.codehaus.mojo
animal-sniffer-maven-plugin
1.16


Release Notes

https://github.com/mojohaus/animal-sniffer/issues?q=milestone%3A1.16+is%3Aclosed

Enjoy,

The Mojo team.

Robert

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-plugin-testing-harness

[ahardy42]

After a concentrated stint of experimentation, I have setup my tests using
the maven-plugin-testing-harness so that the tests run with a live remote
repository and have all the resources provided in the target/test-classes
directory.

The solution is here:
https://stackoverflow.com/questions/45241317/hard-time-mojo-testing-with-maven-plugin-testing-harness/45833419#answer-45833419

Sorry if the question title betrays my frustration. The limited feedback I
got here on this user list was also surprising. Obviously with no feedback
to speak of, I have no idea why no-one from the maven community wanted to
communicate on this subject. I would of course be grateful now to get some
feedback of any kind. I'm not asking for anyone to spend more than a minute
to write a reply - I have essentially finished my work with the testing
harness. 

Why was it so difficult? Are the inner workings all in the process of
re-development for maven 4?



--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-plugin-testing-harness-tp5911556p5912964.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org