r 3.0.
>
Understood. Let's see where this lifecycle thing leads me then.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27676878.html
Sent from the Maven Developer
esult of this work so I'm not overly keen on adding anything new until
after 3.0.
> --
> View this message in context:
> http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27673418.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
points? Are these usable on the
daily builds of M3? If I'm going to set this up, I would prefer to do this
on the IMHO better solution.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27673418.html
Sent from the Maven Dev
as little as you want. If you come up with
>> common patterns for a particular flavor of development you can hide it all
>> with a lifecycle if that's what you're trying to do with your team. It
>> might be more onerous then you would like, and we're fixing th
with a lifecycle if that's what you're trying to do with your team. It
> might be more onerous then you would like, and we're fixing that, but you
> certainly don't have to expose that to your developers. This is how we
> typically setup teams either by putting common
the work you have to do in order to
make it work for those developers. Ultimately whether there are mixins,
extension points, whatever, the resultant is a small POM for the target project
and that's totally possible now. Not as elegant as with a mixin, but certainly
possible.
>
>
2ness. (I still think it's a good
metaphore.) EJB2 also exposes too much of its innards.
I've read the sheets on Maven 3 and it looks promissing; I'm reading what
I'm looking for. Extention points, plugin, mixin... Maybe I'm simply trying
just a minute too soon.
--
View t
I most certainly can put the jackets on.
Can I try the Maven 3 feature already?
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27666958.html
Sent from the Maven Developers mailing list archive at Nabble.com.
t;>
>
> You make a compelling point. But considering the knowledge gap between you,
> the developers of Maven, and me, that is too idealistic. I simply do not
> pretend to have the knowledge to make enterprise level design decisions on
> this. My projects are medium in
put the jackets on.
Can I try the Maven 3 features already?
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27666959.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
put the jackets on.
Can I try the Maven 3 feature already?
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27666958.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
wondering
> if I need to introduce MAVANT; maven build cycle where ANT tasks are
> attached to the phases, using Ivy for reference resolving. But that sounds
> an awful lot like Gradle.
>
> First see what Maven 3 will bring. Is there any documentation aside the
> teaser
tached to the phases, using Ivy for reference resolving. But that sounds
an awful lot like Gradle.
First see what Maven 3 will bring. Is there any documentation aside the
teaser articles, on how to use the new features?
--
View this message in context:
http://old.nabble.com/custom-maven-plugin
out new features incrementally (that is
a lot harder then it sounds). Sure, if you make your Ant build you can do
whatever you want, it only affects you. We have a slightly larger set of users
to worry about.
>
> Thanks for answering th
Stephen Connolly-2 wrote:
>
> There is only one person I have ever seen who crafts "well setup" ant
> builds... Peter Reilly
>
> And unless you are Peter Reilly...
>
Well, you haven't seen mine, have you :-)
--
View this message in context:
http://o
, I'm just
> expressing
> my amazement about that the answer is not what I expected.
>
> Thanks for answering though!
> --
> View this message in context:
> http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27658340.html
> Sent from the Maven Developers
, this small rant naturally is not focused on you, I'm just expressing
my amazement about that the answer is not what I expected.
Thanks for answering though!
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27658340.html
Sent from the Maven
n is
> "the" way to go. Maybe Ant with some default build scripts and Ivy is
> better.
> --
> View this message in context:
> http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27657303.html
> Sent from the Maven Developers mailing list archive at Nabble.
e Ant with some default build scripts and Ivy is
better.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27657303.html
Sent from the Maven Developers mailing list archive at Nabble.com.
--
se in which it will execute. I cannot seem
to find any (good) documentation on how to configure a default phase it
should in. I would like to only include the plugin in the project's pom
and
that's it.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-p
cution, and thus a phase where it should execute in, in the plugin's
> pom. Together with the parameters and stuff.
> --
> View this message in context:
> http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27651482.html
> Sent from the Maven Developers mailing
ine
other packaging types? That is confusing. I would expect that I can define
an execution, and thus a phase where it should execute in, in the plugin's
pom. Together with the parameters and stuff.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp276
> to find any (good) documentation on how to configure a default phase it
>> should in. I would like to only include the plugin in the project's pom
>> and
>> that's it.
>> --
>> View this message in context:
>&g
;s it.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27626122.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-un
#x27;s pom and
that's it.
--
View this message in context:
http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27626122.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscri
25 matches
Mail list logo
