I have resource filtering setup and working correctly (when I build a
war or mvn jetty:run), but when I deploy to tomcat from Eclipse 3.3/
WTP 1.5, the ${} values are not parsed at that point. Does anyone have
any suggestion to get that working? I saw this with WTP 2.0 (http://docs.codehaus.or
-INF/additionalClasspathElement>
However, my tests don't seem to be returning. I can see it execute the
first one, then just sit there.
On Apr 15, 2008, at 12:21 PM, Jared Blitzstein wrote:
I'm doing a d
I'm doing a demo app using JUnit 4 and Spring annotations and having
some trouble getting maven to run my tests. They launch and run
correctly in eclipse, but mvn test cannot find my xml context files
because they're not on the classpath (they're in /webapp/WEB-INF/) and
my JUnit test is us
we've been
using it so I say +1 for Hudson as well.
On Tue, Apr 15, 2008 at 11:50 AM, Jared Blitzstein
<[EMAIL PROTECTED]> wrote:
Just an FYI, bamboo 2.0 went live today. I've looked at both
Continuum,
Bamboo, Hudson, and Team City. I've hit some weird issues with
Hudson
Just an FYI, bamboo 2.0 went live today. I've looked at both
Continuum, Bamboo, Hudson, and Team City. I've hit some weird issues
with Hudson that I couldn't work out (note: the author was willing to
lend a hand but I didn't have enough time) and had to just move on,
but it built 4 out of 5
t, but
apparently not. Any thoughts?
On Aug 15, 2007, at 3:42 PM, Adam Hardy wrote:
Jared Blitzstein on 14/08/07 19:40, wrote:
I have a few configuration files that need to be filtered when
run. When I run in jetty or build a war for deployment, they are
filtered correctly. But when I deplo
I have a few configuration files that need to be filtered when run.
When I run in jetty or build a war for deployment, they are filtered
correctly. But when I deploy to tomcat from eclipse, they are not. Is
there a way I can make sure eclipse publishes / tomcat uses a
filtered set of values
I have a few apps that I build using maven2 as part of a sweet and
they all have the same version number of 4.8.x (major.minor.build)
right now. When building with maven2 by hand, the pom has
4.8.${buildVersion} and when I call the goal of
war:exploded I pass in -DbuildVersion=5 so this re
ified.
The solution for me was to use the 2.0.2 version of the war-plugin
instead
of 2.0.
Heinrich Nirschl wrote:
On Fri, 2007-04-27 at 15:17 -0400, Jared Blitzstein wrote:
Thanks, I've read that as well as http://maven.apache.org/guides/
getting-started/index.html#How%20do%20
Is there a POM property that can return the absolute path or itself?
I have a dependency that must use the systemPath tag but the absolute
path could be different for all our developers, but it's always the
same relative to the pom. Any idea how to accomplish this with just
entries in the P
Is there a way to pass in maven_opts at run time? I have the
environment variable set and it works when I run maven from my
console, but I'm using a build manager and it seems to be calling
maven and it's ignoring the environment variable some how. I was
wondering if there was a way I could
in profiles in the parent pom, include the
children as in the parent pom, and use the parent tag in
the children to share properties with all your poms.
Or is there a specific reason this is not sufficient?
Wayne
On 5/2/07, Jared Blitzstein <[EMAIL PROTECTED]> wrote:
I have 5 projects
I have 5 projects that I want to build as a suite. I created a multi-
module to do this and it's fine out of the box for just calling the
sub projects. But I need to be able to set variables in the multi-
module to pass in like the version, profile, and some other basic
things. But I also ne
Are you running the deploy goal or something else that executes that
phase? Also I'm not sure if you're supposed to define a target.
On Apr 30, 2007, at 8:48 PM, Baz wrote:
All,
I read the page in
http://maven.apache.org/plugins/maven-antrun-plugin/usage.html but
i still
cannot make a sim
Anyone else have a problem with antrun ignoring overwrite="false"? I
have the following in my pom
maven-antrun-plugin
On Apr 27, 2007, at 12:28 PM, Heinrich Nirschl wrote:
On 4/27/07, Jared Blitzstein <[EMAIL PROTECTED]> wrote:
I'm using the webapp archetype and our apps are configured to have
the properties files in /WEB-INF/config/ rather than /WEB-INF/
classes/ which maven defaults to for resource fil
I'm using the webapp archetype and our apps are configured to have
the properties files in /WEB-INF/config/ rather than /WEB-INF/
classes/ which maven defaults to for resource filtering. I see the
"targetPath" tag in the resource tag but that's only for packages,
not directories outside clas
17 matches
Mail list logo
