L.S.,
Normally, you should be able to add an exclusion pattern to the source
folder in Eclipse's build path configuration in order to skip the
archetypes. You will have to do this manually every time when you
import the projects, because I don't think the maven eclipse plug-in can
generate this information in the .classpath files automatically.
Hope this helps,
Gert Vanthienen
[EMAIL PROTECTED]
Guillaume Nodet wrote:
The problem comes from Eclipse which considers the .java
files as classes to compile. In the case of archetypes,
they are just resources to be bundled, and there is no
real code to compile. Not sure how to tell Eclipse to
not compile these files.
On 10/2/06, Robbins <[EMAIL PROTECTED]> wrote:
Hi,
I have a problem when I build the source code of the new version of
ServiceMix (3.0)...
It seems that the build is OK; after this operation, I follow the
steps of
this link:
http://servicemix.goopen.org/sm30ug/importing-servicemix-into-eclipse.html
Two projects fail in the eclipse workspace: servicemix-service-engine &
servicemix-binding-component.
I suppose that the problem lies in the build step, because if I open
a java
file out of one of these projects, the first line reads as:
package ${packageName};
which obviously should have been replaced. Does anyone have any idea
of how
this issue can be solved?
Thank you so much for all suggestions
H. Robbins
--
View this message in context:
http://www.nabble.com/Problem-in-eclipse-tf2369739.html#a6601603
Sent from the ServiceMix - User mailing list archive at Nabble.com.
