Carlos Sanchez added a comment - 11/Apr/08 02:29 PM

Carlos Sanchez added a comment - 11/Apr/08 02:29 PM is this the first atlassian release? what was the deal about the group name, technically it should be under com.cenqua.clover or something like that

Nick Pellow added a comment - 15/Apr/08 12:33 AM

Nick Pellow added a comment - 15/Apr/08 12:33 AM Hi Carlos, Since the maven1 project has been mothballed, Atlassian is now hosting the source code (http://svn.atlassian.com/fisheye/changelog/public/contrib/clover/maven1-clover-plugin/trunk ) . This means the plugin can be maintained and remain under version control. The attached plugin has been upgraded to use the latest version of Clover - 2.2.1 . This is something many of our users have asked for. We'd hope the group name can stay the same. This will make upgrading the plugin as simple as getting users to adjust the plugin version id. Please correct me if I am wrong. If you require any more information or details regarding this, please don't hesitate to contact us. Best Regards, Nick

James William Dumay added a comment - 21/Apr/08 11:47 PM

James William Dumay added a comment - 21/Apr/08 11:47 PM Carlos, are we able to get some more traction on this please?

James William Dumay added a comment - 05/Jun/08 02:11 AM

James William Dumay added a comment - 05/Jun/08 02:11 AM Carlos, The POM deployed for clover to the maven2 repository seems to be invalid See http://jira.atlassian.com/browse/CLOV-268 Since MAVENUPLOAD-2078 we have a valid POM for this artifact. I guess the automatic synchronizer does not deploy things that already exist in central? Thanks James

Carlos Sanchez added a comment - 05/Jun/08 12:56 PM

Carlos Sanchez added a comment - 05/Jun/08 12:56 PM removed the <build> section No, things deployed don' t get overwritten