Sonar dependency management

View: New views
4 Messages — Rating Filter:   Alert me  

Sonar dependency management

by Julien HENRY :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

After restarting my Sonar instance, I discovered that many dependencies were downloaded again on the client that is running
mvn sonar:sonar

For example, I already had org.codehaus.sonar.runtime.jdbc-driver:parent:20091016150119 but after restarting Sonar instance the version 20091023184353 was downloaded. As the restart date was 23th October I suppose that the version of each dependency is computed according to Sonar instance start date.
I suppose there is some good raison to do this, but I also see some bad points:
  - having to download again the full set of dependencies is time consuming
  - if the Sonar instance is planned to reboot every night (for example), each day all clients using Sonar will download all dependencies and the local repository will grow dramatically.

Could you tell me what is the point of having a non fixed version number for these dependencies? Is there a way to prevent the full download behaviour after rebooting Sonar?

Thanks,

Julien





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Sonar dependency management

by Olivier Gaudin-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Julien,

You are correct that this could be improved. Could you file a Jira issue for it ?
Out of curiosity, are you saying you intend to reboot Sonar every night ?

Olivier



On Mon, Oct 26, 2009 at 8:57 AM, Julien HENRY <henryju@...> wrote:
Hi,

After restarting my Sonar instance, I discovered that many dependencies were downloaded again on the client that is running
mvn sonar:sonar

For example, I already had org.codehaus.sonar.runtime.jdbc-driver:parent:20091016150119 but after restarting Sonar instance the version 20091023184353 was downloaded. As the restart date was 23th October I suppose that the version of each dependency is computed according to Sonar instance start date.
I suppose there is some good raison to do this, but I also see some bad points:
 - having to download again the full set of dependencies is time consuming
 - if the Sonar instance is planned to reboot every night (for example), each day all clients using Sonar will download all dependencies and the local repository will grow dramatically.

Could you tell me what is the point of having a non fixed version number for these dependencies? Is there a way to prevent the full download behaviour after rebooting Sonar?

Thanks,

Julien





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email




Re: Sonar dependency management

by Freddy Mallet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Julien,

FYI this mechanism has been set up to automatically use all new jdbc drivers, checkstyle/pmd extensions or Sonar plugins put on the sonar web directories without any requirements on the name of those jar files. But as Olivier said, it can be greatly improved.

Freddy

On Mon, Oct 26, 2009 at 7:42 PM, Olivier Gaudin <gaudol@...> wrote:
Hello Julien,

You are correct that this could be improved. Could you file a Jira issue for it ?
Out of curiosity, are you saying you intend to reboot Sonar every night ?

Olivier




On Mon, Oct 26, 2009 at 8:57 AM, Julien HENRY <henryju@...> wrote:
Hi,

After restarting my Sonar instance, I discovered that many dependencies were downloaded again on the client that is running
mvn sonar:sonar

For example, I already had org.codehaus.sonar.runtime.jdbc-driver:parent:20091016150119 but after restarting Sonar instance the version 20091023184353 was downloaded. As the restart date was 23th October I suppose that the version of each dependency is computed according to Sonar instance start date.
I suppose there is some good raison to do this, but I also see some bad points:
 - having to download again the full set of dependencies is time consuming
 - if the Sonar instance is planned to reboot every night (for example), each day all clients using Sonar will download all dependencies and the local repository will grow dramatically.

Could you tell me what is the point of having a non fixed version number for these dependencies? Is there a way to prevent the full download behaviour after rebooting Sonar?

Thanks,

Julien





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





Re : [sonar-user] Sonar dependency management

by Julien HENRY :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Freddy and Olivier,

I've raised an issue: SONAR-1238

I don't plan to reboot Sonar every night, as we are currently performing hot backup of our environment. But I know we had some services that required a downtime period every nights for the backup. So I suppose that in case we set up a shared server, Sonar may be stopped on a regular basis.

Regards,

Julien

>
>De : Freddy Mallet <freddy.mallet@...>
>À : user@...
>Envoyé le : Lun 26 Octobre 2009, 19 h 53 min 34 s
>Objet : Re: [sonar-user] Sonar dependency management
>
>Hi Julien,
>
>FYI this mechanism has been set up to automatically use all new jdbc drivers, checkstyle/pmd extensions or Sonar plugins put on the sonar web directories without any requirements on the name of those jar files. But as Olivier said, it can be greatly improved.
>
>Freddy
>
>
>On Mon, Oct 26, 2009 at 7:42 PM, Olivier Gaudin <gaudol@...> wrote:
>
>>>Hello Julien,
>>
>>You are correct that this could be improved. Could you file a Jira issue for it ?
>>Out of curiosity, are you saying you intend to reboot Sonar every night ?
>>
>>>>Olivier
>>
>>
>>
>>
>>
>>On Mon, Oct 26, 2009 at 8:57 AM, Julien HENRY <henryju@...> wrote:
>>
>>>>>
>>>Hi,
>>>
>>>>>>After restarting my Sonar instance, I discovered that many dependencies were downloaded again on the client that is running
>>>>>>mvn sonar:sonar
>>>
>>>>>>For example, I already had org.codehaus.sonar.runtime.jdbc-driver:parent:20091016150119 but after restarting Sonar instance the version 20091023184353 was downloaded. As the restart date was 23th October I suppose that the version of each dependency is computed according to Sonar instance start date.
>>>>>>
>>>
>>>I suppose there is some good raison to do this, but I also see some bad points:
>>>>>>  - having to download again the full set of dependencies is time consuming
>>>>>>  - if the Sonar instance is planned to reboot every night (for example), each day all clients using Sonar will download all dependencies and the local repository will grow dramatically.
>>>
>>>>>>Could you tell me what is the point of having a non fixed version number for these dependencies? Is there a way to prevent the full download behaviour after rebooting Sonar?
>>>
>>>>>>Thanks,
>>>
>>>>>>Julien
>>>
>>>
>>>
>>>
>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe from this list, please visit:
>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email