Couldn't we setup a custom profile for QA checks (pmd, checkstyle, clirr
...) that we activate in a separate project in the CI server ?
It's what I begin to do at work. The advantage is to keep the integration
build fast and we can have a look at the QA builds to improve them.
Arnaud
On Mon, Jul
Hi,
I agree too.
IMHO we don't have to block a release because they are checkstyle
errors : releasing something must not be nightmare (we are here to
help users and fix issues).
Ok except for missing license headers in source files.
We will find some exceptions which will prevent automatisation of
On 21/07/2008, at 4:56 PM, Arnaud HERITIER wrote:
Couldn't we setup a custom profile for QA checks (pmd, checkstyle,
clirr
...) that we activate in a separate project in the CI server ?
It's what I begin to do at work. The advantage is to keep the
integration
build fast and we can have a
I'm having problems getting this set up to work from behind a http proxy.
I've set up subversion's servers file correctly
Here's what I get from the bootstrap:
started
ERROR: svn: No credential to try. Authentication failed
org.tmatesoft.svn.core.SVNCancelException: svn: No credential to try.
It is maybe a stupid question, but I think it's still using ant 1.6.5. I
know that switching to 1.7 (I did locally) issue a weird path with space
problem on Windows. Ant 1.7.1 is out but I don't know if the problem is
fixed and I am lazy to search in BugSuperZilla.
To me, the biggest limitation
That seems better thanks. We really need some unit tests for this
dependency reduced pom logic. It looks like ShadeMojoTest doesn't
actually test ShadeMojo but duplicates DefaultShaderTest.
Do you want me to retrospectively raise an issue for this?
Cheers,
Mark
2008/7/18 Daniel Kulp [EMAIL
http://jira.codehaus.org/browse/MANTRUN-68
is scheduled for version 1.3.
I think Carlos wanted to get a version of the plugin out with all the
fixes, before upgrading Ant.
Yes, the spaces in a Windows path was fixed in 1.7.1.
Stephane Nicoll wrote:
It is maybe a stupid question, but I think
Olivier Lamy wrote:
Hi,
I agree too.
IMHO we don't have to block a release because they are checkstyle
errors : releasing something must not be nightmare (we are here to
help users and fix issues).
Right, I totally agree with that. I just wrote down things that are
worth looking at during
I may have missed something - are these values getting populated into
project.getOriginalModel(), or is that method in some other way
unsuitable?
originalModel already has versions populated (essentially it's _not_ the
original model). Even if it really was the original model, I still need
On 20-Jul-08, at 11:26 AM, Vincent Siveton wrote:
Hi,
2008/7/19, Jason van Zyl [EMAIL PROTECTED]:
This is great as long as it does not become bureaucratic and
onerous for
everyone to do a release.
Totally agree with you: it could be time consuming for the release
manager and for the
I'll start looking at this when I swap out Maven SCM to do everything
for us.
On 21-Jul-08, at 4:16 AM, Stephen Connolly wrote:
I'm having problems getting this set up to work from behind a http
proxy.
I've set up subversion's servers file correctly
Here's what I get from the bootstrap:
Hi Folks,
I manage to make 3 mojos to instrument, run, gather metadata and report emma
coverage.
Run is done by surefire on test phase.
Question, how do I tell maven to run one mojo before test phase and after
test phase run metadata and then report?
VELO
On Thu, Jul 17, 2008 at 12:00 PM,
Makes sense.
Thanks for the info.
S.
On Mon, Jul 21, 2008 at 11:54 AM, Dennis Lundberg [EMAIL PROTECTED]
wrote:
http://jira.codehaus.org/browse/MANTRUN-68
is scheduled for version 1.3.
I think Carlos wanted to get a version of the plugin out with all the
fixes, before upgrading Ant.
Yes,
+1
On Sun, Jul 20, 2008 at 4:16 PM, Carlos Sanchez [EMAIL PROTECTED] wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
Hi everyone,
I'd like to check and see how close people think we're getting to a
release of the maven-shade-plugin. I understand there are some
outstanding issues related to excludes, but at this point the pending
1.2 release is blocking the maven 2.0.10 release.
Can we talk about specific
Hi John,
The thread regarding excessive excludes is here:
http://www.nabble.com/Shade-plugin%27s-over-zealous-exclusions-tt18462091.html
The latest is that Daniel made some changes which appeared to fix my
problems, although I'd like to see some unit tests for the dependency
reduced pom logic.
+1
Carlos Sanchez wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
+1
Carlos Sanchez wrote:
Release was rolledback and performed again, site and staging repo
updated, please restart the voting process
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125styleName=Htmlversion=12210
Staging repo:
http://people.apache.org/~carlos/staging-repo
I think it's OK to do a release of it now, especially if it's blocking
2.0.10.
I've tested it with CXF and it looks OK there. No regressions in the
dep-reduced pom. It would be NICE if the OpenEJB folks could do a
quick test with their code, but I wouldn't hold it up for that to
I'm also investigating other ways we might be able to work around the
2.0.10 release without requiring the new shade-plugin release, fwiw.
It might be a good idea to make sure the tests are in place on this
release of the shade plugin; I think we can put some temporary code into
maven for
Does anyone consider the maven-shade-plugin to be one that should get a
standard version in the super pom?
Paul
On Mon, Jul 21, 2008 at 11:53 AM, John Casey [EMAIL PROTECTED] wrote:
I'm also investigating other ways we might be able to work around the
2.0.10 release without requiring the new
On Jul 18, 2008, at 12:28 PM, Jesse McConnell wrote:
djencks,
I am not sure what the client side of a jaspi api would look like, can
you give an example of what it would be doing?
The basic idea is that, in a client, you'd be calling a authentication
context before sending the message to
Why is this particular API of interest?
Trying to the container security inside G to grab plugins from a
remote repository?
On 21-Jul-08, at 2:39 PM, David Jencks wrote:
On Jul 18, 2008, at 12:28 PM, Jesse McConnell wrote:
djencks,
I am not sure what the client side of a jaspi api
On Jul 21, 2008, at 8:55 AM, Daniel Kulp wrote:
I think it's OK to do a release of it now, especially if it's
blocking 2.0.10.
I've tested it with CXF and it looks OK there. No regressions in
the dep-reduced pom. It would be NICE if the OpenEJB folks could
do a quick test with
+1
--
Olivier
2008/7/18 Vincent Siveton [EMAIL PROTECTED]:
Hi,
Important note: this release changes the groupId for the artifacts:
http://maven.markmail.org/message/s6l35jjjyz242lfa?q=plugin+testing+reorganization+from:%22Vincent+Siveton%22page=1
We solved several issues:
I've gone over the docs, to make sure they are OK. I also went through a
couple of the other pre release checks.
While doing this I found an error in the Clirr report that might be
worth having a look at:
In method 'public boolean
updateExcludesInDeps(org.apache.maven.project.MavenProject,
Method should probably be private or package protected. Thus, this
would be irrelevant.
Dan
On Jul 21, 2008, at 4:03 PM, Dennis Lundberg wrote:
I've gone over the docs, to make sure they are OK. I also went
through a couple of the other pre release checks.
While doing this I found
I'm getting a java.lang.NoClassDefFoundError when running a test and
yet, the code compiles fine. Any ideas as to what's going on? The
exact same code compiles and test fine on another box which has the
same mvn and java version.
There are no differences between 'mvn
Hi,
We are having Multi module maven project in our application. One of the modules
in our application is hibernate based. When I try to import this project from
the SVN repository META-INF directory is auto created in hibernate module. We
have no plans of having any specific information in
29 matches
Mail list logo
