Bottom line is either we can make the project to build using the maven
or use eclipse built-in build.
1) If we use maven, we need to depend on maven and maven eclipse
2) If we use eclipse build, we can provide option to user to
a) add the dependencies manually.
b) and/or given a maven repo location and version, manually download
the resources from URL and save in the project and use them just.
Since (2) is minimum dependency route, I am OK with pursuing that. I see
that what you are proposing below
I would use the above as default, but in "preferences" for the project,
I will let them change it.
I would just use the hard coded based on given version, as with every
> either by hardcoded names or by parsing pom.xml to get both the the
> repository location and the dependencies.
version this will change. Parsing pom.xml is bad idea, as this can be
No separate metadata location needed. Just copy them into the project
> The Cdk wizard may have a check-box to force a download or use an old
> download. Downloaded jars can be kept in metadata location of the
> workspace. Each Cdk project may either use a local copy which gets
> copied from the metadata location or may directly point to the
> metadata location to always get pointed to the latest download.
the very first time when they create the connector. If some reason
download is not successful or on users wish let them add manually. It
does not matter how they got the jars.
> This is to facilitate build and export without maven installed and a
> maven build. Let me know what you think.