[
http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250412#action_250412
]
Kristian Rosenvold commented on SUREFIRE-667:
---------------------------------------------
The common way this problem is handled is by making a maven-plugin that handles
the starting the container environment. Such a plugin runs in its own
classloader, and can use configuration/classpath that is totally separate from
the module being built.
This would normally mean the module itself (the portlet) will not have direct
dependencies to the container environment, and this would normally avoid most
of the problems you describe. There are a *lot* of different examples of this,
for instance weblogic-maven-plugin, weblogic-jetty-plugin or some of the cargo
stuff.
I do not know if Liferay has/uses a plugin of its own or can use plugins for
the underlying container. In combination with failsafe it should be fairly easy
to fix. If you need to adapt one of the existing plugins to make it work with
Liferay, that should also be fairly simple and could probably be contributed
back to Liferay.
> 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
