I expected this answer. My current workaround looks like that: manually deploying the sourecs-jar and the javadoc-jar into my local repo. For jMonkeyEngine it is not possible to convert the jar to a real maven artifact. It is mandatory to address this jar file absolute in the machines installation. On execution there will be a lookup for native libraries relative to jMonkeyEnige3.jar
Is there no other solution? -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Anders Hammar Gesendet: Dienstag, 1. Februar 2011 14:20 An: Maven Users List Betreff: Re: Attach sources/javadoc to system-scoped dependency Add the artifact (including javadoc and sources artifacts) to your repository manager and use a normal compile scope. Then it will work automatically. Using system scope is deprecated and highly discouraged as your build is not portable. /Anders On Tue, Feb 1, 2011 at 14:03, Hauschild, Klaus (EXT) < [email protected]> wrote: > Hi, > > we're using a system scoped dependency to jMonkeyEngine3 like this: > <dependency> > <groupId>com.jme3</groupId> > <artifactId>jMonkeyEngine3</artifactId> > <version>3</version> > <scope>system</scope> > <systemPath>${env.JME3_HOME}/jMonkeyEngine3.jar</systemPath> > </dependency> > The integration by m2e into Eclipse and building packages with Maven are > very fine. But in Eclipse there are no sources nor javadoc available without > manipulations by hand. I'm looking for an automatic solution. > > Is there a way? > > Thanks, Klaus > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
