Re: Archive format for automated upload requests
On Mon, 2003-12-01 at 22:52, Jason van Zyl wrote: Howdy, I now have all the requisite bits and bobs (thanks strachan) for a little server that can process upload requests in an automated fashion but I wouldn't mind a little input on the contents of the archive uploaded and some ideas on the workflow and security related issues. We can easily make a plugin to assemble the archive so it include the artifact in a JAR format, the license and whatever else is needed. The artifact can easily be extracted and pushed to ibiblio along with the license and anything else we need. If we can push through this quickly I will get the app up and running and remove the bottleneck of having the limited number of repo admins processing the requests. Hopefully this will open the flood gates and allow anyone who wants to push artifacts into the central repo and this should also help with pushing POMs into the central repo which will be required for transitive deps. As a start how about: - project.xml: which can be renamed with the info in the POM itself - license file: do we have a standard name for this? - artifact to be uploaded Anything else? A simple zip/jar file would do as items can be easily extracted. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Archive format for automated upload requests
Hi Jason, Jason van Zyl wrote on Tuesday, December 02, 2003 12:42 PM: On Mon, 2003-12-01 at 22:52, Jason van Zyl wrote: As a start how about: - project.xml: which can be renamed with the info in the POM itself - license file: do we have a standard name for this? - artifact to be uploaded Anything else? How do you handle packages with native extensions as available with SWT or JAI ? Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archive format for automated upload requests
Having an app to do uploads: +1 Allowing anyone to load artifacts with no security measures: -googleplex (and if anyone adds a priceless line, I will personally send a hungry shark with laser beams to eat you) Jason van Zyl wrote: Howdy, I now have all the requisite bits and bobs (thanks strachan) for a little server that can process upload requests in an automated fashion but I wouldn't mind a little input on the contents of the archive uploaded and some ideas on the workflow and security related issues. We can easily make a plugin to assemble the archive so it include the artifact in a JAR format, the license and whatever else is needed. The artifact can easily be extracted and pushed to ibiblio along with the license and anything else we need. If we can push through this quickly I will get the app up and running and remove the bottleneck of having the limited number of repo admins processing the requests. Hopefully this will open the flood gates and allow anyone who wants to push artifacts into the central repo and this should also help with pushing POMs into the central repo which will be required for transitive deps. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Archive format for automated upload requests
Having an app to do uploads: +1 Allowing anyone to load artifacts with no security measures: -googleplex Should we consider having people/groups/organizations register as uploaders, with a security key that they sign their uploaded archives withwith? Or is this just too much effort for little bang for the buck? /* Joakim Erdfelt - Cingular Wireless */
Re: Archive format for automated upload requests
Something needs to be done as it is unacceptable to let Joe Random upload into the repo. Signing is a good start. Erdfelt, Joakim wrote: Having an app to do uploads: +1 Allowing anyone to load artifacts with no security measures: -googleplex Should we consider having people/groups/organizations register as uploaders, with a security key that they sign their uploaded archives withwith? Or is this just too much effort for little bang for the buck? /* Joakim Erdfelt - Cingular Wireless */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archive format for automated upload requests
On Tue, 2003-12-02 at 08:50, Ben Walding wrote: Having an app to do uploads: +1 Allowing anyone to load artifacts with no security measures: -googleplex There will definitely need to be some security. I wouldn't turn it on for production mode without it. I've ask some folks and even sent a message to Counterpane, where Bruce Schneier works, to ask for some help. But to start maybe a login where a user has registered and deposited a public key. The the archives can signed and we can check them when they are submitted. (and if anyone adds a priceless line, I will personally send a hungry shark with laser beams to eat you) Jason van Zyl wrote: Howdy, I now have all the requisite bits and bobs (thanks strachan) for a little server that can process upload requests in an automated fashion but I wouldn't mind a little input on the contents of the archive uploaded and some ideas on the workflow and security related issues. We can easily make a plugin to assemble the archive so it include the artifact in a JAR format, the license and whatever else is needed. The artifact can easily be extracted and pushed to ibiblio along with the license and anything else we need. If we can push through this quickly I will get the app up and running and remove the bottleneck of having the limited number of repo admins processing the requests. Hopefully this will open the flood gates and allow anyone who wants to push artifacts into the central repo and this should also help with pushing POMs into the central repo which will be required for transitive deps. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Archive format for automated upload requests
On Tue, 2003-12-02 at 08:56, Erdfelt, Joakim wrote: Having an app to do uploads: +1 Allowing anyone to load artifacts with no security measures: -googleplex Should we consider having people/groups/organizations register as uploaders, with a security key that they sign their uploaded archives withwith? +1 Or is this just too much effort for little bang for the buck? I didn't read this before I fired off my last message :-) It's definitely worth it. I guarantee once the app is running the central repository will start growing at a great rate. /* Joakim Erdfelt - Cingular Wireless */ -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Archive format for automated upload requests
-Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: Maven Developers List Subject: RE: Archive format for automated upload requests Hi Jason, Jason van Zyl wrote on Tuesday, December 02, 2003 12:42 PM: On Mon, 2003-12-01 at 22:52, Jason van Zyl wrote: As a start how about: - project.xml: which can be renamed with the info in the POM itself - license file: do we have a standard name for this? - artifact to be uploaded Anything else? How do you handle packages with native extensions as available with SWT or JAI ? I have written some highly experimental code which partially handles this: http://cvs.apache.org/viewcvs.cgi/maven-components/maven-artifact/src/test/j ava/org/apache/maven/artifact/layout/DefaultRepositoryLayoutTest.java?rev=HE ADcontent-type=text/vnd.viewcvs-markup http://cvs.apache.org/viewcvs.cgi/maven-components/maven-artifact/src/main/c onf/ Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
