Re: svn commit: r506479 - in /maven/continuum/trunk: continuum-api/src/main/java/org/apache/maven/continuum/ continuum-api/src/main/java/org/apache/maven/continuum/store/ continuum-core/src/main/java/

[Trygve Laugstøl]

[EMAIL PROTECTED] wrote:

Author: evenisse
Date: Mon Feb 12 07:19:35 2007
New Revision: 506479

URL: http://svn.apache.org/viewvc?view=rev&rev=506479
Log:
Fix some jdo calls for performance improvment

Modified:

maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/Continuum.java

maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/store/ContinuumStore.java

maven/continuum/trunk/continuum-core/src/main/java/org/apache/maven/continuum/DefaultContinuum.java

maven/continuum/trunk/continuum-core/src/test/java/org/apache/maven/continuum/DefaultContinuumTest.java

maven/continuum/trunk/continuum-store/src/main/java/org/apache/maven/continuum/store/JdoContinuumStore.java

maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/ProjectGroupAction.java

maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/SummaryAction.java

maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/component/BuildDefinitionSummaryAction.java

maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/component/NotifierSummaryAction.java

Modified: 
maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/Continuum.java
URL: 
http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/Continuum.java?view=diff&rev=506479&r1=506478&r2=506479
==
--- 
maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/Continuum.java
 (original)
+++ 
maven/continuum/trunk/continuum-api/src/main/java/org/apache/maven/continuum/Continuum.java
 Mon Feb 12 07:19:35 2007
@@ -80,6 +80,9 @@
 public ProjectGroup getProjectGroupWithProjects( int projectGroupId )
 throws ContinuumException;
 
+public ProjectGroup getProjectGroupWithBuildDetails( int projectGroupId )

+throws ContinuumException;


Can we call this getProjectGroupWithBuildDetailsByProjectGroupId(..) to 
make it consistent?



 public ProjectGroup getProjectGroupByGroupId( String groupId )
 throws ContinuumException;
 
@@ -115,7 +118,11 @@
 
 BuildResult getLatestBuildResultForProject( int projectId );
 
+Map getLatestBuildResults( int projectGroupId );


ditto here,


 Map getLatestBuildResults();
+
+Map getBuildResultsInSuccess( int projectGroupId );


and here.


 Map getBuildResultsInSuccess();


[snip]

--
Trygve

JIRA ID for plugins run twice when parent defines execution?

[Jason Dillon]

Anyone know what the JIRA ID is for the bug where a child poms plugin  
executions get run twice because a parent plugin also defines  
executions for the same plugin?


--jason

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: License for POM files

[Carlos Sanchez]

you could check the parent pom. In this case not even the parent has license.

Anything that should be done in the future to clarify the legal aspects?

On 2/14/07, Deepak Bhole <[EMAIL PROTECTED]> wrote:

On Tue, 2007-02-13 at 12:21 -0800, Carlos Sanchez wrote:
> The license should be inside the pom  section, or in the
> maven1 repo in the .license files
>

Very few of the poms I am seeing have licenses. For example, even the
critical plexus ones don't have one:

http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-8/plexus-archiver-1.0-alpha-8.pom

In many cases, it it hard to tell who wrote the file. Like the above
file for instance, I don't know if it was written by the plexus guys (in
which case that license applies), or if someone from maven side wrote it
(APL in that case)...

Deepak


> On 2/13/07, Deepak Bhole <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > What license are the pom files in the maven2 repository
> > (repo1.maven.org/maven2) under? We need to know if we are allowed to
> > redistribute those poms with Fedora.
> >
> > Thanks,
> > Deepak
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Resolving dependencies

[Samuel Le Berrigaud]

Good to you as well Franz,

And thanks for the links. Sorry for bothering everyone with something
that IS documented...

I will have a look and 'play' again...

Thanks,
SaM

On 2/15/07, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:

Good day to you, Samuel,

Kindly take a look at the "Creating and resolving an artifact" and
"Resolving transitively" sections of [1].

Cheers,
Franz

[1] http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook

On 2/14/07, Samuel Le Berrigaud <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I was trying to resolve dependencies from a plugin. I am not sure
> which part of the API I should use for that.
>
> What I want is to get all dependencies for a project and their
> transitive dependencies in Set. At the same time dependencies that are
> not present locally should be downloaded.
>
> I 'played' a bit with the ArtifactResolver and tried with both methods
> resolve and resolveTransitively but it doesn't seem to do the trick
> for me.
>
> I am not sure what should be the parameters (more precisely where I
> can get them from). I had a look at different plugin but could figure
> out one simple consistent way of doing it...
>
> If someone has some code I could/should look it would be nice. Or just
> let me know which API is the best for what I want to do.
>
> Thanks,
>
> --
> Samuel Le Berrigaud
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Samuel Le Berrigaud

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Resolving dependencies

[Franz Allan Valencia See]

Good day to you, Samuel,

Kindly take a look at the "Creating and resolving an artifact" and
"Resolving transitively" sections of [1].

Cheers,
Franz

[1] http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook

On 2/14/07, Samuel Le Berrigaud <[EMAIL PROTECTED]> wrote:

Hi all,

I was trying to resolve dependencies from a plugin. I am not sure
which part of the API I should use for that.

What I want is to get all dependencies for a project and their
transitive dependencies in Set. At the same time dependencies that are
not present locally should be downloaded.

I 'played' a bit with the ArtifactResolver and tried with both methods
resolve and resolveTransitively but it doesn't seem to do the trick
for me.

I am not sure what should be the parameters (more precisely where I
can get them from). I had a look at different plugin but could figure
out one simple consistent way of doing it...

If someone has some code I could/should look it would be nice. Or just
let me know which API is the best for what I want to do.

Thanks,

--
Samuel Le Berrigaud

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Resolving dependencies

[Samuel Le Berrigaud]

Hi all,

I was trying to resolve dependencies from a plugin. I am not sure
which part of the API I should use for that.

What I want is to get all dependencies for a project and their
transitive dependencies in Set. At the same time dependencies that are
not present locally should be downloaded.

I 'played' a bit with the ArtifactResolver and tried with both methods
resolve and resolveTransitively but it doesn't seem to do the trick
for me.

I am not sure what should be the parameters (more precisely where I
can get them from). I had a look at different plugin but could figure
out one simple consistent way of doing it...

If someone has some code I could/should look it would be nice. Or just
let me know which API is the best for what I want to do.

Thanks,

--
Samuel Le Berrigaud

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Control of maven using prerequisites

[Brian E. Fox]

I was thinking about preventing someone from overriding the config in a
child. If I'm setting something to be enforced in a super-pom, then I
don't want someone coming along and turning it off down below.

-Original Message-
From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 11:15 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites

Plugins can not be removed from the build.
However configuration portions can be overridden.

If you have checks that must always run, hardcode it.
Or use a resource from an URL or artifact to get the values.
Just don't let someone use the plugin configuration to change the value.

- Joakim

Brian E. Fox wrote:
> Actually I was talking about specifying other plugin/dependency
plugins
> to be enforced but I see your point. How would we make it not possible
> to override in a child? Using a static value to store previously
entered
> config?
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 14, 2007 10:37 PM
> To: Maven Developers List
> Subject: Re: Control of maven using prerequisites
>
>
> On 14 Feb 07, at 10:28 PM 14 Feb 07, Brian E. Fox wrote:
>
>   
>> So the initial feature list for the "maven-enforcer-plugin" is:
>> OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
>> Configuration Management standpoint? Most other things can already be
>> controlled via pluginManagement/dependencyManagement...although it
>> doesn't stop someone from overriding at a local pom level.
>>
>> 
>
> Maybe this is a new flavor of plugin that can't be reconfigured or  
> have any other configurations merged. Not sure if you could  
> categorically state you want X, Y, and Z for your entire system but  
> programmatically we could effectively make it impossible to change.
>
> Jason.
>
>   
>> -Original Message-
>> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, February 14, 2007 9:56 PM
>> To: Maven Developers List
>> Subject: Re: Control of maven using prerequisites
>>
>>
>> On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:
>>
>> 
>>> Now that 2.0.5 is out and more frequent releases are expected, I  
>>> think
>>> that http://jira.codehaus.org/browse/MNG-2423 is even more
important.
>>> Currently the prerequisites value is not inherited and thus we
>>> can't use
>>> it in a company "super-pom" to enforce a minimum Maven version. My
>>> workaround is to create an empty plugin that has a prereq and
include
>>> that in the super-pom. This seems kludgey an kind of unnecessary  
>>> since
>>> there is a field in the pom to do this...it just only applies if
>>> defined
>>> in each child pom or when building from a reactor that contains  
>>> it. Is
>>> there any chance this can get bumped to 2.0.6? I'm willing to try
and
>>> submit a patch I could get a pointer where to look.
>>>
>>>   
>> The prereq is specifically for plugins, or other tools, that need a
>> specific version of Maven. It was not meant as a means of enforcement
>> for your development environment. Trying to mix these concerns would
>> cause problems.
>>
>> I think what you need is a plugin that runs in the validate phase
>> (call it the Enforcer Plugins :-) that checks things like jdk
>> version, mvn version, operating system or whatever else you might
>> want. Configure this in your parent POM and then you're all set.
>>
>> Jason.
>>
>> 
>>> Thanks,
>>>
>>> Brian
>>>
>>>   
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> 
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Control of maven using prerequisites

[Jason Dillon]

FYI, docs for that are here:

http://geronimo.apache.org/maven/genesis/plugins/tools-maven- 
plugin/usage.html


Was thinking of moving some of that to a plugin in the mojo project  
whenever I find some time...


--jason


On Feb 14, 2007, at 8:12 PM, Joakim Erdfelt wrote:


Check out the geronimo tools-maven-plugin
Found at
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/ 
tools-maven-plugin/


It is used by the current geronimo for enforcing various minimum  
aspects

of the build environment.

Example: (from
http://svn.apache.org/repos/asf/geronimo/daytrader/trunk/pom.xml )


org.apache.geronimo.genesis.plugins
tools-maven-plugin


validate-java-version
validate

require-java-version


1.5*






Enjoy

- Joakim


Brian E. Fox wrote:

So the initial feature list for the "maven-enforcer-plugin" is:
OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
Configuration Management standpoint? Most other things can already be
controlled via pluginManagement/dependencyManagement...although it
doesn't stop someone from overriding at a local pom level.

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 9:56 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites


On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:


Now that 2.0.5 is out and more frequent releases are expected, I  
think
that http://jira.codehaus.org/browse/MNG-2423 is even more  
important.

Currently the prerequisites value is not inherited and thus we
can't use
it in a company "super-pom" to enforce a minimum Maven version. My
workaround is to create an empty plugin that has a prereq and  
include
that in the super-pom. This seems kludgey an kind of unnecessary  
since

there is a field in the pom to do this...it just only applies if
defined
in each child pom or when building from a reactor that contains  
it. Is
there any chance this can get bumped to 2.0.6? I'm willing to try  
and

submit a patch I could get a pointer where to look.




The prereq is specifically for plugins, or other tools, that need a
specific version of Maven. It was not meant as a means of enforcement
for your development environment. Trying to mix these concerns would
cause problems.

I think what you need is a plugin that runs in the validate phase
(call it the Enforcer Plugins :-) that checks things like jdk
version, mvn version, operating system or whatever else you might
want. Configure this in your parent POM and then you're all set.

Jason.



Thanks,

Brian





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Control of maven using prerequisites

[Joakim Erdfelt]

Plugins can not be removed from the build.
However configuration portions can be overridden.

If you have checks that must always run, hardcode it.
Or use a resource from an URL or artifact to get the values.
Just don't let someone use the plugin configuration to change the value.

- Joakim

Brian E. Fox wrote:
> Actually I was talking about specifying other plugin/dependency plugins
> to be enforced but I see your point. How would we make it not possible
> to override in a child? Using a static value to store previously entered
> config?
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 14, 2007 10:37 PM
> To: Maven Developers List
> Subject: Re: Control of maven using prerequisites
>
>
> On 14 Feb 07, at 10:28 PM 14 Feb 07, Brian E. Fox wrote:
>
>   
>> So the initial feature list for the "maven-enforcer-plugin" is:
>> OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
>> Configuration Management standpoint? Most other things can already be
>> controlled via pluginManagement/dependencyManagement...although it
>> doesn't stop someone from overriding at a local pom level.
>>
>> 
>
> Maybe this is a new flavor of plugin that can't be reconfigured or  
> have any other configurations merged. Not sure if you could  
> categorically state you want X, Y, and Z for your entire system but  
> programmatically we could effectively make it impossible to change.
>
> Jason.
>
>   
>> -Original Message-
>> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, February 14, 2007 9:56 PM
>> To: Maven Developers List
>> Subject: Re: Control of maven using prerequisites
>>
>>
>> On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:
>>
>> 
>>> Now that 2.0.5 is out and more frequent releases are expected, I  
>>> think
>>> that http://jira.codehaus.org/browse/MNG-2423 is even more important.
>>> Currently the prerequisites value is not inherited and thus we
>>> can't use
>>> it in a company "super-pom" to enforce a minimum Maven version. My
>>> workaround is to create an empty plugin that has a prereq and include
>>> that in the super-pom. This seems kludgey an kind of unnecessary  
>>> since
>>> there is a field in the pom to do this...it just only applies if
>>> defined
>>> in each child pom or when building from a reactor that contains  
>>> it. Is
>>> there any chance this can get bumped to 2.0.6? I'm willing to try and
>>> submit a patch I could get a pointer where to look.
>>>
>>>   
>> The prereq is specifically for plugins, or other tools, that need a
>> specific version of Maven. It was not meant as a means of enforcement
>> for your development environment. Trying to mix these concerns would
>> cause problems.
>>
>> I think what you need is a plugin that runs in the validate phase
>> (call it the Enforcer Plugins :-) that checks things like jdk
>> version, mvn version, operating system or whatever else you might
>> want. Configure this in your parent POM and then you're all set.
>>
>> Jason.
>>
>> 
>>> Thanks,
>>>
>>> Brian
>>>
>>>   
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> 
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Control of maven using prerequisites

[Joakim Erdfelt]

Check out the geronimo tools-maven-plugin
Found at
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/tools-maven-plugin/

It is used by the current geronimo for enforcing various minimum aspects
of the build environment.

Example: (from
http://svn.apache.org/repos/asf/geronimo/daytrader/trunk/pom.xml )


org.apache.geronimo.genesis.plugins
tools-maven-plugin


validate-java-version
validate

require-java-version


1.5*






Enjoy

- Joakim


Brian E. Fox wrote:
> So the initial feature list for the "maven-enforcer-plugin" is:
> OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
> Configuration Management standpoint? Most other things can already be
> controlled via pluginManagement/dependencyManagement...although it
> doesn't stop someone from overriding at a local pom level.  
>
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 14, 2007 9:56 PM
> To: Maven Developers List
> Subject: Re: Control of maven using prerequisites
>
>
> On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:
>
>   
>> Now that 2.0.5 is out and more frequent releases are expected, I think
>> that http://jira.codehaus.org/browse/MNG-2423 is even more important.
>> Currently the prerequisites value is not inherited and thus we  
>> can't use
>> it in a company "super-pom" to enforce a minimum Maven version. My
>> workaround is to create an empty plugin that has a prereq and include
>> that in the super-pom. This seems kludgey an kind of unnecessary since
>> there is a field in the pom to do this...it just only applies if  
>> defined
>> in each child pom or when building from a reactor that contains it. Is
>> there any chance this can get bumped to 2.0.6? I'm willing to try and
>> submit a patch I could get a pointer where to look.
>>
>> 
>
> The prereq is specifically for plugins, or other tools, that need a  
> specific version of Maven. It was not meant as a means of enforcement  
> for your development environment. Trying to mix these concerns would  
> cause problems.
>
> I think what you need is a plugin that runs in the validate phase  
> (call it the Enforcer Plugins :-) that checks things like jdk  
> version, mvn version, operating system or whatever else you might  
> want. Configure this in your parent POM and then you're all set.
>
> Jason.
>
>   
>> Thanks,
>>
>> Brian
>>
>> 
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Control of maven using prerequisites

[Brian E. Fox]

Actually I was talking about specifying other plugin/dependency plugins
to be enforced but I see your point. How would we make it not possible
to override in a child? Using a static value to store previously entered
config?

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 10:37 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites


On 14 Feb 07, at 10:28 PM 14 Feb 07, Brian E. Fox wrote:

> So the initial feature list for the "maven-enforcer-plugin" is:
> OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
> Configuration Management standpoint? Most other things can already be
> controlled via pluginManagement/dependencyManagement...although it
> doesn't stop someone from overriding at a local pom level.
>

Maybe this is a new flavor of plugin that can't be reconfigured or  
have any other configurations merged. Not sure if you could  
categorically state you want X, Y, and Z for your entire system but  
programmatically we could effectively make it impossible to change.

Jason.

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 14, 2007 9:56 PM
> To: Maven Developers List
> Subject: Re: Control of maven using prerequisites
>
>
> On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:
>
>> Now that 2.0.5 is out and more frequent releases are expected, I  
>> think
>> that http://jira.codehaus.org/browse/MNG-2423 is even more important.
>> Currently the prerequisites value is not inherited and thus we
>> can't use
>> it in a company "super-pom" to enforce a minimum Maven version. My
>> workaround is to create an empty plugin that has a prereq and include
>> that in the super-pom. This seems kludgey an kind of unnecessary  
>> since
>> there is a field in the pom to do this...it just only applies if
>> defined
>> in each child pom or when building from a reactor that contains  
>> it. Is
>> there any chance this can get bumped to 2.0.6? I'm willing to try and
>> submit a patch I could get a pointer where to look.
>>
>
> The prereq is specifically for plugins, or other tools, that need a
> specific version of Maven. It was not meant as a means of enforcement
> for your development environment. Trying to mix these concerns would
> cause problems.
>
> I think what you need is a plugin that runs in the validate phase
> (call it the Enforcer Plugins :-) that checks things like jdk
> version, mvn version, operating system or whatever else you might
> want. Configure this in your parent POM and then you're all set.
>
> Jason.
>
>>
>>
>> Thanks,
>>
>> Brian
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven banner?

[Jason Dillon]

What happened to the banner when executing Maven?  I'm glad its not  
there by default, but I'd like to turn it on for remote builds so  
that my logs capture what version of Maven was used.


Maybe a '--banner' flag or something?  Or maybe a new goal on the  
help plugin, to show maven version, and some settings like os and  
java version fluff?


--jason

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Control of maven using prerequisites

[Jason van Zyl]

On 14 Feb 07, at 10:28 PM 14 Feb 07, Brian E. Fox wrote:


So the initial feature list for the "maven-enforcer-plugin" is:
OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
Configuration Management standpoint? Most other things can already be
controlled via pluginManagement/dependencyManagement...although it
doesn't stop someone from overriding at a local pom level.



Maybe this is a new flavor of plugin that can't be reconfigured or  
have any other configurations merged. Not sure if you could  
categorically state you want X, Y, and Z for your entire system but  
programmatically we could effectively make it impossible to change.


Jason.


-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 9:56 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites


On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:

Now that 2.0.5 is out and more frequent releases are expected, I  
think

that http://jira.codehaus.org/browse/MNG-2423 is even more important.
Currently the prerequisites value is not inherited and thus we
can't use
it in a company "super-pom" to enforce a minimum Maven version. My
workaround is to create an empty plugin that has a prereq and include
that in the super-pom. This seems kludgey an kind of unnecessary  
since

there is a field in the pom to do this...it just only applies if
defined
in each child pom or when building from a reactor that contains  
it. Is

there any chance this can get bumped to 2.0.6? I'm willing to try and
submit a patch I could get a pointer where to look.



The prereq is specifically for plugins, or other tools, that need a
specific version of Maven. It was not meant as a means of enforcement
for your development environment. Trying to mix these concerns would
cause problems.

I think what you need is a plugin that runs in the validate phase
(call it the Enforcer Plugins :-) that checks things like jdk
version, mvn version, operating system or whatever else you might
want. Configure this in your parent POM and then you're all set.

Jason.




Thanks,

Brian




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: License for POM files

[Deepak Bhole]

On Tue, 2007-02-13 at 12:21 -0800, Carlos Sanchez wrote:
> The license should be inside the pom  section, or in the
> maven1 repo in the .license files
> 

Very few of the poms I am seeing have licenses. For example, even the
critical plexus ones don't have one:

http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-8/plexus-archiver-1.0-alpha-8.pom

In many cases, it it hard to tell who wrote the file. Like the above
file for instance, I don't know if it was written by the plexus guys (in
which case that license applies), or if someone from maven side wrote it
(APL in that case)...

Deepak


> On 2/13/07, Deepak Bhole <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > What license are the pom files in the maven2 repository
> > (repo1.maven.org/maven2) under? We need to know if we are allowed to
> > redistribute those poms with Fedora.
> >
> > Thanks,
> > Deepak
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Control of maven using prerequisites

[Brian E. Fox]

So the initial feature list for the "maven-enforcer-plugin" is:
OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
Configuration Management standpoint? Most other things can already be
controlled via pluginManagement/dependencyManagement...although it
doesn't stop someone from overriding at a local pom level.  

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 9:56 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites


On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:

> Now that 2.0.5 is out and more frequent releases are expected, I think
> that http://jira.codehaus.org/browse/MNG-2423 is even more important.
> Currently the prerequisites value is not inherited and thus we  
> can't use
> it in a company "super-pom" to enforce a minimum Maven version. My
> workaround is to create an empty plugin that has a prereq and include
> that in the super-pom. This seems kludgey an kind of unnecessary since
> there is a field in the pom to do this...it just only applies if  
> defined
> in each child pom or when building from a reactor that contains it. Is
> there any chance this can get bumped to 2.0.6? I'm willing to try and
> submit a patch I could get a pointer where to look.
>

The prereq is specifically for plugins, or other tools, that need a  
specific version of Maven. It was not meant as a means of enforcement  
for your development environment. Trying to mix these concerns would  
cause problems.

I think what you need is a plugin that runs in the validate phase  
(call it the Enforcer Plugins :-) that checks things like jdk  
version, mvn version, operating system or whatever else you might  
want. Configure this in your parent POM and then you're all set.

Jason.

>
>
> Thanks,
>
> Brian
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Control of maven using prerequisites

[Jason van Zyl]

On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:


Now that 2.0.5 is out and more frequent releases are expected, I think
that http://jira.codehaus.org/browse/MNG-2423 is even more important.
Currently the prerequisites value is not inherited and thus we  
can't use

it in a company "super-pom" to enforce a minimum Maven version. My
workaround is to create an empty plugin that has a prereq and include
that in the super-pom. This seems kludgey an kind of unnecessary since
there is a field in the pom to do this...it just only applies if  
defined

in each child pom or when building from a reactor that contains it. Is
there any chance this can get bumped to 2.0.6? I'm willing to try and
submit a patch I could get a pointer where to look.



The prereq is specifically for plugins, or other tools, that need a  
specific version of Maven. It was not meant as a means of enforcement  
for your development environment. Trying to mix these concerns would  
cause problems.


I think what you need is a plugin that runs in the validate phase  
(call it the Enforcer Plugins :-) that checks things like jdk  
version, mvn version, operating system or whatever else you might  
want. Configure this in your parent POM and then you're all set.


Jason.




Thanks,

Brian




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Subscription: Outstanding Repository Maintenance: Uploads

[jira]

Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (23 issues)
Subscriber: mavendevlist


Key Summary
MAVENUPLOAD-1220Upload mx4j 3.0.2
http://jira.codehaus.org/browse/MAVENUPLOAD-1220
MAVENUPLOAD-1384Please upload JODConverter 2.1.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1384
MAVENUPLOAD-1374Dozer is a powerful, yet simple Java Bean to Java Bean mapper 
that recursively copies data from one object to another. 
http://jira.codehaus.org/browse/MAVENUPLOAD-1374
MAVENUPLOAD-1337Upload of latest Findbugs (v. 1.1.3) artifacts to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-1337
MAVENUPLOAD-1362Upload tapestry-flash to central repo
http://jira.codehaus.org/browse/MAVENUPLOAD-1362
MAVENUPLOAD-1361Upload tapestry-prop 1.0.0 to Central repo
http://jira.codehaus.org/browse/MAVENUPLOAD-1361
MAVENUPLOAD-1355Upload Core JSF Validator (commons validator integration)
http://jira.codehaus.org/browse/MAVENUPLOAD-1355
MAVENUPLOAD-1346New IzPack jar's
http://jira.codehaus.org/browse/MAVENUPLOAD-1346
MAVENUPLOAD-1282PMD 3.9 bundle
http://jira.codehaus.org/browse/MAVENUPLOAD-1282
MAVENUPLOAD-1307XML Bind Builder [Ant]
http://jira.codehaus.org/browse/MAVENUPLOAD-1307
MAVENUPLOAD-1306XML Bind Generator
http://jira.codehaus.org/browse/MAVENUPLOAD-1306
MAVENUPLOAD-1308XML Bind Builder [Maven]
http://jira.codehaus.org/browse/MAVENUPLOAD-1308
MAVENUPLOAD-1305XML Bind Runtime
http://jira.codehaus.org/browse/MAVENUPLOAD-1305
MAVENUPLOAD-1284upload new artifact to The Central Repository
http://jira.codehaus.org/browse/MAVENUPLOAD-1284
MAVENUPLOAD-1264UrlRewriteFilter 2.6
http://jira.codehaus.org/browse/MAVENUPLOAD-1264
MAVENUPLOAD-1267Upload of novell jldap
http://jira.codehaus.org/browse/MAVENUPLOAD-1267
MAVENUPLOAD-1149Upload jboss-seam-ui-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1149
MAVENUPLOAD-1148Upload jboss-seam-debug-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1148
MAVENUPLOAD-1147Upload jboss-seam-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1147
MAVENUPLOAD-1130Rhino js-1.5R4.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1130
MAVENUPLOAD-1128Rhino js-1.5R3
http://jira.codehaus.org/browse/MAVENUPLOAD-1128
MAVENUPLOAD-1129Rhino js-1.5R4-RC3
http://jira.codehaus.org/browse/MAVENUPLOAD-1129
MAVENUPLOAD-976Please upload SUN Java 1.2 rutime 
http://jira.codehaus.org/browse/MAVENUPLOAD-976


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

[jira]

Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (41 issues)
Subscriber: mavendevlist


Key Summary
MEV-499 Latest version of clover plugin in maven.metadata.xml
http://jira.codehaus.org/browse/MEV-499
MEV-498 javax.xml.ws:jaxws-api:2.1 is bad
http://jira.codehaus.org/browse/MEV-498
MEV-36  Exo POM(s) missing dependency versions
http://jira.codehaus.org/browse/MEV-36
MEV-483 Still invalid deps in 3.2.1, 3.2.2, 3.2.3, 3.2.4
http://jira.codehaus.org/browse/MEV-483
MEV-479 Invalid POI POM
http://jira.codehaus.org/browse/MEV-479
MEV-478 jakarta-poi requires commons-lang as dependency
http://jira.codehaus.org/browse/MEV-478
MEV-457 Geronimo jar fails to download
http://jira.codehaus.org/browse/MEV-457
MEV-352 Relocate cvslib in netbeans groupId to cvsclient in org.netbeans.lib
http://jira.codehaus.org/browse/MEV-352
MEV-427 relocate ehcache:ehcache to net.sf.ehcache
http://jira.codehaus.org/browse/MEV-427
MEV-471 javax.xml:jsr173:1.0 should be relocated to 
javax.xml.bind:jsr173_api:1.0
http://jira.codehaus.org/browse/MEV-471
MEV-469 jaxb-api available with two different groupIds
http://jira.codehaus.org/browse/MEV-469
MEV-375 Relocate xpp to xpp3
http://jira.codehaus.org/browse/MEV-375
MEV-173 xmlpull JARs exist in two different places on ibiblio
http://jira.codehaus.org/browse/MEV-173
MEV-459 Velocity should not depend on Velocity-dep
http://jira.codehaus.org/browse/MEV-459
MEV-443 Several projects have maven-metadata.xml files that are missing 
released versions
http://jira.codehaus.org/browse/MEV-443
MEV-461 Missing pom for commons-logging-api-1.1
http://jira.codehaus.org/browse/MEV-461
MEV-455 bad checksums on repo1.maven.org
http://jira.codehaus.org/browse/MEV-455
MEV-454 testng-spring has a invalid dependency on testng.
http://jira.codehaus.org/browse/MEV-454
MEV-450 plexus-velocity 1.1.2 includes invalid external snapshot 
repositories
http://jira.codehaus.org/browse/MEV-450
MEV-449 lucene 1.9.1 JAR is hosed.
http://jira.codehaus.org/browse/MEV-449
MEV-448 xmlrpc POM should include commons-codec
http://jira.codehaus.org/browse/MEV-448
MEV-441 Several projects have bad maven-metadata.xml files that are 
screwing up dependencies with version range feature
http://jira.codehaus.org/browse/MEV-441
MEV-20  clean up bad IDs in the repository
http://jira.codehaus.org/browse/MEV-20
MEV-436 JOTM 2.0.10 incorrectly specifies javax.resource/connector-1.0 it 
needs connector-1.5.
http://jira.codehaus.org/browse/MEV-436
MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded 
variables
http://jira.codehaus.org/browse/MEV-296
MEV-405 pom for cactus:cactus:13-1.7.2
http://jira.codehaus.org/browse/MEV-405
MEV-404 pom for cactus:cactus-ant:13-1.7.2
http://jira.codehaus.org/browse/MEV-404
MEV-401 Incoherences / duplication between javax.xml and com.sun.xml
http://jira.codehaus.org/browse/MEV-401
MEV-334 Stax POM points to an invalid XMLBeans dependency
http://jira.codehaus.org/browse/MEV-334
MEV-384 velocity 1.4 dependencies are wrong
http://jira.codehaus.org/browse/MEV-384
MEV-364 Fix dependencies of common-lang 1.0 (add test scope for junit)
http://jira.codehaus.org/browse/MEV-364
MEV-356 Missing dep on jboss-common in jbossmq-client & jnp-client 4.0.2
http://jira.codehaus.org/browse/MEV-356
MEV-351 xmlc-xerces-2.2.7.1.jar is unnecessary and  xmlc-apis.jar is 
required.
http://jira.codehaus.org/browse/MEV-351
MEV-330 WebWork 2.2.1 POM should list FreeMarker as a dependency since it's 
required for plain ol' JSPs
http://jira.codehaus.org/browse/MEV-330
MEV-325 Description of jaxb-api 1.0.1 is wrong
http://jira.codehaus.org/browse/MEV-325
MEV-320 Hibernate 3.1.x POMs pull in Sun jars
http://jira.codehaus.org/browse/MEV-320
MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype
http://jira.codehaus.org/browse/MEV-201
MEV-48  openejb poms
http://jira.codehaus.org/browse/MEV-48
MEV-45  Full list of poms that doesn't respect the m2 format
http://jira.codehaus.org/browse/MEV-45
MEV-33  XOM POM references xercesImpl v.2.2.1 which does not exist in repo
http://jira.codehaus.org/browse/MEV-33
MEV-31  XOM POM references xmlParserAPIs v2.6.1 which is not in the repo
http://jira.codehaus.org/browse/MEV-31


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add

Control of maven using prerequisites

[Brian E. Fox]

Now that 2.0.5 is out and more frequent releases are expected, I think
that http://jira.codehaus.org/browse/MNG-2423 is even more important.
Currently the prerequisites value is not inherited and thus we can't use
it in a company "super-pom" to enforce a minimum Maven version. My
workaround is to create an empty plugin that has a prereq and include
that in the super-pom. This seems kludgey an kind of unnecessary since
there is a field in the pom to do this...it just only applies if defined
in each child pom or when building from a reactor that contains it. Is
there any chance this can get bumped to 2.0.6? I'm willing to try and
submit a patch I could get a pointer where to look.

 

Thanks,

Brian

Re: JBoss Support

[Hilco Wijbenga]

On 2/14/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Hilco, the list is probably stripping attachments, so best thing to do
> is open a JIRA issue and attach your patch:
> http://jira.codehaus.org/browse/CONTINUUM


http://jira.codehaus.org/browse/CONTINUUM-1167

Re: [continuum] BUILD ERROR: Maven Archiver

[Jason van Zyl]

Thanks.

jason.

On 14 Feb 07, at 6:32 PM 14 Feb 07, Brett Porter wrote:


I've removed this since it was deleted from SVN.

On 15/02/2007, at 6:26 AM, [EMAIL PROTECTED] wrote:

Online report : http://maven.zones.apache.org/continuum/ 
buildResult.action?buildId=7314&projectId=239

Build statistics:
  State: Error
  Previous State: Ok
  Started at: Wed, 14 Feb 2007 19:26:14 +
  Finished at: Wed, 14 Feb 2007 19:26:16 +
  Total time: 2s
  Build Trigger: Schedule
  Build Number: 0
  Exit code: 0
  Building machine hostname: maven.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_10(Sun Microsystems Inc.)

* 
***

SCM Changes:
* 
***

No files changed

* 
***

SCM Changes since last success:
* 
***
* 
***

Dependencies Changes:
* 
***

No dependencies changed

* 
***

Build Error:
* 
***

Provider message: The svn command failed.
Command output:
- 
--

svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: Cannot replace a directory from within
- 
--





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [continuum] BUILD ERROR: Maven Archiver

[Brett Porter]

I've removed this since it was deleted from SVN.

On 15/02/2007, at 6:26 AM, [EMAIL PROTECTED] wrote:

Online report : http://maven.zones.apache.org/continuum/ 
buildResult.action?buildId=7314&projectId=239

Build statistics:
  State: Error
  Previous State: Ok
  Started at: Wed, 14 Feb 2007 19:26:14 +
  Finished at: Wed, 14 Feb 2007 19:26:16 +
  Total time: 2s
  Build Trigger: Schedule
  Build Number: 0
  Exit code: 0
  Building machine hostname: maven.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_10(Sun Microsystems Inc.)

** 
**

SCM Changes:
** 
**

No files changed

** 
**

SCM Changes since last success:
** 
**
** 
**

Dependencies Changes:
** 
**

No dependencies changed

** 
**

Build Error:
** 
**

Provider message: The svn command failed.
Command output:
-- 
-

svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: Cannot replace a directory from within
-- 
-





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven 2.0.5 Released

[Jörg Schaible]

Congrats! Really waited long for this. But I know the huge effort and work
behind this  - so a biig THANK YOU GUYS!

- Jörg

Jason van Zyl wrote:

> The Maven team would like to announce the release of Maven 2.0.5.
> 
> You can find the roadmap for the release here:
> 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
> order=DESC
> 
> The release notes can be found here:
> 
> http://maven.apache.org/release-notes.html
> 
> And you can download it from here:
> 
> http://maven.apache.org/download.html
> 
> Thanks,
> 
> The Maven Apache Team!



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] release maven-rar-plugin 2.2

[Arnaud HERITIER]

+1

Arnaud

On 2/14/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:


+1

Vincent

2007/2/14, Stephane Nicoll <[EMAIL PROTECTED]>:
> +1
>
> Stéphane
>
> On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
> > Hello, the 2.2 release of the maven-rar-plugin has been pending for
> > many months now.  There are a few key bugs fixed in this release:
> >
> > Release Notes - Maven 2.x Rar Plugin - Version 2.2
> >
> > ** Bug
> >  * [MRAR-8] - Rar plugin includes files from rarSourceDirectory
> > in the generated rar
> >  * [MRAR-13] - .svn dirs are included in the rar package
> >
> > ** Improvement
> >  * [MRAR-5] - Move the description of the mojo from @description
> > to the top of the class's comment block
> >
> > ** Test
> >  * [MRAR-6] - Create tests for Rar plugin using test harness
plugin
> >
> > The staged artifacts are here:
> >
> >  http://people.apache.org/~jvanzyl/staging/maven-rar-plugin/
> >
> > Please vote :-)
> >
> > --jason
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven 2.0.5 Released

[Jason Dillon]

Rejoice!

--jason


On Feb 14, 2007, at 1:53 PM, Jason van Zyl wrote:


The Maven team would like to announce the release of Maven 2.0.5.

You can find the roadmap for the release here:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


The release notes can be found here:

http://maven.apache.org/release-notes.html

And you can download it from here:

http://maven.apache.org/download.html

Thanks,

The Maven Apache Team!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven 2.0.5 Released

[Jason van Zyl]

The Maven team would like to announce the release of Maven 2.0.5.

You can find the roadmap for the release here:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC


The release notes can be found here:

http://maven.apache.org/release-notes.html

And you can download it from here:

http://maven.apache.org/download.html

Thanks,

The Maven Apache Team!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JBoss Support

[Tilman.Rossmy]

Thanx Wendy...but doesn't really help...the exception I get depends on
the JBoss version...with 4.0.1SP1 I get:

ERROR: invalid console appender config detected, console stream is
looping

Found this in the JBoss Forum:
"Fixed it - my application was configuring log4j as well as Jboss.
Removing my code fixes the issue."
So my question:
Which class configures log4j in the Continuum stack?


-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 6:53 PM
To: continuum-dev@maven.apache.org
Subject: Re: JBoss Support

On 2/14/07, Tilman Rossmy <[EMAIL PROTECTED]> wrote:
> Hi Hilco! Can't find no jboss-web.xml in this post, but it's just what

> I need right now, so maybe you can post the xml? Thanx Tilman

This might help...
http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+JBoss

Hilco, the list is probably stripping attachments, so best thing to do
is open a JIRA issue and attach your patch:
http://jira.codehaus.org/browse/CONTINUUM

--
Wendy

Re: javamail 1.4 in central maven repo

[Carlos Sanchez]

the rule of thumb is
- if it's different to what they provide in their web page complain to US
- if it's the same, complain to THEM

On 2/14/07, Wayne Fay <[EMAIL PROTECTED]> wrote:

Tom, this isn't really the right place for this (and I'm not even in
the Maven Dev team), but I'll go ahead and respond all the same.
Normally you might report these kinds of issues through JIRA, in the
MEV (Maven Evangelism) component:
http://jira.codehaus.org/browse/MEV

The Maven team is only indirectly involved with the majority of
artifacts available in the Maven repo. The development group who
created the artifact is ultimately responsible for things like this.

In this particular case, I think you should open a bug with the
Glassfish team under the mail component:
https://glassfish.dev.java.net/javaee5/mail/

It seems like they are the owners of this artifact, see the pom:
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom

Wayne

On 2/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi.
>
>
>
> I'm not really sure if this is the correct place to contact regarding
> the maven repo contents but lets try. To me it looks like the javamail
> (javax.mail) 1.4 package in the central maven repository
> (http://repo1.maven.org/maven2) is missing the com.sun.mail.dsn package
> which should be part of the javamail release .. am I completely lost
> here?
>
>
>
> Thanks and apologies if this is the wrong place to contact.
>
>
>
> BR,
>
> Tom
>
>
>
> --
>
> Tom Andersson
>
> Accenture Technology Solutions
>
>  [EMAIL PROTECTED]
> 
>
> +358-40-7725180
>
>
>
>
>
> This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in error, 
please notify the sender immediately and delete the original.  Any other use of 
the email by you is prohibited.
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JBoss Support

[Wendy Smoak]

On 2/14/07, Tilman Rossmy <[EMAIL PROTECTED]> wrote:

Hi Hilco! Can't find no jboss-web.xml in this post, but it's just what I need
right now, so maybe you can post the xml? Thanx Tilman


This might help...
http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+JBoss

Hilco, the list is probably stripping attachments, so best thing to do
is open a JIRA issue and attach your patch:
http://jira.codehaus.org/browse/CONTINUUM

--
Wendy

Re: JBoss Support

[Tilman Rossmy]

Hi Hilco! Can't find no jboss-web.xml in this post, but it's just what I need 
right now, so maybe you can post the xml? Thanx Tilman

How to customize the Snapshot pattern?

[Alexis Midon]

Hi all,

Here is my problem: I would like to customize the Snapshot pattern.

The reason is that my maven project is a small part of a bigger project. The
global continious build generates a build-id I want to use as the snapshot
identifier.
So that my artifacts and all others "external" components are tagged in the
same way.

I ckecked the maven code but didn't find anything interesting. Snapshot is
not an interface, so custom implementations cannot be provided :(
Moreover using a timestamp instead of a specific class/interface is a real
constraint because custom Comparator couldn't be implemented to compare
snapshots.

I tried to use the  tag by appending my build-id, but
unfortunately the final name is not exported to repositories.

So it seems I had reached an impasse, except if one of you has a great
idea!!

Thanks in advance for your help.

Alexis

Re: javamail 1.4 in central maven repo

[Wayne Fay]

Tom, this isn't really the right place for this (and I'm not even in
the Maven Dev team), but I'll go ahead and respond all the same.
Normally you might report these kinds of issues through JIRA, in the
MEV (Maven Evangelism) component:
http://jira.codehaus.org/browse/MEV

The Maven team is only indirectly involved with the majority of
artifacts available in the Maven repo. The development group who
created the artifact is ultimately responsible for things like this.

In this particular case, I think you should open a bug with the
Glassfish team under the mail component:
https://glassfish.dev.java.net/javaee5/mail/

It seems like they are the owners of this artifact, see the pom:
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom

Wayne

On 2/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Hi.



I'm not really sure if this is the correct place to contact regarding
the maven repo contents but lets try. To me it looks like the javamail
(javax.mail) 1.4 package in the central maven repository
(http://repo1.maven.org/maven2) is missing the com.sun.mail.dsn package
which should be part of the javamail release .. am I completely lost
here?



Thanks and apologies if this is the wrong place to contact.



BR,

Tom



--

Tom Andersson

Accenture Technology Solutions

 [EMAIL PROTECTED]


+358-40-7725180





This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: More control over what WARNING messages are displayed

[Brian E. Fox]

I wrote this one eons ago that is related:
http://jira.codehaus.org/browse/MNG-1974 

-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Tuesday, February 13, 2007 11:28 PM
To: Maven Developers List
Subject: Re: More control over what WARNING messages are displayed

On Feb 13, 2007, at 5:51 PM, Barrie Treloar wrote:

> On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
>> Any comments from the Maven developers on this one?
>>
>> I really think all these WARNING messages are more harmful than 
>> useful... running a build thats all I see when I glance at the 
>> console.  They really make it much more harder than really needed to 
>> _see_ what is really going on.
>>
>> That, and if you need to add a few more repos to pick up artifacts, 
>> the output of mvn due to all of these WARNING messages increases 
>> significantly.  Logs end up as 80% WARNING, 20% actual build related 
>> output.
>
> I think it would be nice to do this for all the reasons you have 
> listed.
>
> Is there a JIRA issue created for it yet?

Not sure if one was created yet, need to look...

--jason



-
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Filtering used by resources plugin

[Daniel Kulp]

On Wednesday 14 February 2007 00:52, Jason van Zyl wrote:
> On 13 Feb 07, at 11:14 PM 13 Feb 07, Jason Dillon wrote:
> > Is the code used to filter w/properties used by the resources
> > plugin easily accessible by other plugins?
>
> No.
>
> Brian Topping tried to separate out the logic into a component. It's
> definitely needed in the sources and war plugin so that the behavior
> is consistent.
>
> Jason.

And remote-resources plugin.   There's actually a couple TODO's in there 
related to this.   I should log those in JIRA.Off to JIRA.


-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: License for POM files

[Dan Tran]

I beleive all plexus poms, not even the root parent, contains the license
element.

According to Brett, I assume it is apache2 type license since it is in
repo1.  However
a written statement is even better.

-D


On 2/14/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:


Deepak Bhole wrote:
> Hi,
>
> What license are the pom files in the maven2 repository
> (repo1.maven.org/maven2) under? We need to know if we are allowed to
> redistribute those poms with Fedora.

They either have the license of the project in question (as they come
from the project) or they're written by us and thus (I assume) are
covered by the Apache Software License. Some of the poms are also
generated, but they are easy to spot.

--
Trygve


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name transformation

[Jochen Wiedmann]

On 2/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


What do you mean exactly by name transformation? Using finalName, or
how things are named moving to the local and remote repository?


The current use case is the xml-maven-plugin, which transforms a given
set of files into another set of files. The user would like the
transformed files to have a different extension, for example ".xml" ->
".pdf" (in case of using FOP as the transformer).

In the case of Ant a concept called FileMapper was developed to handle
such cases:

   http://ant.apache.org/manual/CoreTypes/mapper.html

My question is, whether there already exists such a thing in
Plexus/Maven and if not, whether there is interest to create it.


Thanks,

Jochen


--
How fast can a year go? As fast as your childs first year.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: [VOTE] Release Maven 2.0.5 (take 2)

[Marc Wilhelm]

+1
Works fine on my projects

Marc

-Ursprüngliche Nachricht-
Von: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 12. Februar 2007 05:33
An: Maven Developers List
Betreff: [VOTE] Release Maven 2.0.5 (take 2)


Hi,

The assemblies that people are interested in are staged here:

http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ 
maven-core/2.0.5/

Here is the JIRA roadmap:

http://jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/ 
order=DESC

+1

Thanks,

Jason.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

javamail 1.4 in central maven repo

[tom.andersson]

Hi.

 

I'm not really sure if this is the correct place to contact regarding
the maven repo contents but lets try. To me it looks like the javamail
(javax.mail) 1.4 package in the central maven repository
(http://repo1.maven.org/maven2) is missing the com.sun.mail.dsn package
which should be part of the javamail release .. am I completely lost
here?

 

Thanks and apologies if this is the wrong place to contact.

 

BR,

Tom

 

--

Tom Andersson

Accenture Technology Solutions

 [EMAIL PROTECTED]
 

+358-40-7725180

 



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

Re: More control over what WARNING messages are displayed

[Jason van Zyl]

On 14 Feb 07, at 4:41 AM 14 Feb 07, Barrie Treloar wrote:


There is no config file, we set the threshold programmatically. New
logger stuff in plexus will allow more domain like logging
configuration. But not in 2.0.x.


What logging system is used? Java Logging, Log4J, Apache?
(I haven't got around to looking at the code yet)



It's pluggable, but we just use a console logger now which avoids all  
the frameworks but we are going to make a base logging implementation  
(using our interfaces) using slf4j which does a good job of marrying  
all the frameworks together. That should take care of the commons- 
logging mess.



Is there a way to specify the log format string?


That we've exposed in Maven, no.


It would be handy to have the context in the output for development
purposes so you can track down the class and module that is outputting
the log.  I might add this to the JIRA issue.


There are probably issues that exist and we definitely have them  
plexus. Joakim was interested in doing the slf4j implemenation in  
Plexus so you might want to chat with him.


Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name transformation

[Jason van Zyl]

On 14 Feb 07, at 3:00 AM 14 Feb 07, Jochen Wiedmann wrote:


[Forwarding to [EMAIL PROTECTED], because I received no reply on [EMAIL 
PROTECTED]

Hi,

I currently have a patch for the xml-maven-plugin, which suggests the
following: The plugin currently reads a set of files and transforms
them. The result is stored in a different directoy. Currently there is
no possibility to transform the name. The patch suggests to make the
extension configurable.

IMO, name transformation is a general concept. For example, Ant does
handle it in a quite generic way. Is there something in Maven that I
might reuse? Surely other plugins might encounter similar topics.



What do you mean exactly by name transformation? Using finalName, or  
how things are named moving to the local and remote repository?


Jason.


Jochen

--
How fast can a year go? As fast as your childs first year.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: MRM-153 (archiva to handle relocation for maven1 clients)

[nicolas de loof]

I've attached a Path to return a "ProxiedArtifact" instead of a File from
ProxyRequestHandler
The test case has also be updated
The ProxiedDavServer can then update pathInfo and to return the expected
artifact.

Nico.



2007/2/14, Joakim Erdfelt <[EMAIL PROTECTED]>:


Or refactor the repository conversion routines a bit to expose the path
conversion routines. ;-)

Archiva is undergoing a lot of work right now.
Please keep us honest and get those jira's filed.

- Joakim

nicolas de loof wrote:
> I've reopened this issue as the DAV-based request (/repository/id)
> replacing
> the proxy-based request (/proxy/id) has broken this feature.
>
> As explained in Jira, the ProxiedDavServer doesn't use the result of the
> proxyRequestHandler.get() method invocation, that may have changed the
> target path. Solving this has two options :
>
> - build the path from the returned File (requires some
> getAbsolutePath().substring() that are not very clean). Perhaps there is
> methods to get the path of the artifact based on the File object ?
> - change proxyRequestHandler to return a path and not a File (or some
> composite object)
>
> What do you think would be better ?
>
> Nico.
>

Re: MRM-153 (archiva to handle relocation for maven1 clients)

[Joakim Erdfelt]

Or refactor the repository conversion routines a bit to expose the path
conversion routines. ;-)

Archiva is undergoing a lot of work right now.
Please keep us honest and get those jira's filed.

- Joakim

nicolas de loof wrote:
> I've reopened this issue as the DAV-based request (/repository/id)
> replacing
> the proxy-based request (/proxy/id) has broken this feature.
>
> As explained in Jira, the ProxiedDavServer doesn't use the result of the
> proxyRequestHandler.get() method invocation, that may have changed the
> target path. Solving this has two options :
>
> - build the path from the returned File (requires some
> getAbsolutePath().substring() that are not very clean). Perhaps there is
> methods to get the path of the artifact based on the File object ?
> - change proxyRequestHandler to return a path and not a File (or some
> composite object)
>
> What do you think would be better ?
>
> Nico.
>

Bug in compiler configuration, generated source root not passed on to compiler

[Jörn Guy Süß]

Hello,

I am just trying to set up a fairly simple task, the POM is attached at the
end. I have a parser gen (SableCC), which I run through ant to make
generated sources. It runs in the appropriate phase and works. I would like
to jar-package the result, which is the default.

Here is the catch:

The configuration for the compiler is correctly determined:

[DEBUG]   (f) compileSourceRoots = [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\src\main\java, C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\generated-sources\main\jav
a]

But when the compiler starts, it suddenly is down to:

[DEBUG] Source directories: [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\src\main\java]


I am using a V1.4, but I do not see why that should change anything.

IMHO this is pretty serious, but the JIRA tracking is so confusing that I
could not post it.

It looks like I will patch it and place my source in main/java, but that is
really ugly and I would like to do it right.


Jörn Guy Süß

Research Fellow

Room 350, General Purpose South Building (building 78) Division of Systems
and Software Engineering School of Information Technology and Electrical
Engineering The University of Queensland Queensland 4072 AUSTRALIA

Phone: +61 7 3365 2883; Fax: +61 7 3365 4999

email: [EMAIL PROTECTED]

TRACE SNIPPET, showing the error

[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' -->
[DEBUG]   (f) basedir = C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser
[DEBUG]   (f) buildDirectory = C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target
[DEBUG]   (f) classpathElements = [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\classes, C:\Documents and
Settings\jgsuess\.m2\repository\org\sablecc\sablecc\3.1\sablecc-3.1.jar,
C:\Documents and
Settings\jgsuess\.m2\repository\junit\junit\3.8.2\junit-3.8.2.jar]
[DEBUG]   (f) compileSourceRoots = [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\src\main\java, C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\generated-sources\main\jav
a]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) compilerVersion = 1.4
[DEBUG]   (f) debug = true
[DEBUG]   (f) executable = C:\j2sdk1.4.2_12\bin\javac
[DEBUG]   (f) fork = false
[DEBUG]   (f) includes = [generated-sources/main/java/**/*.java]
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory = C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\classes
[DEBUG]   (f) outputFileName = SMARTCat-parser-1.0-SNAPSHOT
[DEBUG]   (f) projectArtifact =
au.edu.uq.itee:SMARTCat-parser:jar:1.0-SNAPSHOT
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) source = 1.4
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) target = 1.4
[DEBUG]   (f) verbose = true
[DEBUG] -- end configuration --
[INFO] compiler:compile
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories: [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\src\main\java]
[DEBUG] Classpath: [C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\classes
 C:\Documents and
Settings\jgsuess\.m2\repository\org\sablecc\sablecc\3.1\sablecc-3.1.jar
 C:\Documents and
Settings\jgsuess\.m2\repository\junit\junit\3.8.2\junit-3.8.2.jar]
[DEBUG] Output directory: C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\classes
[INFO] Nothing to compile - all classes are up to date
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-resources-plugin:2.2:testResources' -->
[DEBUG]   (f) filters = []
[DEBUG]   (f) outputDirectory = C:\Documents and
Settings\jgsuess\workspace\SMARTCat.parser\target\test-classes
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (f) resources = [EMAIL PROTECTED]
[DEBUG] -- end configuration --





  4.0.0

  au.edu.uq.itee

  SMARTCat-parser

  SMARTCat parser built on sable

  1.0-SNAPSHOT

  http://itee.uq.edu.au/~mdavv

  

  junit

  junit

  3.8.2



  org.sablecc

  sablecc

  3.1

  

  

  
org.apache.maven.plugins

maven-compiler-plugin


  true

  true

  C:\j2sdk1.4.2_12\bin\javac

  1.4

  1.4

  1.4

  
generated-sources/main/java/**/*.java
  

  

  
maven-antrun-plugin


  
generate-sources


  

  



  

  
 
${project.build.directory}/generated-sources/main/java



  run

  



  
org.sablecc

sablecc

3.1
  

  
org.sablecc

sablecc-anttask

1.0.1
  

  

  





-
To unsubs

Re: [VOTE] release maven-rar-plugin 2.2

[Vincent Siveton]

+1

Vincent

2007/2/14, Stephane Nicoll <[EMAIL PROTECTED]>:

+1

Stéphane

On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Hello, the 2.2 release of the maven-rar-plugin has been pending for
> many months now.  There are a few key bugs fixed in this release:
>
> Release Notes - Maven 2.x Rar Plugin - Version 2.2
>
> ** Bug
>  * [MRAR-8] - Rar plugin includes files from rarSourceDirectory
> in the generated rar
>  * [MRAR-13] - .svn dirs are included in the rar package
>
> ** Improvement
>  * [MRAR-5] - Move the description of the mojo from @description
> to the top of the class's comment block
>
> ** Test
>  * [MRAR-6] - Create tests for Rar plugin using test harness plugin
>
> The staged artifacts are here:
>
>  http://people.apache.org/~jvanzyl/staging/maven-rar-plugin/
>
> Please vote :-)
>
> --jason
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: More control over what WARNING messages are displayed

[Barrie Treloar]

There is no config file, we set the threshold programmatically. New
logger stuff in plexus will allow more domain like logging
configuration. But not in 2.0.x.


What logging system is used? Java Logging, Log4J, Apache?
(I haven't got around to looking at the code yet)

Is there a way to specify the log format string?
It would be handy to have the context in the output for development
purposes so you can track down the class and module that is outputting
the log.  I might add this to the JIRA issue.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

MRM-153 (archiva to handle relocation for maven1 clients)

[nicolas de loof]

I've reopened this issue as the DAV-based request (/repository/id) replacing
the proxy-based request (/proxy/id) has broken this feature.

As explained in Jira, the ProxiedDavServer doesn't use the result of the
proxyRequestHandler.get() method invocation, that may have changed the
target path. Solving this has two options :

- build the path from the returned File (requires some
getAbsolutePath().substring() that are not very clean). Perhaps there is
methods to get the path of the artifact based on the File object ?
- change proxyRequestHandler to return a path and not a File (or some
composite object)

What do you think would be better ?

Nico.

Re: License for POM files

[Trygve Laugstøl]

Deepak Bhole wrote:

Hi,

What license are the pom files in the maven2 repository
(repo1.maven.org/maven2) under? We need to know if we are allowed to
redistribute those poms with Fedora.


They either have the license of the project in question (as they come
from the project) or they're written by us and thus (I assume) are
covered by the Apache Software License. Some of the poms are also 
generated, but they are easy to spot.


--
Trygve


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name transformation

[Jochen Wiedmann]

On 2/14/07, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:


the xml-maven-plugin is developped at mojo.codehaus.org
The correct list should be: user@mojo.codehaus.org or dev@mojo.codehaus.org

Had you though uploading your patch as a jira issue ? (
http://jira.codehaus.org/browse/MOJO)


Raphael, you get me wrong: I am the developer of the xml-maven-plugin
and have all required powers to apply the patch. My question is how to
approach it.

As I said, name transformation is a general concept. Ant handles it by
creating its so called "File Mappers". Rather than reenventing the
wheel, I'd like to reuse something existing and make the solution
flexible. The question is: Are there any such wheels? :-)


Thanks,

Jochen



--
How fast can a year go? As fast as your childs first year.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Name transformation

[Raphaël Piéroni]

Hi Joshen,

the xml-maven-plugin is developped at mojo.codehaus.org
The correct list should be: user@mojo.codehaus.org or dev@mojo.codehaus.org

Had you though uploading your patch as a jira issue ? (
http://jira.codehaus.org/browse/MOJO)
Raphaël

2007/2/14, Jochen Wiedmann <[EMAIL PROTECTED]>:


[Forwarding to [EMAIL PROTECTED], because I received no reply on [EMAIL 
PROTECTED]

Hi,

I currently have a patch for the xml-maven-plugin, which suggests the
following: The plugin currently reads a set of files and transforms
them. The result is stored in a different directoy. Currently there is
no possibility to transform the name. The patch suggests to make the
extension configurable.

IMO, name transformation is a general concept. For example, Ant does
handle it in a quite generic way. Is there something in Maven that I
might reuse? Surely other plugins might encounter similar topics.

Jochen

--
How fast can a year go? As fast as your childs first year.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Name transformation

[Jochen Wiedmann]

[Forwarding to [EMAIL PROTECTED], because I received no reply on [EMAIL 
PROTECTED]

Hi,

I currently have a patch for the xml-maven-plugin, which suggests the
following: The plugin currently reads a set of files and transforms
them. The result is stored in a different directoy. Currently there is
no possibility to transform the name. The patch suggests to make the
extension configurable.

IMO, name transformation is a general concept. For example, Ant does
handle it in a quite generic way. Is there something in Maven that I
might reuse? Surely other plugins might encounter similar topics.

Jochen

--
How fast can a year go? As fast as your childs first year.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]