[
http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252632#action_252632
]
lisak commented on SUREFIRE-667:
--------------------------------
Here is a blog post about the archetype, the last paragraph explains it...
http://liferayblog.appspot.com/blog/liferay-spring-plugin-with-unit-testing-support
and it can be checked out here :
https://github.com/l15k4/liferay-spring-plugin-with-unit-testing-support
It is not finished (working) due to 2 facts,
they are doing tool, that generates maven dependencies (definitions) based on
list of jars that liferay is using. There is more then hundreds of them, so it
doesn't make sense to hardcode them into pom.xml but generate them (versions
mainly) based on Liferay version.
and this resources issue I'm dealing with ...
if these two issues were gone, it'd would be ready for use
> 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
