[jira] Closed: (SCM-76) scm:update should have @aggregator

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-76?page=all ]
 
Emmanuel Venisse closed SCM-76:
---

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.0-beta-2

Fixed.

> scm:update should have @aggregator
> --
>
>  Key: SCM-76
>  URL: http://jira.codehaus.org/browse/SCM-76
>  Project: Maven SCM
> Type: Bug
>   Components: maven-plugin
> Reporter: Brett Porter
> Assignee: Emmanuel Venisse
>  Fix For: 1.0-beta-2

>
>
> run from a reactor root will update all the children, so no need to run over 
> subprojects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-1) Publish site for 1.0

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-1?page=all ]

Emmanuel Venisse updated SCM-1:
---

Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Publish site for 1.0
> 
>
>  Key: SCM-1
>  URL: http://jira.codehaus.org/browse/SCM-1
>  Project: Maven SCM
> Type: Task
> Versions: 1.0-alpha-1
> Reporter: Jason van Zyl
> Assignee: Emmanuel Venisse
>  Fix For: 1.0-beta-2

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-5) Create user guide/Guide for the impatient programmer (gipper)

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-5?page=all ]

Emmanuel Venisse updated SCM-5:
---

Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Create user guide/Guide for the impatient programmer (gipper)
> -
>
>  Key: SCM-5
>  URL: http://jira.codehaus.org/browse/SCM-5
>  Project: Maven SCM
> Type: Task
> Versions: 1.0-alpha-1
> Reporter: Jason van Zyl
>  Fix For: 1.0-beta-2

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-2) Create POJO facade

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-2?page=all ]

Emmanuel Venisse updated SCM-2:
---

Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Create POJO facade
> --
>
>  Key: SCM-2
>  URL: http://jira.codehaus.org/browse/SCM-2
>  Project: Maven SCM
> Type: Task
> Versions: 1.0-alpha-1
> Reporter: Jason van Zyl
>  Fix For: 1.0-beta-2

>
>
> Make an easy to use POJO facade for maven-scm.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-6) Development/Testing guide

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-6?page=all ]

Emmanuel Venisse updated SCM-6:
---

Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Development/Testing guide
> -
>
>  Key: SCM-6
>  URL: http://jira.codehaus.org/browse/SCM-6
>  Project: Maven SCM
> Type: Task
> Versions: 1.0-alpha-1
> Reporter: Jason van Zyl
>  Fix For: 1.0-beta-2

>
>
> Guide on how to create new scm providers utilizing the abstract scm test case 
> for easy testing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-17) test structure needs further clean up

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-17?page=all ]

Emmanuel Venisse updated SCM-17:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> test structure needs further clean up
> -
>
>  Key: SCM-17
>  URL: http://jira.codehaus.org/browse/SCM-17
>  Project: Maven SCM
> Type: Test
>   Components: maven-scm-provider-clearcase, maven-scm-provider-cvs, 
> maven-scm-provider-local, maven-scm-provider-starteam, 
> maven-scm-provider-perforce, maven-scm-provider-svn
> Reporter: Brett Porter
>  Fix For: 1.0-beta-2

>
>
> The following is needed:
> - all providers need to utilise the TCK where possible. 
> - any tests in providers that can be generalised should be moved to the TCK
> - other tests in the providers should just test provider specific functions, 
> and probably not be integration tests like the TCK is
> - need further tests for other commands, including those yet to be added
> - review coverage for each provider

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-19) resolve file status ambiguities

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-19?page=all ]

Emmanuel Venisse updated SCM-19:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> resolve file status ambiguities
> ---
>
>  Key: SCM-19
>  URL: http://jira.codehaus.org/browse/SCM-19
>  Project: Maven SCM
> Type: Task
>   Components: maven-scm-api
> Reporter: Brett Porter
>  Fix For: 1.0-beta-2

>
>
> currently ScmFileStatus just reports whatever the provider gave back, but 
> means different things in different SCM's.
> eg. "updated" in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED.
> "added" in CVS is UPDATED, in SVN it is ADDED.
> The API should hide this from the user, though perhaps be able to give the 
> extended info if necessary.
> I suggest isXXX flags instead:
> isUpdated()
> isAdded() - just came from an update
> isMerged()
> isInConflict()
> isNew() - new locally
> etc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-10) Use cvslib instead of cvs command line in cvs provider

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-10?page=all ]

Emmanuel Venisse updated SCM-10:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Use cvslib instead of cvs command line in cvs provider
> --
>
>  Key: SCM-10
>  URL: http://jira.codehaus.org/browse/SCM-10
>  Project: Maven SCM
> Type: Task
> Versions: 1.0-alpha-1
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
>  Fix For: 1.0-beta-2

>
>
> if cvslib support ext protocol.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-57) m2 maven-scm-plugin should use the same configurations/properties with M1 plugin

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-57?page=all ]

Emmanuel Venisse updated SCM-57:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> m2 maven-scm-plugin should use the same configurations/properties with M1 
> plugin
> 
>
>  Key: SCM-57
>  URL: http://jira.codehaus.org/browse/SCM-57
>  Project: Maven SCM
> Type: Bug
>   Components: maven-plugin
> Versions: 1.0-alpha-3
>  Environment: xp
> Reporter: Dan Tran
>  Fix For: 1.0-beta-2

>
>
> I think m2 should try to make scm plugin configuration compatible with m2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-31) The scm url validator should return a code corresponding to the error

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-31?page=all ]

Emmanuel Venisse updated SCM-31:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> The scm url validator should return a code corresponding to the error
> -
>
>  Key: SCM-31
>  URL: http://jira.codehaus.org/browse/SCM-31
>  Project: Maven SCM
> Type: Improvement
> Versions: 1.0-alpha-1
> Reporter: Jason van Zyl
>  Fix For: 1.0-beta-2

>
>
> I would like an error code to be returned so that I can use the error code to 
> select an i18n key that will provide users with a localized error message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-18) complete commands and expose through ScmManager

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-18?page=all ]

Emmanuel Venisse updated SCM-18:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> complete commands and expose through ScmManager
> ---
>
>  Key: SCM-18
>  URL: http://jira.codehaus.org/browse/SCM-18
>  Project: Maven SCM
> Type: Task
>   Components: maven-scm-provider-clearcase, maven-scm-provider-cvs, 
> maven-scm-provider-starteam, maven-scm-provider-local, 
> maven-scm-provider-svn, maven-scm-provider-perforce, maven-scm-api
> Reporter: Brett Porter
>  Fix For: 1.0-beta-2

>
>
> many commands are not completely implemented, or not implemented at all, and 
> some that are have not been exposed through the ScmManager interface.
> These all need to be rounded out and tested via the TCK for a final 1.0 
> release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-21) separate revision and tag handling

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-21?page=all ]

Emmanuel Venisse updated SCM-21:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> separate revision and tag handling
> --
>
>  Key: SCM-21
>  URL: http://jira.codehaus.org/browse/SCM-21
>  Project: Maven SCM
> Type: Task
>   Components: maven-scm-api
> Reporter: Brett Porter
>  Fix For: 1.0-beta-2

>
>
> while in CVS revision# and tag are handled in the same way, the concepts can 
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (SCM-42) Create a ChangeSorter for sort and group ChangeSet list

2005-11-17 Thread Emmanuel Venisse (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-42?page=all ]

Emmanuel Venisse updated SCM-42:


Fix Version: (was: 1.0-beta-1)
 1.0-beta-2

> Create a ChangeSorter for sort and group ChangeSet list
> ---
>
>  Key: SCM-42
>  URL: http://jira.codehaus.org/browse/SCM-42
>  Project: Maven SCM
> Type: Improvement
>   Components: maven-scm-api
> Versions: 1.0-alpha-2
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
>  Fix For: 1.0-beta-2

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (SCM-75) messages are logged twice

2005-11-17 Thread Brett Porter (JIRA) 
messages are logged twice
-

 Key: SCM-75
 URL: http://jira.codehaus.org/browse/SCM-75
 Project: Maven SCM
Type: Bug
  Components: maven-scm-provider-cvs  
Reporter: Brett Porter


running scm:update on the wadi project was logging everything twice (both under 
normal, and under -X). It seemed to log more times as it went through a reactor 
too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (SCM-74) users for scm:update instead of the one in the checkout

2005-11-17 Thread Brett Porter (JIRA) 
users  for scm:update instead of the one in the checkout


 Key: SCM-74
 URL: http://jira.codehaus.org/browse/SCM-74
 Project: Maven SCM
Type: Bug
  Components: maven-scm-provider-cvs, maven-plugin  
Reporter: Brett Porter


this is problematic with a :ext:ssh: checkout, and a :pserver: connection, as 
it gives the cryptic error "password is required" (which should be explained 
more anyway about doing a cvs login, or even use plexus-interactivity to do the 
login step)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: no such provider 'clearcase'

2005-11-17 Thread Brett Porter 

You can also add it within the plugin tag in your pom

Emmanuel Venisse wrote:

you need to update the release plugin pom and rebuild it.

you need for release plugin tag, checkin, checkout, update remove and 
status commands.


Emmanuel

Re: no such provider 'clearcase'

2005-11-17 Thread Wim Deblauwe 
ok, I will look into that.

For the status command: what is it exactly? I could not find much info in the javadocs of the interface.

regards,

Wim2005/11/17, Emmanuel Venisse <[EMAIL PROTECTED]>:
you need to update the release plugin pom and rebuild it.you need for release plugin tag, checkin, checkout, update remove and status commands.EmmanuelWim Deblauwe a écrit :> Can I do this in my 
pom.xml of my test project or do I need to update> the release plugin source code?>> Not much, I have very little time. What I want to try first is tag to> use in the release plugin. But I guess that I will need to implement the
> checking of checked out files first. Is that status?>> regards,>> Wim>> 2005/11/17, Emmanuel Venisse <[EMAIL PROTECTED]
> [EMAIL PROTECTED]>>:>> you must add clearcase provider dependencies in release plugin>> Where are you with clearcase provider implementation?
>> Emmanuel>> Wim Deblauwe a écrit :>  > Any idea why I get this error when I try 'mvn release:prepare'?>  >>  > [INFO] Scanning for projects...
>  > [INFO] Searching repository for plugin with prefix: 'release'.>  > [INFO]>  >> >  > [INFO] Building Utils Logging Module
>  > [INFO]task-segment: [release:prepare] (aggregator-style)>  > [INFO]>  >> >  > [INFO] [release:prepare]
>  > [INFO] Verifying there are no local modifications ...>  > [INFO]>  >> >  > [ERROR] BUILD ERROR
>  > [INFO]>  >> >>  > [INFO] An error is occurred in the status process.>  >
>  > Embedded error: Can't load the scm provider.>  > No such provider: 'clearcase'.>  > [INFO]>  >> 
>>  > [INFO] For more information, run Maven with the -e switch>  > [INFO]>  >> >  > [INFO] Total time: 3 seconds
>  > [INFO] Finished at: Thu Nov 17 11:45:32 CET 2005>  > [INFO] Final Memory: 3M/6M>  > [INFO]>  >> 
>  >>  > I've set this in my pom.xml:>  >>  > >  >
scm:clearcase:>  > scm:clearcase:>  >   >  >>  > And I've did a 'mvn install' of the maven-scm-provider-clearcase
> plugin.>  >>  > regards,>  >>  > Wim>>

Re: no such provider 'clearcase'

2005-11-17 Thread Emmanuel Venisse 

you need to update the release plugin pom and rebuild it.

you need for release plugin tag, checkin, checkout, update remove and status 
commands.

Emmanuel

Wim Deblauwe a écrit :
Can I do this in my pom.xml of my test project or do I need to update 
the release plugin source code?


Not much, I have very little time. What I want to try first is tag to 
use in the release plugin. But I guess that I will need to implement the 
checking of checked out files first. Is that status?


regards,

Wim

2005/11/17, Emmanuel Venisse <[EMAIL PROTECTED] 
>:


you must add clearcase provider dependencies in release plugin

Where are you with clearcase provider implementation?

Emmanuel

Wim Deblauwe a écrit :
 > Any idea why I get this error when I try 'mvn release:prepare'?
 >
 > [INFO] Scanning for projects...
 > [INFO] Searching repository for plugin with prefix: 'release'.
 > [INFO]
 >

 > [INFO] Building Utils Logging Module
 > [INFO]task-segment: [release:prepare] (aggregator-style)
 > [INFO]
 >

 > [INFO] [release:prepare]
 > [INFO] Verifying there are no local modifications ...
 > [INFO]
 >

 > [ERROR] BUILD ERROR
 > [INFO]
 >


 > [INFO] An error is occurred in the status process.
 >
 > Embedded error: Can't load the scm provider.
 > No such provider: 'clearcase'.
 > [INFO]
 >


 > [INFO] For more information, run Maven with the -e switch
 > [INFO]
 >

 > [INFO] Total time: 3 seconds
 > [INFO] Finished at: Thu Nov 17 11:45:32 CET 2005
 > [INFO] Final Memory: 3M/6M
 > [INFO]
 >

 >
 > I've set this in my pom.xml:
 >
 > 
 > scm:clearcase:
 > scm:clearcase:
 >   
 >
 > And I've did a 'mvn install' of the maven-scm-provider-clearcase
plugin.
 >
 > regards,
 >
 > Wim

Re: no such provider 'clearcase'

2005-11-17 Thread Wim Deblauwe 
Can I do this in my pom.xml of my test project or do I need to update the release plugin source code?

Not much, I have very little time. What I want to try first is tag to
use in the release plugin. But I guess that I will need to implement
the checking of checked out files first. Is that status?

regards,

Wim2005/11/17, Emmanuel Venisse <[EMAIL PROTECTED]>:
you must add clearcase provider dependencies in release pluginWhere are you with clearcase provider implementation?EmmanuelWim Deblauwe a écrit :> Any idea why I get this error when I try 'mvn release:prepare'?
>> [INFO] Scanning for projects...> [INFO] Searching repository for plugin with prefix: 'release'.> [INFO]> 
> [INFO] Building Utils Logging Module> [INFO]task-segment: [release:prepare] (aggregator-style)> [INFO]> > [INFO] [release:prepare]
> [INFO] Verifying there are no local modifications ...> [INFO]> > [ERROR] BUILD ERROR> [INFO]> 
> [INFO] An error is occurred in the status process.>> Embedded error: Can't load the scm provider.> No such provider: 'clearcase'.> [INFO]> 
> [INFO] For more information, run Maven with the -e switch> [INFO]> > [INFO] Total time: 3 seconds> [INFO] Finished at: Thu Nov 17 11:45:32 CET 2005
> [INFO] Final Memory: 3M/6M> [INFO]> >> I've set this in my pom.xml:>> > scm:clearcase:
> scm:clearcase:>   >> And I've did a 'mvn install' of the maven-scm-provider-clearcase plugin.>> regards,
>> Wim

Re: no such provider 'clearcase'

2005-11-17 Thread Emmanuel Venisse 

you must add clearcase provider dependencies in release plugin

Where are you with clearcase provider implementation?

Emmanuel

Wim Deblauwe a écrit :

Any idea why I get this error when I try 'mvn release:prepare'?

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 


[INFO] Building Utils Logging Module
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 


[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
[INFO] 


[ERROR] BUILD ERROR
[INFO] 


[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
No such provider: 'clearcase'.
[INFO] 


[INFO] For more information, run Maven with the -e switch
[INFO] 


[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Nov 17 11:45:32 CET 2005
[INFO] Final Memory: 3M/6M
[INFO] 



I've set this in my pom.xml:


scm:clearcase:
scm:clearcase:
  

And I've did a 'mvn install' of the maven-scm-provider-clearcase plugin.

regards,

Wim

no such provider 'clearcase'

2005-11-17 Thread Wim Deblauwe 
Any idea why I get this error when I try 'mvn release:prepare'?

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 
[INFO] Building Utils Logging Module
[INFO]    task-segment: [release:prepare] (aggregator-style)
[INFO] 
[INFO] [release:prepare]
[INFO] Verifying there are no local modifications ...
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
No such provider: 'clearcase'.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Nov 17 11:45:32 CET 2005
[INFO] Final Memory: 3M/6M
[INFO] 

I've set this in my pom.xml:



    

        scm:clearcase:

        scm:clearcase:

  

And I've did a 'mvn install' of the maven-scm-provider-clearcase plugin.

regards,

Wim