I have put together a visual of the system, some information on using
m2eclipse to debug the entire platform, and the use of Hudson for
testing the resulting system.
http://docs.codehaus.org/display/MAVEN/Developing+Maven+2.1
The guide included there (put together by Igor) should allow anyon
Milos, can you help me copy the Mevenide job from deadlock?
I can see from the output here what the CLI looks like but there are a
couple options I don't really understand:
http://deadlock.netbeans.org/hudson/job/mevenide/423/console
On 22-Jun-08, at 3:13 PM, Milos Kleint wrote:
On Sun, Jun
On 05/07/2008, at 1:44 AM, Jason van Zyl wrote:
Are you dropping new files into the local repository or integrating
this as part of the metadata? Do these files only work locally?
The current impl, from what I've seen of it, drops properties files
into the local repository only, and doesn'
Thanks Benjamin, I agree with this.
On 05/07/2008, at 7:12 PM, Benjamin Bentmann wrote:
Brett Porter wrote:
I disagree on JIRA issues - for making release notes and keeping
track I think it's best to have an issue whenever possible.
Having detailed release notes is surely a good point sinc
Hi,
2008/7/5, Benjamin Bentmann <[EMAIL PROTECTED]>:
> Vincent Siveton wrote:
>
>
> >
> http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/developers/conventions
> >
>
> code.apt
> * <>: Document public interfaces well, i.e. all non-trivial
> public and protected functions should incl
Vincent Siveton wrote:
So, I am in favour to use unicode to all resources bundles. What others think?
To repeat my argument from MSITE-287: I believe using ASCII only with
Unicode escapes is simply the most robust choice for an international
dev community. For instance, somebody who accident
Hi,
2008/7/5, Brett Porter <[EMAIL PROTECTED]>:
> Just a couple of comments...
>
> code.apt:
> ~~ * Using SVN properties like \$Id: \$ => Is it a wanted goal for all
> files like java or apt?
> I think this is helpful, though maybe optional. I don't really think it's
We can start to include it
Hi Dennis,
2008/7/5, Dennis Lundberg <[EMAIL PROTECTED]>:
> I never really closed out the discussion we had earlier, regarding how to
> encode properties files. Now we have an example of a change of encoding of
> properties, so I want to take the opportunity to finish that discussion.
> Hopefully
I never really closed out the discussion we had earlier, regarding how
to encode properties files. Now we have an example of a change of
encoding of properties, so I want to take the opportunity to finish that
discussion. Hopefully we can reach consensus this time :-) When we do
I'll put into o
Thanks to everybody who came up with idea for improvement!
I'm going to start implementing this now. To start out in an agile way,
I will put this into the Maven site. That way we can easily change
things and just push out a new site.
When we have settled in on what we want I'll start moving
Vincent Siveton wrote:
http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/developers/conventions
code.apt
* <>: Document public interfaces well, i.e. all
non-trivial public and protected functions should include Javadoc that
indicates what it does.
I would like to point out ther
Brett Porter wrote:
I disagree on JIRA issues - for making release notes and keeping track I
think it's best to have an issue whenever possible.
Having detailed release notes is surely a good point since it's the
easiest way for users to rate a new release in terms of benefits/risks
when upd
12 matches
Mail list logo
