pom.xml for product A
since
I really do not know which version of xyz will pass QA. Does it make
sense?
Baz
On 7/26/07, John Patrick [EMAIL PROTECTED] wrote:
Baz,
I would put this type of information into a profile within the pom. Then
its
simple and repeatable. Also trackable
Baz,
I would put this type of information into a profile within the pom. Then its
simple and repeatable. Also trackable if your project is under source
control, instead of just relying on people knowing the correct command line
arguments to use.
Personally I think building a different version
Initial thoughts are you could have it as a seperate project and get the
dependency plugin to unpack it.
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
On 26/07/07, John Coleman [EMAIL PROTECTED] wrote:
Hi,
We want to farm off some of our common resources (java
mvn install
should solve your issue.
package creates the artifact within the projects target directory, but when
working on a multi module project you need to do install so it uploads the
artifacts into you local repository so they are avaliable to the rest of the
modules.
I hope that helps,
The common approache is to use deploy to get the war to the 'deployment'
location. Install is just to install into your local repository so its
avaliable to other projects your working on.
On 10/05/07, Arrowx7 [EMAIL PROTECTED] wrote:
Hello,
I have mevenide2 installed, and when I run
Is anyone else having issues with surefire plugin ignoring configuration.
According to
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html the
configuration value of skipExec is valid and will compile but not execute
tests.
skiptrue/skip works skipExectrue/skipExec doesn't work
Kiran,
Project level defined repositories can be specified within the pom: e.g.
[Extract from http://maven.apache.org/pom.html]
project
...
repositories
repository
idcentral/id
nameMaven Repository Switchboard/name
layoutdefault/layout
101 - 107 of 107 matches
Mail list logo