On 6 June 2010 02:27, Jemos Infra jemos.in...@googlemail.com wrote:
Hi,
Can somebody point me to the Maven 3 branch with Google guice? I
undertsand that Google guice will replace Plexus classworlds, but the
trunk still has Plexus in it. I'd like to have a look at what Maven 3
will look like
Stuart, a couple of things re the below:
1) The first URL downloads spice-inject and the whole Guice. Question:
was Guice extended for this compatibility layer? What actually is the
compatibility layer? Is it just spice or the whole lot? If it's just
spice, could we avoid from build the whole
The Maven team is pleased to announce the release of the Maven JXR and
Maven JXR Plugin, version 2.2.
The JXR Plugin produces a cross-reference of the project's sources. The
generated reports make it easier for the user to reference or find
specific lines of code. It is also handy when used with
On 6 June 2010 17:22, Jemos Infra jemos.in...@googlemail.com wrote:
Stuart, a couple of things re the below:
1) The first URL downloads spice-inject and the whole Guice. Question:
was Guice extended for this compatibility layer? What actually is the
compatibility layer? Is it just spice or
Stuart, thank you for your email. Do you think that future emails
related to the process below (mainly if I found any difficulties in
building the whole thing plus observations, suggestions, etc) should be
addressed to the dev mailing list?
M.
On Sun, 2010-06-06 at 18:11 +0800, Stuart McCulloch
On 6 June 2010 19:27, Jemos Infra jemos.in...@googlemail.com wrote:
Stuart, thank you for your email. Do you think that future emails
related to the process below (mainly if I found any difficulties in
building the whole thing plus observations, suggestions, etc) should be
addressed to the
Hi Stuart,
Any objections If I create a branch in asf svn repo ?
2010/6/6 Stuart McCulloch mccu...@gmail.com:
On 6 June 2010 19:27, Jemos Infra jemos.in...@googlemail.com wrote:
Stuart, thank you for your email. Do you think that future emails
related to the process below (mainly if I found
On 6 June 2010 22:16, Olivier Lamy ol...@apache.org wrote:
Hi Stuart,
Any objections If I create a branch in asf svn repo ?
sure, fine with me
2010/6/6 Stuart McCulloch mccu...@gmail.com:
On 6 June 2010 19:27, Jemos Infra jemos.in...@googlemail.com wrote:
Stuart, thank you for your
Nexus can utilize anything contained in the repository. Whether a piece of
metadata exists alongside the artifact or within it, a Nexus plugin could be
created to process the information. So you don't need to change the way Grails
plugins are packaged in order to extract the metadata and make
stuff is here :
http://svn.apache.org/repos/asf/maven/maven-3/branches/guice-support/
Thanks !
2010/6/6 Stuart McCulloch mccu...@gmail.com:
On 6 June 2010 22:16, Olivier Lamy ol...@apache.org wrote:
Hi Stuart,
Any objections If I create a branch in asf svn repo ?
sure, fine with me
On Sun, 2010-06-06 at 16:58 +0200, Olivier Lamy wrote:
stuff is here :
http://svn.apache.org/repos/asf/maven/maven-3/branches/guice-support/
Thanks !
Hi Oliver, I take it this branch contains everything that's needed,
right? I mean Maven-3, the Plexus-Guice adapter and all required
yup.
It build fine and it works for some builds I have tested since I have
installed it (at least on my laptop :-) ) .
2010/6/6 Jemos Infra jemos.in...@googlemail.com:
On Sun, 2010-06-06 at 16:58 +0200, Olivier Lamy wrote:
stuff is here :
Yep, Nexus would be fantastic for this - we're basically trying to
come up with the most efficient mechanism to do the following:
1. A Grails developer releases a plugin. This process first entails
(ideally) Grails uploading it to a Maven repo (i.e. Nexus).
2. Grails (during its
Can we use the CI server to check how this branch supports the IT test
harnesss ? It could make us more confident / help to detect
incompatibilities when switching to Guive will become a concrete option.
Nicolas
2010/6/6 Olivier Lamy ol...@apache.org
yup.
It build fine and it works for some
I have been running this patch on my CI (including m3 IT's) for quite
some time now, and it works really well here. Obviously, the more the
merrier!
But then again, from a user's perspective this change really adds very
little to the excitement. It's supposed to be a transparent change
without
klauer wrote:
The Maven Surefire plugin allows you to explicitly set a single test or
set of tests using wildcard matching:
I'm aware of -Dtest, but that's not what I want.
klauer wrote:
And as for your better command line output, why not just use the
command line
to output the test
I have a maven mantained project with some modules . One module contains one
XML file and one parsing class :Parser.java.
Second module depends on the first module. There is a class that extends the
parsing class in the first module , but maven seems cannot test the class in
the second module.
Using the following configuration, the site reports end up
C:/opt/builds/releases/${branch}/${module}/siteReports as I expect. The
test reports, however, keep getting placed under target/surefire-reports.
I've tried with and without the reportsDirectory and I've tried reversing
the order of
Could it be that it is looking for Data.xml at path
foo/secondModule/Data.xml. I'm guessing that this is a plain Java thing and
not related to Maven.
/Anders
On Mon, Jun 7, 2010 at 04:30, smallufo small...@gmail.com wrote:
I have a maven mantained project with some modules . One module
19 matches
Mail list logo
