I'm not sure to complete understand your needs but I think using war overlays may fill your needs : http://maven.apache.org/plugins/maven-war-plugin/overlays.html
Create one war with the common stuff Create another with the specific stuff war and with a dependency of type war to the common war. It will merge the common-war with the specific war ... Manuel On Thu, Jul 24, 2008 at 10:23 PM, Jean-Paul Vallée < [EMAIL PROTECTED]> wrote: > Hi, > I want to use maven for creating portlets. > The portlets will be deployed on a liferay portal > So the problem i want to solve is: > I do not want to make my portlets specific to a portal implementation, > so using maven, i want to create 2 artifacts: com.mycompany:portlet-foo > and com.mycompany:portlet-liferay-specific-foo > com.mycompany:portlet-liferay-specific-foo depending on > com.mycompany:portlet-foo > i want in the com.mycompany:portlet-liferay-specific-foo project only > the delta(i mean the specific files and modification needed by liferay, > pluto, jboss...) > and when packaging com.mycompany:portlet-liferay-specific-foo i want it > integrate also the files and structure from com.mycompany:portlet-foo > As this i could have a solution to have my portlets not specific to a > portal solution > > Other question, even it is not specific to maven (sorry), is there a > portlet container plugin that could just make me test my 'not specific' > portlets. > > Thanks > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
