Sorry, been crazy at work. We should try to release a 1.1.2 release and manually create the POMs (perhaps by copying from the 1.2 branch?).
On 2/21/07, Achim Hügen <[EMAIL PROTECTED]> wrote:
James, could you please give me a short update? Do you plan to release a 1.1.2 version before 1.2? What needs to be done to release 1.1.2 ? Achim James Carman schrieb: > Hehe, that might just work! :-) We could use the HiveDoc maven plugin > that was proposed here a while back, right (can't recall who wrote it > off the top of my head)? I tried it and it worked quite well! We > should maybe make it a subproject or something > > > On 2/11/07, Achim Hügen <[EMAIL PROTECTED]> wrote: >> I assume that you refer to the new site I created. In deed it was >> built by >> maven, >> but that's a separate project: >> http://svn.apache.org/repos/asf/hivemind/hivemind-site/ >> >> As far as I know there is no translator. The main problem is, that >> all the >> xml >> entity stuff is not working anymore, which was used for most of the >> hyperlinks. >> Hivedoc generation isn't integrated either. >> >> Since the 1.1.2 release is pending so long I would suggest >> to build the site using ant and create the poms manually. >> Whereas "manually" could mean to use maven in the trunk and just >> change the file names and version numbers. >> >> Achim >> >> >> Am Sun, 11 Feb 2007 14:12:37 +0100 schrieb James Carman >> <[EMAIL PROTECTED]>: >> >> > Oh, it says "built by maven" down in the corner. How much work is it >> > to go from forrest pages to maven2 stuff? Is there a translator we >> > can use? >> > >> > On 2/11/07, Achim Hügen <[EMAIL PROTECTED]> wrote: >> >> No, the current web site was built with ant. >> >> We must create the poms manually. I don't know how it was done the >> last >> >> time. >> >> >> >> Achim >> >> >> >> Am Sun, 11 Feb 2007 14:06:57 +0100 schrieb James Carman >> >> <[EMAIL PROTECTED]>: >> >> >> >> > I don't understand. We have the website built with Maven right >> now. >> >> > Where did that come from? Can't we release from that branch? The >> >> > users would like a POM out there in the maven repos that has >> >> > dependencies and everything. Our ant-based build won't create that >> >> > for them. >> >> > >> >> > >> >> > On 2/10/07, James Carman <[EMAIL PROTECTED]> wrote: >> >> >> Ahhh, cool. Okay, we'll do that, then. >> >> >> >> >> >> On 2/10/07, Achim Hügen <[EMAIL PROTECTED]> wrote: >> >> >> > We should make a 1.1.2 release from the branch. >> >> >> > >> >> >> > The trunk is not releasable at all in the moment, because >> >> >> > the conversion to maven 2 is incomplete. >> >> >> > The documentation has not been converted completely from >> forrest to >> >> >> xdoc >> >> >> > and the infrastructure for building a complete site >> >> >> > out of the modules is missing. >> >> >> > Additionally I fear that various changes from 1.1.2 are not >> >> >> > included in the branch (just a feeling). >> >> >> > >> >> >> > Achim >> >> >> > >> >> >> > Am Fri, 09 Feb 2007 23:58:57 +0100 schrieb James Carman >> >> >> > <[EMAIL PROTECTED]>: >> >> >> > >> >> >> > > What about how to do it in Maven2? I think we just call mvn >> >> >> assemble? >> >> >> > > >> >> >> > > >> >> >> > > On 2/9/07, Achim Hügen <[EMAIL PROTECTED]> wrote: >> >> >> > >> Oops, the clover license link was misplaced: >> >> >> > >> >> >> >> >> >> >> (https://svn.apache.org/repos/private/committers/donated-licenses/clover/) >> >> >> >> > >> >> >> >> > >> Achim >> >> >> > >> >> >> >> > >> >> >> >> > >> Achim Hügen schrieb: >> >> >> > >> > That's what I have learned so far regarding this topic: >> >> >> > >> > >> >> >> > >> > - obtain clover license and copy to ANT_HOME/lib >> >> >> > >> > - install forrest 0.7 and set FORREST_HOME >> >> >> > >> > >> >> >> > >> > - Change the version number in project.properties >> >> >> > >> > - update src/documentation/content/xdocs/index.xml >> >> >> > >> > (e.g. "This documentation describes HiveMind 1.1 , >> which is >> >> >> currently >> >> >> > >> > in an late beta state.") >> >> >> > >> > >> >> >> > >> >> >> >> >> >> >> (https://svn.apache.org/repos/private/committers/donated-licenses/clover/) >> >> >> >> > >> > >> >> >> > >> > - run: ant dist >> >> >> > >> > - run: ant dist-build >> >> >> > >> > - sign the release files using GPG ? >> >> >> > >> > - upload website and dist files to people.apache.org >> >> >> > >> > - post announcement? >> >> >> > >> > >> >> >> > >> > Is something missing? >> >> >> > >> > Achim >> >> >> > >> > >> >> >> > >> > James Carman schrieb: >> >> >> > >> >> I like that idea, but we would probably have to make it >> a new >> >> >> release >> >> >> > >> >> (which we need to do anyway), since it would contain >> >> different >> >> >> > >> "bits". >> >> >> > >> >> Maybe we should just cut 1.1.2 and get it out the door (we >> >> >> voted on >> >> >> > >> >> it a long time ago if I remember correctly). I just >> need to >> >> >> get some >> >> >> > >> >> help with it, as I have never cut a release before. >> >> >> > >> >> >> >> >> > >> >> On 1/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> >> >> wrote: >> >> >> > >> >>> +1 >> >> >> > >> >>> >> >> >> > >> >>> I would really love to see this done. >> >> >> > >> >>> >> >> >> > >> >>> Marcus >> >> >> > >> >>> >> >> >> > >> >>> > -----Original Message----- >> >> >> > >> >>> > From: Johan Lindquist [mailto:[EMAIL PROTECTED] >> >> >> > >> >>> > Sent: Tuesday, January 30, 2007 10:15 AM >> >> >> > >> >>> > To: [email protected] >> >> >> > >> >>> > Subject: Version 1.1.1 jars & Ibiblio >> >> >> > >> >>> > >> >> >> > >> >>> > -----BEGIN PGP SIGNED MESSAGE----- >> >> >> > >> >>> > Hash: SHA1 >> >> >> > >> >>> > >> >> >> > >> >>> > Hi all, >> >> >> > >> >>> > >> >> >> > >> >>> > What would the process be of putting up a new set of >> 1.1.1 >> >> >> > >> >>> > jars for hivemind on Ibiblio be? Reason for the >> question >> >> is >> >> >> > >> >>> > no dependencies are declared in the pom and therefore >> >> must be >> >> >> > >> >>> > resolved manually when using Maven 2. >> >> >> > >> >>> > >> >> >> > >> >>> > I can create the Jira if needed. >> >> >> > >> >>> > >> >> >> > >> >>> > Cheers, >> >> >> > >> >>> > >> >> >> > >> >>> > Johan >> >> >> > >> >>> > >> >> >> > >> >>> > - -- >> >> >> > >> >>> > you too? >> >> >> > >> >>> > -----BEGIN PGP SIGNATURE----- >> >> >> > >> >>> > Version: GnuPG v1.4.6 (GNU/Linux) >> >> >> > >> >>> > Comment: Using GnuPG with Mozilla - >> >> >> http://enigmail.mozdev.org >> >> >> > >> >>> > >> >> >> > >> >>> > >> >> >> iD8DBQFFvwx41Tv8wj7aQ34RAk/nAJ0d9uFu+EY9FliMkyZUUBBuj3ZtZgCfbcsM >> >> >> > >> >>> > eqOegaaGmwqhWBuAF5lYopg= >> >> >> > >> >>> > =qHNL >> >> >> > >> >>> > -----END PGP SIGNATURE----- >> >> >> > >> >>> > >> >> >> > >> >>> >> >> >> > >> >>> >> >> >> > >> >> >> >> >> > >> > >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >
