[ 
https://issues.apache.org/jira/browse/NPANDAY-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143128#comment-13143128
 ] 

Stoyan Damov commented on NPANDAY-476:
--------------------------------------

The fix explained (as commented by Lars, patch is attached to NPANDAY-322):

In {{Connect.cs}} refactored a bit so that methods dealing with resync 
solution/project references have appropriate names.
Extracted the resync logic into implementation methods and refactored button 
click event handlers to call these.
In the implementation methods added a boolean flag whether to resync from the 
remote or local repositories and then just delegated to the appropriate 
{{ReferenceManager.ResyncXxx}} call.

In {{ReferenceManager.cs}}'s {{IReferenceManager}} added 
{{ResyncArtifactsFromLocalRepository}} method.

Refactored {{ResyncArtifacts}} and {{ResyncArtifactsFromLocalRepository}} to 
call an implementation method, passing whether the resync should be done from 
the remote or local repository.

                
> Add "Resync references from local repository" in VS addin
> ---------------------------------------------------------
>
>                 Key: NPANDAY-476
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-476
>             Project: NPanday
>          Issue Type: New Feature
>          Components: Visual Studio Add-in
>    Affects Versions: 1.4-incubating
>            Reporter: Stoyan Damov
>            Assignee: Lars Corneliussen
>            Priority: Minor
>              Labels: addin, feature, local, references, repository, resync, 
> vs2010
>             Fix For: 1.4.1-incubating
>
>
> *Patch is attached to NPANDAY-322*
> As a developer of new modules, I'd like to be able to test & debug & refactor 
> away the modules before I commit/push them to VCS and get these deployed into 
> the remote repository by the build server.
> This is currently not possible.
> I'm working on X and Y (Y depends on X). 
> I think I'm done on X and install X-1.0-SNAPSHOT in my local repo.
> I then add a dependency on X-1.0-SNAPSHOT in Y.
> Now, if I make a change in X, I'd like to re-install it in the local repo and 
> use the updated X-1.0-SNAPSHOT in Y but I don't want to deploy X-1.0-SNAPSHOT 
> in the remote repo.
> However, if I resync the references I'd currently hit NPANDAY-322, or in the 
> best case I could get someone else's X-1.0-SNAPSHOT (which could have been 
> updated in the remote repo while I'm working on X as well). However, I want 
> to get the local repo's X, not the remote one's.
> I don't want to push X's changes and wait on the build server to deploy the 
> new snapshot because I don't want to "hurt" the rest of the developers with 
> something which might still have bugs in it, and I also don't want to get 
> other devs's X-1.0-SNAPSHOT.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to