Thomas,
Like I said, it is hard to say anything really meaningful without
looking at your projects.
You can't change order of entries in "maven dependencies" container
(something we'll fix in the future builds), but you can still add
arbitrary entries to Eclipse buildpath and change their order.
regards,
Eugene
Thomas Tardy wrote:
Hello,
I don't think it's a maven configuration issue. I have tested it in
eclipse without the m2eclipse plugin and maven at all. It looks like
eclipse is ignoring the fact that the EAR Libraries in an EJB project
are being exported or not. But eclipse looks at the project dependency
order in the XxxTest project. Because our EJB project has the name
GbCadastreAslEjb it's before the GbCadastreCommon in the project
dependency order. Therefore the classes from the common project are
being resolved by GbCadastreAslEjb --> EAR Libraries --> common.jar.
Is there a way to manipulate the project order built up by the
m2eclipse plugin? Default is alphabetical.
Kind Regards,
Thomas
On Jan 25, 2008 10:43 AM, Eugene Kuleshov <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Thomas,
I can't think of any useful suggestions based on your description. It
could be pretty much anything, starting from a typo in some pom.xml
If you think there is a bug in m2eclipse, please fill a jira
issue and
attach complete project that would allow to reproduce it. See
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
regards,
Eugene
Thomas Tardy wrote:
> Hello again,
>
> I'm sorry to annoy you again but this is a realy urgent issue. Does
> anybody know why the dependencies are being resolved as described?
>
> Thanks for any help!
>
> Regards,
> Thomas
>
>
> On Jan 24, 2008 4:19 PM, Thomas Tardy <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>
wrote:
>
> I forgot to say, that the EAR Libraries in the XxxEjb
project are
> not being exportet. Therefore it's surprising me why the XxxTest
> project can see these Jars.
>
>
> On Jan 24, 2008 3:57 PM, Thomas Tardy <
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>> wrote:
>
> Hello,
>
> first of all, I have to explain the project structure.
>
> *XxxEar*: Eclipse Ear Project
> Contains all JARs
> No Maven build.
> Contains a Jar of the XxxCommon Project
>
> *XxxEjb*: Eclipse Ejb Project
> Contains the Ejbs. Gets the dependencies from the EAR
Libraries.
> Maven dependencies for compile time.
> Uses the EAR Dependecy of the XxxCommon Project.
>
> *XxxCommon*: Eclipse Java Project
> Contains some utility classes.
> Maven dependencies.
>
> *XxxTest*: Eclipse Java Project
> Contains test classes.
> Maven dependencies to XxxCommon and XxxEjb for remote
testing.
> M2Eclipse resolves both projects as project dependencies
>
> The problem I have is that the XxxTest Projects gets the
> classes from the XxxCommon project not directly from
project?
> The classes from the Jar in the XxxEar Project are being
used.
>
> Does anybody know why the behavior is like I described? How
> can I change it?
>
> Thanks for your help!
> Thomas
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
