Ok, so I reply to myself...
My needs were not to duplicate code (JSR168) between a generic version of my
portlets and the specific portlet (needed by one particular portal
solution).
My first idea was this one because of the intrusive needs due to the portal
solution (liferay, pluto...). These
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.
Thanks, Jeff and manuel
I think i will have a look at overlays, your explainations seem to be what i
want to do.
But, is there a smarter way to do what i want, ie merge generic and specific
artifact when building the specific artifact.
Hi,
I think we have two cases that are similar: Firstly, EJBs where only
deployment descriptors are different. For this we use
+ parent
+- generic
+- specific1
+- specific2
All the sources are in generic/src/main/java.
parent has packagingpom/packaging and
Have a look at cargo.codehaus.org.
Jeff MAURY
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
