It is also what i think. it was just a reminder ;-)
Raphaël
2008/2/6, Brett Porter <[EMAIL PROTECTED]>:
> Sorry, thought I had until tomorrow :)
>
> Will take a look later today.
>
> On 07/02/2008, at 5:40 AM, Raphaël Piéroni wrote:
>
> > Hi,
> > To sum up the vote for now:
> >
> > Binding (PMC)
+1
Vincent
2008/2/1, Raphaël Piéroni <[EMAIL PROTECTED]>:
> Hi,
>
> Here comes the time for calling the first release of the Maven
> Archetype plugin version 2.0-alpha-1.
>
> Staging repo:
> http://people.apache.org/~rafale/staging-repo/maven-archetype-plugin/
>
> Staging site:
> No staging site
Hi,
2008/2/6, Daniel Kulp <[EMAIL PROTECTED]>:
>
> Dan,
>
> I'm cannot really answer the question about what @aggregator does, but I
> can say the javadoc example is not a good one. There are many of us
> that think the javadoc mojo should NOT have it and have our javadoc
Agree. MJAVADOC-104 is
Hi,
2008/2/6, Benjamin Bentmann <[EMAIL PROTECTED]>:
> I apologize for this spam but I couldn't resist...
np. Comments are always welcome there!
> > what does the @aggregator annotation do, exactly?
>
> Doesn't this question illustrate a common symptom in Maven land, i.e. the
> lack of proper do
Stephen Connolly wrote:
I would have expected that there would be two javadoc mojo's something
like javadoc:javadoc which just generates the javadoc for the current
module, and javadoc:unified-javadoc which would be an @aggregator mojo that
produces the unified javadoc of all child modules.
For the really 'edgy' guys out there: I've fixed the maven-scm-provider-git to
also work with
git-1.5.4.
$> git-clone http://ns1.backwork.net/git/maven-scm-providers-git.git
as usual...
Please provide feedback, so we can move this to codehaus if it's mature enough.
LieGrü,
strub
--- Mark Str
Stuart McCulloch wrote:
On 07/02/2008, Dan Fabulich <[EMAIL PROTECTED]> wrote:
Based on preliminary research, I hypothesize that @aggregator is simply
broken so it's therefore not needed on any plugin, including javadoc.
hmm, well I use @aggregator on some local mojos and it seems to do
what
+1. I tested basic artifact to project creation on windows.
-Original Message-
From: Raphaël Piéroni [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 06, 2008 10:41 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Archetype plugin version 2.0-alpha-1
Hi,
To sum up the vo
On 6-Feb-08, at 6:30 AM, Jim Bethancourt wrote:
Hi everyone,
I found out last week that my presentation proposal, "Migrating to
Maven 2
Demystified", was accepted for presentation at this year's JavaOne.
Nice.
In the
presentation, I will be showing how to Mavenize Google's Guice
framewo
Hello,
I am pinging the list about this issue. It seems to be related to some DI
with plexus, or at least that's what I can infer... I tried changing
packages to org.apache.m.d.module.muse but this did not change anything. I
may be doing something in my code, or in my pom,or in the plexus
descript
Yeah, I can add attribution when I commit a patch. Also, see the issues...I
specifically asked people who have windows to try it out, since I'm unable
to. I was reassured by the fact that at least one of these issues had
corroborating comments agreeing with the original proposed solution. :-)
-j
John,
Can you make sure attribute patches in the commit logs? It helps those
of us watching commits but not all JIRAs to know who is contributing :)
The only reason I suspected it was a patch was because it was for
Windows :)
Incidentally - someone really needs to test this beyond just th
Sorry, thought I had until tomorrow :)
Will take a look later today.
On 07/02/2008, at 5:40 AM, Raphaël Piéroni wrote:
Hi,
To sum up the vote for now:
Binding (PMC) : Arnaud
Non Binding (Committer) : Mauro (still not on the list), Milos,
Raphaël
Non Binding (User) :
checked against the lis
Hi Siarhei,
I imagine they will be posted on the JavaOne website after the conference,
and I'll be sure they are added to the Maven docs area.
Cheers,
Jim
On Feb 6, 2008 2:18 PM, Siarhei Dudzin <[EMAIL PROTECTED]> wrote:
> Any chance of publishing the slides when possible (PDF is fine too)?
>
>
Any chance of publishing the slides when possible (PDF is fine too)?
On Feb 6, 2008 5:28 PM, Christian Edward Gruber <
[EMAIL PROTECTED]> wrote:
> No, but I will be submitting a talk about build systems (using Maven2
> as the implementation) and their effect on architecture and process
> change e
On 07/02/2008, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> Max Bowsher wrote:
>
> > Daniel Kulp wrote:
> >> Dan,
> >>
> >> I'm cannot really answer the question about what @aggregator does, but
> I
> >> can say the javadoc example is not a good one. There are many of us
> that
> >> think the java
My understanding is that this is all related to the work that is being done
on the build plan for 2.1.
AFAIK the idea behind @aggregator is that it specifies the mojo as being one
that operates on all child modules. So for example javadoc would want to do
this in order to provide a unified javadoc
Hi,
To sum up the vote for now:
Binding (PMC) : Arnaud
Non Binding (Committer) : Mauro (still not on the list), Milos, Raphaël
Non Binding (User) :
checked against the list in
http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
I am unsure the vote as passed.
According to http://www.apa
Max Bowsher wrote:
Daniel Kulp wrote:
Dan,
I'm cannot really answer the question about what @aggregator does, but I
can say the javadoc example is not a good one. There are many of us that
think the javadoc mojo should NOT have it and have our javadoc plugins
locked down to a previous ver
Ok it's in the right place now.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Wednesday, February 06, 2008 9:10 AM
To: Maven Developers List
Subject: Re: Missing Maven 2.0.8 sources
Brian,
Are you sure? I still don't see them either
Daniel Kulp wrote:
Dan,
I'm cannot really answer the question about what @aggregator does, but I
can say the javadoc example is not a good one. There are many of us
that think the javadoc mojo should NOT have it and have our javadoc
plugins locked down to a previous version for the same rea
Brian,
Are you sure? I still don't see them either on the mirrors or on Apache:
http://www.apache.org/dist/maven/source/
Paul
On Feb 5, 2008 12:11 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> These are uploaded now. Give it a few hours to sync.
>
> -Original Message-
> From: [EMAIL PRO
Sorry, that was sort of my point - many implementation-specific tricks
make it into OR/M configuration, and sometimes code. Or rather
assumptions about subtle behaviour or one ORM are factored into the
design, but another ORM may not perform in the same way under the same
conditions because
Just as an FYI, There is a blog post
http://fishbowl.pastiche.org/2007/12/20/maven_broken_by_design that raised
concerns at our company regarding Maven's ability to perform repeatable
builds. Personally, I think Maven has features to address all or most issues
cited in the blog. generateReleasePom
On Feb 5, 2008 11:56 PM, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
> Not entirely related to Arnaud's question.. I've moved around some issues to
> the 1.0.2 bucket in jira yesterday. And if there are other issues that you
> might think should be in that bucket, please feel free to move them :)
Hibernate can be used in a completely JPA-compliant mode, so it would be
(theoretically) just as swappable as any other JPA implementation as long as
you don't use any hibernate-specific extensions.
On Feb 5, 2008 10:12 PM, Christian Edward Gruber <[EMAIL PROTECTED]>
wrote:
> Toplink is mentioned
No, but I will be submitting a talk about build systems (using Maven2
as the implementation) and their effect on architecture and process
change efforts at Agile2008.
regards,
Christian.
On 6-Feb-08, at 09:30 , Jim Bethancourt wrote:
Hi everyone,
I found out last week that my presentation
I apologize for this spam but I couldn't resist...
what does the @aggregator annotation do, exactly?
Doesn't this question illustrate a common symptom in Maven land, i.e. the
lack of proper documentation, just too well?
Specifically, in 2.4 I added @aggregator to the surefire-report plugin
w
Dan,
I'm cannot really answer the question about what @aggregator does, but I
can say the javadoc example is not a good one. There are many of us
that think the javadoc mojo should NOT have it and have our javadoc
plugins locked down to a previous version for the same reason. With
@aggreg
On Feb 6, 2008 2:33 PM, Benjamin Bentmann <[EMAIL PROTECTED]> wrote:
> > OK I've put forward a patch for MCHANGES-88 - although its based on
> > copying something that works (project info reports) rather than
> > understanding what the correct way to handle reports being run
> > individually.
>
> U
OK I've put forward a patch for MCHANGES-88 - although its based on
copying something that works (project info reports) rather than
understanding what the correct way to handle reports being run
individually.
Until r430440 of the maven-reporting-impl, the AbstractMavenReport provided
a default i
Hi everyone,
I found out last week that my presentation proposal, "Migrating to Maven 2
Demystified", was accepted for presentation at this year's JavaOne. In the
presentation, I will be showing how to Mavenize Google's Guice framework one
step at a time, while being minimally invasive to the code
32 matches
Mail list logo
