How to resolve artifact conflict when deploying applications

[Gary Shin <gs...@gmail.com>]

Hi,
    I wanted to deploy an application which is built using maven, it
contains a list of self written jars and third-party (apache software) jars.
So what is the best way to deploy it in geronimo without conflicting with
the existing geronimo jars.
Eg:-  Say my application has older version of axis2 jar, i don't want it to
conflict with geronimo's axis2.

I hope the question is clear, please provide suggestions and workarounds to
deal with this.

Thanks
SG

Re: How to resolve artifact conflict when deploying applications

[chi runhua <ch...@gmail.com>]

For G3.0, the deployment codes will covert the old hidden-classes
configuration to the new import-package style.
<hidden-classes>javax.faces</hidden-classes> would be
<import-package>!javax.faces</import-package>.

<inverse-classloading> is not supported anymore.

Jeff C

On Wed, Jun 22, 2011 at 3:03 PM, Gary Shin <gs...@gmail.com> wrote:

> What if it is Geronimo 3, does this feature still exist. Please let me
> know, so i would like to give it a try.
>
> Thanks,
> SG
>
>
> On Tue, Jun 21, 2011 at 8:44 PM, chi runhua <ch...@gmail.com> wrote:
>
>> If you are using Geronimo 2.2 or 2.1, you can define the classloading
>> order by using <hidden-classes> of <inverse-classloading> in the deployment
>> plan.
>>
>> See https://cwiki.apache.org/GMOxDOC22/geronimo-webxml.html
>>
>> HTH.
>>
>> Jeff
>>
>>
>> On Wed, Jun 22, 2011 at 8:21 AM, Gary Shin <gs...@gmail.com> wrote:
>>
>>> Hi,
>>>     I wanted to deploy an application which is built using maven, it
>>> contains a list of self written jars and third-party (apache software) jars.
>>> So what is the best way to deploy it in geronimo without conflicting with
>>> the existing geronimo jars.
>>> Eg:-  Say my application has older version of axis2 jar, i don't want it
>>> to conflict with geronimo's axis2.
>>>
>>> I hope the question is clear, please provide suggestions and workarounds
>>> to deal with this.
>>>
>>> Thanks
>>> SG
>>>
>>
>>
>

Re: How to resolve artifact conflict when deploying applications

[Gary Shin <gs...@gmail.com>]

What if it is Geronimo 3, does this feature still exist. Please let me know,
so i would like to give it a try.

Thanks,
SG

On Tue, Jun 21, 2011 at 8:44 PM, chi runhua <ch...@gmail.com> wrote:

> If you are using Geronimo 2.2 or 2.1, you can define the classloading order
> by using <hidden-classes> of <inverse-classloading> in the deployment plan.
>
> See https://cwiki.apache.org/GMOxDOC22/geronimo-webxml.html
>
> HTH.
>
> Jeff
>
>
> On Wed, Jun 22, 2011 at 8:21 AM, Gary Shin <gs...@gmail.com> wrote:
>
>> Hi,
>>     I wanted to deploy an application which is built using maven, it
>> contains a list of self written jars and third-party (apache software) jars.
>> So what is the best way to deploy it in geronimo without conflicting with
>> the existing geronimo jars.
>> Eg:-  Say my application has older version of axis2 jar, i don't want it
>> to conflict with geronimo's axis2.
>>
>> I hope the question is clear, please provide suggestions and workarounds
>> to deal with this.
>>
>> Thanks
>> SG
>>
>
>

Re: How to resolve artifact conflict when deploying applications

[chi runhua <ch...@gmail.com>]

If you are using Geronimo 2.2 or 2.1, you can define the classloading order
by using <hidden-classes> of <inverse-classloading> in the deployment plan.

See https://cwiki.apache.org/GMOxDOC22/geronimo-webxml.html

HTH.

Jeff

On Wed, Jun 22, 2011 at 8:21 AM, Gary Shin <gs...@gmail.com> wrote:

> Hi,
>     I wanted to deploy an application which is built using maven, it
> contains a list of self written jars and third-party (apache software) jars.
> So what is the best way to deploy it in geronimo without conflicting with
> the existing geronimo jars.
> Eg:-  Say my application has older version of axis2 jar, i don't want it to
> conflict with geronimo's axis2.
>
> I hope the question is clear, please provide suggestions and workarounds to
> deal with this.
>
> Thanks
> SG
>