[
http://jira.codehaus.org/browse/ARCHETYPE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed ARCHETYPE-270.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha-5
Assignee: Benjamin Bentmann
Fixed in [r833730|http://svn.apache.org/viewvc?view=revision&revision=833730].
> RemoteCatalogArchetypeDataSource leaves open wagon connection when archetype
> catalog retrieval fails
> ----------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-270
> URL: http://jira.codehaus.org/browse/ARCHETYPE-270
> Project: Maven Archetype
> Issue Type: Bug
> Reporter: Dan
> Assignee: Benjamin Bentmann
> Fix For: 2.0-alpha-5
>
>
> If you have an archetype catalog entry with a bad url/archetype catalog file
> (the file isn't there), the RemoteArchetypeCatalogDataSource blows up when it
> tries to get the file over wagon. After it blows up, the wagon connection is
> not disconnected - as a result, there is an orphaned job in progress
> 'Updating indexes: 0%' (which is also badly named). The problem is on line 88:
> wagon.connect( wagonRepository );
> (get fails) >>>>>>> wagon.get( fileName , catalog );
> wagon.disconnect();
> return readCatalog( new FileReader( catalog ) );
> I assume it should disconnect in the catch() block below
--
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
