Re: Moving maven site plugin 3.x source to plugins trunk was [ Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3 ]

2010-10-20 Thread Dennis Lundberg
On 2010-10-20 14:44, Olivier Lamy wrote: > Hi, > I agree. (and moving current trunk to plugins/branches/maven-site-plugin-2.x). > +1 for me. > > Others ? I'm not sure which way is best to go. As I see it, we will have activity on both 2.x and 3.x for at least a year going forward. I would like

Re: Moving maven site plugin 3.x source to plugins trunk was [ Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3 ]

2010-10-20 Thread Brett Porter
That would be a bit unusual... Olivier's suggestion is more consistent with how it has been done already in core, etc. I presume that the amount of activity on the 2.x version will die down now? On 21/10/2010, at 12:41 AM, Vincent Siveton wrote: > I think we could leave the current maven-site-p

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Brian Fox
If the profile affects things like dependencies, then having script-like behavior becomes pretty troublesome for tools attempting to analyze the pom/tree outside of the dev environment. For example a repo manager. On Wed, Oct 20, 2010 at 12:01 PM, Jason van Zyl wrote: > It's a matter of defining

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Jason van Zyl
It's a matter of defining what is mutable in MavenProject from a plugin and lifecycle participants (which are new in Maven 3). A profile activator would need full context, or a lifecycle participant which can hook in before the build execution occurs could mutate/activate profiles. On Oct 20, 2

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Paul Benedict
Couldn't a maven plugin be written to pre-process the POM structure and do the evaluation? I would rather see that than ever making it part of Maven core. On Wed, Oct 20, 2010 at 10:50 AM, Justin Edelson wrote: > On 10/20/10 11:47 AM, Jason van Zyl wrote: >> I think we just need to make it easier

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Justin Edelson
On 10/20/10 11:47 AM, Jason van Zyl wrote: > I think we just need to make it easier to create and add profile activators. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@mave

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Jason van Zyl
On Oct 20, 2010, at 11:41 AM, Vincent Siveton wrote: > And what about profile activation? I mean do you think it could be a > good idea to add scripting in the activation part? No, I think that could be remedied without having to resort to scripting. Once you open the door it just gets opened w

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Vincent Siveton
And what about profile activation? I mean do you think it could be a good idea to add scripting in the activation part? I know that pom.xml is not like ant and other, but in some cases, using antrun to do basic validation could be overkill IMHO Cheers Vincent 2010/10/20 Jason van Zyl : > > On Oc

Re: [Discuss] Using Expression Language in POM

2010-10-20 Thread Jason van Zyl
On Oct 20, 2010, at 10:06 AM, Vincent Siveton wrote: > Hi guys, > > I don't remember if this topic was already discussed in the past. > > Some of our plugins have a boolean parameter. In my case, I > want to use expression to init this boolean, i.e. > ${project.packaging} != "pom" or similar.

[Discuss] Using Expression Language in POM

2010-10-20 Thread Vincent Siveton
Hi guys, I don't remember if this topic was already discussed in the past. Some of our plugins have a boolean parameter. In my case, I want to use expression to init this boolean, i.e. ${project.packaging} != "pom" or similar. So, WDYT to add expression interpretor for plugins parameters? Cheer

Re: Moving maven site plugin 3.x source to plugins trunk was [ Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3 ]

2010-10-20 Thread Vincent Siveton
I think we could leave the current maven-site-plugin there, juste create plugins/trunk/maven-site-plugin-3.x Vincent 2010/10/20 Olivier Lamy : > Hi, > I agree. (and moving current trunk to plugins/branches/maven-site-plugin-2.x). > +1 for me. > > Others ? > > 2010/10/20 Vincent Siveton : >> Hi Ol

Moving maven site plugin 3.x source to plugins trunk was [ Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3 ]

2010-10-20 Thread Olivier Lamy
Hi, I agree. (and moving current trunk to plugins/branches/maven-site-plugin-2.x). +1 for me. Others ? 2010/10/20 Vincent Siveton : > Hi Olivier, > > Just a thought, wdyt to move the src code to /maven/plugins/trunk ? > > Cheers, > > Vincent > > 2010/10/18 Olivier Lamy : >> Hi, >> I'd like to rel

Re: [VOTE] Release Maven Site Plugin 3.0-beta-3 for maven 3

2010-10-20 Thread Vincent Siveton
Hi Olivier, Just a thought, wdyt to move the src code to /maven/plugins/trunk ? Cheers, Vincent 2010/10/18 Olivier Lamy : > Hi, > I'd like to release a new beta (3.0-beta-3) of Maven Site Plugin  for Maven 3. > We solved 8 issues : > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11

MSHADE-88

2010-10-20 Thread ant elder
I've raised http://jira.codehaus.org/browse/MSHADE-88 about a problem using the shade plugin with pom type dependencies, would anyone be able to review and comment on the patch in that? TIA, ...ant (Apologies if this email ends up duplicated, the original appears held up in moderation) --