Totally agree... this becomes unmanageable and also means that an artifact
deployed to a repository server with the same coordinates (GAV) will have
different content depending on what profile was activated during the
build..
Bad idea...
On Thu, December 6, 2012 10:30 pm, Anders Hammar wrote:
> I
I would like to state that this is not a good usage of profiles. You should
create four different Maven projects.
/Anders
On Fri, Dec 7, 2012 at 2:08 AM, Ashish Gupta wrote:
> Hi,
>
> I have 4 profiles. There are four directories in the source tree
> corresponding to each profile. I would like
ok, we got it:
see http://jira.codehaus.org/browse/MDEP-187
if you upgrade m-dependency-p to 2.6, you'll get a better error message
then you should probably try to "mvn package site", to have the package phase
executed before the site tries to use the result artifacts
Regards,
Hervé
Le jeudi
Sure here is the build log from the site build (regular build works).
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.2:site (default-cli) on
project stand-alone: failed to get report for
org.apache.maven.plugins:maven-surefire-report-plugin: Failed to
execute goal
org
You need to provide more information.
Ron
On 06/12/2012 2:09 PM, Javix wrote:
it means
true
Regards
From: Ron Wheeler [via Maven] [ml-node+s40175n5735905...@n5.nabble.com]
Sent: 06 December 2012 14:33
To: CAMBOUR Serguei
Subject: Re: Getting profile settings v
it means
true
Regards
From: Ron Wheeler [via Maven] [ml-node+s40175n5735905...@n5.nabble.com]
Sent: 06 December 2012 14:33
To: CAMBOUR Serguei
Subject: Re: Getting profile settings values in a Java class
Or the error messages.
Or what the "it" is in "So I have to
if you run with mvn -X and give us the full stack trace, perhaps we can see
what's going wrong
Le jeudi 6 décembre 2012 06:34:52 David Hoffer a écrit :
> Note that the copy-dependencies goal in the stand-alone module is not
> really relevant/useful in the site build. Rather it's a key part of
>
Bingo! That worked like a charm! Thanks Roy!!
On 2012-12-06 09:49 , "Lyons, Roy" wrote:
>
>This is what you want
>
>
>http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-th
>e
>-poms-not-at-the-top
-
To u
This is what you want
http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-the
-poms-not-at-the-top
On 12/5/12 4:36 PM, "Coarr, Matt" wrote:
>Hello,
>
>I'm able to use "mvn release:prepare" but I run into an issue when I use
>"mvn release:perform".
>
>My problem is th
Note that the copy-dependencies goal in the stand-alone module is not
really relevant/useful in the site build. Rather it's a key part of
the regular...clean, install, release phases...that module just copies
artifacts and builds an aggregate artifact (i.e. it does not have
source code). But I'm
Or the error messages.
Or what the "it" is in "So I have to set it up explicitly every time in
the POM file. Here is my configuration:"
Ron
On 06/12/2012 3:35 AM, Anders Hammar wrote:
This is probably difficult to solve without access to the actual
problematic project.
/Anders
On Thu, Dec
This happens if I build locally and when built with our CI build
server. When I build locally it will use disk C and the disk is not
full. These folders are just the normal maven build folders so if
there is something using the file...it's a Maven process.
We are using Maven3...perhaps the site
Most probably, it means that one of the file is used by another
application, thus cannot be deleted.
On Thu, Dec 6, 2012 at 1:47 PM, David Hoffer wrote:
> Those last two lines make no sense to me as this happens on systems
> with Admin/root permissions. There doesn't seem to be any way this
>
Disk full? Have you tried building from C:?
/Anders
On Thu, Dec 6, 2012 at 1:47 PM, David Hoffer wrote:
> Those last two lines make no sense to me as this happens on systems
> with Admin/root permissions. There doesn't seem to be any way this
> can be a permissions issue, so I assume that's a
Those last two lines make no sense to me as this happens on systems
with Admin/root permissions. There doesn't seem to be any way this
can be a permissions issue, so I assume that's an incorrect/misleading
message.
-Dave
On Wed, Dec 5, 2012 at 11:23 PM, Hervé BOUTEMY wrote:
> please read the la
This is probably difficult to solve without access to the actual
problematic project.
/Anders
On Thu, Dec 6, 2012 at 9:25 AM, Javix wrote:
> I knew those option to desactivate a profile. The problem that I can't
> figure
> out how to solve is WHY the same Maven configuration works in one proje
I knew those option to desactivate a profile. The problem that I can't figure
out how to solve is WHY the same Maven configuration works in one project
and not at all in another? By the way, if comment out the line
true
and run
mvn test -P [profile_to_use]
it works fine too. But in another
17 matches
Mail list logo
