Re: Maven2 ant tasks
commons-codec is fixed. On 4/27/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > 1. ant-optional has problems (can't decide if it belongs to the group > > ant or ant-optional). > > group is ant, artifact id is ant-optional. > > > Actually, as a general question, would it not be > > better to have all the commons downloads in the group commons, rather > > than duplicating the actual library name > > (commons-logging/commons-logging)? > > Definitely, but this is a historical issue. We will now be working > with projects to improve the quality of their exported metadata and > try and introduce some consistency. > > > 2. javassist 3.0 and commons-codec 1.3 have no pom.xml (and some others > > too, but I forgot to note them down) > > I'm working on commons-codec now. I'll note the others down. > > > 4. commons-configuration has all kinds of problems, with the > > mockobjects:mockobjects... dependency and a lot of others besides - > > apparently secondary dependencies - I can't be bothered to list them > > all, there are just too many (in the end, I just hacked the local > > pom.xml to get rid of them). > > Right, I've already spoken to them about that and it seems we may need > to just hack the POM in our copy as well for the moment. > > > Is there any way of providing an 'at-least' definition? For example, I > > could specify that my project required at least version 2.2 of xerces, > > and maven/ant would make sure I had that version or later. It would be > > great to avoid having 73 versions of xerces in the local repository just > > because developers don't upgrade to the latest dot version in their pom > > (or in their projects). If project owners really think there will be > > compatibility problems, perhaps they could specify a general version > > (for example xerces-1.*, xerces-2.*) or a range (xerces-1.4:xerces-1.6). > > This might reduce the flood of downloads that seems to accompany every > > maven project I build. > > We are planning that feature for the June release at the moment. > > > I don't want to be negative - I love this feature of maven and I am very > > happy that it is now available to us ant users. > > No problem. I realise our docs also don't explain things for non-Maven > users very well, so thanks for the feedback. > > - Brett > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 ant tasks
> 1. ant-optional has problems (can't decide if it belongs to the group > ant or ant-optional). group is ant, artifact id is ant-optional. > Actually, as a general question, would it not be > better to have all the commons downloads in the group commons, rather > than duplicating the actual library name > (commons-logging/commons-logging)? Definitely, but this is a historical issue. We will now be working with projects to improve the quality of their exported metadata and try and introduce some consistency. > 2. javassist 3.0 and commons-codec 1.3 have no pom.xml (and some others > too, but I forgot to note them down) I'm working on commons-codec now. I'll note the others down. > 4. commons-configuration has all kinds of problems, with the > mockobjects:mockobjects... dependency and a lot of others besides - > apparently secondary dependencies - I can't be bothered to list them > all, there are just too many (in the end, I just hacked the local > pom.xml to get rid of them). Right, I've already spoken to them about that and it seems we may need to just hack the POM in our copy as well for the moment. > Is there any way of providing an 'at-least' definition? For example, I > could specify that my project required at least version 2.2 of xerces, > and maven/ant would make sure I had that version or later. It would be > great to avoid having 73 versions of xerces in the local repository just > because developers don't upgrade to the latest dot version in their pom > (or in their projects). If project owners really think there will be > compatibility problems, perhaps they could specify a general version > (for example xerces-1.*, xerces-2.*) or a range (xerces-1.4:xerces-1.6). > This might reduce the flood of downloads that seems to accompany every > maven project I build. We are planning that feature for the June release at the moment. > I don't want to be negative - I love this feature of maven and I am very > happy that it is now available to us ant users. No problem. I realise our docs also don't explain things for non-Maven users very well, so thanks for the feedback. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 ant tasks
Hi, These are the problems I came across while setting up my current projects to use the tasks: 1. ant-optional has problems (can't decide if it belongs to the group ant or ant-optional). Actually, as a general question, would it not be better to have all the commons downloads in the group commons, rather than duplicating the actual library name (commons-logging/commons-logging)? 2. javassist 3.0 and commons-codec 1.3 have no pom.xml (and some others too, but I forgot to note them down) 3. mysql-connector-java has the wrong jar name (xx-stable-bin...) 4. commons-configuration has all kinds of problems, with the mockobjects:mockobjects... dependency and a lot of others besides - apparently secondary dependencies - I can't be bothered to list them all, there are just too many (in the end, I just hacked the local pom.xml to get rid of them). Is there any way of providing an 'at-least' definition? For example, I could specify that my project required at least version 2.2 of xerces, and maven/ant would make sure I had that version or later. It would be great to avoid having 73 versions of xerces in the local repository just because developers don't upgrade to the latest dot version in their pom (or in their projects). If project owners really think there will be compatibility problems, perhaps they could specify a general version (for example xerces-1.*, xerces-2.*) or a range (xerces-1.4:xerces-1.6). This might reduce the flood of downloads that seems to accompany every maven project I build. I don't want to be negative - I love this feature of maven and I am very happy that it is now available to us ant users. Best wishes John -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 3:17 PM To: Maven Users List Subject: Re: Maven2 ant tasks > *** CHECKSUM MISMATCH - currently disabled fail due to bad repository > checksums *** This is just a warning, and can be ignored for now (as you can see, it has been disabled due to bad data in the repository). > Also, it fails when there is no pom.xml (javassist, commons-codec and > many others). They should have been converted over - please give us a list of the ones that are causing your problems (or file them here http://jira.codehaus.org/browse/MEV) and we'll look into correcting them. I can see that commons-codec is definitely missing data.. Cheers, Brett - 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]
Re: Maven2 ant tasks
> *** CHECKSUM MISMATCH - currently disabled fail due to bad repository > checksums *** This is just a warning, and can be ignored for now (as you can see, it has been disabled due to bad data in the repository). > Also, it fails when there is no pom.xml (javassist, commons-codec and > many others). They should have been converted over - please give us a list of the ones that are causing your problems (or file them here http://jira.codehaus.org/browse/MEV) and we'll look into correcting them. I can see that commons-codec is definitely missing data.. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
