Another possibility, if you're not in a J2EE container and don't necessarily
have access to JNDI (or don't want to rely on server config vs. a
self-contained JAR/WAR) is to package all the environment configurations
together and use something like Spring and an environment variable to filter
a
Maybe you could write a shell script to do this for you? This is sort
of a hack, but I don't know of any clean way to do it using Maven. I
have a similar problem with client-specific properties included in one
of the projects and the filtering done by a profile/command argument.
To build all of
motivated users who want to get their work done.
In the (short) amount of time we've spent discussing this issue, you
could have already written and tested your addition to the Eclipse
plugin, and you'd be on dealing with the next issue in your project.
Wayne
On 11/2/07, Dave Feltenberger [EMAIL
Configure the dependencies plugin to copy your two dependencies to a
temporary directory.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
I agree with you, Vanja. And if the developers on the project are
definitely using Eclipse, you can create a Maven Builder for Eclipse
that hooks into the Eclipse build lifecycle. See the
additionalBuildCommands tag here:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html.
All,
Does anybody know if it's possible (and if so, how) to add the native
library location to a classpath entry? Specifically the Eclipse
.project classpath attribute
org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY. I'd
like to have some dlls in my library path without having to
, and contribute
it back for future inclusion in the next release of the Eclipse
plugin.
Wayne
On 11/2/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
All,
Does anybody know if it's possible (and if so, how) to add the native
library location to a classpath entry? Specifically the Eclipse
All -
I'm still experiencing the error described here:
http://jira.codehaus.org/browse/MASSEMBLY-117
It says it was fixed in 2.2-beta-1, which I've verified is the only
version in repository\org\apache\maven\plugins\maven-assembly-plugin
(i.e. I'm using the plugin that was supposed to have fixed
Yes, unfortunately the Eclipse plugin isn't smart enough to put a
blank .project and .classpath file in the typepom/type project(s).
Copy the .project from one of the sub-modules, change the project
name, and remove all the project references. Then do the same with
the .classpath, removing the
All -
I have a multi-module build (maybe 15 modules in all), and one of the
projects is failing to resolve a dependency on an artifact with a
classifier.
WebServiceProject
- WAR artifact
- client stubs (using a classifier)
ProjectConsumingWebService
- depends on WebServiceProject-client
/2/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
All -
I have a multi-module build (maybe 15 modules in all), and one of the
projects is failing to resolve a dependency on an artifact with a
classifier.
WebServiceProject
- WAR artifact
- client stubs (using a classifier
includes
include*.sh/include
/includes
filteredtrue/filtered
/fileSet
/fileSets
the resources are *not* filtered. This isn't intentional, is it?
Dave
On 9/21/07, Dave
All,
I'm having an issue filtering resources with the assembly plugin.
In the documentation at:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-files.html
there is an example of using the assembly plugin. Here is the part in
the pom that says
That's interesting - why separate locations? To avoid having to refresh in
Eclipse when a maven build is run?
On 9/13/07, Jim Sellers [EMAIL PROTECTED] wrote:
I've had the most success with using maven and eclipse by:
1) having both systems build to a separate locations
2) using command line
to ask
users:
I have always used m2. How would that compare to q4e?
Thanks,
Rodrigo
On 9/14/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
That's interesting - why separate locations? To avoid having to refresh
in
Eclipse when a maven build is run?
On 9/13/07, Jim Sellers
eclipse and have it
totally rebuild everything. ;-)
Jim
On 9/14/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
That's interesting - why separate locations? To avoid having to refresh
in
Eclipse when a maven build is run?
On 9/13/07, Jim Sellers [EMAIL PROTECTED] wrote:
I've had
Can't you just pass in a -D argument and execute the argument that's passed
in?
e.g.
mvn install -DantTarget=targetToCall
then in the antrun execution:
ant
antfile=src/main/ant-builds/buildJnlps.xml
target=${antTarget} /
On 9/11/07, Wayne Fay [EMAIL PROTECTED] wrote:
I would just move
to be. Calling Maven
just so it will call Ant for me is too indirect when I can just call
Ant directly, right? What's the advantage when it works fine with ant
target and I have no interest in utilizing the Maven lifecycle for
this particular Ant target/call?
Wayne
On 9/11/07, Dave Feltenberger
I think Arnaud's advice is right if you're going to keep one project for
everything - set up the profiles. You may need to re-arrange the source
tree a little bit, though - looks like you have several different source
trees, one for each category of tests. I'm not sure how the surefire plugin
All,
Do you have recommendations on a good Maven2 plugin for Eclipse? I just
tried M2 Eclipse from Codehaus (http://m2eclipse.codehaus.org) and it seems
a little klunky - my Eclipse projects have build errors (they didn't prior
to the plugin, and compiling using the poms from the command line
Hi -
I have the following flat project layout:
workspace/parent-proj/pom.xml
workspace/child1/pom.xml (artifactId = child-project-1)
workspace/child2/pom.xml (artifactId = childProject2)
workspace/child3/pom.xml etc.
When I run mvn eclipse:eclipse on the parent-proj, it writes out the project
Hi Alex,
I know if you use the Eclipse plugin, you can put this in your parent pom:
...
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
Hi -
I'm working on a project that has the need to do the following, and I can't
think of an elegant way of achieving it using Maven without having to call
out to Ant:
We have several clients, each of which get a customized Java Web Start /
.jnlp file. There are only 5 clients now, but the
23 matches
Mail list logo
