Re: settings or profile; using maven2 ant tasks
Hello Mick, I do not have a solution yet. I am also looking at ivy. Ivy has an ant task to create the build order from a fileset of build.xml files. I have just created an issue on JIRA asking for the creation of such a task in maven2. If my project was to choose the solution Ant + Maven2 Ant tasks, we would definitively need that. Regards, Antoine Mick Knutson wrote: > I have to do the same thing in a few weeks. Would you mind sharing your > solution when you are done please? > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: settings or profile; using maven2 ant tasks
I have to do the same thing in a few weeks. Would you mind sharing your solution when you are done please? On 9/19/06, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: Hello, I am trying to setup builds using Ant and Maven2 ant tasks. I would like to have the following setup : - all third party jars are stored in ClearCase and are accessed through filesystem. It is assumed we setup the filesystem to follow maven layout (do not know exactly how, but will find out) - all internal artifacts are published via WebDav on an Apache Server - developers have on top of that a local, file system based repository, which overrides the WebDav repository - the central builds take the third party jars from file system, and retrieve the internal dependencies from WebDav - for the developers, it works the same with the file system based repository added to the equation Could you suggest how to make this work with a settings.xml or profile.xml, and as little configuration as possible in the individual build files or pom files. We will write pom.xml files for each project. Ideally, we would check in the profile.xml or settings.xml somewhere in ClearClase and make sure that it is used, we do not want the developers to each pick his configuration, rather we want to make it imperative. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks DJ MICK http://www.djmick.com http://www.myspace.com/mickknutson
settings or profile; using maven2 ant tasks
Hello, I am trying to setup builds using Ant and Maven2 ant tasks. I would like to have the following setup : - all third party jars are stored in ClearCase and are accessed through filesystem. It is assumed we setup the filesystem to follow maven layout (do not know exactly how, but will find out) - all internal artifacts are published via WebDav on an Apache Server - developers have on top of that a local, file system based repository, which overrides the WebDav repository - the central builds take the third party jars from file system, and retrieve the internal dependencies from WebDav - for the developers, it works the same with the file system based repository added to the equation Could you suggest how to make this work with a settings.xml or profile.xml, and as little configuration as possible in the individual build files or pom files. We will write pom.xml files for each project. Ideally, we would check in the profile.xml or settings.xml somewhere in ClearClase and make sure that it is used, we do not want the developers to each pick his configuration, rather we want to make it imperative. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 Ant Tasks : is there a task to find a project build order from a parent POM
Hi, I am currently evaluating several dependency/repository managements solutions. Among the possible choices, we are looking at sticking with ant but using the maven2 antlib for repository management, including writing POMs. Is there an Ant task available which can determine a build order from a parent pom ? The class org.apache.maven.project.ProjectSorter in maven-artifact-ant-2.0.4-dep.jar seems to be doing what we need, but I don't know whether this class has an Ant facade. If there is no such task, I will open a JIRA issue to create one. I will be grateful for all feedback from the Maven developers. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checksum failure and how to build maven2 ant tasks?
The difference is a line ending in the remote checksum. We caught a couple of things like that and will try to get them fixed before the beta-1 release. To build the ant tasks, run "m2 assembly:assembly" from the maven-artifact-ant directory. You will need to have built the m2 libraries it depends on first - the easiest way is to just bootstrap the whole thing (from the top level directory) and use the latest version. - Brett On 8/27/05, Rick Mann <[EMAIL PROTECTED]> wrote: > Hi. I tried adding some more dependencies to my ant build script > using the maven-artifact-ant-2.0-alpha-3-dep.jar. When I tried to > build, it reported this: > > > [artifact:dependencies] Resolving dependencies... > > [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ > > mail-1.3.2.pom > > [artifact:dependencies] Transferring 0K > > [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ > > mail-1.3.2.pom > > [artifact:dependencies] Transferring 0K > > [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum > > failed on download: local = > > 'ec6e8527f18fb7b815e6bbc113741cffb51898fe'; remote = > > 'ec6e8527f18fb7b815e6bbc113741cffb51898fe > > [artifact:dependencies] ' - IGNORING > > [artifact:dependencies] Downloading: javax/activation/activation/ > > 1.0.2/activation-1.0.2.pom > > [artifact:dependencies] Transferring 0K > > [artifact:dependencies] Downloading: javax/activation/activation/ > > 1.0.2/activation-1.0.2.pom > > [artifact:dependencies] Transferring 0K > > [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum > > failed on download: local = > > 'fbc8f5ebd0af648dcf3a931705aa3f293be00a5c'; remote = > > 'fbc8f5ebd0af648dcf3a931705aa3f293be00a5c > > [artifact:dependencies] ' - IGNORING > > [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ > > mail-1.3.2.jar > > [artifact:dependencies] [WARNING] Unable to get resource from > > repository http://repo1.maven.org/maven2 > > The checksums seem to be identical, so decided to add some additional > logging to maven. I've checked out the sources to maven2, and am > currently building maven, but I don't know if that will build the ant > artifact .jar. > > Can someone tell me how to build this piece of things? Thanks! > > -- > Rick > > > > - > 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]
Checksum failure and how to build maven2 ant tasks?
Hi. I tried adding some more dependencies to my ant build script using the maven-artifact-ant-2.0-alpha-3-dep.jar. When I tried to build, it reported this: [artifact:dependencies] Resolving dependencies... [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ mail-1.3.2.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ mail-1.3.2.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'ec6e8527f18fb7b815e6bbc113741cffb51898fe'; remote = 'ec6e8527f18fb7b815e6bbc113741cffb51898fe [artifact:dependencies] ' - IGNORING [artifact:dependencies] Downloading: javax/activation/activation/ 1.0.2/activation-1.0.2.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] Downloading: javax/activation/activation/ 1.0.2/activation-1.0.2.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'fbc8f5ebd0af648dcf3a931705aa3f293be00a5c'; remote = 'fbc8f5ebd0af648dcf3a931705aa3f293be00a5c [artifact:dependencies] ' - IGNORING [artifact:dependencies] Downloading: javax/mail/mail/1.3.2/ mail-1.3.2.jar [artifact:dependencies] [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 The checksums seem to be identical, so decided to add some additional logging to maven. I've checked out the sources to maven2, and am currently building maven, but I don't know if that will build the ant artifact .jar. Can someone tell me how to build this piece of things? Thanks! -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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]
Maven2 ant tasks
Hi This looks like a great feature, but I'm having some problems getting it to work. I'm getting this message: *** CHECKSUM MISMATCH - currently disabled fail due to bad repository checksums *** with pretty much every dependency (all the commons-xxx packages, for example). Also, it fails when there is no pom.xml (javassist, commons-codec and many others). Any ideas? Can I disable md5 checking (assuming I would want to, of course...)? Thanks John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
