No. We could take advantage of http://maven.apache.org/ant-tasks.html to
create various ant scripts to do that. However, since I'm still not
sure what this supposed support for non-maven builds really looks like
it is hard to have a good answer to the question.
Ralph
Joerg Heinicke wrote:
On 09.01.2008 00:11, Ralph Goers wrote:
Maybe we are on the same page, but I'm unclear what you mean by
"include". A cocoon release should consist of nothing more than
deploying artifacts to the maven repository. End users should be
getting the release by specifying the version number of the release
in the archetypeVersion.
That's exactly what I don't want to have as ONLY option. IMO we must
provide the classic kind of a release. Otherwise a comment like we are
going to put into the FAQ ("You really don't need Maven!") is also
just a joke. Should one grab each jar from the Maven repository by hand?
Joerg
