[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250499#action_250499 ]
lisak commented on SUREFIRE-667: -------------------------------- The resources (spring configs mainly) in Liferay plugins are being loaded very traditionally within containers. From container's web application context webapps/APP/WEB-INF/classes/META-INF/spring-stuff.xml ... Liferay portal is webapp depending on a standard jar having META-INF/spring-stuff.xml inside .... I really don't see what is wrong with it. It is actually very convenience as far as I know. You know, Liferay is build with Ant, and there appears to be an effort lastly to slowly migrate to maven. So far there is a possibility to use it for plugins development, but still using Ant is considered the default and it works very well. I prefer maven and the guy who maintains Maven stuff in Liferay isn't very communicative, I sent him some patches a month ago and I didn't even get response back. > Setting up maven resources when testing in addition to testResources > -------------------------------------------------------------------- > > Key: SUREFIRE-667 > URL: http://jira.codehaus.org/browse/SUREFIRE-667 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin > Affects Versions: 2.6 > Reporter: vychtrle > > Hey, > I think that developers would need resource goal of resource plugin to be set > up differently for > test phase, than for build phase. When testing one needs to exclude stuff > from src/main/resources. It seems it can't be done, testResources goal > is irrelevant for this because it can't operate on src/main/* and resource > goal can have only one > setting in pom definition, that takes effect in both test and build > phase... > For example, I'd need following settings to look differently (some > excludes) in testing phase : > <resources> > <resource> > <directory>${project.basedir}/src/main/java</directory> > <includes> > <include>**/*.java</include> > <include>service.properties</include> > </includes> > </resource> > <resource> > > <directory>${project.basedir}/src/main/resources</directory> > <includes> > <include>**/*.xml</include> > <include>**/*.properties</include> > </includes> > </resource> > </resources> > The ideal behavior would be if one could define "src/main/*" in > <testResources> but it unfortunately can't be done right now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira