I have modified the Maven 2 Eclipse plugin to accept a configuration
option that will write an additional attribute to the classpathentry
for src types.
If this is of interest to you guys, let me know and I'll add a Jira
ticket and attach a patch (with test).
For example, here's the first
You can enter your email again instead of re-registering.
- Brett
Dion Gillard wrote:
Will the released version allow u to download it more than once?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
Will the released version allow u to download it more than once?
On 4/26/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> I should just give a heads up - this will be getting an update, when it
> is "officially" released. Stay tuned.
>
> - Brett
>
> Brian E. Fox wrote:
> > BTW, this book looks like
Three's a logic error here - it won't actually validate if a field is
missing, or if an unknown field is found.
I suggest constructing a set of entries, then doing the asserts based on
set.contains( name );
Cheers,
Brett
[EMAIL PROTECTED] wrote:
Author: oching
Date: Tue Apr 25 20:13:09 2006
I should just give a heads up - this will be getting an update, when it
is "officially" released. Stay tuned.
- Brett
Brian E. Fox wrote:
BTW, this book looks like a great resource. Thanks to Vincent, Jason,
Brett et all for putting this together. Finally I can stop explaining to
everyone how
BTW, this book looks like a great resource. Thanks to Vincent, Jason,
Brett et all for putting this together. Finally I can stop explaining to
everyone how awesome maven is and let them figure it out for themselves!
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Tuesda
http://www.mergere.com/products.jsp you want to readup on that
-D
On 4/25/06, Joel Sherriff <[EMAIL PROTECTED]> wrote:
>
> No, I thought that would substite the literal "something". What I'm
> really trying to do, of course,
> Is to substitute project attributes such as version or artifactId o
No, I thought that would substite the literal "something". What I'm
really trying to do, of course,
Is to substitute project attributes such as version or artifactId or
groupId - none of which is working
Either.
@parameter expression="${project.version}"
Gives me "null" as well.
-Original
did you pass in somethingelse to the configuration?
or -Dsomething=xyz?
-D
On 4/25/06, Joel Sherriff <[EMAIL PROTECTED]> wrote:
>
>
> Here's another question, now that I've accepted the uglyness of my task
> :-)
>
> I'm trying @parameter substitution and am not having any luck at all,
> what
Here's another question, now that I've accepted the uglyness of my task
:-)
I'm trying @parameter substitution and am not having any luck at all,
what could I be doing to cause it not to work?
I have this very simple plugin:
public class Sensor extends AbstractMojo
{
/*
* @parameter expressio
Ah, that helps - thanks. That gets me closer. Is there any other trick
I can use to bury or shrink this large chunk of xml that I'm going to be
forcing the users to add to their pom?
sixthsensesoftware.plugin
sixthsense-plugin
compile
sorry, only one phase per . So you need multiple
elements.
On 4/25/06, Joel Sherriff <[EMAIL PROTECTED]> wrote:
>
>
>
> >@phase phase is the default phase, so that you dont have to setup
> element in your pom.
>
> Hmmm, I'm not following you. Could you type that a little slower?
>
> > To run
>@phase phase is the default phase, so that you dont have to setup
element in your pom.
Hmmm, I'm not following you. Could you type that a little slower?
> To run your mojo in multiple phases, you need to set them up in your
build 's executions
Do you mean something like:
@phase phase is the default phase, so that you dont have to setup
element in your pom.
To run your mojo in multiple phases, you need to set them up in your build
's executions
-D
On 4/25/06, Joel Sherriff <[EMAIL PROTECTED]> wrote:
>
>
> Thanks for the input. I've been researching all day an
Thanks for the input. I've been researching all day and still haven't
seen anything that makes me think I can do what I want (log all build
phases without modifing the project pom), but that doesn't mean it's not
possible. Is there any other way to do this other than a plugin?
If so it's not ob
hi Marteijn,
Yes, packaging determines the project type - and you can definitly define
you own packaging types (provided you create the appropriate plugin). See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.htmlfor
information on creating your own packaging and matching
Hello everybody,
I am new to maven 2.0. but experienced 1.0 user.
Do i understand correctly that packaging defines the type of product that is
being build. If so, can you define more than one and define your own custom
types. like installer and application. With matching plugins.
Thanks
Marteij
Jörg Schaible wrote:
Hi Brett,
Brett Porter wrote on Monday, April 24, 2006 2:12 PM:
There are apparently bugs in the current SVN version that
mean it cannot
be released. I believe they are all in JIRA.
As I said after the 2.0.1 release, we'll happily accept backports of
the fixes you need f
Hi Brett,
Brett Porter wrote on Monday, April 24, 2006 2:12 PM:
> There are apparently bugs in the current SVN version that
> mean it cannot
> be released. I believe they are all in JIRA.
>
> As I said after the 2.0.1 release, we'll happily accept backports of
> the fixes you need for a 2.0.2.
didn't have the time to test, sorry.
On 4/24/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> +1
>
> (Sorry for the late reply, voting over the weekend is probably why
> many people didn't vote)
> On 24 Apr 06, at 1:54 PM 24 Apr 06, Lukas Theussl wrote:
>
> > Thanks Arnaud!
> >
> > I don't have en
Hello Joel,
Why don't try checking the continuum project. It might
satisfy your requirements.
check this url :
http://maven.apache.org/continuum/about.html#what-is-continuum
If not, you can start by creating plugin that will store the
current project information
21 matches
Mail list logo
