Re: Central repository index
On 28/08/2008, at 10:14 AM, Jason van Zyl wrote: Is this referring to the index files that live in the central repository [1] ? I think if we're going to provide an official index, it should be one that comes from the Maven project, not from any particular repository manager. It's integrated in m2e, Netbeans, IDEA, and a whole slew of open source organizations so I'm not sure how much more of a defacto standard in real life you're going to get. But, I agree and I'm not at all suggesting the Nexus index is the official index from Maven. I don't think we even need to say there is an official index. Happy to move into another directory, and anyone else can publish whatever indices they like. Let users choose what they want to use. Sorry, a bit late catching up on mail. FWIW, if defining a standard for the index format and versioning, etc within the Maven project itself came up here I'd think it was a good idea. I'm also fine with allowing multiple types for now as you say. As for what is on central now, as a repository maintainer, I don't know how .index got there, how to clean up old versions, or how to update it if it's out of date (which it seems to be). I presume if asked by Maven users I should just tell them that the Maven team are not responsible for it, go nag the Nexus lists. And with regard to Archiva dev as James raised, I'm sure we can deal with the question of what format, APIs, etc over on its dev list based on what it needs, as it is not really relevant for here. We've had a few m2e users request that so it's a good thing to do. It's hardly a stretch to do either based on the similarities of the format and as long as it's going to work across different versions as Milos pointed out, and can be extensible, it should work for us. Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
James, I am not exactly sure what is the problem for Archiva or any other project to use nexus indexer API. For instance, Archiva is already using number of dependencies from outside of Maven project and even from outside Apache umbrella and it doesn't seem to be an issue. As Jason already mentioned, index format could change, but we do make sure that API still works, so you it would simply mean to update one of the project dependencies. Also, you are more then welcome to discuss features and contribute code to the nexus indexer component. regards, Eugene James William Dumay wrote: I'm cool sticking with the Nexus index format - it works and there has been a successful uptake with different tool vendors - so it seems to be the defacto standard. We will certainly be using it in a future version of Archiva. What I would like to see would be that the index code becomes part of the Maven project itself and be the index standard for Maven repositories. This is good for the simple reason that other repository projects will not have to play constant catchup with Nexus if that index format changes - changes to the format can be discussed and worked on with the Maven community. On another note, if any fundamental changes are made to Maven in the future it ensures that the index format can grow with those changes. -- View this message in context: http://www.nabble.com/Central-repository-index-tp19191981p19194698.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
On Thu, Aug 28, 2008 at 8:02 AM, Eugene Kuleshov [EMAIL PROTECTED] wrote: James, I am not exactly sure what is the problem for Archiva or any other project to use nexus indexer API. For instance, Archiva is already using number of dependencies from outside of Maven project and even from outside Apache umbrella and it doesn't seem to be an issue. As Jason already mentioned, index format could change, but we do make sure that API still works, so you it would simply mean to update one of the project dependencies. as a user of the nexus indexer (in netbeans integration), I'm hoping this kind of statements only mean compatible changes in the index that will not break users of the old APIs. Can you confirm? Milos Also, you are more then welcome to discuss features and contribute code to the nexus indexer component. regards, Eugene James William Dumay wrote: I'm cool sticking with the Nexus index format - it works and there has been a successful uptake with different tool vendors - so it seems to be the defacto standard. We will certainly be using it in a future version of Archiva. What I would like to see would be that the index code becomes part of the Maven project itself and be the index standard for Maven repositories. This is good for the simple reason that other repository projects will not have to play constant catchup with Nexus if that index format changes - changes to the format can be discussed and worked on with the Maven community. On another note, if any fundamental changes are made to Maven in the future it ensures that the index format can grow with those changes. -- View this message in context: http://www.nabble.com/Central-repository-index-tp19191981p19194698.html Sent from the Maven Developers mailing list archive at Nabble.com. - 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: Central repository index
On 27-Aug-08, at 11:22 PM, Milos Kleint wrote: On Thu, Aug 28, 2008 at 8:02 AM, Eugene Kuleshov [EMAIL PROTECTED] wrote: James, I am not exactly sure what is the problem for Archiva or any other project to use nexus indexer API. For instance, Archiva is already using number of dependencies from outside of Maven project and even from outside Apache umbrella and it doesn't seem to be an issue. As Jason already mentioned, index format could change, but we do make sure that API still works, so you it would simply mean to update one of the project dependencies. as a user of the nexus indexer (in netbeans integration), I'm hoping this kind of statements only mean compatible changes in the index that will not break users of the old APIs. Can you confirm? Throughout the life of 1.x.x any APIs that are there will remain, and I don't see why that practice would need to change even after 1.x.x. Milos Also, you are more then welcome to discuss features and contribute code to the nexus indexer component. regards, Eugene James William Dumay wrote: I'm cool sticking with the Nexus index format - it works and there has been a successful uptake with different tool vendors - so it seems to be the defacto standard. We will certainly be using it in a future version of Archiva. What I would like to see would be that the index code becomes part of the Maven project itself and be the index standard for Maven repositories. This is good for the simple reason that other repository projects will not have to play constant catchup with Nexus if that index format changes - changes to the format can be discussed and worked on with the Maven community. On another note, if any fundamental changes are made to Maven in the future it ensures that the index format can grow with those changes. -- View this message in context: http://www.nabble.com/Central-repository-index-tp19191981p19194698.html Sent from the Maven Developers mailing list archive at Nabble.com. - 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
Milos Kleint wrote: as a user of the nexus indexer (in netbeans integration), I'm hoping this kind of statements only mean compatible changes in the index that will not break users of the old APIs. Can you confirm? Absolutely. But I still recommend to update to the latest when you can (currently the latest is 1.0 release). regards, Eugene -- View this message in context: http://www.nabble.com/Central-repository-index-tp19191981p19200071.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
On Thu, Aug 28, 2008 at 3:03 PM, Eugene Kuleshov [EMAIL PROTECTED] wrote: Milos Kleint wrote: as a user of the nexus indexer (in netbeans integration), I'm hoping this kind of statements only mean compatible changes in the index that will not break users of the old APIs. Can you confirm? Absolutely. But I still recommend to update to the latest when you can (currently the latest is 1.0 release). Sure, I actually did within netbeans maven trunk a few days back. but as with any software there's a long tail of people who keep using old versions of the software. There's various degrees of failure that can show up. Getting exceptions with old client+new index file is unacceptable, getting wrong or empty results is better (but still wrong) What I meant is that the lifecycle of the software depending on the APIs of nexus indexer is different than the library itself and sometimes change (both on the product dev and user side) takes time. At the same time it's fairly easy to upload new index for the new API to central... Milos regards, Eugene -- View this message in context: http://www.nabble.com/Central-repository-index-tp19191981p19200071.html Sent from the Maven Developers mailing list archive at Nabble.com. - 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: Central repository index
On 27-Aug-08, at 5:59 PM, James William Dumay wrote: Jason, I'm cool sticking with the Nexus index format - it works and there has been a successful uptake with different tool vendors - so it seems to be the defacto standard. We will certainly be using it in a future version of Archiva. What I would like to see would be that the index code becomes part of the Maven project itself and be the index standard for Maven repositories. This is good for the simple reason that other repository projects will not have to play constant catchup with Nexus if that index format changes - changes to the format can be discussed and worked on with the Maven community. On another note, if any fundamental changes are made to Maven in the future it ensures that the index format can grow with those changes. Thoughts? I doubt we'll move it here. We like it where it is, and nothing precludes working in a way you describe above just because it's not here. We like being able to release twice a day if we want to, and I think we've done a good job at making the technology solid and usable by everyone and the license will always remain EPL. The API is also going to allow for extensibility by anyone as the base index is not going to change a whole lot. We are planning on providing a partitioning mechanism so the base doesn't change a whole lot and folks can use, if they so choose, the extension mechanism to create indices of whatever they want from repositories. Thanks, James On 28/08/2008, at 10:14 AM, Jason van Zyl wrote: On 27-Aug-08, at 4:58 PM, Wendy Smoak wrote: [moved from [EMAIL PROTECTED] On Wed, Aug 27, 2008 at 2:39 PM, Jason van Zyl [EMAIL PROTECTED] wrote: For any tool you see saying they support Nexus indexes make sure they are using our APIs. We guarantee nothing in the way of the format, but we have gone to excruciating lengths to make sure the API we have provided is super stable. Anything that tries to read the indices directly will ultimately get burned so just make sure you know how the tools you choose are producing a Nexus index. We can certainly protect the API, we can't really promise no format changes in the index format. Is this referring to the index files that live in the central repository [1] ? I think if we're going to provide an official index, it should be one that comes from the Maven project, not from any particular repository manager. It's integrated in m2e, Netbeans, IDEA, and a whole slew of open source organizations so I'm not sure how much more of a defacto standard in real life you're going to get. But, I agree and I'm not at all suggesting the Nexus index is the official index from Maven. I don't think we even need to say there is an official index. Happy to move into another directory, and anyone else can publish whatever indices they like. Let users choose what they want to use. [1] http://repo1.maven.org/maven2/.index/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Simplex sigillum veri. (Simplicity is the seal of truth.) - 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
On 27-Aug-08, at 4:58 PM, Wendy Smoak wrote: [moved from [EMAIL PROTECTED] On Wed, Aug 27, 2008 at 2:39 PM, Jason van Zyl [EMAIL PROTECTED] wrote: For any tool you see saying they support Nexus indexes make sure they are using our APIs. We guarantee nothing in the way of the format, but we have gone to excruciating lengths to make sure the API we have provided is super stable. Anything that tries to read the indices directly will ultimately get burned so just make sure you know how the tools you choose are producing a Nexus index. We can certainly protect the API, we can't really promise no format changes in the index format. Is this referring to the index files that live in the central repository [1] ? I think if we're going to provide an official index, it should be one that comes from the Maven project, not from any particular repository manager. It's integrated in m2e, Netbeans, IDEA, and a whole slew of open source organizations so I'm not sure how much more of a defacto standard in real life you're going to get. But, I agree and I'm not at all suggesting the Nexus index is the official index from Maven. I don't think we even need to say there is an official index. Happy to move into another directory, and anyone else can publish whatever indices they like. Let users choose what they want to use. [1] http://repo1.maven.org/maven2/.index/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Central repository index
Jason, I'm cool sticking with the Nexus index format - it works and there has been a successful uptake with different tool vendors - so it seems to be the defacto standard. We will certainly be using it in a future version of Archiva. What I would like to see would be that the index code becomes part of the Maven project itself and be the index standard for Maven repositories. This is good for the simple reason that other repository projects will not have to play constant catchup with Nexus if that index format changes - changes to the format can be discussed and worked on with the Maven community. On another note, if any fundamental changes are made to Maven in the future it ensures that the index format can grow with those changes. Thoughts? Thanks, James On 28/08/2008, at 10:14 AM, Jason van Zyl wrote: On 27-Aug-08, at 4:58 PM, Wendy Smoak wrote: [moved from [EMAIL PROTECTED] On Wed, Aug 27, 2008 at 2:39 PM, Jason van Zyl [EMAIL PROTECTED] wrote: For any tool you see saying they support Nexus indexes make sure they are using our APIs. We guarantee nothing in the way of the format, but we have gone to excruciating lengths to make sure the API we have provided is super stable. Anything that tries to read the indices directly will ultimately get burned so just make sure you know how the tools you choose are producing a Nexus index. We can certainly protect the API, we can't really promise no format changes in the index format. Is this referring to the index files that live in the central repository [1] ? I think if we're going to provide an official index, it should be one that comes from the Maven project, not from any particular repository manager. It's integrated in m2e, Netbeans, IDEA, and a whole slew of open source organizations so I'm not sure how much more of a defacto standard in real life you're going to get. But, I agree and I'm not at all suggesting the Nexus index is the official index from Maven. I don't think we even need to say there is an official index. Happy to move into another directory, and anyone else can publish whatever indices they like. Let users choose what they want to use. [1] http://repo1.maven.org/maven2/.index/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Simplex sigillum veri. (Simplicity is the seal of truth.) - 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]
