Re: Best combination

[Greg Morgan <dr...@cox.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

raghu121 wrote:
> Hi,
> 
> I want to start using maven, jira, confluence and other OSS products in my
> OSS project which I intend to revive soon. Had not been able to do much with
> my projet due to too much office work.
> 
> My OSS project is  under LGL on sourceforge.
> I want to make the most effective use of all these- MAVEN, JIRA, CONFLUENCE,
> etc in my project website hosted on SF. I also would like to use maven as a
> build tool for the project.
> 
> The idea is to not only work on my project but also keep myself efefctively
> up to date on the happening technologies.
> 
> 1. Please advice me the most efefctive combination of the tools to use.
> 2. Which of all these can I host from my SF website
> 
> Thanks.
> 
> 
> R

Maven has wagon providers, http://maven.apache.org/wagon/, to move your
files around for any project hosting site that you want to use.  You
could go with Codehaus as Kalle recommended or SF as your project is
already there.

Effective combination in my experience sometimes becomes a matter of
taste and available time.  I know that dbunit.sf.net is hosted on SF and
uses Maven2.  However, using their project may not be a good SF how to
because they started as Maven 1 and converted to Maven 2.  It doesn't
look like they made a pure switch to Maven 2.  There still may be some
Maven 1 artifacts in what they are doing. There's nothing wrong with
their successful project but they struggle with refactoring and time
limits just like other projects do.  Also note that dbunit is using the
concepts from all the tools that you listed but not the same tool by
brand name!  Watch your time limits on the learning curve for tools
verses reviving the code in your project.

Again from experience, don't run your own wiki like dbunit is trying to
do http://www.dbunit.org/cgi-bin/wiki.pl .  Let the professionals run
the wiki systems so that you can focus on the content of the application
that you are developing.  If you do run a wiki, then consider using SFs
new wiki system or Codehaus Jira wiki, then make it a closed wiki so
that you avoid the wiki spam maintenance.  Also consider using the
content management system that Maven provides.  From your post, you
don't have time to manage wiki spam.

An alternative to a wiki is Maven's apt documents. I've written pages
and pages of wiki documents.  I can make just as effective documents in
the Maven apt format as I can a wiki. I like that the code and the
documentation are all together in one place.  Being the Oracle database
weenie that I am at work, I even generate apt formatted documents from
sqlplus queries!  Apt rocks.

The idea for your project is that you will want to create a parent pom
project, a mainline project for your application, a site project, and an
externals directory to pull all the others to a local work station via
subversion.  A separate site project allows you to have people
contribute wiki like documents but separated from your code in
subversion.  You can then provide authorization to protect the one group
from the other until trust has been built up in the project community.
I'd recommend this Maven configuration for any hosting provider that you
select.

Hehe  My recommendation comes from mentoring the ideas from here
http://svn.apache.org/viewvc/maven/

Regards,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHKYrDxyxe5L6mr7IRAsXWAKCcgTwIM615CYpFqbevzqGEstDCjwCghP7T
O1aSgtFBL4pyp6bnxErvYSo=
=EWFk
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org