Re: [exoplatform] Problem with build a portlet component

["Alexey Zavizionov" <alexey.zavizionov@xxxxxxxxxxxxxxxxxx>]

Hello, Abdel

Did you try within pom.xml your's Portlet B project describe
dependency portlet A with type "war", like as:
     <dependency>
        <groupId>com.example.projects</groupId>
        <artifactId>documentedprojectdependency</artifactId>
        <version>1.0-SNAPSHOT</version>
        <type>war</type>
        <scope>runtime</scope>
     </dependency>
?

Regards,
Alexey

On 5/23/07, red <a_red@xxxxxxx> wrote:
> Hi,
>
> I have a problem to build a portlet component.
> I have a portlet A with the pom-packaging exo-portlet. I can build it.
> I have a portlet B which has a dependence to Portlet A. I see by building
> this component, that maven lookup for a package of Portlet A as jar file
> instead of exo-portlet or war file. I have a work-around, I copy the package
> war file of Portlet A  to a jar file in the maven repository.
> How can I resolve this problem ?
>
> Thanks
> Abdel
>
> --
> View this message in context: 
> http://www.nabble.com/Problem-with-build-a-portlet-component-tf3802994.html#a10760704
> Sent from the eXo Platform mailing list archive at Nabble.com.
>
>
>
>
> --
> You receive this message as a subscriber of the exoplatform@xxxxxxxxxxxxx 
> mailing list.
> To unsubscribe: mailto:exoplatform-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws