I created MNG-5397 Jira issue for Use SLF4J for logging, with a classical
comment to link to svn revision.
I just added a link to equivalent git commit, now we're using git.
One thing I used to do with svn in such a case is changing svn:log to add Jira
issue reference to the revision commit
You can't. Once a commit has been pushed there's no change that can be done.
In practice, if you want the 2-way reference, you need to add the
jira-reference to the commit up-front with the classical [MNG-5379]
prefix in the message.
Kristia
2012/12/2 Hervé BOUTEMY herve.bout...@free.fr:
I
Hello,
you could use git notes http://git-scm.com/2010/08/25/notes.html for this.
Regards Mirko
--
Sent from my mobile
On Dec 2, 2012 9:42 AM, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:
You can't. Once a commit has been pushed there's no change that can be
done.
In practice, if
yes, that would do the job: great!
But the article explains lots of problems to effectively use this on a shared
repository: do you know if it's ok with actual git version (1.7.*) and Apache
setup?
(notice: I'm using git through my IDE which doesn't tell anything about notes)
Regards,
Hervé
Downloads from central in the last 12 months:
Logback: 1,136,846
Log4J2: 6,748
Do you have the number for all log4j artifacts? log4j2 just got released but is
a native successor of log4j1.
LieGrue,
strub
From: Jason van Zyl ja...@tesla.io
To: Maven
Hervé,
I have not used this yet. However it seems mostly merging would be a
problem. Just annotating commits in the appropriate Jira/Ticket namespace
will probably run seldomly into this situation.
Normally I would put the ticket into the summary line as well.
Regards Mirko
--
Sent from my
Some time ago, I modernized the surefire IT's using a builder on top
of Verifier. I think they are much simpler and more concise than they
used to be.
Typical samples can be seen here;
I can run a query. I would be fine using Log4J1. Well used in the field and I
doubt there would be any surprises. No one suggested using it, but I think
that's a more sensible choice than a project no one uses. I don't see much
value in being on the bleeding edge of a logging project.
On Dec
On Dec 2, 2012, at 5:48 AM, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:
Some time ago, I modernized the surefire IT's using a builder on top
of Verifier. I think they are much simpler and more concise than they
used to be.
Typical samples can be seen here;
2012/12/2 Jason van Zyl ja...@tesla.io:
I think the way the ITs used to work was better. Where a single project was
entirely self-contained and there was a declarative file that described the
desired outputs.
Well I think this is one of the design goals I *almost* managed to
achieve when I
I think trying anything new that's easier is good. The only thing we need to be
cognizant of is making sure the body of ITs work to test all the versions of
Maven.
But I think project self-containment is a good goal. I just liked the setup
where there was a project and a file that described
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue how
to figure out why.
/Anders
I'm going to start the preparation for rolling the release.
Thanks,
Jason
--
Jason van Zyl
Founder CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
-
Our achievements
Hi Anders
It looks like ASF Jenkins has been upgraded to 1.492, which should help
us with the unwanted constant rebuilds in some of our other projects.
Which jobs are hung?
I can only see one: core-integration-testing-maven-3-embedded
On 2012-12-02 20:12, Anders Hammar wrote:
The
Can we have a thread dump of that?
K
Den 2. des. 2012 kl. 21:39 skrev Dennis Lundberg denn...@apache.org:
Hi Anders
It looks like ASF Jenkins has been upgraded to 1.492, which should help
us with the unwanted constant rebuilds in some of our other projects.
Which jobs are hung?
I can
On Sat, Dec 1, 2012 at 7:08 PM, Jason van Zyl ja...@tesla.io wrote:
On Dec 1, 2012, at 1:42 AM, Arnaud Héritier aherit...@gmail.com wrote:
Ok. Yes that's sure it has to be discussed. That's why I reopened the
subject.
About the implementation :
* as a user I have really no preference, I
I agree but sincerely I'm sure that less than 0,01% of our users will
customize their logs.
On Sat, Dec 1, 2012 at 9:27 PM, Anders Hammar and...@hammar.net wrote:
In any case doing a choice nowadays for 3.1.0 won't prevent us to change
it
in the future. I really hope that the ability to
It's the core-integration-testing-maven-3 job that hangs. I've aborted it a
few times hoping it would fix itself somehow. No luck though.
Also, there's some problems with Jenkins not finding git installation on
some nodes. But that's a different topic, but possibly related to the
upgrade?
Thanks a lot to have pushed it.
I tested it with success
I like it, at least something that will improve the user experience soon.
Note : Like Olivier's branch the default logging setup has an issue because
the default color is set to black (or white) which are backgrounds colors
commonly used.
+1
I don't think we'll have another minor release before the end of the year.
For sure it won't be included in a bug fix release.
We already release a minor release without (or so few) end-user value, we
won't start to add new feature in a bug fix release :-)
Arnaud
On Sat, Dec 1, 2012 at 7:33
On 2012-12-02 22:01, Anders Hammar wrote:
It's the core-integration-testing-maven-3 job that hangs. I've aborted it a
few times hoping it would fix itself somehow. No luck though.
Also, there's some problems with Jenkins not finding git installation on
some nodes. But that's a different
The Windows node is one, but I believe I saw the same problem on some other
node as well.
/Anders (mobile)
Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org:
On 2012-12-02 22:01, Anders Hammar wrote:
It's the core-integration-testing-maven-3 job that hangs. I've aborted
it a
The Windows node is one, but I believe I saw the same problem on some
other node as well.
The same problem on the solaris node as well.
/Anders
/Anders (mobile)
Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org:
On 2012-12-02 22:01, Anders Hammar wrote:
It's the
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue how
to figure out why.
I've disabled the core-integration-testing-maven-3 job for now. We're
just blocking other build jobs as it is now.
As I pointed
24 matches
Mail list logo
