Re: What does this WARNING mean?

Thanks... I'm not sure why that is a warn either... :-\ --jason On Apr 24, 2008, at 4:40 AM, Hervé BOUTEMY wrote: where: http://maven.apache.org/ref/2.0.9/maven-project/xref/org/apache/maven/project/DefaultMavenProjectBuilder.html#525 hope this will help to understand why: I don't really

a way to extend the dependencies at build time

Hi, i have a strange requirement, i need a possibility to extend the dependencies of a MavenProject in a plugin or component during build time. I tried adding dependencies in a validation phase plugin, with no success. Is there a official way to do this? Maybe a dynamic profile? Defaults

Re: a way to extend the dependencies at build time

I discourage any dynamic tweaking of the project. Among other things is breaks IDE integration. appfuse' warpath plugin does this sort of thing somehow. I would say it's a hack however and might not work in future versions.. Milos On Thu, Apr 24, 2008 at 9:33 AM, Richard van Nieuwenhoven [EMAIL

Re: a way to extend the dependencies at build time

Hi, the reason i need it is that a plugin generates code that depends on a framework in a specific configuration. And the knowledge witch combination of frameworks is needed, is provided by the generator (the plugin). I do not like to duplicate this knowledge in evey module that uses the plugin,

Re: a way to extend the dependencies at build time

oh well. you assume the IDE integration is and shall be running the build. I try to avoid that for performance reasons in netbeans integration. Milos On Thu, Apr 24, 2008 at 12:24 PM, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote: Hi, the reason i need it is that a plugin generates code

Re: a way to extend the dependencies at build time

On 24/04/2008, Richard van Nieuwenhoven [EMAIL PROTECTED] wrote: Hi, the reason i need it is that a plugin generates code that depends on a framework in a specific configuration. And the knowledge witch combination of frameworks is needed, is provided by the generator (the plugin). I do

Re: a way to extend the dependencies at build time

Hi, That is why i ask for an official solution, a plugin will probably not work. But is there an other? like a custom dependence resolution component for this project. Or a global custom dependence resolution component. Or a way to dynamically create a global or local profile. Or .. any

[Discuss] New Jira project for shared?

Hi, I am preparing the release of maven-doxia-tools (MSITE-301) which is the first step for several plugins releases. Background: - maven-doxia-tools is in shared svn space and the Jira project for shared is a MNG component. - we have also an component called doxia integration in MSITE -

RE: a way to extend the dependencies at build time

Have you looked at the new import scope feature? -Original Message- From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 6:47 AM To: Maven Developers List Subject: Re: a way to extend the dependencies at build time Hi, That is why i ask for an

RE: [Discuss] New Jira project for shared?

I thought we already had this, but I guess it was for the sandbox. Sounds logical to add it for shared. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vincent Siveton Sent: Thursday, April 24, 2008 8:51 AM To: Maven Developers List Subject: [Discuss]

Re: a way to extend the dependencies at build time

I did this with Maven 1 and I'm sure it would work with Maven 2, but it may not be what your want. The way I handled it was to dynamically construct the pom in a target directory along with the project files and then invoke the goal (plugin) calls Maven again just for that project. Richard

Re: [Discuss] New Jira project for shared?

Sounds good to me, MSHARED? Mark On 24/04/2008, Vincent Siveton [EMAIL PROTECTED] wrote: Hi, I am preparing the release of maven-doxia-tools (MSITE-301) which is the first step for several plugins releases. Background: - maven-doxia-tools is in shared svn space and the Jira project

Where should release plugin copy from?

In my experience the release plugin currently works like this: 1. modifies working copy poms to release version 2. commits poms 3. does a repo-repo copy to the new tag 4. updates working copy poms to the new version 5. commits new-version poms. Some projects (activemq) have a versioning scheme

RE: Where should release plugin copy from?

I was pretty sure it does tag from the working copy? -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 1:07 PM To: Maven Developers List Subject: Where should release plugin copy from? In my experience the release plugin currently works like

Re: [proposal] eclipse plugin extensibility

Flex / Flex builder I created a flexbuilder-mojo, who inherit from maven-eclipse-plugin If this goes on, I can create flexbuilder extension. VELO On Wed, Apr 23, 2008 at 9:39 AM, Simone Gianni [EMAIL PROTECTED] wrote: Hi Nicolas, yes, many Maven plugins have an Eclipse counterpart, and

Re: Where should release plugin copy from?

On Apr 24, 2008, at 10:18 AM, Brian E. Fox wrote: I was pretty sure it does tag from the working copy? well from a release I did on march 12 New Revision: 636232 URL: http://svn.apache.org/viewvc?rev=636232view=rev Log: [maven-release-plugin] prepare release directory-parent-1.0

RE: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3

Taking back the -1 since I found this to be a local configuration issue. I found that the default behavior no longer prompts you for the version you are creating, just the group,artifact,version,package. You have to say N to the prompt and re-enter all the values to change the version. This is

[VOTE][Result] Release Maven Archetype plugin version 2.0-alpha-3 [take 2]

Hi It is now time to count the votes. +1 non binding: Raphaël, Jason, Milos +1 binding: Lukas, Arnaud -1 binding: Brian (in the wrong thread but still counted ;-)) The vote failed. I fix the issue Brian saw with version and i rewrap for a new vote. Regards, Raphaël 2008/4/23 Milos Kleint

Re: [Discuss] New Jira project for shared?

For me too, I created MPA-113 Cheers, Vincent 2008/4/24 Mark Hobson [EMAIL PROTECTED]: Sounds good to me, MSHARED? Mark On 24/04/2008, Vincent Siveton [EMAIL PROTECTED] wrote: Hi, I am preparing the release of maven-doxia-tools (MSITE-301) which is the first step for

[VOTE] Release Maven archetype plugin version 2.0-alpha-3 [take 3]

Hi, We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088 Staging repo: http://people.apache.org/~rafale/archetype-stage-repository/ Staging site: http://maven.apache.org/plugins/maven-archetype-plugin-2.0-alpha-3/ Guide to testing

RE: [VOTE] Release Maven archetype plugin version 2.0-alpha-3 [take 3]

+1 looks good. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raphaël Piéroni Sent: Thursday, April 24, 2008 6:10 PM To: Maven Developers List Subject: [VOTE] Release Maven archetype plugin version 2.0-alpha-3 [take 3] Hi, We solved 22 issues:

Re: [Discuss] New Jira project for shared?

On 24/04/2008, at 8:58 PM, Brian E. Fox wrote: I thought we already had this, but I guess it was for the sandbox. Sounds logical to add it for shared. That's what I thought too. Go for it. - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/

Re: Where should release plugin copy from?

I think we've talked a bit about a more flexible workflow to the release, and doing some alternatives like creating a branch at the release point and switching to it. I think it would be best for us to lock down a 2.0 final release first before taking something like that on, but if you

[jira] Subscription: Design Best Practices

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-612 implement conflict resolution techniques

Re: [VOTE] Release Maven archetype plugin version 2.0-alpha-3 [take 3]

+1 --jason On Apr 25, 2008, at 5:10 AM, Raphaël Piéroni wrote: Hi, We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=14088 Staging repo: http://people.apache.org/~rafale/archetype-stage-repository/ Staging site: