Re: Do we want to apply genesis 2.0 resource filtering best practice ?

2009-07-16 Thread David Jencks


On Jul 15, 2009, at 10:46 PM, Shawn Jiang wrote:

I noticed there's a maven resource best practice defined in genesis- 
default-flava-2.0.pom.


1, Put normal resource under : ${project.basedir}/ src/main/resources
2, Put the resource that needs filtering under: ${project.basedir}/
src/main/filtered-resources

At the same time, many projects in Geronimo does not follow this  
practice.  A JIRA was opened for this : https://issues.apache.org/jira/browse/GERONIMO-4737


If no objection, I'm going to use GERONIMO-4737 to fix this kind of  
problems in current code base.   Any comments ?


Looks like a good idea to me!
thanks
david jencks


--
Shawn




Re: Do we want to apply genesis 2.0 resource filtering best practice ?

2009-07-16 Thread Jason Dillon
Me too :-)  I guess that is why I put that in there, just never  
updated projects to use it.


--jason


On Jul 16, 2009, at 1:08 PM, David Jencks wrote:



On Jul 15, 2009, at 10:46 PM, Shawn Jiang wrote:

I noticed there's a maven resource best practice defined in genesis- 
default-flava-2.0.pom.


1, Put normal resource under : ${project.basedir}/ src/main/resources
2, Put the resource that needs filtering under: ${project.basedir}/
src/main/filtered-resources

At the same time, many projects in Geronimo does not follow this  
practice.  A JIRA was opened for this : https://issues.apache.org/jira/browse/GERONIMO-4737


If no objection, I'm going to use GERONIMO-4737 to fix this kind of  
problems in current code base.   Any comments ?


Looks like a good idea to me!
thanks
david jencks


--
Shawn






Do we want to apply genesis 2.0 resource filtering best practice ?

2009-07-15 Thread Shawn Jiang
I noticed there's a maven resource best practice defined in
genesis-default-flava-2.0.pom.

1, Put normal resource under : ${project.basedir}/ src/main/resources
2, Put the resource that needs filtering under: ${project.basedir}/
src/main/filtered-resources

At the same time, many projects in Geronimo does not follow this practice.
A JIRA was opened for this :
https://issues.apache.org/jira/browse/GERONIMO-4737

If no objection, I'm going to use GERONIMO-4737 to fix this kind of problems
in current code base.   Any comments ?
-- 
Shawn