Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

When you specify type=pom you are depending on the pom which puts an inter-project dependency (i.e. forces the reactor order) but does not put on the classpath... at least from what I recall... other than that you could create a custom packaging and say that the custom packaging is not added to th

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

On Sun, Dec 13, 2015 at 3:59 PM, Robert Scholte wrote: > Op Sun, 13 Dec 2015 21:23:16 +0100 schreef Andreas Gudian > : > > >> 2015-12-13 12:05 GMT+01:00 Robert Scholte : >> >>> The first time I heard about JDK9s Jigsaw having a classpath and a >>> modulepath, which can be used at the same time AND

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

Op Sun, 13 Dec 2015 21:23:16 +0100 schreef Andreas Gudian : 2015-12-13 12:05 GMT+01:00 Robert Scholte : The first time I heard about JDK9s Jigsaw having a classpath and a modulepath, which can be used at the same time AND both containing jars, I had a big "OH NO!". We can't change the

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

2015-12-13 19:04 GMT+01:00 Benson Margulies : > On Sun, Dec 13, 2015 at 9:40 AM, Benson Margulies > wrote: > > On Dec 13, 2015 3:25 AM, "Stephen Connolly" > > wrote: > >> > >> pom? > > > > > > 1. The feature descriptor is xml > > > > 2. I believe that this still adds transitive dependencies to t

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

2015-12-13 12:05 GMT+01:00 Robert Scholte : > The first time I heard about JDK9s Jigsaw having a classpath and a > modulepath, which can be used at the same time AND both containing jars, I > had a big "OH NO!". We can't change the pom, so the first thing that > came to my mind was indeed usin

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

On Sun, Dec 13, 2015 at 9:40 AM, Benson Margulies wrote: > On Dec 13, 2015 3:25 AM, "Stephen Connolly" > wrote: >> >> pom? > > > 1. The feature descriptor is xml > > 2. I believe that this still adds transitive dependencies to the dependency > graph. How about the following proposition: of the t

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

On Dec 13, 2015 3:25 AM, "Stephen Connolly" wrote: > pom? > 1. The feature descriptor is xml 2. I believe that this still adds transitive dependencies to the dependency graph. > > On Saturday 12 December 2015, Benson Margulies > wrote: > > > Sometimes, we want to declare a dependency witho

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

The first time I heard about JDK9s Jigsaw having a classpath and a modulepath, which can be used at the same time AND both containing jars, I had a big "OH NO!". We can't change the pom, so the first thing that came to my mind was indeed using the scope for this. But that'll have a huge

Re: I wish we had a way to declare a dependency that wouldn't participate in the classpath

pom? On Saturday 12 December 2015, Benson Margulies wrote: > Sometimes, we want to declare a dependency without changing a classpath. > > Project A builds an OSGi bundle and a Karaf feature (classifier > 'feature', type 'xml'). > > Project B wants to consume the feature. it wants to declare the

I wish we had a way to declare a dependency that wouldn't participate in the classpath

Sometimes, we want to declare a dependency without changing a classpath. Project A builds an OSGi bundle and a Karaf feature (classifier 'feature', type 'xml'). Project B wants to consume the feature. it wants to declare the feature descriptor as a dependency, to (a) ensure reactor order, and (b)