Hi,
I want to create a profile that can help me run an auto-generated script onto
the target m/c. Since i would want this on a build m/c to be executed only
once, i figured it would be better to keep this target in a separate profile.
Here is what the skeleton looks like in my parent
HI Sumit,
The simplest thing might be to make a separate module which does nothing but
run your script. Then it would only run when executing that module.
If you are doing this once for each build, you don’t even need the profile.
Regards,
Russ
On Dec 23, 2013, at 3:16 PM, Sumit Kumar
inheritfalse/inherit
On 23 December 2013 20:16, Sumit Kumar skbrnwl-...@yahoo.com wrote:
Hi,
I want to create a profile that can help me run an auto-generated script
onto the target m/c. Since i would want this on a build m/c to be executed
only once, i figured it would be better to keep
As a side question - is there a way to get something to ONLY run in inherited
projects?
I have a few things in my parent POM I'd like to propagate down without needing
to put them in plugin-management and redeclaring them.
On 24 Dec 2013, at 12:30, Stephen Connolly wrote:
Hi,
I want to create a profile that can help me run an auto-generated script onto
the target m/c. Since i would want this on a build m/c to be executed only
once, i figured it would be better to keep this target in a separate profile.
Here is what the skeleton looks like in my parent
What about an auto-activated profile based on a file (non) existence ?
activation
file
missingsrc/missing
/file
/activation
That way, your script is only executed at parent level and not on
children...
No ?
Benoît.
-Message d'origine-
De : Sumit Kumar
