RE: More details required on new upload procedure
> For each version, I agree. But also for each artifact generated by the > project, no? > > Imagine the aspectj jars. There are 2: aspectjrt.jar and > aspectjtools.jar. We need 2 POMs, one for each, right? Definitely. Simply in maven-land those are two projects so we need two poms. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
On Sun, 2004-06-13 at 10:13, Vincent Massol wrote: > > ATM, I just want to help deploy artifacts to ibiblio. At the very least > I need to understand the end format required on ibiblio so that I can > mimic it manually. Hokay. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
On Sun, 2004-06-13 at 10:13, Vincent Massol wrote: > > > You need 3 poms (so 2 poms are needed for maven-jar-plugin) > > You need to have a pom for each combinataion of a triple > > (artifactId, groupId, version) > > For each version, I agree. But also for each artifact generated by the > project, no? > > Imagine the aspectj jars. There are 2: aspectjrt.jar and > aspectjtools.jar. We need 2 POMs, one for each, right? Yup. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 13 June 2004 19:26 > To: Maven Developers List > Subject: Re: More details required on new upload procedure > > On Sun, 2004-06-13 at 08:57, Vincent Massol wrote: > > Hi, > > > > I'm in the process of uploading the abbot jars on ibiblio. With the new > > procedure I also need to upload some POM (please note that the abbot > > build does not use maven). I've read > > http://maven.apache.org/repository-upload.html but I still have a few > > questions: > > > > 1/ Should there be a POM file per artifact? That sounds strange to me as > > a POM is related to a project rather than an artifact but I've looked at > > ibiblio/maven and it seems that's what's done in some cases (like > > aspectj). I'd like confirmation. > > The POM is related to a project which produces an artifact. I think > maybe you're confusing that with a group like aspectj. Everytime > anything is deployed to ibiblio a POM must be present. The bundle > creating tool takes care of that for maven projects. Yep. I have since answered my own email. My understand now is that we need a POM for each artifact. > > > 2/ What is the minimal information the POM should contain. If it only > > contains element + //, is it ok? Don't > > tell me it requires a full POM! That would be as bad as lengthy as > > mavenizing each project... > > Discussed on the list and I see that Carlos answered, feel free to place > the information in the FAQ. Yep. Will do. > > > 3/ What name should the pom file(s) have? -.pom? > > If the project is not yet versioned, should SNAPSHOT be used? > > Just put it in as project.xml. The tool in maven-components/maven-meeper > will take care of the rest. They are just shell scripts for now but a > full blown app will come with m2 alpha 1. > > > 4/ Where is located the tool that will take an upload bundle (result of > > create-upload-bundle)? I'd like to see what operations it does so that I > > can deliver something equivalent or even better, use it... > > The new tool will use wagon so you'll want to coordinate with myself and > Michal before starting anything. The shell scripts work perfectly fine > for now and now that we have update JIRA on codehaus I can now use the > xmlrpc interface. If you want to help with meeper just contact me > offline and I can point you in the right direction if you want to help. ATM, I just want to help deploy artifacts to ibiblio. At the very least I need to understand the end format required on ibiblio so that I can mimic it manually. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
> -Original Message- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 13 June 2004 19:22 > To: Maven Developers List > Subject: RE: More details required on new upload procedure > > > > > > > > We need one POM per each version of the project but for upload process > > > it is sane to required a presence of the pom everytime even if it is > > > already in the repository. > > > > Are you sure? That's not exactly what's on ibiblio. In several places, > > there is one POM per artifact, which I think is right. > > > > In any case, it needs better explanation in the FAQ section I think. > > > > Not sure if I understand you. What I am saying is that if you have > > maven-jar-plugin-1.1.jar > maven-jar-plugin-1.2.jar > maven-artifact-plugin-1.1.jar > > You need 3 poms (so 2 poms are needed for maven-jar-plugin) > You need to have a pom for each combinataion of a triple > (artifactId, groupId, version) For each version, I agree. But also for each artifact generated by the project, no? Imagine the aspectj jars. There are 2: aspectjrt.jar and aspectjtools.jar. We need 2 POMs, one for each, right? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
On Sun, 2004-06-13 at 11:21, Vincent Massol wrote: > > > 4/ Where is located the tool that will take an upload bundle > > > (result of create-upload-bundle)? I'd like to see what > > > operations it does so that I can deliver something equivalent > > > or even better, use it... > > > > Don't know ;) > > Jason? maven-component/maven-meeper Just some shell scripts for now, but they work well and I will use those until meeper is finished. The xmlrpc interface is now available in the version of JIRA we have and the ssh/scp wagon now works well so it is now possible to make the first simple version of meeper. Meeper is also the sample application for the Maven book btw. > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: More details required on new upload procedure
On Sun, 2004-06-13 at 08:57, Vincent Massol wrote: > Hi, > > I'm in the process of uploading the abbot jars on ibiblio. With the new > procedure I also need to upload some POM (please note that the abbot > build does not use maven). I've read > http://maven.apache.org/repository-upload.html but I still have a few > questions: > > 1/ Should there be a POM file per artifact? That sounds strange to me as > a POM is related to a project rather than an artifact but I've looked at > ibiblio/maven and it seems that's what's done in some cases (like > aspectj). I'd like confirmation. The POM is related to a project which produces an artifact. I think maybe you're confusing that with a group like aspectj. Everytime anything is deployed to ibiblio a POM must be present. The bundle creating tool takes care of that for maven projects. > 2/ What is the minimal information the POM should contain. If it only > contains element + //, is it ok? Don't > tell me it requires a full POM! That would be as bad as lengthy as > mavenizing each project... Discussed on the list and I see that Carlos answered, feel free to place the information in the FAQ. > 3/ What name should the pom file(s) have? -.pom? > If the project is not yet versioned, should SNAPSHOT be used? Just put it in as project.xml. The tool in maven-components/maven-meeper will take care of the rest. They are just shell scripts for now but a full blown app will come with m2 alpha 1. > 4/ Where is located the tool that will take an upload bundle (result of > create-upload-bundle)? I'd like to see what operations it does so that I > can deliver something equivalent or even better, use it... The new tool will use wagon so you'll want to coordinate with myself and Michal before starting anything. The shell scripts work perfectly fine for now and now that we have update JIRA on codehaus I can now use the xmlrpc interface. If you want to help with meeper just contact me offline and I can point you in the right direction if you want to help. > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
> > > > We need one POM per each version of the project but for upload process > > it is sane to required a presence of the pom everytime even if it is > > already in the repository. > > Are you sure? That's not exactly what's on ibiblio. In several places, > there is one POM per artifact, which I think is right. > > In any case, it needs better explanation in the FAQ section I think. > Not sure if I understand you. What I am saying is that if you have maven-jar-plugin-1.1.jar maven-jar-plugin-1.2.jar maven-artifact-plugin-1.1.jar You need 3 poms (so 2 poms are needed for maven-jar-plugin) You need to have a pom for each combinataion of a triple (artifactId, groupId, version) Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
> -Original Message- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 13 June 2004 19:04 > To: Maven Developers List > Subject: Re: More details required on new upload procedure > > On Sun, 2004-06-13 at 14:57, Vincent Massol wrote: > > Hi, > > > > I'm in the process of uploading the abbot jars on ibiblio. With the new > > procedure I also need to upload some POM (please note that the abbot > > build does not use maven). I've read > > http://maven.apache.org/repository-upload.html but I still have a few > > questions: > > > > 1/ Should there be a POM file per artifact? That sounds strange to me as > > a POM is related to a project rather than an artifact but I've looked at > > ibiblio/maven and it seems that's what's done in some cases (like > > aspectj). I'd like confirmation. > > > > We need one POM per each version of the project but for upload process > it is sane to required a presence of the pom everytime even if it is > already in the repository. Are you sure? That's not exactly what's on ibiblio. In several places, there is one POM per artifact, which I think is right. In any case, it needs better explanation in the FAQ section I think. [snip] -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: More details required on new upload procedure
On Sun, 2004-06-13 at 14:57, Vincent Massol wrote: > Hi, > > I'm in the process of uploading the abbot jars on ibiblio. With the new > procedure I also need to upload some POM (please note that the abbot > build does not use maven). I've read > http://maven.apache.org/repository-upload.html but I still have a few > questions: > > 1/ Should there be a POM file per artifact? That sounds strange to me as > a POM is related to a project rather than an artifact but I've looked at > ibiblio/maven and it seems that's what's done in some cases (like > aspectj). I'd like confirmation. > We need one POM per each version of the project but for upload process it is sane to required a presence of the pom everytime even if it is already in the repository. > 2/ What is the minimal information the POM should contain. If it only > contains element + //, is it ok? Don't > tell me it requires a full POM! That would be as bad as lengthy as > mavenizing each project... > I think this is minimal. But more is better. For example dependency report is already able to point you to the web site of given dependency if url tag is present. License section can be used for determining valid license of your project (e.g. if you have been infected by GPL viral license) > 3/ What name should the pom file(s) have? -.pom? yes. > If the project is not yet versioned, should SNAPSHOT be used? > Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
> -Original Message- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: 13 June 2004 13:14 > To: 'Maven Developers List' > Subject: RE: More details required on new upload procedure > > Hi Vincent, > > Hope it helps > I does, thanks. See below. > > > -Original Message- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 13, 2004 2:58 PM > > To: 'Maven Developers List' > > Subject: More details required on new upload procedure > > > > Hi, > > > > I'm in the process of uploading the abbot jars on ibiblio. > > With the new procedure I also need to upload some POM (please > > note that the abbot build does not use maven). I've read > > http://maven.apache.org/repository-upload.html but I still have a few > > questions: > > > > 1/ Should there be a POM file per artifact? That sounds > > strange to me as a POM is related to a project rather than an > > artifact but I've looked at ibiblio/maven and it seems that's > > what's done in some cases (like aspectj). I'd like confirmation. > > Each artifact may have different dependencies (as aspectj has) Ah, right! I got confused. Yeah, we're talking about artifacts not projects. It makes sense to have one POM per artifact. However that's not the way the "create upload bundle" goal seem to work. It simply puts the project's project.xml file in the bundle. Probably a limitation. There should definitely be a pom per artifact to support transitive dependencies. > > > > > 2/ What is the minimal information the POM should contain. If > > it only contains element + > > //, is it ok? Don't tell me it requires a > > full POM! That would be as bad as lengthy as mavenizing each > > project... > > Quoting Jason van Zyl: > > > If you don't use maven then it would at least be nice to have the > > groupId > artifactId > name > currentVersion > dependencies > > > I suppose "artifactId" should be "id" ok. Cool. I believe this should be added to the FAQ. Jason, ok if I add this to the FAQ? > > > > > 3/ What name should the pom file(s) have? > name>-.pom? > > If the project is not yet versioned, should SNAPSHOT be used? > > The upload bundles I've seen use "project.xml" That's before they are processed. It seems the names in the repo are -.pom which makes sense. > > > > > 4/ Where is located the tool that will take an upload bundle > > (result of create-upload-bundle)? I'd like to see what > > operations it does so that I can deliver something equivalent > > or even better, use it... > > Don't know ;) Jason? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More details required on new upload procedure
Hi Vincent, Hope it helps > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 13, 2004 2:58 PM > To: 'Maven Developers List' > Subject: More details required on new upload procedure > > Hi, > > I'm in the process of uploading the abbot jars on ibiblio. > With the new procedure I also need to upload some POM (please > note that the abbot build does not use maven). I've read > http://maven.apache.org/repository-upload.html but I still have a few > questions: > > 1/ Should there be a POM file per artifact? That sounds > strange to me as a POM is related to a project rather than an > artifact but I've looked at ibiblio/maven and it seems that's > what's done in some cases (like aspectj). I'd like confirmation. Each artifact may have different dependencies (as aspectj has) > > 2/ What is the minimal information the POM should contain. If > it only contains element + > //, is it ok? Don't tell me it requires a > full POM! That would be as bad as lengthy as mavenizing each > project... Quoting Jason van Zyl: If you don't use maven then it would at least be nice to have the groupId artifactId name currentVersion dependencies I suppose "artifactId" should be "id" > > 3/ What name should the pom file(s) have? name>-.pom? > If the project is not yet versioned, should SNAPSHOT be used? The upload bundles I've seen use "project.xml" > > 4/ Where is located the tool that will take an upload bundle > (result of create-upload-bundle)? I'd like to see what > operations it does so that I can deliver something equivalent > or even better, use it... Don't know ;) > > 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]
