Perso (not a maven dev one).
I prefer the sync solution.
Because if not, I need to add a new repository in my setting.xml
(already have corporate release one , corporate snapshots one,
snapshots.codehaus , cvs.apache one).
If i try mvn -U this will cause a very long build.
Is there any way to
Thanks Brett,
The checkstyle individual mojo based approach seems more flexible.
Having thought about my requirement some more i have a further question.
Bascially what i want to do is create a 'build summary/status' jetspeed Rss
portlet to give headline items for the last (continuum) build.
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one who
closed it (even if it's a Won't fix or duplicated status).
It's easier to see who closed it
Hi all,
We are ready to release a new version of the PMD plugin.
All bugs issues are solved and there's only one enhancement opened in Jira.
Changes in this version include:
New Features:
o New property maven.pmd.targetjdk to define the target JDK. Fixes
MPPMD-19. Thanks to Wim
Probably being paranoid, but is there anything I have left to fix here
Brett? I should probably go checkout JIRA to be sure.
On 3/17/06, Brett Porter [EMAIL PROTECTED] wrote:
Just as a further note - if anyone is able to test, or help fix the bugs
that have been so far under MSUREFIRE, that'd
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one who
closed it (even if it's a Won't fix or duplicated status).
It's
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:31
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects (particularly in m1) a
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:31
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:50
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:50
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Vincent Massol wrote:
-Original Message-
From: Alan D. Cabrera
SNIP
Actually I believe we should simply configure jira to not allow an issue
to
be closed without an assignee. The same should apply for not specifying a
fix for field, etc. Those fields should be defined as mandatory. Not
sure
how to do this with jira but I supposed it's possible.
I
As far as I'm concerned, setting the assignee to yourself when you close
it has been accepted practice for some time (but we don't need to go
back and change all the old ones).
That way, if it is reopened, the person that closed it can deal with it.
- Brett
Arnaud HERITIER wrote:
Hi guys,
There are those two API changes that I haven't updated properly or verified:
http://jira.codehaus.org/browse/MSUREFIRE-67 (getExtraOutput thing)
http://jira.codehaus.org/browse/MSUREFIRE-69 (test-output directory)
So you could certainly help with them, and I'm sure the others if you
are
I agree. I don't want that we update all closed issues up until now, but
only that we take care to define the assignee from now.
Arnaud
On 3/18/06, Brett Porter [EMAIL PROTECTED] wrote:
As far as I'm concerned, setting the assignee to yourself when you close
it has been accepted practice for
Hi,
Could anyone explain what version is really correct. I took a look at
PropertiesConverter from
trunk/plexus-containers/plexus-container-default
(http://tinyurl.com/r6rsw) and it seems systemProperties should be
accompanied with property subelements. I've just had to change it in
Geronimo
Honestly, apart from statistical purposes, I don't see the point in
having closed issues assigned to somebody at all. Would all the people
who have moved on to m2 take up an old m1 issue if it gets reopened
today? What about people who have left the project? IMO it's the project
16 matches
Mail list logo
