Hi
the NAR plugin uses its own lifecycle as documented here:
http://java.freehep.org/freehep-nar-plugin/lifecycle.html
it does connect java compilation to native compilation to allow
JNI code to be compiled in, using header files generated from the java
code.
It does NOT separate the compile and link phases... but I guess it
could.
If I get to work on this we can unify the whole thing.
Regards
Mark Donszelmann
On Jul 29, 2009, at 10:28 PM, Ringo De Smet wrote:
Hello,
I want to ask again what the correct state is regarding adding new
lifecycles, as a followup to this thread:
http://www.nabble.com/MECLIPSE-37-creating-a-new-custom-lifecycle-for-m-eclipse-p-td20846234.html
Investigation is currently taking place to use Maven +
freehep-nar-plugin to perform the builds of our native components. I'm
also investigating the sources of that plugin in case something is not
working as wanted so I can patch the plugin and provide our developers
with a custom version. One of the things I'm experimenting with is to
separate the compile from the link phase, so that other processing can
take place (other phases) in between, and that we can drop unneeded
phases.
The idea was to create a new lifecycle for building native artifacts:
<lifecycles>
<lifecycle>
<id>native</id>
<phases>
<phase>validate</phase>
<phase>initialize</phase>
<phase>generate-sources</phase>
<phase>compile</phase>
<phase>process-classes</phase>
<phase>link</phase>
<phase>generate-test-sources</phase>
<phase>test-compile</phase>
<phase>process-test-classes</phase>
<phase>test-link</phase>
<phase>test</phase>
<phase>prepare-package</phase>
<phase>package</phase>
<phase>verify</phase>
<phase>install</phase>
<phase>deploy</phase>
</phases>
</lifecycle>
</lifecycles>
Then, I would bind a lifecyclemapping for the nar packaging type to my
"native" lifecycle like this:
<component>
<role>org.apache.maven.lifecycle.mapping.LifecycleMapping
</role>
<role-hint>nar</role-hint>
<implementation>
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
</implementation>
<configuration>
<lifecycles>
<lifecycle>
<id>native</id>
<phases>
... phase to mojo mappings
... followed by xml closing tags
I found a few references to changes regarding lifecycles in Maven
2.1.0 and Maven 2.2.0. Can I implement this setup in one of the later
Maven versions?
Greetings,
Ringo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
