On 4/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> OK just to be clear, your problem is solved? You've sent this email 2
> or 3 times now and I'm getting confused.
My problem *is* solved (i embeded maven 2.0.3-SNAPSHOT).
I sent 3 mails by accident. I though that you never received the
previous mails since i hadn't subscribed to the list yet. I
apologize. I'll be more careful next time.
ankostis
>
> > The problem gets fixed when using subsequent maven releases.
> >
> > I re-compiled mavenide with maven-embedder-2.0.3-SNAPSHOT-dep.jar and
> > problem solved!
>
> Wayne
>
>
> On 4/14/06, Kostis Anagnostopoulos <[EMAIL PROTECTED]> wrote:
> > Hi to all,
> >
> > I think i found a bug:
> >
> > I use maven 2.0.4.
> > I have a project/subproject structure like that:
> >
> > /prj0
> > +prj1
> > +prj2
> >
> > The prj0 is a pom-type project.
> > The prj1 is jar-type;
> > The prj2 is ejb-type;
> > The prj2 *depends* on prj1.
> >
> > I have imported the parent project into eclise and activated mevenide.
> > (Notice that since the 'eclise:eclipse' goal does not generate
> > '.project' and '.classpath'
> > files for pom-type projects, the parent project does not get
> > automatically recognized
> > by eclipse.)
> >
> > When i choose 'Maven2|Update Source Folders', i get the following
> > error in eclipse's console:
> >
> > 12/4/2006 7:19:44 EEST: Unable to read project /prj0/prj2/pom.xml;
> > org.apache.maven.project.ProjectBuildingException: Duplicate project
> > ID found in <workspace_dir>/prj0/prj1/pom.xml
> >
> > and the update halts.
> >
> > Note that since the order of processing of mevenide is alphabetically
> > and my project names are such that prj2 gets processed before prj1, i
> > get only the src folders of prj2).
> >
> > If i remove the prj1 dependency from prj2, then no problem.
> >
> > The problem gets fixed when using subsequent maven releases.
> >
> > I re-compiled mavenide with maven-embedder-2.0.3-SNAPSHOT-dep.jar and
> > problem solved!
> >
> > Anagnostopoulos Kostis
> >
>
