Hi Jason,
On 01/05/10 13:54, Jason van Zyl wrote:
On May 1, 2010, at 10:31 AM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
Didn't Henrique just remove the packaging element from the component definition
of the artifact handler to get this to work?
In fact, I have also changed the plu
On May 1, 2010, at 10:31 AM, Benjamin Bentmann wrote:
> Jason van Zyl wrote:
>
>> Didn't Henrique just remove the packaging element from the component
>> definition of the artifact handler to get this to work?
>
> Yes, to get the artifact handler to work with Maven 2 as originally intended.
>
Jason van Zyl wrote:
Didn't Henrique just remove the packaging element from the component definition
of the artifact handler to get this to work?
Yes, to get the artifact handler to work with Maven 2 as originally
intended.
Benjamin
---
On May 1, 2010, at 7:15 AM, Benjamin Bentmann wrote:
> Jason van Zyl wrote:
>
>> Why don't we just proactively ignore the packaging in artifact handlers?
>
> M3 already does, that was the reason for the issue because the
> maven-wolifecycle-plugin relies on the bug in Maven 2.
>
Didn't Henri
Jason van Zyl wrote:
Why don't we just proactively ignore the packaging in artifact handlers?
M3 already does, that was the reason for the issue because the
maven-wolifecycle-plugin relies on the bug in Maven 2.
Benjamin
On Apr 30, 2010, at 3:59 PM, Benjamin Bentmann wrote:
> Henrique Prange wrote:
>
>> It did the trick. The solution worked for both Maven 2.2.1 and Maven 3,
>> as you said.
>
> Glad to hear.
>
Why don't we just proactively ignore the packaging in artifact handlers?
>> Just out of curiosity, wi
Henrique Prange wrote:
It did the trick. The solution worked for both Maven 2.2.1 and Maven 3,
as you said.
Glad to hear.
Just out of curiosity, will the definition of a lifecycle extension
change after Maven 3 integration with Guice is complete?
Not sure what kind of change you exactly ha
Hi Benjamin,
It did the trick. The solution worked for both Maven 2.2.1 and Maven 3,
as you said.
Just out of curiosity, will the definition of a lifecycle extension
change after Maven 3 integration with Guice is complete?
Thank you very much for your help.
Cheers,
Henrique
On 30/04/10 1
Henrique Prange wrote:
When building from the parent module using Maven 3, the following
classpath entry has been produced:
[...]/Wonder/Frameworks/Core/JavaWOExtensions/target/JavaWOExtensions-5.0.0-SNAPSHOT.woframework
And the produced classpath entry for the same build using Maven 2.2.1:
[
Henrique Prange wrote:
I've tried to build a project with multiple modules using Maven
3.0-beta-1 unsuccessfully. I got some weird compilation problems
"weird compilation problems" belong to those kind of problems that are
nearly impossible to troubleshoot. Concrete solutions require concrete
Hi all,
I've tried to build a project with multiple modules using Maven
3.0-beta-1 unsuccessfully. I got some weird compilation problems on
child modules when trying to build from the parent module. But if I try
to build the child module directly, it works.
Any thoughts if is it a bug or som
I've not been able to find out where that came back from recently, but
the build was broken due to it.
You need to remove maven-assembly-plugin from your local cache and let
it be downloaded again.
- Brett
On 18/8/06 1:29 AM, Arnaud Bailly wrote:
Hi,
I am trying to build maven from sources
Hi,
I am trying to build maven from sources (trunk) and I have
problems. Compilation of components seems to be ok but it chokes on
CLI creation. Here is the full error trace:
Running Maven...
/home/nono/soft/maven/bootstrap/target/installation/bin/mvn -e --batch-mode
clean assembly:assembly
+ E
13 matches
Mail list logo
