I should correct myself - xdoc will support the link to subversion as
well - i re-read the doxia macro doc and it should be ok.

However, that leaves the links - I will go ahead and replace all
entities for the moment and think about a fix- it may be that the xdoc
plugin needs a patch (to support entities) or that there is some other
way around.  In any case, a 1.2.1 release is probably more important for
the moment?

I'll keep you posted.

Cheers,

Johan

James Carman wrote:
> I would rather make the jump to doing things the "maven way" if at all
> possible.  I'm not married to the current build process if there's an
> alternative.
> 
> 
> On 2/12/07, Johan Lindquist <[EMAIL PROTECTED]> wrote:
> Been looking into some of the work required and it looks like xdoc for
> Maven 2.0 is quite far away from supporting entities at the moment ...
> 
> So, the question is - i can simply replace all entities with the
> corresponding values, but we loose some of the link management currently
> in the build - does this matter at all?
> 
> Also, i think the WIKI source inclusion that was mentioned on this list
> previously (for adding links to examples from the documentation) is
> making its way into the APT format - you can link into subversion URLs
> quite nicely ... Is APT format an absolute no or would this option work?
> 
> Cheers,
> 
> Johan
> 
> Achim Hügen wrote:
>> That would be a great help!
>> I already created most site.xml files for HiveMind 2 which could be
> used
>> for 1.2 too:
>> http://svn.apache.org/viewvc?view=rev&revision=504916
>> http://svn.apache.org/viewvc?view=rev&revision=504914
> 
>> The site generation should use the maven-skin from the hivemind-site
>> project.
> 
>> <skin>
>>    <groupId>org.apache.hivemind</groupId>
>>    <artifactId>maven-skin</artifactId>
>>    <version>2.0.0</version>
>> </skin>
> 
>> The skin is not available in the maven repository, you must check
>> out this project:
>> http://svn.apache.org/repos/asf/hivemind/hivemind-site/
>> and run "maven install" in the maven-skin folder.
> 
>> Everything which is under ...src/documentation/content/xdocs/ must be
>> converted and moved to ...src/site/xdoc.
>> Some conversion work has been done already for the framework module:
> 
> http://svn.apache.org/repos/asf/hivemind/hivemind1/trunk/framework/src/site/xdoc/
> 
> 
> 
>> Achim
> 
>> Johan Lindquist schrieb:
>> So, from what I can understand from this thread, the docs work just not
>> all the links etc that are processed by Forrest?
> 
>> If no one has started looking at converting this, I can do so today if
>> you like.  I think that having the 1.1.2 branch work correctly with
>> Maven 2 would be a great step forward until 2.0 is ready.
> 
>> Cheers,
> 
>> Johan
> 
>> James Carman wrote:
> 
>>>>> 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
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>> 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?

Reply via email to