|Re: How to reference a project as an dependency for Dynamic web project [message #549931 is a reply to message #549776]
||Wed, 28 July 2010 13:43
| Larry Isaacs
Registered: July 2009
On 7/27/2010 6:26 PM, J. N. wrote:|
> Perfect, worked like a charm. Thanks a million.
> Last question would be about fixing that warning. What exactly happened
> in background or in other words where can I see a result of that fix ...
> some property page with libraries for export.
If you go to the Libraries tab on the Java Build Path page and expand a
jar that is marked for inclusion in WEB-INF/lib, you will see a child
item that says "Publish/export dependency: Added to parent module". You
can select this item and click "Remove" to "un-mark" the jar for inclusion.
You can also mark jars for inclusion using the "Referenced Projects
Classpath Entries" type in the Deployment Assembly page. However, this
can be somewhat confusing as it currently offers to mark for inclusion
all jars in all projects, not just the projects your current web project
depends on. Also, it's not clear that with the Deployment Assembly
approach, if you mark a jar for inclusion that is in a web project, you
are marking it so an EAR project will know that this web application
depends on this jar. It does not mark jars in web projects in a way
that includes it in the web project's WEB-INF/lib.
The Problems view approach works for marking dependent jars in both web
projects and utility projects. The Problems view approach also offers
the possibility to explicitly exclude the jar and make the warning go
away without including the jar.
> One suggestion if I may ; would be great for you to have a few more
> complex totorials about how to use WTP. In our work we still use Sysdeo
> tomcat plugin, but we could benefit from WTP features. I was not allowed
> to migrate to Dynamic project because a lack of documentation opn the
> net. I found few tutorials, but all of them are very basic and does not
> explain things (there are just steps do this to that) with complex
> projects you need to know more about what happens in background. Is
> there any good resource / documentation about all the features of WTP ?
The problem here is "easier said than done". I know in my case, I have
a limited number of cycles to devote to the Tomcat plug-ins in Eclipse.
Devoting them to working on the code tends to take priority over
working on documentation. The problem with documenting the migration of
external projects to WTP is that the starting point for those external
projects is just too varied. It would take a book, or a huge
programming effort, to deal all the different possibilities. To make
documenting practical, you would have to make a bunch of simplifying
assumptions. Unfortunately that makes it likely that not all migration
issues will be addressed for many external projects. It's better to say
to create a new Dynamic Web Project and port the content from the
external project to the Dynamic Web Project. When porting the content,
you have the responsibility to know if that content has special issues
or dependencies that must be addressed.
> Thanks and wish you a good luck with this project looks awesome so far :)
Powered by FUDForum
. Page generated in 0.27713 seconds