Document type classpath resolution

cditcher
Posts: 29
Joined: Thu Jun 21, 2012 6:47 pm
Location: Victoria BC, Canada

Document type classpath resolution

Post by cditcher » Fri Mar 11, 2016 3:41 am

We deploy a product as an oXygen add-on which is a great feature and works well for our application. This may be trivial, but currently I have to add each dependency to the classpath tab individually. See below:

Image

So currently, we list

Code: Select all

${baseFramework}/lib/[jarname-version].jar
for each dependent jar on our classpath. This approach works but is cumbersome. Is there a way to be less specific? Like

Code: Select all

${baseFramewor}/lib/**.jar
? I have tried a few different approaches but and none have worked so far.

It would be helpful for us when verion numbers change, or a bunch of new jars are needed for deployment etc.

Thanks,

Chris

Radu
Posts: 6582
Joined: Fri Jul 09, 2004 5:18 pm

Re: Document type classpath resolution

Post by Radu » Fri Mar 11, 2016 9:24 am

Hi Chris,

It's a nice idea, we implemented it about a month ago so Oxygen 18 will allow you to use simple patterns to specify the JAR libraries to include from a folder.
We'll release Oxygen 18 in about 2 months and I will try to update this forum thread when we do.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

Radu
Posts: 6582
Joined: Fri Jul 09, 2004 5:18 pm

Re: Document type classpath resolution

Post by Radu » Thu May 05, 2016 9:54 am

Hi,

Just to update this thread, Oxygen 18.0 should have support for this feature.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

cditcher
Posts: 29
Joined: Thu Jun 21, 2012 6:47 pm
Location: Victoria BC, Canada

Re: Document type classpath resolution

Post by cditcher » Tue Aug 16, 2016 11:39 pm

Thanks! That will make our deployments easier. We are looking at updating to 18 soon.

Post Reply