Re: [tycho-user] compile/build time dependency but not in MANIFEST.MF

["Sievers, Jan" <jan.sievers@xxxxxxx>]

you can use a jars.extra.classpath entry in build.properties, see [1] for example

Regards,
Jan

[1] https://github.com/sonatype/sonatype-tycho/tree/master/tycho-its/projects/TYCHO253extraClassPathEntries/org.eclipse.tycho.testExtraClasspathTest1 




From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Greg Amerson
Sent: Dienstag, 7. Juni 2011 16:43
To: Tycho Users
Subject: Re: [tycho-user] compile/build time dependency but not in MANIFEST.MF

I have figured out one way to do this.  I can list those osgi bundles that I need on the compile classpath in the MANIFEST.MF and mark them as optional.  That way my bundles will install into a fresh eclipse with requiring the compile time only bundles.  However, in the future will need a more robust way to do this. 

Question: if I have a target platform will all of those bundles be available on the maven.compile.classpath ant classpathref?
On Mon, Jun 6, 2011 at 5:12 PM, Greg Amerson <gregory.amerson@xxxxxxxxxxx> wrote:
Hello all,

Is there a way to specify a compile time dependency for a plugin/bundle in a pom.xml?  I need some osgi bundles to be on the classpath when tycho builds my plugin because I have to execute some ant tasks as a part of code-generation step that needs some additional jars.  But I don't want to list these dependencies in my MANIFEST.MF since those dependencies only required at compile time and not  at runtime.  Also I want to prevent those bundles from being installed by p2 so I don't want them listed in MANIFEST.MF file.  

-- 
Greg Amerson (@greg_amerson)
Liferay, Inc. (#liferay)



-- 
Greg Amerson (@greg_amerson)
Liferay, Inc. (#liferay)