Hi,
I have this failure on my laptop too.
Someone else have it too ?
--
Olivier
8/2/22, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Online report :
> http://maven.zones.apache.org/continuum/buildResult.action?buildId=42494&projectId=13
>
> Build statistics:
> State: Failed
> Previous State: Fa
Yeah, thanks, I know about using multiple executions.
It is a shame that you have to put an execution in an arbitrary phase
just to make the configuration behave (at least it seems that way to
me). The use case that I have fits very nicely into
generate-test-resources to export date from a source
Put multiple blocks inside the . You would
probably need to use two phases though.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ryan Ovrevik
Sent: Thursday, February 21, 2008 10:19 PM
To: dev@maven.apache.org
Subject: Re: Configuration not selected pro
Issue Subscription
Filter: Design & Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-3313NetBeans projects, more than ant project, more than fre
I was specifying a plugin twice with-in a profile to control the order
of operations across two plugins with in a particular phase. The
scenario is as follows (simplified):
* Use sql-maven to drop and create a database.
* Use dbunit to import some data.
* Use sql-unit again to drop some columns on
No one uses this anymore and I turned off the registry a long time
ago. I think before the 2.0.4 release. Not sure if this is needed at
all anymore.
Moving toward requiring versions and no auto-update will render this
moot as well.
On 21-Feb-08, at 4:30 PM, [EMAIL PROTECTED] wrote:
Auth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
just to give my feedback on the thread:
+1 for NOT overloading 2.1
When it is about further versions and long term future of maven:
- -infinity for
artifact="org.apache.maven:maven-project:2.0.8"
How do you want to express versions range
+1
On Thu, Feb 21, 2008 at 2:01 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Hi all,
> I'd like to propose that we release both the assembly plugin and one of
> its shared-component dependencies: maven-repository-builder. See below for
> more information on what's included in these releases. I hav
Vincent Siveton wrote:
Hi,
2008/2/20, Dennis Lundberg <[EMAIL PROTECTED]>:
I think that we should be able to copy that entire file to maven-parent.
That way all our projects will share the same look.
It was the goal :)
We should probably *not* copy the though, because the main Maven
sit
Hi,
I have upgraded jar plugin and surefire plugin versions (2.2 and
2.4.2) in rev 629958.
Thanks,
--
Olivier
2008/2/21, Dennis Lundberg <[EMAIL PROTECTED]>:
> Wendy Smoak wrote:
> > On Tue, Feb 19, 2008 at 1:52 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >> Hi
> >>
> >> To get the late
Vincent Siveton wrote:
Hi,
I noticed that due to [1], the groupId for
maven-plugin-testing-harness is no more org.apache.maven.shared.
Moreover, we will do a jump from 1.1 to 2.4 [2].
Similar problems occur for maven-plugin-tools-* and only
maven-plugin-plugin is not affected by this version pb.
Wendy Smoak wrote:
On Tue, Feb 19, 2008 at 1:52 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi
To get the latest version of maven-source-plugin into our toolchain, I'd
like to release maven parent pom r628845 as version 8.
Source:
https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom
Hi all,I'd like to propose that we release both the assembly plugin and one of its shared-component dependencies: maven-repository-builder. See below for more information on what's included in these releases. I have two staging repositories for these projects:maven-assembly-plugin:http://people.ap
unless you have to define the plugin more than once because of profiles
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IIRC, model validation happens after inheritance and profile
injection, to ensure the project has every opportunity to fill in
missing sections.
So, performing this sort of check in the model validator would be
appropriate. I added a check for duplicate dependencies recently,
IIRC, and th
Work in progress ...
I've created a PlexusClassPathXmlApplicationContext that accept both Spring
context files and plexus descriptors as resources.
I also enhanced the XSLT to declare a bean alias for plexus components :
- plexus roles are by convention the FQCN of the interface
- spring IDs are
I was thinking this was across multiple poms (inheritance) but yes in
the same pom that's not good.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 21, 2008 10:19 AM
To: Maven Developers List
Subject: Re: Configuration not selected properly when a pl
We should probably add some logic to the project/POM validator to
detect duplicated plugin entries (by the plugin's
groupId:artifactId:version) and fail the build with a useful error
message. That would prompt users to consolidate multiple plugin
sections that refer to the same plugin.
-j
On Tue, Feb 19, 2008 at 1:52 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Hi
>
> To get the latest version of maven-source-plugin into our toolchain, I'd
> like to release maven parent pom r628845 as version 8.
>
> Source:
>
> https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=
Hi,
2008/2/20, Wendy Smoak <[EMAIL PROTECTED]>:
> It looks like some changes in maven-plugin-testing-harness caused
> errors in the tests in the Install plugin. This is the first build
> that shows the problem:
>
> http://maven.zones.apache.org/continuum/buildResult.action?buildId=39712&proje
20 matches
Mail list logo