Ah good, I didn't know this! This is something interesting to know indeed.
Thanks for the precision, i'll go have a look
Jer
On Mon, 07 Nov 2005 14:26:06 +0100, Jeff Jensen
<[EMAIL PROTECTED]> wrote:
Regarding the wiki/others helping, do you know that the code and docs are
available to you from subversion? When having something to contribute,
you
can get it and patch it. I have done this many times on m1.1, and was an
easy process. The "hardest" part was waiting for a committer to get the
patch into svn. This usually only took up to 2 days, but did take about
2
weeks a couple of times.
-----Original Message-----
From: Jadoulle Jérôme [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 2:28 AM
To: users@maven.apache.org
Subject: [MAVEN 2] Update
/maven.apache.org/guides/introduction/introduction-to-repositories.html
Hello,
I am trying to set-up an in-house remote repository for my company.
We did this already in the past using maven 1.02 (though I wasn't the
guy in
charge) and we now want to move to V2.0.
Problem is that documentation about how to do this in a generic fashion
(I
don't want the connection information to be written in each POM.xml
file) is
still referring to Maven 1.0 "build.properties" file... Which doesn't
help
me.
So, I would be grateful to you to have this introduction to repositories
to
be updated to match the V2 and it's Settings.xml file.
In fact, I think it would help a lot of people to have:
- XSD schema sort of reference pages about each XML file users
are
likely to change (settings.xml, pom.xml,...).
- More precise documentation for "basic examples". I personally
think that, in the current state, you rely too much on user's knowledge,
which is, when he starts to use maven for the first, quite limitated.
I am certainly not saying that you are making a bad job, not at all. I
am
just telling that I would have a far better Maven experience if more
precise
documentation was made available to users. Reference pages are very
important, I think.
A last note: I bet that part of your answer will tell that you prefer
focus
on correcting bugs and bring more functionality to the community and that
you are already doing all what you can concerning the documentation. And
you'll be right! But did you think about putting documentation in a
wiki or
something, where all willing-to-help users would be able to make the
knowledge base grow and correct documentation errors, imperfections,... ?
Perhaps this would be a very interesting thing to do. What do you think
of
it?
Anyway, thank you very much for at least having read this mail,
Jérôme JADOULLE
**********************************************************************
This email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they are
addressed.
If you have received this email in error please notify the system
manager.
Rijksdienst voor Pensioenen
Office National des Pensions
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
