Not really
when you flag your plugin as providing extensions, then it gets included
into the classloader which is used to look for LifecycleMapping definitions.
The default classloader already has the mapping files for jar/ejb/etc...
So it's no strictly speaking hard coded... more loosely co
I got your suggestion, the source code is here. I can use this way to
generate a new LifecycleMapping.
but I don't understand why jar/ejb/rar/war packaging are not use this way,
are they hard code in the Maven-Core project?
private Object findExtension( MavenProject project, String role, String
>
You need to mark your plugin as an extension
something like
test
test
0.1-SNAPSHOT
chensimiao
com.gmail.chensimiao
chensimiao-maven-plugin
1.0-SNAPSHOT
true
that way maven knows that it should look in
com.gmail.chensimiao:chensimiao-maven-plugin:1.
I traced the source core of maven and that the Maven-core will look up
for componentManagerManager by the key
"org.apache.maven.lifecycle.mapping.LifecycleMapping"+packaging_type,Im sure
the default packaging type ,jar,ear,rar for example, have register to the
PlexusContainer. but I don't know how
I think you will find the Repo infos there:
http://plexus.codehaus.org/source-repository.html
- jens
>I want to define a new packaging type called jcar to package my own project.
>i read the maven source , and find the maven-core use
>PlexusContainer.lookup() to find a new LifecycleMapping
>t
I want to define a new packaging type called jcar to package my own project.
i read the maven source , and find the maven-core use
PlexusContainer.lookup() to find a new LifecycleMapping
to, can anybody tell me how that process works? and where to download
PlexusContainer source code so i can read
