--
You received this message because you are subscribed to the Google Groups "DaisyDiff" group.
To post to this group, send email to dais...@googlegroups.com.
To unsubscribe from this group, send email to daisydiff+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/daisydiff?hl=en.
I have thought of this myself and in fact for internal development I
use Maven to build daisydiff and not Ant. However it is noted that
"Only releases can be uploaded to the central repository, that means
files that won't change and that only depend on other files already
released and available in the repository."
Daisydiff at the moment is based on
<dependency>
<groupId>org.eclipse.core</groupId>
<artifactId>runtime</artifactId>
<version>20070801</version>
</dependency>
which (unless I am missing something) is not itself in Maven Central.
So possible choices are
A. Test daisydiff with a version of eclipse core that exists in Maven central
B. Embed eclipse core in daisydiff itself
C. Something else that I haven't though of.
So Jan what do you suggest we do?
Actually, I just noticed that it is a bit more complicated than this.
At the moment daisyDiff is based on
A. The eclipse runtime jar
B. Eclipse "compare" code which is already embedded in the DaisyDiff
source code.
See http://code.google.com/p/daisydiff/source/browse/#svn/trunk/daisydiff/src/java/org/eclipse/compare
The runtime jar is actually used from the Eclipse "compare" code and
not daisyDiff itself.
Also it seems to be that eclipse runtime versions from the maven repo
(even from 2007) are completely different that those found at the
Daisy
Diff Source code.