Re: Preparing Maven SCM 1.0
Emmanuel Venisse wrote: Emmanuel Venisse a écrit : Trygve Laugstøl a écrit : Emmanuel Venisse wrote: Hi, I'd like to release Maven 1.0 in next weeks. As you can see, I updated jira for this version. Before to do it, we need to fix some major issues with some providers. [snip] The issues you listed are only technical issues with the provider, not something that should you from releasing 1.0 of the API. I think that at the same time that the API is releases we split out the providers from the API and give them their own release cycle. We have some changes in API like list and export commands. That makes it easier to release providers as necessary and we get a stable API that doesn't move (or doesn't move but is released) every time someone fixes an issue in the Foo provider. With 1.0 release, I'll release providers too with 1.0 version, then, providers will have their own release cycle with a version like 1.0.x for providers that use API 1.0, 1.1.x for providers that use API 1.1... An other possibility would be to release all when we want to release API or a provider like we do it in some other projects like Modello That is true, but I see no reason to do that in Modello either. Maven SCM will move much faster that Modello, in particular when new providers are added, it is kinda silly to release all the providers just because a new provider was added. -- Trygve
Re: Preparing Maven SCM 1.0
I'm not sure how much I can do in the next two weeks as we are finishing a release and I'm on vacation the last week of March. I will discuss with Patrick tomorrow whether he can provide some help in brainstorming the best solution to the issue and setting up Continuum here locally for testing purposes since we don't use Continuum. It would be very helpful if you could get that open source license from perforce.com. Live testing would provide much greater code coverage. mike On 3/13/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Perforce: Perforce provider doesn't work at all with continuum. Actually, it doesn't support to run scm commands on more than one view in a jvm instance. This problem exist since a long time and need to be fixed for 1.0. We can probably install a Perforce server somewhere (on the zone?) with an OSS license. Mike, can you help?
Re: Preparing Maven SCM 1.0
Grzegorz Slowikowski a écrit : - Original Message - From: "Emmanuel Venisse" <[EMAIL PROTECTED]> To: Sent: Tuesday, March 13, 2007 3:13 PM Subject: Preparing Maven SCM 1.0 Hi, I'd like to release Maven 1.0 in next weeks. As you can see, I updated jira for this version. Before to do it, we need to fix some major issues with some providers. ... Svn: I'd like to implement a pure java provider but svn4j at codehaus isn't ready yet, so we'll do it later. It isn't a problem because the native provider works fine. ... Emmanuel I think the one and only pure Java svn provider is svnkit (the name changed fron "javasvn"). It is stable and full of features. SmartSVN (commercial java svn GUI) is using it. I know them but the license isn't compatible with Apache license :( Emmanuel
Re: Preparing Maven SCM 1.0
- Original Message - From: "Emmanuel Venisse" <[EMAIL PROTECTED]> To: Sent: Tuesday, March 13, 2007 3:13 PM Subject: Preparing Maven SCM 1.0 Hi, I'd like to release Maven 1.0 in next weeks. As you can see, I updated jira for this version. Before to do it, we need to fix some major issues with some providers. ... Svn: I'd like to implement a pure java provider but svn4j at codehaus isn't ready yet, so we'll do it later. It isn't a problem because the native provider works fine. ... Emmanuel I think the one and only pure Java svn provider is svnkit (the name changed fron "javasvn"). It is stable and full of features. SmartSVN (commercial java svn GUI) is using it.
Re: Preparing Maven SCM 1.0
Emmanuel Venisse a écrit : Hi, I'd like to release Maven 1.0 in next weeks. As you can see, I updated jira for this version. Before to do it, we need to fix some major issues with some providers. CVS: Lot of users have pb with the actual cvs provider because each some cvs client doesn't understand all "standard" parameters described in cvs book. The majority of problems are with the changelog command and the date range. So I'll write a pure java cvs provider but we'll continue to maintain the native provider too. Perforce: Perforce provider doesn't work at all with continuum. Actually, it doesn't support to run scm commands on more than one view in a jvm instance. This problem exist since a long time and need to be fixed for 1.0. We can probably install a Perforce server somewhere (on the zone?) with an OSS license. Mike, can you help? With a Perforce instance available, we'll can implement the TCK. Svn: I'd like to implement a pure java provider but svn4j at codehaus isn't ready yet, so we'll do it later. It isn't a problem because the native provider works fine. Note to all providers contributors: Can you look at your specific issues? Move all issues you can fix in a short term to 1.0 and test your provider with release plugin AND continuum. Emmanuel
Preparing Maven SCM 1.0
Hi, I'd like to release Maven 1.0 in next weeks. As you can see, I updated jira for this version. Before to do it, we need to fix some major issues with some providers. CVS: Lot of users have pb with the actual cvs provider because each some cvs client doesn't understand all "standard" parameters described in cvs book. The majority of problems are with the changelog command and the date range. So I'll write a pure java cvs provider but we'll continue to maintain the native provider too. Perforce: Perforce provider doesn't work at all with continuum. Actually, it doesn't support to run scm commands on more than one view in a jvm instance. This problem exist since a long time and need to be fixed for 1.0. We can probably install a Perforce server somewhere (on the zone?) with an OSS license. Mike, can you help? Svn: I'd like to implement a pure java provider but svn4j at codehaus isn't ready yet, so we'll do it later. It isn't a problem because the native provider works fine. Note to all providers contributors: Can you look at your specific issues? Move all issues you can fix in a short term to 1.0 and test your provider with release plugin AND continuum. Emmanuel
