I updated components.xml to <addedToClasspath>true</addedToClasspath>. It did not make any difference. Sar dependecies were not on the build classpath. Would I need to do anything else to get addedToClasspath to work?
-----Oorspronkelijk bericht----- Van: Tom Huybrechts [mailto:[EMAIL PROTECTED] Verzonden: maandag 10 april 2006 10:20 Aan: Maven Users List Onderwerp: Re: [m2] Eclipse plugin does not seem to make references for packaging "sar" That's because addedToClasspath = false in the components.xml for jboss-sar see https://svn.mojo.codehaus.org/mojo/trunk/mojo/mojo-sandbox/jboss-sar-mav en-plugin/src/main/resources/META-INF/plexus/components.xml Maybe that is also an explanation for why the dependency isn't added to the Eclipse project. Tom On 4/10/06, Peschier J. (Jeroen) <[EMAIL PROTECTED]> wrote: > > > In addition to project references not being made for sar projects, I > also observed that building projects that depend on sar artifacts > doesn't work. It seems that sar artifacts are not added to the build > classpath. > > I have tried setting the sar dependency scoped to "compile" and > "provided". Neither seem to add the sar in the build classpath. > > As a workaround I can add the sar project reference manually in Eclipse > (boo). However the Maven reactor build remains broken preventing me to > compile/install/deploy an ear with sar components. > > > -----Original Message ----- > From: Peschier J. (Jeroen) > Sent: vrijdag 7 april 2006 17:07 > To: Maven Users List > Subject: [m2] Eclipse plugin does not seem to make references for > packaging "sar" > > > I have some projects that depend on projects with packaging "sar". I > observe the following behaviour: > > - Running eclipse:eclipse from the parent POM, project references to > dependencies with packaging jar and ejb are made. However the project > references for sar projects seem to be omitted. > - Running eclipse:eclipse from a child POM, classpath references to jars > and ejbs in the local repository are made. Here, references to sars seem > to be omitted as well. > > The docs for the maven-eclipse-plugin don't list which package-type are > actually supported. Does the package type matter when making project > references? Short of declaring a dependency in the POM, is there another > way to force a project reference to be added when the eclipse plugin > runs? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
