I just wanted to know if the ant, ivy and forest stuffs (build.xml, ivy.xml,
etc.) are still in use. Are these files doing something that maven can't?

--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com

On Tue, 2011-01-11 at 09:39 +0100, Chapuis Bertil wrote:
> I just wanted to know if the ant, ivy and forest stuffs (build.xml, ivy.xml,
> etc.) are still in use. Are these files doing something that maven can't?

Hmm, the ant stuff have been to "easily" start a droid and generate the
documentation (based on forrest). The ivy stuff is obsolete due to the
dep mgt. of maven. Regarding the documentation based on Forrest, I
personally prefer forrest over the maven based, but that is personal
preference. Maybe we should have a vote whether we want to keep forrest
or switch to Maven.

salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/

I'm not familiar with Ivy.  I didn't like forrest in my limited encounters with
it.  I'd be for sticking with just maven.

Otis
----
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/

----- Original Message ----
> From: Chapuis Bertil <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Tue, January 11, 2011 3:39:01 AM
> Subject: DROIDS-107 / Module reorganization and trunk cleaning
>
> I just wanted to know if the ant, ivy and forest stuffs (build.xml,  ivy.xml,
> etc.) are still in use. Are these files doing something that maven  can't?
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>

It would be great, when all tasks could be achieved with one tool.

+1 for maven
On Wed, Jan 12, 2011 at 8:17 PM, Otis Gospodnetic
<[EMAIL PROTECTED]>wrote:

> I'm not familiar with Ivy.  I didn't like forrest in my limited encounters
> with
> it.  I'd be for sticking with just maven.
>
> Otis
> ----
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> ----- Original Message ----
> > From: Chapuis Bertil <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Sent: Tue, January 11, 2011 3:39:01 AM
> > Subject: DROIDS-107 / Module reorganization and trunk cleaning
> >
> > I just wanted to know if the ant, ivy and forest stuffs (build.xml,
>  ivy.xml,
> > etc.) are still in use. Are these files doing something that maven
>  can't?
> >
> > --
> > Bertil Chapuis
> > Agimem Sàrl
> > http://www.agimem.com
> >
>

I like Apache Forrest but I'm agree with tobr, only one tool.

+1 for maven

2011/1/13 tobr dev <[EMAIL PROTECTED]>

> It would be great, when all tasks could be achieved with one tool.
>
> +1 for maven
>
>
> On Wed, Jan 12, 2011 at 8:17 PM, Otis Gospodnetic
> <[EMAIL PROTECTED]>wrote:
>
> > I'm not familiar with Ivy.  I didn't like forrest in my limited
> encounters
> > with
> > it.  I'd be for sticking with just maven.
> >
> > Otis
> > ----
> > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > Lucene ecosystem search :: http://search-lucene.com/
> >
> >
> >
> > ----- Original Message ----
> > > From: Chapuis Bertil <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > Sent: Tue, January 11, 2011 3:39:01 AM
> > > Subject: DROIDS-107 / Module reorganization and trunk cleaning
> > >
> > > I just wanted to know if the ant, ivy and forest stuffs (build.xml,
> >  ivy.xml,
> > > etc.) are still in use. Are these files doing something that maven
> >  can't?
> > >
> > > --
> > > Bertil Chapuis
> > > Agimem Sàrl
> > > http://www.agimem.com
> > >
> >
>

+1 for maven.

Since I never used forrest, can someone please describe what forrest was
doing for the documentation? Does the maven site plugin do the same?
On 13 January 2011 16:12, Javier Puerto <[EMAIL PROTECTED]> wrote:

> I like Apache Forrest but I'm agree with tobr, only one tool.
>
> +1 for maven
>
> 2011/1/13 tobr dev <[EMAIL PROTECTED]>
>
> > It would be great, when all tasks could be achieved with one tool.
> >
> > +1 for maven
> >
> >
> > On Wed, Jan 12, 2011 at 8:17 PM, Otis Gospodnetic
> > <[EMAIL PROTECTED]>wrote:
> >
> > > I'm not familiar with Ivy.  I didn't like forrest in my limited
> > encounters
> > > with
> > > it.  I'd be for sticking with just maven.
> > >
> > > Otis
> > > ----
> > > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > > Lucene ecosystem search :: http://search-lucene.com/
> > >
> > >
> > >
> > > ----- Original Message ----
> > > > From: Chapuis Bertil <[EMAIL PROTECTED]>
> > > > To: [EMAIL PROTECTED]
> > > > Sent: Tue, January 11, 2011 3:39:01 AM
> > > > Subject: DROIDS-107 / Module reorganization and trunk cleaning
> > > >
> > > > I just wanted to know if the ant, ivy and forest stuffs (build.xml,
> > >  ivy.xml,
> > > > etc.) are still in use. Are these files doing something that maven
> > >  can't?
> > > >
> > > > --
> > > > Bertil Chapuis
> > > > Agimem Sàrl
> > > > http://www.agimem.com
> > > >
> > >
> >
>

--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com

On Mon, 2011-01-17 at 16:43 +0100, Chapuis Bertil wrote:
> +1 for maven.
>
> Since I never used forrest, can someone please describe what forrest was
> doing for the documentation? Does the maven site plugin do the same?

Not really, however for our usecase maven should be enough. In the end
we only want our documentation as html.

Forrest is a publishing framework that works like following:
- input plugin (different formats and markups (html, xml, xdoc,...) TO
forrest internal format)
- internal plugin (extend core forrest functionality)
- output to different format (from the internal format we create
different outputs like pdf, html, txt, ...)

We are using xdocs for the documentation that we have ATM
http://svn.apache.org/repos/asf/incubator/droids/trunk/src/documentation/content/xdocs/

I am not the maven doc expert but would maven accept xdocs as input
format or does it need it in a special format?

salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/

I just had a look on the maven site plugin page. It seems that xdoc can be
used to generate documentation.
On 20 January 2011 12:00, Thorsten Scherler <[EMAIL PROTECTED]> wrote:

> On Mon, 2011-01-17 at 16:43 +0100, Chapuis Bertil wrote:
> > +1 for maven.
> >
> > Since I never used forrest, can someone please describe what forrest was
> > doing for the documentation? Does the maven site plugin do the same?
>
> Not really, however for our usecase maven should be enough. In the end
> we only want our documentation as html.
>
> Forrest is a publishing framework that works like following:
> - input plugin (different formats and markups (html, xml, xdoc,...) TO
> forrest internal format)
> - internal plugin (extend core forrest functionality)
> - output to different format (from the internal format we create
> different outputs like pdf, html, txt, ...)
>
> We are using xdocs for the documentation that we have ATM
>
> http://svn.apache.org/repos/asf/incubator/droids/trunk/src/documentation/content/xdocs/
>
> I am not the maven doc expert but would maven accept xdocs as input
> format or does it need it in a special format?
>
> salu2
> --
> Thorsten Scherler <thorsten.at.apache.org>
> codeBusters S.L. - web based systems
> <consulting, training and solutions>
> http://www.codebusters.es/
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com

Sorry, I just forgot to add the link :-).

http://maven.apache.org/guides/mini/guide-site.html

On 20 January 2011 23:02, Chapuis Bertil <[EMAIL PROTECTED]> wrote:

> I just had a look on the maven site plugin page. It seems that xdoc can be
> used to generate documentation.
>
>
> On 20 January 2011 12:00, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
>
>> On Mon, 2011-01-17 at 16:43 +0100, Chapuis Bertil wrote:
>> > +1 for maven.
>> >
>> > Since I never used forrest, can someone please describe what forrest was
>> > doing for the documentation? Does the maven site plugin do the same?
>>
>> Not really, however for our usecase maven should be enough. In the end
>> we only want our documentation as html.
>>
>> Forrest is a publishing framework that works like following:
>> - input plugin (different formats and markups (html, xml, xdoc,...) TO
>> forrest internal format)
>> - internal plugin (extend core forrest functionality)
>> - output to different format (from the internal format we create
>> different outputs like pdf, html, txt, ...)
>>
>> We are using xdocs for the documentation that we have ATM
>>
>> http://svn.apache.org/repos/asf/incubator/droids/trunk/src/documentation/content/xdocs/
>>
>> I am not the maven doc expert but would maven accept xdocs as input
>> format or does it need it in a special format?
>>
>> salu2
>> --
>> Thorsten Scherler <thorsten.at.apache.org>
>> codeBusters S.L. - web based systems
>> <consulting, training and solutions>
>> http://www.codebusters.es/
>>
>>
>
>
> --
> Bertil Chapuis
> Agimem Sàrl
> http://www.agimem.com
>
>
--
Bertil Chapuis
Agimem Sàrl
http://www.agimem.com