Hey!

Thanks for your fast answer!

 

Yes the problem is indeed the same, I think. The problem is that projects in
the eclipse workspace are not referenced through JARs in the local
repository. They are just links to eclipse projects. I really don't
understand this "feature". The only advantage I can see is that during
development you don't need to execute a "install" on the project which
another projects depends on.

 

But there are lots of problems coming with this "feature" like the
versioning problem (always taking the current eclipse project stat
regardless of versioning information in the POM.xml).

 

Please tell me if I'm wrong.

 

When will the next release be available?

The problem is, that a very good friend of mine needs this plugin for his
school leaving exam. 

 

Thank you very much for your help.

Best wishes

Florian Salbrechter

 

  _____  

From: Piet van Remortel [mailto:[EMAIL PROTECTED] 
Sent: Freitag, 25. Mai 2007 07:24
To: Florian Salbrechter
Subject: Re: [m2eclipse-user] maven plugin + tomcat devloader

 

Hi Florian,

 

sounds like a problem that is similar to what we were struggling with
yesterday (!)

 

We changed the plugin code a bit to be able to use references to JARs, even
when an eclipse project is in scope with the same name.

Default behaviour is to give preference to eclipse projects.

 

Decision in our adapted version is based on the version number also.

 

We have to check the result of the code changes today, but if it seems
stable, I'll let you know and post this on the mailing list.

 

regards,

 

Piet

 

--

Piet van Remortel, Phd

PowerScan BVBA

 

Tel: +32 3 870 97 65

Mob: +32 497 393 166

 





 

On 24 May 2007, at 19:58, Florian Salbrechter wrote:





Hi!

 

I'm developing a JSF web application with sysdeo tomcat plugin in eclipse.

I have 2 projects:

 

* A project manager application which contains the logic

* The JSF web application

 

In the JSF web application I add the dependency to the first project. This
works fine for eclipse.

Then I add all classes to the DevLoader Classpath.

 

But the problem is that the dependency link to the first project is not
expressed as a link to a JAR in the local repository. It is just a reference
to another eclipse project. The DevLoader cannot find the first project and
I get a ClassCast exception when I try to instantiate any domain object.

 

Thanks for your help!

 





 

Reply via email to