1

Resolved

compile-plugin has two deploy phases for ArtifactType.NETPLUGIN

description

Maybe package was intended for goal 'npanday.plugin:maven-mojo-generator-plugin:generate-bindings'?
 
forType( ArtifactType.NETPLUGIN ) {
LifecycleMappingBuilder b->
b.validate (default_validate)
b.generate_sources (default_generate_sources)
b.process_sources (default_process_sources)
b.process_resources (default_process_resources)
b.compile (np_compile)
b.test_compile (np_test_compile)
b.deploy ('npanday.plugin:maven-mojo-generator-plugin:generate-bindings')
b.test (np_test)
b.install (default_install)
b.deploy (np_convert, mv_deploy)
}

comments

jocaba wrote Jul 28, 2010 at 5:55 AM

Is this still occurring in the trunk? I can't seem to locate the mentioned file...

Thanks,

brettporter wrote Jul 29, 2010 at 4:15 AM

it's still there: plugins/maven-compile-plugin/src/main/groovy/npanday/plugin/compile/CompileLifecycleMap.groovy

jocaba wrote Aug 25, 2010 at 6:37 AM

Removed the 2nd deploy phase in trunk

wrote Feb 14, 2013 at 1:18 AM

wrote May 16, 2013 at 6:33 AM

wrote May 16, 2013 at 6:33 AM

wrote Jun 14, 2013 at 7:48 AM