I'm well on my way in creating my first Maven plugin. One unexpected
behavior, but I've coded around that. But what I require now is some what
deviating; the plugin creates a special jar similar to onejar, containing
all files that are required at runtime as a single deliverable.
Naturally
Stephen Connolly-2 wrote:
fetching the artifact directly can cause issues when you want to use the
release plugin if the artifact you want to fetch is part of the reactor
you
are fetching.
The plugin knows it requires bootstrap-1.0.jar; it needs to fetch it
somehow, unpack it and
tbee wrote:
- include bootstrap-1.0.jar as a resource in plugin-1.0.jar, so it can be
opened as a resource when the plugin runs
That was easy; first use the maven-dependency-plugin to put all dependencies
in a separate folder and then configure a resource including only the one
jar
jvanzyl wrote:
Building up to 3.0 I'm focusing on Maven 3.0 working with M2Eclipse,
Tycho, Nexus and Hudson. There are some changes that are still getting
cycled through as a result of this work so I'm not overly keen on adding
anything new until after 3.0.
Understood. Let's see
jvanzyl wrote:
Most people we deal don't actually find that, it's usually not understand
the tool and the impatient find it easier to roll their own solution.
During my research I found many developers of well know open source projects
tried and failed migrating to Maven. After all that
jvanzyl wrote:
Most people we deal don't actually find that, it's usually not understand
the tool and the impatient find it easier to roll their own solution.
During my research I found many developers of well know open source projects
tried and failed migrating to Maven. After all that
Hm. There is a tad too much assumption in that previous post. First let me
introduce myself; 15 years ago I graduated with honors from a software
engineering study. I've done everything from C, Cobol, lowlevel embedded
systems and assembly (I worked on one of the first mobile GPS hardware),
jvanzyl wrote:
The migration to Maven is not because I want to migrate one of my
projects;
I'm setting up the development toolchain for our company, using one of
our
more complex projects as the testcase.
As the first test case?
By yourself, with a team?
Yes.
Small team; 3
jvanzyl wrote:
I answer more tomorrow, but for now here's a blog on making a custom
lifecycle.
That certainly looks doable, basically I need to create a onejar (or our
alternative that is) packaging. Seems logical.
If you have two plugins, e.g. something to do at the beginning and
Stephen Connolly-2 wrote:
If you want to bind your plugin to pre-existing phases, then you must
either
create your own packaging type (will will require you to add your plugin
with extensionstrue/extensions IIRC) or you need to use executions
to
bind the plugin to the lifecycle of the
Stephen Connolly-2 wrote:
I'm talking about in the projects that use your plugin
Seeing how these build file are growing and growing, and the amount of lines
that are required to include a plugin, I'm starting to doubt if Maven is
the way to go. Maybe Ant with some default build scripts
Stephen Connolly-2 wrote:
what maven gives you is a consistent set of phases that any developer only
has to learn once.
Agree and that is the lure of Maven. But if you look at the plugins,
execution tags and the weird behavior of per default compiling against java
1.3 (in stead of the
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:
jvanzyl wrote:
Sure, if you're dealing with a single module there's no benefit of
inheritance. If you really find you want goals of certain plugins to be
executed automatically then yes, you make a custom packaging and make it
transparent by referring to the packaging. This is all with
I've create a custom maven plugin and can start it from a project, but I need
to explicitely configure the phase 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
15 matches
Mail list logo
