Hi Brad,
I committed your patch yesterday. It is in the snapshot i uploaded yesterday.
Yep, i was not planing to document it. But i know where to;
it is in the "handcrafting an archetype" example.
Regards,
Raphaël
2008/9/17 Brad Szabo <[EMAIL PROTECTED]>:
> Hi Raphaël,
>
> The additional exa
On Wed, Sep 17, 2008 at 9:07 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Some of the ITs use an alternate settings.xml file which won't have a local
> repo specified.
>
> It's one of the things I added to the ITProblems list. I really think that
> the entire suite should use a sandboxed local rep
This plugin can build a subset of interdependent projects in a reactor. It
should be useful in large reactor builds that include irrelevant stuff
you're not working on.
http://maven.apache.org/plugins/maven-reactor-plugin/
A few important notes:
* This is maven-reactor-plugin's first offici
Hi Raphaël,
The additional examples are helpful, thanks!
Were you planning on mentioning the file renaming support
(http://jira.codehaus.org/browse/ARCHETYPE-191) in these documentation
updates, I don't see them.
Do you think I should create a new JIRA for the enhanced file renaming
support a
Some of the ITs use an alternate settings.xml file which won't have a
local repo specified.
It's one of the things I added to the ITProblems list. I really think
that the entire suite should use a sandboxed local repository that is
prepopulated with required dependencies (but not downloaded
Hi folks,
I think i documented enough for this release.
Please review the documentation at
http://people.apache.org/~rafale/site/maven-archetype-plugin/index.html
I will be happy if any one can review the sources with respect to the
apache licensing convention.
I do not plan to enhance the plug
2008/9/13, Wendy Smoak <[EMAIL PROTECTED]>:
> On Sat, Sep 13, 2008 at 7:13 AM, Raphaël Piéroni
> <[EMAIL PROTECTED]> wrote:
>
> >> Do you mean this gets created at build time? At run time? I know I
> >> found a file in there to edit...
> >
> > what i do usually, is run the profile,
> > gra
Hi,
just for some fun, I executed
mvn clean install -D maven.repo.local=M:\it-repo
on core-integration-tests-support and right afterwards
mvn clean test -P run-its -D maven.repo.local=M:\it-repo
on core-integration-tests where "mvn" refers to Maven 2.0.9. After some
time it ended up with
+1
John Casey wrote:
Hi everyone,
After fixing 70 issues and spending about 2 months going through release
candidate after release candidate, we finally have a stable codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release
notes are here:
http://jira.codehaus.org/
+1
2008/9/16 Jason Dillon <[EMAIL PROTECTED]>
> +1
>
> --jason
>
>
> On Sep 16, 2008, at 4:12 AM, John Casey wrote:
>
> Hi everyone,
>>
>> After fixing 70 issues and spending about 2 months going through release
>> candidate after release candidate, we finally have a stable codebase!
>>
>> To th
+1
--jason
On Sep 16, 2008, at 4:12 AM, John Casey wrote:
Hi everyone,
After fixing 70 issues and spending about 2 months going through
release candidate after release candidate, we finally have a stable
codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The
release
+1
-Lukas
John Casey wrote:
Hi everyone,
After fixing 70 issues and spending about 2 months going through release
candidate after release candidate, we finally have a stable codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release
notes are here:
http://jira.code
+1 (not binding)
John Casey-5 wrote:
>
> Hi everyone,
>
> After fixing 70 issues and spending about 2 months going through release
> candidate after release candidate, we finally have a stable codebase!
>
> To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release
> notes are h
Hi Nick,
Thanks for this suggestion. I tested this and it works.
It will certainly help reduce the XML bloat for now.
Cheers,
Nick
On 16/09/2008, at 7:15 PM, Nick Stolwijk wrote:
As far as I know you have to specify the goals in your projects, which
uses your plugin. If you have the right @p
Jason van Zyl wrote:
The ITs for example could easily use the invoker in shared.
Not as is I believe. The maven-invoker is intended to run Maven, not
more. The maven-verifier on the other hand appears to be a conglomerate
of these functionalities
- invoke Maven
- assert pre-/post-build cond
I'm enumerated the many verifiers and many invokers we have. The ITs
for example could easily use the invoker in shared.
On 15-Sep-08, at 8:14 PM, Dennis Lundberg wrote:
Brian E. Fox wrote:
If the only dependency for integration tests is the verifier, then
there's not much point in moving it
Here are the results of my initial tests of what has been implemented:
The scm commands that look like they've been attempted: scm:add,
scm:checkout
1. scm:add is broken when tried against a real Accurev
2. scm:checkout is fundamentally flawed... but does work
3. The scm URL format used at pres
You could have your plugin define a custom packaging and then bind the
plugin goals to phases for that custom packaging's lifecycle.
Otherwise I think you're low on luck
On Tue, Sep 16, 2008 at 10:15 AM, Nick Stolwijk <[EMAIL PROTECTED]>wrote:
> As far as I know you have to specify the goals in
As far as I know you have to specify the goals in your projects, which
uses your plugin. If you have the right @phase annotations it should
be enough to add only the executions like so:
one
two
three
As far as I know it is not possible to automatica
Hi,
I have 3 MOJOs in a single maven plugin. Each MOJO needs to be
executed during specific build phases.
What is the best way to make this possible, without forcing users of
the plugin to insert explicit executions into their pom.xml ?
i.e. is it possible to make the following configuratio
+1
Arnaud
On Tue, Sep 16, 2008 at 3:43 AM, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
> +1
>
> Thanks,
> Deng
>
> On Mon, Sep 15, 2008 at 8:29 PM, Dennis Lundberg <[EMAIL PROTECTED]>
> wrote:
>
> > Hi
> >
> > Here's another parent in need of a release.
> >
> > Diff for the pom.xml:
> >
> >
> ht
+1!
- Fabrice
[EMAIL PROTECTED]
On Mon, Sep 15, 2008 at 11:12 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> After fixing 70 issues and spending about 2 months going through release
> candidate after release candidate, we finally have a stable codebase!
>
> To that end, I'd like t
22 matches
Mail list logo
