[EMAIL PROTECTED] wrote:
yes, i will try to extract all the necessary stuff out of my project
to create a sample project.
Thnx. that would be a big help.
But one question in general:
What does the m2plugin if the current dependent project in workspace
has an other version number? Let me say if i have project A that
declares a dependency to project B -version 1.0 that is checked out in
the same workspace and have the version 0.9. I will assume the
dependency point to the deployed jar found in the repository with the
correct version instead of using that project in workspace. correct?
Good question and I think right now it is not taking exact version
into the account, but it most likely should. I recall there is a TODO
item for this in ClassPathResolver...
But in general i assume that not in all project it is a good solution
to reference projects in workspace. It offers you a really great
interaction mode to fix problems or develop features across multiple
projects, but it requires you to have all projects up to date and
checked out in your Workspace. (simply you must keep all in sync)
There is always pros and cons. You don't have to check the source code
into the workspace (but if you do, I don't think it is that big issue to
keep it up to date if you work with the snapshots), but then if you'll
need to step trough that code you would need source for that dependency
deployed to your local repository (or grabbed from the maven
repository). I don't think many projects do deploy sources for snapshots...
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
