> Well the classpath needs to be the same for compile-time as for
> runtime (or at least the runtime classpath is equal to or extends
> the compile-time classpath) to ensure the correct ordering.
I wasn't clear, but I agree.
>> If it's pre-launch, then we also have to maintain that list all the
>> time (which is kind of tricky -- is it there because you added it
>> or is it there because it was a transitive dep -- if it's
>> transitive, then we need to only remove it if it's gone from all
>> the frameworks that contain it recursively).
> i.e., you end up with two TreeSets (declaredDependencies,
> transitiveDependencies) and the resulting set is the union of the two.
Which is sooooort of what happens when you launch, except that the
classpath is already flattened and I back into this.
> (at the risk of going out on a limb) perhaps instead of rewriting
> something, you could reuse something like these:
> http://maven.apache.org/ant-tasks.html, woproject-maven2...
Awesome! At last there won't be any confusion at all for WOLips
users ...
ms
This archive was generated by hypermail 2.0.0 : Wed Sep 10 2008 - 09:36:57 EDT