Vincent Massol wrote: > 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+?
It's already on the list. Please take a look at the design wiki. > 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. Firstly, the plugins should have *nothing* to do with the bootstrap. Except for plugins requiring a new version of Maven, you can use the last release, otherwise use a nightly. For the plugins that you believe are buggy or missing features in the last release, just install those ones. Don't install everything, every day, because you'll end up with a very unstable system. Even better, tell us which things are preventing you from doing your work. Last time I checked, you are a developer here. Engage in discussions about what needs to be done to get those plugins released. Maybe even help out fixing some bugs to get the release over the line. > 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. The deploy situation hasn't changed since 2.0. There is no magic combination: if you are using scp or sftp, then its wagon-ssh. If you are using scpexe, its wagon-ssh-external. The problems we have: * jsch has a problem with the session being down. Retrying fixes it. * scpexe has problems with setting the wrong permissions by default * scpexe doesn't work with putty as of the last release. * all of them are quite slow as we don't aggregate the operations under one connection I recommend we use sftp everywhere and just retry if there are failures until we find a better solution, as scpexe is just broken with those two issues. If you have any other issues, please report them. IMO, someone should spend some time on this before we release 2.0.2. > 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. I'll do it now. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
