On Thursday 06 March 2008 Brian E. Fox wrote:
> This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing
> this on 2.0.8 or earlier?
The reported issue still exists with maven 2.0.9 and maven-eclipse-plugin
2.5.1, so it's probably different to MNG-2277.
Related issues, a sample p
Hi!
On Thursday 06 March 2008 Brian E. Fox wrote:
> This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing
> this on 2.0.8 or earlier?
Actually it was 2.0.7. I'll try it with 2.0.8 as soon as I can and report
back if there are still problems.
- martin
--
Martin Höller
This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing this
on 2.0.8 or earlier?
-Original Message-
From: Martin Höller [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 5:41 AM
To: Maven Users List
Subject: Re: Try to run install before eclipse:eclipse
On
On Thursday 06 March 2008 [EMAIL PROTECTED] wrote:
> Making install run before eclipse:eclipse is a bad idea in some cases.
We would need it only in multi-module projects if some artifacts cannot be
found in the repository.
> In particular, when a project doesn't compile it is currently possible
Users List
Subject: Re: Try to run install before eclipse:eclipse
Making install run before eclipse:eclipse is a bad idea in some cases.
In particular, when a project doesn't compile it is currently possible
to still run eclipse:eclipse. Making install a pre-requisite would block
that, whic
On 06/03/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Making install run before eclipse:eclipse is a bad idea in some cases.
> In particular, when a project doesn't compile it is currently possible
> to still run eclipse:eclipse. Making install a pre-requisite would block
> that, which wo
n eclipse".
Hth,
Nick S.
-Original Message-
From: 109s [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 10:58
To: users@maven.apache.org
Subject: RE: Try to run install before eclipse:eclipse
Poor thing. I don't want to describe every developer what they have to do
after getting the sources
Making install run before eclipse:eclipse is a bad idea in some cases.
In particular, when a project doesn't compile it is currently possible
to still run eclipse:eclipse. Making install a pre-requisite would block
that, which would be really anoying.
I think what the original poster is saying is
Poor thing. I don't want to describe every developer what they have to do
after getting the sources from CVS. I thought eclipse:eclipse could be
enough.
Is there maybe a way for example to call ant and call back maven with
install in this situation?
Greets
Andi
Nick Stolwijk-4 wrote:
>
> Hi,
>
Hi,
This is not possible to configure in your pom file. However, it should be
possible to adjust the maven Eclipse Plugin to execute the install phase. (Just
like surefire-reports execute the test phase) For this there should be a mojo
added to the Maven Eclipse Plugin. This sounds like a nice
10 matches
Mail list logo
