Check the dependenciesToScan property in the latest Failsafe version. It
tells the plugin to scan for the test class patterns in the specified
artifacts.
Am Freitag, 18. Oktober 2013 schrieb Dan Kaplan :
I've found an ok solution. I just extend the class in the module I plan
to run the tests
Hi!
Here is the short version of what I want: I've got a JEE6 webapp with a
web.xml file, where the context-parameter facelets.DEVELOPMENT should be
enabled in development mode but disabled for releases.
My idea to solve this problem is as follows:
1) Define the context parameter in web.xml
Hi,
You should just override the context-param when deploying on the real
production server.
On Fri, Oct 18, 2013 at 9:40 AM, Martin Hoeller mar...@xss.co.at wrote:
Hi!
Here is the short version of what I want: I've got a JEE6 webapp with a
web.xml file, where the context-parameter
On 18 Okt 2013, Adrien Rivard wrote:
You should just override the context-param when deploying on the real
production server.
What do you mean by override?
You don't want me to extract the released WAR artifact (which is actually
included in an EAR), modify the web.xml and repackage it. Do
Most server allow you to externally override context-param without
modifying the war (which would be even worst than using profiles IMO)
see
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html#Context_Parameters
for
tomcat
On Fri, Oct 18, 2013 at 10:45 AM, Martin Hoeller
On 18 Okt 2013, Adrien Rivard wrote:
Most server allow you to externally override context-param without
modifying the war
I can't find anything for JBoss 7, which is the application-server i use.
If this is not possible, your suggestion doesn't work for me :(
(which would be even worst than
https://issues.jboss.org/browse/AS7-4296
On 18 October 2013 11:10, Martin Hoeller mar...@xss.co.at wrote:
On 18 Okt 2013, Adrien Rivard wrote:
Most server allow you to externally override context-param without
modifying the war
I can't find anything for JBoss 7, which is the
Hi,
I am using the maven-dependency-plugin version 2.8.
If I run mvn dependency:build-classpath for one of my project I get the
correct order of the dependencies, but if I generate the classpath in the
maven build itself of my project then the order is messed up.
The plugin configuration I am
Hi,
I am building snapshots artifacts in CI tool Hudson and deploying them into
nexus using distribution management in my pom.xml and Snapshot is getting
replaced by timestamp in final artifact name on uploading into nexus because
non-unique snapshots are no more valid in maven 3, that is fine.
I tried using that, but it didn't work. Probably because includes
still looks on the file system?
On Thu, Oct 17, 2013 at 11:10 PM, Andreas Gudian
andreas.gud...@gmail.comwrote:
Check the dependenciesToScan property in the latest Failsafe version. It
tells the plugin to scan for the test
It should be looking in the class path, not the file system.
On Oct 18, 2013, at 12:42 PM, Dan Kaplan d...@mirthcorp.com wrote:
I tried using that, but it didn't work. Probably because includes
still looks on the file system?
On Thu, Oct 17, 2013 at 11:10 PM, Andreas Gudian
Thanks for clarifying about the prerequisite for Maven committer school. I
asked this question to know if there is any implicit prerequisite like
Must know, Maven, Java, JIRA etc...
I would like to be volunteer for this. Please guide.
On Sat, Oct 12, 2013 at 11:03 PM, Stephen Connolly
12 matches
Mail list logo
