>________________________________
>From: Adam Murdoch <[email protected]>
>
>
>Hi,
>
>
>I'd rather we went with a variation on option 3. It's actually very simple:
>* Change the BasePlugin so that the default configuration no longer extends
>archives.
>* Change the JavaPlugin so that it adds the Jar to both the runtime and
>archives configurations.
>* Change the WarPlugin so that it no longer disables the Jar task or removes
>it from any configuration.
>
Isn't there still the problem with both the Jar and War in the archives
configuration?
I specifically pulled the war out of the archives configuration to get around
the warning from javac. I can see if the compile dependency uses classes
instead of the jar that just stuffing it into the runtime would be sufficient,
but I didn't think that was how project dependencies worked yet.
I must be missing something if just those simple changes (plus the changes to
ear) remove the issues. If default is still used for project dependencies,
then what is actually included in that configuration? Would compile
dependencies point to depended-upon project runtime?
-Spencer
