Hi, This make me think that maybe, there is 2 concepts hidden in the <packaging/> element: project-kind and project-deliverable.
For example we could have a class library packaged in a jar file. But we also could have that same class library packaged in a zip file. Or we could have a java application packaged in a jar file. Some project kinds are class library, aspect library, maven-plugin, web application, desktop application. Some project deliverables are jar file, war file, zip file. Is this revelant or not? Regards, Raphaël 2007/2/6, Matt Brozowski <[EMAIL PROTECTED]>:
On Jan 30, 2007, at 6:38 PM, Brett Porter wrote: > This sort of thing can be addressed in the assembly plugin itself > (though it requires <extensions>true which is a bit gross, but > hopefully we can fix that in 2.1 anyway). > > I've thought about this before, but stumbled on the 'which type' > question. > > I think the real solution to this is to have plugins properly > expose the stuff they generate so that dependency resolution can > take it into account (also could be used from the dependency > plugin, for example). > > Doesn't discount the value of having such a packaging though (might > just need to have a <format> and <otherFormats> tags to make one > special :) I did something like this by making a tgz-plugin that calls assembly and used <packaging>tgz</packaging> I think its a great idea! Matt ________________________________________________________________________ ___ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The OpenNMS Group, Inc. Fax: +1 503 961 7746 Email: [EMAIL PROTECTED] URL: http://www.opennms.com
