Daniel,
I don't have all answers for you, however I have a suggestion.
So, put Eclipse aside for some time and try to create few test
projects that would work as you want Maven from the command line, e.g.
produce war files with content that you want to see. Just make sure
Eclipse don't see any of those files.
You may need to read documentation for maven-war-plugin at
http://maven.apache.org/plugins/maven-war-plugin/
and can also ask questions in the Maven user's mailing list
http://www.nabble.com/Maven---Users-f178.html
Once you make that work with Maven you can try to import it into
Eclipse and if it won't work, you'll have test projects that you could
submit with the bug report that would allow us to reproduce issue and
would help to find a working solution.
I know it is not much, but together we could make it work if we try
hard enough.
Thanks
Eugene
vuzbuz wrote:
And again lots of thanks.
I'd resopond with regard to the numbering:
2. I think I'm a little bit confused here. As far as I can understand you, a
dependency of type [war] and scope [compile] will not offer project A's
classes to project B in compile time (as opposed to a type [jar] dependency
that will). In addition, project A's jsps are not packaged when using WTP's
deploy in Eclipse. What should happen with project A's classes when I deploy
project B with WTP? Right now, I go to tomcat's webapp directory and into
project B's directory, but I don't see project A's classes in the
WEB-INF/classes/ dir. I deduct that when I deployed project B with WTP, even
though I had a dependency on project A's WAR - it didn't package anything
(not the classes nor the jsps).
I think this sums up my main and biggest problem, and I still don't see what
I better double-check. I mention again that when I use mvn:package on
project B, the classes and jsps of project A do appear. So the problem seems
to be plainly with the deployment of project B with WTP, which completely
ignores the maven's dependency on project A's WAR.
5. How shall I develop my infrastructure project (project A) along with some
other project that depends on it (project B)?
if project B has all its dependencies in maven, including the dependency on
project A - I'd have to install a new WAR of project A every time I change
it as part of the development of project B!
It's absurd to me :)
Eclipse gives me the solution, enabling me to create a dependency of project
B on project A without having jars or wars. This way I can change project A
and instantly see the effect on project B, right? But if I'm not to touch
the dependencies of project B manually because of maven, I won't be able to
do it...
So, I hope I made myself clearer this time.
Sorry if it turns out too long and exhausting, but I really appreciate the
help.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
