> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: lundi 2 janvier 2006 22:04 > To: Maven Developers List > Subject: Re: need help for deploying the clover plugin v2.0 > > still thinking about the best way to deal with this. We don't want to > lock the site into a specific version of a plugin every time - it should > be the latest, but we also don't want to use snapshots under some > circumstances.
So we don't have a way to express "latest version but not a snapshot" in our dependencies, right? Maybe this would be a nice feature for Maven 2.1+? > Basically, I just build the plugins I am working on and am prepared to > deal with the consequences. I don't think it's wise to always bootstrap > code that you are not working on or don't specifically need the new > features. Not sure I understand what you mean here. Are you saying that I should not be building trunk or something like that? As a user, you're right, I would rather not have to do this. It's just that if I don't do it I cannot use the plugins as they're buggy or missing the feature I need. Right now I cannot deploy the clover plugin at all as I get errors with all versions I use. I need to figure out the right combination or trunk vs 2.0.2 branch and plugin trunk versions vs released version of plugins. I haven't found it yet and right now both trunk and 2.0.2 branch are failing for me. As I said, I'd be happy for someone to simply run "mvn deploy" and "mvn site site:deploy" for me on the tag for clover plugin v2.0. If not I'll do it but I may require a few more days to find a working solution. Thanks -Vincent > Vincent Massol wrote: > > > >> -----Original Message----- > >> From: Brett Porter [mailto:[EMAIL PROTECTED] > >> Sent: lundi 2 janvier 2006 11:21 > >> To: Maven Developers List > >> Subject: Re: need help for deploying the clover plugin v2.0 > >> > >> Vincent Massol wrote: > >>> Hi there, > >>> > >>> I'm trying to deploy the clover plugin v2.0 but I'm failing. Several > >> issues: > >>> * It seems I'm not part of the maven group on beaver and I get the > >> following > >>> error: > >>> > >> Now you are. We'll flip over to the Apache repo soon. > >>> * Running "mvn site" fails: > >>> > >> Please don't use snapshot plugins for publishing releases. > >> > > > > Ok, I'll try to switch but shouldn't this be specified by the top level > > pom.xml? Maybe in a deployment profile? > > > > Thanks > > -Vincent > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
