You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by David Sean Taylor <da...@bluesunrise.com> on 2004/09/01 23:33:40 UTC
[j2] jsf-demo build and dependencies 'deployment' specific
I'd like to make 2 dependencies in the JSF-Demo application 'target'
specific
The dependency on jsp-api is conditional, depending on the target
application server, or deployment:
<dependency>
<groupId>jspapi</groupId>
<artifactId>jsp-api</artifactId>
<version>2.0-20040521</version>
<properties>
<war.bundle>true</war.bundle>
</properties>
</dependency>
It is required for Tomcat 4, but for Tomcat 5 it is not.
Does anyone know if Maven or Maven-2 will have support for
deployment-specific dependencies?
In the meantime, I've simply unconditionally added the dependencies
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [j2] jsf-demo build and dependencies 'deployment' specific
Posted by David Jencks <da...@yahoo.com>.
On Sep 1, 2004, at 5:30 PM, David Sean Taylor wrote:
> David Sean Taylor wrote:
>
>> David Jencks wrote:
>>
>>> I think you should have app server specific assembly modules, each
>>> with the appropriate dependencies for that app server.
>>>
>>> thanks
>>> david jencks
>>>
>> When you say modules, I think you mean what I understand to be maven
>> projects
yes.
I started on a couple named
installation
-geronimo
-tomcat4
I may have a patch in a day or two... but may get pulled in other
directions.
>> For example, under jetspeed-2 root, we might have:
>>
>> /assembly-modules
>> - tomcat-4
>> - tomcat-5
>> - jboss
>> - weblogic
>
> On second thought, that works great for building the portal, but im
> not sure how that helps my specific problem with building the jsf-demo
> So perhaps it should be:
>
> /portal
> /assembly-modules
> / tomcat-4
> / tomcat-5
> / jboss
>
> etc
>
> and likewise for each portlet application?
That seems like too much. I think there's something wrong if an
application won't work on several different servers. What exactly
happens if you include the dependency and run on tomcat5?
thanks
david jencks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [j2] jsf-demo build and dependencies 'deployment' specific
Posted by David Sean Taylor <da...@bluesunrise.com>.
David Sean Taylor wrote:
> David Jencks wrote:
>
>> I think you should have app server specific assembly modules, each
>> with the appropriate dependencies for that app server.
>>
>> thanks
>> david jencks
>>
> When you say modules, I think you mean what I understand to be maven
> projects
> For example, under jetspeed-2 root, we might have:
>
> /assembly-modules
> - tomcat-4
> - tomcat-5
> - jboss
> - weblogic
On second thought, that works great for building the portal, but im not
sure how that helps my specific problem with building the jsf-demo
So perhaps it should be:
/portal
/assembly-modules
/ tomcat-4
/ tomcat-5
/ jboss
etc
and likewise for each portlet application?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [j2] jsf-demo build and dependencies 'deployment' specific
Posted by David Sean Taylor <da...@bluesunrise.com>.
David Jencks wrote:
> I think you should have app server specific assembly modules, each
> with the appropriate dependencies for that app server.
>
> thanks
> david jencks
>
When you say modules, I think you mean what I understand to be maven
projects
For example, under jetspeed-2 root, we might have:
/assembly-modules
- tomcat-4
- tomcat-5
- jboss
- weblogic
etc.
and to build the war file for a specific app server, simply cd to the
appropriate directory and type maven war or maven quickStart
Is that roughly what you are proposing?
If so, I definately like it
It would also help in that we don't need to modify properties to build
for one app server or another
And all app server specific resources could be moved into their
respective projects (modules)
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [j2] jsf-demo build and dependencies 'deployment' specific
Posted by David Jencks <da...@yahoo.com>.
I think you should have app server specific assembly modules, each with
the appropriate dependencies for that app server.
thanks
david jencks
On Sep 1, 2004, at 2:33 PM, David Sean Taylor wrote:
> I'd like to make 2 dependencies in the JSF-Demo application 'target'
> specific
> The dependency on jsp-api is conditional, depending on the target
> application server, or deployment:
>
> <dependency>
> <groupId>jspapi</groupId>
> <artifactId>jsp-api</artifactId>
> <version>2.0-20040521</version>
> <properties>
> <war.bundle>true</war.bundle>
> </properties>
> </dependency>
> It is required for Tomcat 4, but for Tomcat 5 it is not.
> Does anyone know if Maven or Maven-2 will have support for
> deployment-specific dependencies?
>
> In the meantime, I've simply unconditionally added the dependencies
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org