Hi Niclas,
Niclas Hedhman a écrit :
Gang,
Although there are still a few things to consider and figure out for
2.0, I have spent most of the time the last few weeks trying to get
the final artifacts to build.
Still got a bit more to do on it, but I would like to get some feedback;;
http://repository.ops4j.org/maven2/org/org.qi4j/2.0-beta-1/
I see only the dist artifacts here. Is it on purpose that the individual
artifacts were not deployed?
One particular thing is that I am trying to satisfy the non-Maven
developer by generating the URLs for downloading the dependencies of
each of our components and stick it into ilb/dependencies/ folder. I
have still not worked out how to locate the repository, so Maven
Central is currently hardcoded.
Also, should we ship the entire website, or is it better to get the
'versioning' of website working, and link the particular version from
the release with a redirect?
I think having both would be awesome. Developers should be able to browse
the documentation online with a version switcher and browse it offline from
within the SDK distribution.
I have excluded putting the "-javadoc" jars into the binary distro,
primarily since I think it is only used by the Maven developer and
they pick that up from the repository. The full javadoc (one
hierarchy) is in the dist though, and I think that is a good thing.
Opinions?
Sounds fair to me.
What else?
The idea is that if you download the sources, you should be able to
./gradlew -Dversion=2.0-beta-1 dist
and it will build itself, the binary dist and explode the binary dist
into build/dist of the root project.
But I haven't tested that yet.
I just ran it with "-x signArchives" and it succeeded and produced the
distribution in build/distributions and extracted it in build/dist.
The build now generates dependencies.xml for each module in Maven pom
format, and I will figure out how to auto include that in the
documentation for each module. Suggestion of DocBook format that will
style well is welcome.
Having groupId, artifactId, version and eventually a download url would
be nice.
So, even though I have been rather quiet lately, I have managed to
push some important (boring, ungrateful) stuff forward.
That's tedious work, thanks for that!
Cheers
/Paul
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
