Vincent Massol wrote: >Yes, Jason explained to me what Mojos are. So ideally we would have: > >mojos/ (java beans equivalent to Ant tasks and not tied to plexus nor maven) > > right - but implement the Plugin interface and contribute to a descriptor through some metadata
>plexus/ (focus only on container and use mojos for extra services like >zipping, etc) > > The zipping etc are not mojos, they are pojos. There is really no difference (they both plexus components, configured via a descriptor), but mojos have additional metadata (goal name, lifecycle phase, dependencyresolution required) >Any plan to move the mojos out of m2 and move the plexus zipping et al build >logic into external mojos and consolidate them all? > > > No... the current split makes sense. The archiver is used in several mojos, so they are standalone libraries. It would be weird to include a JAR plugin as a dependency of the WAR plugin - it is better to factor out the common code as just a normal Java library (which happens to be configured as a plexus component also). - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
