Two stage repositories for ServiceMix 7

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Two stage repositories for ServiceMix 7

ksobkowiak
Hi

While releasing ServiceMix 7 the modules are always deployed into 2 stage repositories. Interesting is that the second repository contains always the same modules

  * features
  * the assembly

More interesting: the release process deploys first the modules to the first repository, next the modules mentioned above to the second repository and at the end the rest of the modules (e.g. archetypes, itests) again to the first repository.
Do you have idea for this behavior?

Regards
Krzysztof


On 10.06.2016 22:16, Krzysztof Sobkowiak wrote:
> The staging area is available at
>   https://repository.apache.org/content/repositories/orgapacheservicemix-1158
>   https://repository.apache.org/content/repositories/orgapacheservicemix-1159

--
Krzysztof Sobkowiak (@ksobkowiak)

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
   
Reply | Threaded
Open this post in threaded view
|

Re: Two stage repositories for ServiceMix 7

Gert Vanthienen
Administrator
L.S.,

I suspect this is caused by the dependency the karaf-maven-plugin has
on wagon-http-2.8.jar. If you look at the two staging repositories in
Nexus, you'll notice a difference in the User-Agent string. Some of
the artifacts are in a repository that's seems to have a duplicate
User-Agent header, which appears to be a known issue for that version
of wagon-http, cfr. https://issues.apache.org/jira/browse/WAGON-432

Regards,

Gert Vanthienen


On Fri, Jun 10, 2016 at 10:25 PM, Krzysztof Sobkowiak
<[hidden email]> wrote:

> Hi
>
> While releasing ServiceMix 7 the modules are always deployed into 2 stage repositories. Interesting is that the second repository contains always the same modules
>
>   * features
>   * the assembly
>
> More interesting: the release process deploys first the modules to the first repository, next the modules mentioned above to the second repository and at the end the rest of the modules (e.g. archetypes, itests) again to the first repository.
> Do you have idea for this behavior?
>
> Regards
> Krzysztof
>
>
> On 10.06.2016 22:16, Krzysztof Sobkowiak wrote:
>> The staging area is available at
>>   https://repository.apache.org/content/repositories/orgapacheservicemix-1158
>>   https://repository.apache.org/content/repositories/orgapacheservicemix-1159
>
> --
> Krzysztof Sobkowiak (@ksobkowiak)
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
>
Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
Reply | Threaded
Open this post in threaded view
|

Re: Two stage repositories for ServiceMix 7

ksobkowiak
Hi Gert

Thanks for the hint. I'll check it.

Regards
Krzysztof

On 13.06.2016 11:04, Gert Vanthienen wrote:

> L.S.,
>
> I suspect this is caused by the dependency the karaf-maven-plugin has
> on wagon-http-2.8.jar. If you look at the two staging repositories in
> Nexus, you'll notice a difference in the User-Agent string. Some of
> the artifacts are in a repository that's seems to have a duplicate
> User-Agent header, which appears to be a known issue for that version
> of wagon-http, cfr. https://issues.apache.org/jira/browse/WAGON-432
>
> Regards,
>
> Gert Vanthienen
>
>
> On Fri, Jun 10, 2016 at 10:25 PM, Krzysztof Sobkowiak
> <[hidden email]> wrote:
>> Hi
>>
>> While releasing ServiceMix 7 the modules are always deployed into 2 stage repositories. Interesting is that the second repository contains always the same modules
>>
>>   * features
>>   * the assembly
>>
>> More interesting: the release process deploys first the modules to the first repository, next the modules mentioned above to the second repository and at the end the rest of the modules (e.g. archetypes, itests) again to the first repository.
>> Do you have idea for this behavior?
>>
>> Regards
>> Krzysztof
>>
>>
>> On 10.06.2016 22:16, Krzysztof Sobkowiak wrote:
>>> The staging area is available at
>>>   https://repository.apache.org/content/repositories/orgapacheservicemix-1158
>>>   https://repository.apache.org/content/repositories/orgapacheservicemix-1159

--
Krzysztof Sobkowiak (@ksobkowiak)

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)