date:20060131

Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060201.040001.war

Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060201.040001.txt

[jira] Updated: (MNG-1984) document optional dependencies and dependency exclusions

2006-01-31 Thread Allan Ramirez (JIRA)

 [ http://jira.codehaus.org/browse/MNG-1984?page=all ]

Allan Ramirez updated MNG-1984:
---

Attachment: guide-optional-and-exclusions.apt

> document optional dependencies and dependency exclusions
> 
>
>  Key: MNG-1984
>  URL: http://jira.codehaus.org/browse/MNG-1984
>  Project: Maven 2
> Type: Improvement

>   Components: Documentation: Guides
> Versions: 2.0.2
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation
>  Attachments: dependency-B.apt, dependency-C.apt, dependency-D.apt, 
> dependency.apt, guide-optional-and-exclusions.apt
>
> Original Estimate: 8 hours
>Time Spent: 13 hours
> Remaining: 0 minutes
>
> assemble questions and problems from the users list, and create documentation 
> for managing bad POM dependency data using optional dependencies and 
> dependency exclusions.
> Document in depth how these two features work, and how they impact users of 
> POMs (even if the exclusion is in a transitive dependency).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-695) Publish new testng release files to ibiblio

2006-01-31 Thread Jesse Kuhnert (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-695?page=comments#action_57494 ] 

Jesse Kuhnert commented on MAVENUPLOAD-695:
---

Oh wow, I hadn't realised that you had already updated it as well. I don't have 
all of the maven patches sitting on my computer at home so I'll be able to play 
with everything again tomorrow morning. (est) 

Thanks a ton for all the insightful help! 

> Publish new testng release files to ibiblio
> ---
>
>  Key: MAVENUPLOAD-695
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-695
>  Project: maven-upload-requests
> Type: Task

> Reporter: Jesse Kuhnert
> Assignee: Carlos Sanchez
>  Attachments: testng-4.4.7-jdk14-bundle.jar, testng-4.4.7-jdk15-bundle.jar
>
>
> This is a new ibiblio addition. The bundle jars aren't actually available on 
> a normal public facing website (yet), but are attached to the issue 
> referenced in the bundle url.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-695) Publish new testng release files to ibiblio

2006-01-31 Thread Jesse Kuhnert (JIRA)

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-695?page=all ]
 
Jesse Kuhnert closed MAVENUPLOAD-695:
-

Resolution: Fixed

> Publish new testng release files to ibiblio
> ---
>
>  Key: MAVENUPLOAD-695
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-695
>  Project: maven-upload-requests
> Type: Task

> Reporter: Jesse Kuhnert
> Assignee: Carlos Sanchez
>  Attachments: testng-4.4.7-jdk14-bundle.jar, testng-4.4.7-jdk15-bundle.jar
>
>
> This is a new ibiblio addition. The bundle jars aren't actually available on 
> a normal public facing website (yet), but are attached to the issue 
> referenced in the bundle url.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[maven2 build trunk - SUCCESS - update] Wed Feb 1 03:00:00 GMT 2006

Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.03.tar.gz

Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.03.txt

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

[maven2 build branches/maven-2.0.x - SUCCESS - update] Wed Feb 1 02:45:00 GMT 2006

Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060201.024500.tar.gz

Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060201.024500.txt

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

[maven2 build trunk - SUCCESS - update] Wed Feb 1 02:30:00 GMT 2006

Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.023001.tar.gz

Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.023001.txt

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

[jira] Closed: (MNG-2029) Easy way to identify the working version of a plugin

 [ http://jira.codehaus.org/browse/MNG-2029?page=all ]
 
Brett Porter closed MNG-2029:
-

 Assign To: Brett Porter
Resolution: Won't Fix

this is the role of the help plugin. FAQd.

> Easy way to identify the working version of a plugin
> 
>
>  Key: MNG-2029
>  URL: http://jira.codehaus.org/browse/MNG-2029
>  Project: Maven 2
> Type: Improvement

>   Components: Plugins and Lifecycle
> Versions: 2.0.2
> Reporter: Patrick Lightbody
> Assignee: Brett Porter

>
>
> See chat conversation:
> (16:51:32) PSquad32: how do i tell what version of the install plugin i have?
> (16:52:03) brett: I think I fixed that for the deploy plugin, but not the 
> install one :(
> (16:52:10) brett: uh, good question.
> (16:52:56) brett: there should be an easier way, but its "ls 
> ~/.m2/repository/org/apache/maven/plugins/maven-install-plugin
> This came from when I was filling out MINSTALL-12 and wasn't sure which 
> version of the install plugin I was using. Perhaps "mvn -version install" 
> should return the default plugin version that would be used?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[maven2 build branches/maven-2.0.x - SUCCESS - checkout] Wed Feb 1 00:30:01 GMT 2006

Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060201.003001.tar.gz

Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060201.003001.txt

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

[jira] Created: (MNG-2029) Easy way to identify the working version of a plugin

2006-01-31 Thread Patrick Lightbody (JIRA)

Easy way to identify the working version of a plugin


 Key: MNG-2029
 URL: http://jira.codehaus.org/browse/MNG-2029
 Project: Maven 2
Type: Improvement

  Components: Plugins and Lifecycle  
Versions: 2.0.2
Reporter: Patrick Lightbody


See chat conversation:

(16:51:32) PSquad32: how do i tell what version of the install plugin i have?
(16:52:03) brett: I think I fixed that for the deploy plugin, but not the 
install one :(
(16:52:10) brett: uh, good question.
(16:52:56) brett: there should be an easier way, but its "ls 
~/.m2/repository/org/apache/maven/plugins/maven-install-plugin

This came from when I was filling out MINSTALL-12 and wasn't sure which version 
of the install plugin I was using. Perhaps "mvn -version install" should return 
the default plugin version that would be used?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MNG-2028) Attached mojos with the @aggregator tag can yield bad results in a multi-module project

2006-01-31 Thread John Didion (JIRA)

[ http://jira.codehaus.org/browse/MNG-2028?page=comments#action_57489 ] 

John Didion commented on MNG-2028:
--

Arg...my formatting got wiped out. The above overview of my project should look 
like this:

{noformat}
myproject
   tools
   libraries
  library1
  library2
  library3
{noformat}

> Attached mojos with the @aggregator tag can yield bad results in a 
> multi-module project
> ---
>
>  Key: MNG-2028
>  URL: http://jira.codehaus.org/browse/MNG-2028
>  Project: Maven 2
> Type: Bug

>   Components: Plugins and Lifecycle
> Versions: 2.0.2
> Reporter: John Didion

>
>
> I am using an attached version of the directory assembly plugin. I also have 
> a multi-module project that is several levels deep. Here's an overview
> myproject
>   tools
>   libraries
> library1
> library2
> library3
> If I configure the attached directory assembly plugin in library1's POM and 
> then run maven install from the myproject directory, I get errors about 
> dependency resolution because the presence of the @aggregator tag causes 
> maven to try and resolve dependencies for all modules in the entire project. 
> That means it's trying to resolve dependencies for library3, which is a 
> problem if library3 depends on library2, which hasn't been built yet.
> It makes sense to me that dependency resolution should only happen on the 
> sub-modules of the POM that configures the aggregator plugin, not all modules 
> in the project.
> If this makes sense then I think the fix would be in 
> DefaultPluginManager.executeMojo():
> if ( mojoDescriptor.isDependencyResolutionRequired() != null )
> {
> Collection projects;
> if ( mojoDescriptor.isAggregator() && project.getModules() != 
> null && !project.getModules().isEmpty())
> {
> List modules = project.getModules();
> projects = new ArrayList(modules.size());
> for (Iterator itr = modules.iterator(); itr.hasNext();) {
> String module = (String) itr.next();
> MavenProject moduleProject = // load the project for the 
> module...don't know exactly how to do this
> projects.add(moduleProject);
> }
> }
>  ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MINSTALL-12) Parameters should not be read-only

2006-01-31 Thread Patrick Lightbody (JIRA)

Parameters should not be read-only
--

 Key: MINSTALL-12
 URL: http://jira.codehaus.org/browse/MINSTALL-12
 Project: Maven 2.x Install Plugin
Type: Improvement

Versions: 2.1
 Environment: Maven 2.0.2 binary
Reporter: Patrick Lightbody


When running the following plugin (as a workaround due to a bug in maven):

  
  maven-install-plugin
  org.apache.maven.plugins
  
  
  validate
  
  
${basedir}/repo/opensymphony/webwork/2.2.1-SNAPSHOT/webwork-2.2.1-SNAPSHOT.jar
  opensymphony
  webwork
  2.2.1-SNAPSHOT
  
  
  install-file
  
  
  
  


I get this error:

"Error configuration: org.apache.maven.plugins:maven-install-plugin. Reason: 
ERROR: Cannot override read-only parameter: artifactId in goal: 
install:install-file"

Bret says:

(16:49:33) brett: odd
(16:49:55) brett: hrmph
(16:50:12) brett: they are all read-only, so can only be set on the command line
(16:50:15) brett: I don't know why that is
(16:50:28) PSquad32: should i open a feature request?
(16:50:44) brett: yes, please

So I did. Done.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MNG-2028) Attached mojos with the @aggregator tag can yield bad results in a multi-module project

2006-01-31 Thread John Didion (JIRA)

Attached mojos with the @aggregator tag can yield bad results in a multi-module 
project
---

 Key: MNG-2028
 URL: http://jira.codehaus.org/browse/MNG-2028
 Project: Maven 2
Type: Bug

  Components: Plugins and Lifecycle  
Versions: 2.0.2
Reporter: John Didion


I am using an attached version of the directory assembly plugin. I also have a 
multi-module project that is several levels deep. Here's an overview

myproject
  tools
  libraries
library1
library2
library3

If I configure the attached directory assembly plugin in library1's POM and 
then run maven install from the myproject directory, I get errors about 
dependency resolution because the presence of the @aggregator tag causes maven 
to try and resolve dependencies for all modules in the entire project. That 
means it's trying to resolve dependencies for library3, which is a problem if 
library3 depends on library2, which hasn't been built yet.

It makes sense to me that dependency resolution should only happen on the 
sub-modules of the POM that configures the aggregator plugin, not all modules 
in the project.

If this makes sense then I think the fix would be in 
DefaultPluginManager.executeMojo():

if ( mojoDescriptor.isDependencyResolutionRequired() != null )
{
Collection projects;

if ( mojoDescriptor.isAggregator() && project.getModules() != null 
&& !project.getModules().isEmpty())
{
List modules = project.getModules();
projects = new ArrayList(modules.size());
for (Iterator itr = modules.iterator(); itr.hasNext();) {
String module = (String) itr.next();
MavenProject moduleProject = // load the project for the 
module...don't know exactly how to do this
projects.add(moduleProject);
}
}
 ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MPARTIFACT-64) Move create-upload-bundle goal from repository-plugin to artifact

 [ http://jira.codehaus.org/browse/MPARTIFACT-64?page=all ]
 
Lukas Theussl closed MPARTIFACT-64:
---

 Resolution: Fixed
Fix Version: (was: 1.7.1)
 1.8

> Move create-upload-bundle goal from repository-plugin to artifact
> -
>
>  Key: MPARTIFACT-64
>  URL: http://jira.codehaus.org/browse/MPARTIFACT-64
>  Project: maven-artifact-plugin
> Type: Task

> Reporter: Lukas Theussl
> Assignee: Lukas Theussl
> Priority: Critical
>  Fix For: 1.8

>
>
> Needs to be done when repository gets demoted

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MNG-1919) If deploy with uniqueVersion=false (only generate file ended SNAPSHOT), this is not downloaded

 [ http://jira.codehaus.org/browse/MNG-1919?page=all ]
 
Brett Porter closed MNG-1919:
-

 Assign To: Brett Porter
Resolution: Duplicate

> If deploy with uniqueVersion=false (only generate file ended SNAPSHOT), this 
> is not downloaded
> --
>
>  Key: MNG-1919
>  URL: http://jira.codehaus.org/browse/MNG-1919
>  Project: Maven 2
> Type: Bug

> Versions: 2.0.1
>  Environment: all
> Reporter: Olivier Lamy
> Assignee: Brett Porter

>
>
> If I specify false in the pom.
> The generated file is only one ended with -SNAPSHOT (no problem is cool).
> But it's not downloaded by a client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false, cannot be downloaded by m2 as a snapshot

 [ http://jira.codehaus.org/browse/MNG-1908?page=all ]

Brett Porter updated MNG-1908:
--

Component: Artifacts and Repositories
  Summary: snapshots not deployed using m2, or deployed with uniqueVersion 
= false, cannot be downloaded by m2 as a snapshot  (was: M1 snapshots on legacy 
repos can not be used with m2)

> snapshots not deployed using m2, or deployed with uniqueVersion = false, 
> cannot be downloaded by m2 as a snapshot
> -
>
>  Key: MNG-1908
>  URL: http://jira.codehaus.org/browse/MNG-1908
>  Project: Maven 2
> Type: Bug

>   Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Priority: Critical
>  Fix For: 2.0.3

>
>
> It seems from the log info that m2 is trying to locate the artifact metadata 
> on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[maven2 build trunk - SUCCESS - checkout] Wed Feb 1 00:00:00 GMT 2006

Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.00.tar.gz

Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.00.txt

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

[jira] Closed: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2

2006-01-31 Thread Jason van Zyl (JIRA)

 [ http://jira.codehaus.org/browse/MNG-1980?page=all ]
 
Jason van Zyl closed MNG-1980:
--

Resolution: Fixed

Yes, it will be merged into the 2.0.x branch for the 2.0.3 release.

> "Duplicate project ID found" message with maven-artifact-ant-2.0.2
> --
>
>  Key: MNG-1980
>  URL: http://jira.codehaus.org/browse/MNG-1980
>  Project: Maven 2
> Type: Bug

>   Components: Ant tasks
> Versions: 2.0.2
> Reporter: Tomislav Stojcevich
> Assignee: Jason van Zyl
>  Fix For: 2.0.3

>
>
> The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2.
> [artifact:install] An error has occurred while processing the Maven artifact 
> tasks.
> [artifact:install]  Diagnosis:
> [artifact:install]
> [artifact:install] Unable to build project: 
> D:\Projects\Development\app\pom.xml
> [artifact:install] Duplicate project ID found in 
> D:\Projects\Development\app\pom.xml
> [artifact:install]
> BUILD FAILED
> D:\Projects\Development\app\ant\build.xml:166: Unable to build project: 
> D:\Projects\Development\app\pom.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-708) Hibernate Annotations 3.1 beta 8 upload request

2006-01-31 Thread Nathan Hamblen (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-708?page=comments#action_57486 ] 

Nathan Hamblen commented on MAVENUPLOAD-708:


Silly me, I read "public final draft" and thought it was final.

Bundle is updated with ejb version number 3.0-public-draft-20060118 , at the 
original link.

> Hibernate Annotations 3.1 beta 8 upload request
> ---
>
>  Key: MAVENUPLOAD-708
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-708
>  Project: maven-upload-requests
> Type: Task

> Reporter: Nathan Hamblen

>
>
> Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-695) Publish new testng release files to ibiblio

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-695?page=comments#action_57485 ] 

Carlos Sanchez commented on MAVENUPLOAD-695:


I have created this pom for testng

{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

4.0.0
org.testng
testng
jar
4.4.7
TestNG
http://testng.org
TestNG is a unit testing framework.


https://testng.dev.java.net/source/browse/testng




Apache License, Version 2.0
http://apache.org/licenses/LICENSE-2.0





junit
junit
3.8.1
runtime


qdox
qdox
1.5
runtime


bsh
bsh
2.0b1
runtime





jdk14

1.4



concurrent
concurrent
1.3.4
runtime






{code}

I think you can create the same profile thing in testng plugin or whatever 
you're doing, something like the following

{code}


jdk14

1.4



org.testng
testng
4.4.7
jdk14




jdk15

1.5



org.testng
testng
4.4.7
jdk15




{code}

and the user won't need to chose the jdk

> Publish new testng release files to ibiblio
> ---
>
>  Key: MAVENUPLOAD-695
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-695
>  Project: maven-upload-requests
> Type: Task

> Reporter: Jesse Kuhnert
> Assignee: Carlos Sanchez
>  Attachments: testng-4.4.7-jdk14-bundle.jar, testng-4.4.7-jdk15-bundle.jar
>
>
> This is a new ibiblio addition. The bundle jars aren't actually available on 
> a normal public facing website (yet), but are attached to the issue 
> referenced in the bundle url.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[vote] [m1] plugin releases

2006-01-31 Thread Lukas Theussl


Hi again,

I'd like to release the following m1 plugins for inclusion in m11b3:

[] maven-checkstyle-plugin-3.0
[] maven-clover-plugin-1.11
[] maven-dashboard-plugin-1.9
[] maven-jdepend-plugin-1.6
[] maven-jira-plugin-1.3


Please check the changes and jira reports on the plugin web pages below
for information on what has changed (and what hasn't).

+1 and 72h from me.

Cheers,
Lukas



http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-checkstyle-plugin/
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-clover-plugin/
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-dashboard-plugin/
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-jdepend-plugin/
http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/maven-jira-plugin/



maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 


-DgroupId=maven -DartifactId=maven-checkstyle-plugin -Dversion=3.0-SNAPSHOT

maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 


-DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.11-SNAPSHOT

maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 


-DgroupId=maven -DartifactId=maven-dashboard-plugin -Dversion=1.9-SNAPSHOT

maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 


-DgroupId=maven -DartifactId=maven-jdepend-plugin -Dversion=1.6-SNAPSHOT

maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 


-DgroupId=maven -DartifactId=maven-jira-plugin -Dversion=1.3-SNAPSHOT



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

[jira] Commented: (MAVENUPLOAD-686) Please, upload JXTA 2.3.6 to the ibiblio repository.

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-686?page=comments#action_57483 ] 

Carlos Sanchez commented on MAVENUPLOAD-686:


groupId should be org.jxta.platform

> Please, upload JXTA 2.3.6 to the ibiblio repository.
> 
>
>  Key: MAVENUPLOAD-686
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-686
>  Project: maven-upload-requests
> Type: Task

> Reporter: Loic Lefevre

>
>
> http://lolosav.free.fr/dev/jxta-2.3.6-bundle.jar
> JXTA peers create a virtual network where any peer can interact with other 
> peers and resources directly even when some of the peers and resources are 
> behind firewalls and NATs or are on different network transports.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-659) Upload AjaxTags library

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-659?page=all ]
 
Carlos Sanchez closed MAVENUPLOAD-659:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

> Upload AjaxTags library
> ---
>
>  Key: MAVENUPLOAD-659
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-659
>  Project: maven-upload-requests
> Type: Task

> Reporter: Olivier Lamy
> Assignee: Carlos Sanchez
>  Attachments: ajaxtags-1.1.5-bundle.jar, ajaxtags-1.1.5-bundle.jar, 
> ajaxtags-1.1.5.jar, project.xml
>
>
> Hi,
> Please upload the AjaxTags library version 1.1.5.
> The project url is located http://ajaxtags.sourceforge.net.
> Download link : 
> http://sourceforge.net/project/showfiles.php?group_id=140499&package_id=154180&release_id=370728
> This project is build with maven1.
> Thanks,

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-713) easymock 2.0

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-713?page=all ]
 
Carlos Sanchez closed MAVENUPLOAD-713:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

> easymock 2.0
> 
>
>  Key: MAVENUPLOAD-713
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-713
>  Project: maven-upload-requests
> Type: Task

> Reporter: Alexandre Poitras
> Assignee: Carlos Sanchez
>  Attachments: easymock-2.0-bundle.jar, easymock-2.0-bundle.jar, 
> easymock-2.0-bundle.zip
>
>
> The bundle comes as an attachment
> http://www.easymock.org/

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Re: Help: Removing DTD definition from file

2006-01-31 Thread Lukas Theussl

Have a look at the file tag of the jelly core library:
http://jakarta.apache.org/commons/jelly/tags.html

There are lots of examples of its use in the maven plugins.

-Lukas

Nascif Abousalh-Neto wrote:

Hi,

I am trying to port the DTD removal code from an XML file (coverage.xml from
the Cobertura code coverage tool) so that it can be parsed by a different
plugin.

The file goes like that:

http://cobertura.sourceforge.net/xml/coverage-02.dtd";>

C:/home/playpen/ips/Products/InventoryReplenishmentPlanning/IrpClient/Source/Java

When this file is parsed, even by a SAX parser, the second line causes an HTTP
request which fails when the machine is behind a corporate firewall. Somehow
Maven configuration for proxies does not affect this file (I would call that a
bug...)

I have seen it done in the snapshot plugin using code like this:

http://cobertura.sourceforge.net/xml/coverage-02.dtd";>', '')}"/>

But for the plugin I am working with, the input has to come from a file - the parsing is
done in a Java library, not by Jelly. So instead of calling "x:parse", I want
to save the contents to a file, and then pass the file name to the library.

How can I do that? I thought it would be simple but nothing I tried works. It seems that
"fileWithoutDTD" is actually empty, I can't pipe it to a file using "echo" or
"file". I just need to store the contents of a Jelly variable in a file - no translations, just
saving it.

Any help would be greatly appreciated.

Thanks,
Nascif

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

[jira] Commented: (MAVENUPLOAD-708) Hibernate Annotations 3.1 beta 8 upload request

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-708?page=comments#action_57482 ] 

Carlos Sanchez commented on MAVENUPLOAD-708:


Please be careful with version naming, the ejb spec distributed with hibernate 
annotations is a public draft, not 3.0.
Use version 3.0-public-draft-20060118 in hibernate-annotations pom (I already 
uploaded the right ejb pom)

> Hibernate Annotations 3.1 beta 8 upload request
> ---
>
>  Key: MAVENUPLOAD-708
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-708
>  Project: maven-upload-requests
> Type: Task

> Reporter: Nathan Hamblen

>
>
> Please upload.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Reopened: (MAVENUPLOAD-709) Upload extremecomponents 1.0.1-M4

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-709?page=all ]
 
Tomislav Stojcevich reopened MAVENUPLOAD-709:
-


The sources didn't seem to make it into the repository.

> Upload extremecomponents 1.0.1-M4
> -
>
>  Key: MAVENUPLOAD-709
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-709
>  Project: maven-upload-requests
> Type: Bug

> Reporter: Tomislav Stojcevich
> Assignee: Carlos Sanchez
>  Attachments: extremecomponents-1.0.1-M4-bundle.jar
>
>
> Upload new version.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=comments#action_57480 ] 

Tomislav Stojcevich commented on MAVENUPLOAD-712:
-

Ignore the jtidy, it was taken care of in MAVENUPLOAD-690

> Upload hibernate-tools-3.1.0.beta4
> --
>
>  Key: MAVENUPLOAD-712
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712
>  Project: maven-upload-requests
> Type: Bug

> Reporter: Tomislav Stojcevich
>  Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, 
> hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar, 
> jtidy-r8-21122004-bundle.jar
>
>
> Upload new version.
> Also attached is special version of jtidy that is distributed with the 
> package, the groupid is set to org.hibernate.hibernate-tools for this version 
> as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-712) Upload hibernate-tools-3.1.0.beta4

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=comments#action_57479 ] 

Carlos Sanchez commented on MAVENUPLOAD-712:


version in jtidy bundle includes "jtidy" string!

> Upload hibernate-tools-3.1.0.beta4
> --
>
>  Key: MAVENUPLOAD-712
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-712
>  Project: maven-upload-requests
> Type: Bug

> Reporter: Tomislav Stojcevich
>  Attachments: hibernate-tools-3.1.0.beta4-bundle.jar, 
> hibernate-tools-3.1.0.beta4-bundle.jar, jtidy-r8-21122004-bundle.jar, 
> jtidy-r8-21122004-bundle.jar
>
>
> Upload new version.
> Also attached is special version of jtidy that is distributed with the 
> package, the groupid is set to org.hibernate.hibernate-tools for this version 
> as suggested in MAVENUPOLAD-690 which was created for MAVENUPLOAD-691.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-714) Upload jericho-html-1.5-dev1.jar

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-714?page=all ]
 
Carlos Sanchez closed MAVENUPLOAD-714:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

> Upload jericho-html-1.5-dev1.jar
> 
>
>  Key: MAVENUPLOAD-714
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-714
>  Project: maven-upload-requests
> Type: Bug

> Reporter: Tomislav Stojcevich
> Assignee: Carlos Sanchez
>  Attachments: jericho-html-1.5-dev1-bundle.jar
>
>
> Upload jar.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Re: Fwd: [ANN] Apache JDO 2.0 beta released

2006-01-31 Thread Emmanuel Venisse


yes i think it's the correct groupId (http://www.jpox.org/docs/download.html)

Emmanuel

Carlos Sanchez a écrit :

Is it right to be in javax.jdo when the reference implementation seems
to be jpox?

On 1/31/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:


it is there : http://www.ibiblio.org/maven2/javax/jdo/jdo2-api/2.0-beta/

Thanks. I'll switch.

Emmanuel

Brett Porter a écrit :


we should switch to this - not sure if its in the repo yet.

- Brett

-- Forwarded message --
From: Craig L Russell <[EMAIL PROTECTED]>
Date: Feb 1, 2006 5:47 AM
Subject: [ANN] Apache JDO 2.0 beta released
To: general@db.apache.org
Cc: JDO Expert Group <[EMAIL PROTECTED]>, Apache JDO project



The Apache JDO project http://db.apache.org/jdo is pleased to announce
the release of Apache JDO 2.0 beta, a preview release of Apache JDO 2.0.
Apache JDO is a subproject of the Apache DB project.

JDO is a JCP standard interface for persistence of Java objects.
It is datastore-agnostic and supports relational and non-relational
databases. For details, please see http://jcp.org/en/jsr/detail?id=243

The Apache JDO project builds the JDO API jars used by application
programmers and the JDO TCK jars, used to verify compliance with
the specification. The Apache JDO project does not build an implementation
of JDO 2.0. The JDO 2.0 Reference Implementation is JPOX,
which is available via its own download: http://jpox.org

Apache JDO API and TCK are available as a source download from mirrors
http://www.apache.org/dyn/closer.cgi
/db/jdo/2.0-beta. The jar files are available in binary form as maven form
from mirrors /java-repository/javax.jdo and
/java-repository/org.apache.jdo

JDO 2.0 builds on the JDO 1 API. Applications built to use JDO 1 need only
to be recompiled to run with JDO 2.0.

Features in the JDO 2.0 release include:

- Standard mapping from objects to relational databases
- Multi-tier support without use of Data Transfer Objects
- Improved query support including projections and aggregates
- Stored queries in metadata
- Deletion by query
- Optimized fetching of object graphs without writing special queries
- Extensive List and Map support
- Lazy loading of large collections
- Better support for single-field primary keys
- Object lifecycle event monitoring
- Improved support for bidirectional relationships




Craig Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/jdo

408 276-5638 mailto:[EMAIL PROTECTED]

P.S. A good JDO? O, Gasp!

Re: Fwd: [ANN] Apache JDO 2.0 beta released

2006-01-31 Thread Brett Porter

Yes, its just the API jar.

- Brett

Carlos Sanchez wrote:
> Is it right to be in javax.jdo when the reference implementation seems
> to be jpox?
> 
> On 1/31/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>> it is there : http://www.ibiblio.org/maven2/javax/jdo/jdo2-api/2.0-beta/
>>
>> Thanks. I'll switch.
>>
>> Emmanuel
>>
>> Brett Porter a écrit :
>>> we should switch to this - not sure if its in the repo yet.
>>>
>>> - Brett
>>>
>>> -- Forwarded message --
>>> From: Craig L Russell <[EMAIL PROTECTED]>
>>> Date: Feb 1, 2006 5:47 AM
>>> Subject: [ANN] Apache JDO 2.0 beta released
>>> To: general@db.apache.org
>>> Cc: JDO Expert Group <[EMAIL PROTECTED]>, Apache JDO project
>>> 
>>>
>>>
>>> The Apache JDO project http://db.apache.org/jdo is pleased to announce
>>> the release of Apache JDO 2.0 beta, a preview release of Apache JDO 2.0.
>>> Apache JDO is a subproject of the Apache DB project.
>>>
>>> JDO is a JCP standard interface for persistence of Java objects.
>>> It is datastore-agnostic and supports relational and non-relational
>>> databases. For details, please see http://jcp.org/en/jsr/detail?id=243
>>>
>>> The Apache JDO project builds the JDO API jars used by application
>>> programmers and the JDO TCK jars, used to verify compliance with
>>> the specification. The Apache JDO project does not build an implementation
>>> of JDO 2.0. The JDO 2.0 Reference Implementation is JPOX,
>>> which is available via its own download: http://jpox.org
>>>
>>> Apache JDO API and TCK are available as a source download from mirrors
>>> http://www.apache.org/dyn/closer.cgi
>>> /db/jdo/2.0-beta. The jar files are available in binary form as maven form
>>> from mirrors /java-repository/javax.jdo and
>>> /java-repository/org.apache.jdo
>>>
>>> JDO 2.0 builds on the JDO 1 API. Applications built to use JDO 1 need only
>>> to be recompiled to run with JDO 2.0.
>>>
>>> Features in the JDO 2.0 release include:
>>>
>>> - Standard mapping from objects to relational databases
>>> - Multi-tier support without use of Data Transfer Objects
>>> - Improved query support including projections and aggregates
>>> - Stored queries in metadata
>>> - Deletion by query
>>> - Optimized fetching of object graphs without writing special queries
>>> - Extensive List and Map support
>>> - Lazy loading of large collections
>>> - Better support for single-field primary keys
>>> - Object lifecycle event monitoring
>>> - Improved support for bidirectional relationships
>>>
>>>
>>>
>>>
>>> Craig Russell
>>>
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>>
>>> 408 276-5638 mailto:[EMAIL PROTECTED]
>>>
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>>
>>
>

[jira] Commented: (MANTRUN-40) Properties defined in pom do not propagate to the antrun environment

2006-01-31 Thread Jason Dillon (JIRA)

[ http://jira.codehaus.org/browse/MANTRUN-40?page=comments#action_57478 ] 

Jason Dillon commented on MANTRUN-40:
-

If no fix shows up I can create a patch for it, but was hoping this issue would 
shed some light on the fix that jason mentioned.

> Properties defined in pom  do not propagate to the antrun 
> environment
> -
>
>  Key: MANTRUN-40
>  URL: http://jira.codehaus.org/browse/MANTRUN-40
>  Project: Maven 2.x Antrun Plugin
> Type: Improvement

> Reporter: Jason Dillon
> Priority: Critical

>
>
> Properties defined in pom  do not propagate to the antrun 
> environment.
> For example:
> {code}
> 
> foo
> 
> {code}
> Does *not* get propagate to Ant.  While properties defined within the pom 
> will resolve, the properties are not available as an Ant property.  So from 
> antrun:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo"/>
> {code}
> And then the Ant build.xml:
> {code}
> 
> 
> ${my.property}
> 
> 
> {code}
> The output will be:
> {noformat}
> [echo] ${my.property}
> {noformat}
> Instead of what it *should be*:
> {noformat}
> [echo] foo
> {noformat}
> The workaround is to delegate to a build.xml file with the ant task and 
> redefine each property that is needed:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo">
> 
> 
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-706) Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-706?page=all ]
 
Carlos Sanchez closed MAVENUPLOAD-706:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

Bundles uploaded WITHOUT sources. Source instrucitions are the same for maven 1 
and maven 2. You can give it a try for next version's requests

> Upload wicket-1.1.1-bundle.jar and wicket-extensions-1.1.1-bundle.jar
> -
>
>  Key: MAVENUPLOAD-706
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-706
>  Project: maven-upload-requests
> Type: Task

> Reporter: Martijn Dashorst
> Assignee: Carlos Sanchez
>  Attachments: wicket-1.1.1-bundle.jar
>
>
> http://wicket.sf.net/downloads/wicket-1.1.1-bundle.jar
> http://wicket.sf.net/downloads/wicket-extensions-1.1.1-bundle.jar
> http://wicket.sf.net
> http://wicket.sf.net/team-list.html
> Wicket is a Java web application framework that takes simplicity, separation 
> of concerns and ease of development to a whole new level. Wicket pages can be 
> mocked up, previewed and later revised using standard WYSIWYG HTML design 
> tools. Dynamic content processing and form handling is all handled in Java 
> code using a first-class component model backed by POJO data beans that can 
> easily be persisted using your favourite technology.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MANTRUN-40) Properties defined in pom do not propagate to the antrun environment

2006-01-31 Thread Jason Dillon (JIRA)

[ http://jira.codehaus.org/browse/MANTRUN-40?page=comments#action_57476 ] 

Jason Dillon commented on MANTRUN-40:
-

A brief chat w/jvl yesterday sounded like there was already a fix somewhere... 

But... bug/imporvement/task... I just need it fixed ;-)

> Properties defined in pom  do not propagate to the antrun 
> environment
> -
>
>  Key: MANTRUN-40
>  URL: http://jira.codehaus.org/browse/MANTRUN-40
>  Project: Maven 2.x Antrun Plugin
> Type: Improvement

> Reporter: Jason Dillon
> Priority: Critical

>
>
> Properties defined in pom  do not propagate to the antrun 
> environment.
> For example:
> {code}
> 
> foo
> 
> {code}
> Does *not* get propagate to Ant.  While properties defined within the pom 
> will resolve, the properties are not available as an Ant property.  So from 
> antrun:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo"/>
> {code}
> And then the Ant build.xml:
> {code}
> 
> 
> ${my.property}
> 
> 
> {code}
> The output will be:
> {noformat}
> [echo] ${my.property}
> {noformat}
> Instead of what it *should be*:
> {noformat}
> [echo] foo
> {noformat}
> The workaround is to delegate to a build.xml file with the ant task and 
> redefine each property that is needed:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo">
> 
> 
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-664) jlmenu 1.0

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-664?page=all ]
 
Carlos Sanchez closed MAVENUPLOAD-664:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

> jlmenu 1.0
> --
>
>  Key: MAVENUPLOAD-664
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-664
>  Project: maven-upload-requests
> Type: Task

> Reporter: Ofir Reichenberg
> Assignee: Carlos Sanchez
>  Attachments: jlmenu-1.0-bundle.jar, jlmenu-1.0-bundle.jar, 
> jlmenu-1.0-bundle.jar, jlmenu-1.0-bundle.jar
>
>
> http://jlmenu.sourceforge.net/jlmenu-1.0-bundle.jar
> JavaLayersMenu - tag library for web menus

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MANTRUN-40) Properties defined in pom do not propagate to the antrun environment

 [ http://jira.codehaus.org/browse/MANTRUN-40?page=all ]

Carlos Sanchez updated MANTRUN-40:
--

type: Improvement  (was: Bug)

I don't think this was never intended so it's a new feature, not a bug

> Properties defined in pom  do not propagate to the antrun 
> environment
> -
>
>  Key: MANTRUN-40
>  URL: http://jira.codehaus.org/browse/MANTRUN-40
>  Project: Maven 2.x Antrun Plugin
> Type: Improvement

> Reporter: Jason Dillon
> Priority: Critical

>
>
> Properties defined in pom  do not propagate to the antrun 
> environment.
> For example:
> {code}
> 
> foo
> 
> {code}
> Does *not* get propagate to Ant.  While properties defined within the pom 
> will resolve, the properties are not available as an Ant property.  So from 
> antrun:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo"/>
> {code}
> And then the Ant build.xml:
> {code}
> 
> 
> ${my.property}
> 
> 
> {code}
> The output will be:
> {noformat}
> [echo] ${my.property}
> {noformat}
> Instead of what it *should be*:
> {noformat}
> [echo] foo
> {noformat}
> The workaround is to delegate to a build.xml file with the ant task and 
> redefine each property that is needed:
> {code}
>  inheritAll="true" inheritRefs="true" target="foo">
> 
> 
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MANTRUN-40) Properties defined in pom do not propagate to the antrun environment

2006-01-31 Thread Jason Dillon (JIRA)

Properties defined in pom  do not propagate to the antrun 
environment
-

 Key: MANTRUN-40
 URL: http://jira.codehaus.org/browse/MANTRUN-40
 Project: Maven 2.x Antrun Plugin
Type: Bug

Reporter: Jason Dillon
Priority: Critical


Properties defined in pom  do not propagate to the antrun 
environment.

For example:

{code}

foo

{code}

Does *not* get propagate to Ant.  While properties defined within the pom will 
resolve, the properties are not available as an Ant property.  So from antrun:

{code}

{code}

And then the Ant build.xml:

{code}


${my.property}


{code}

The output will be:

{noformat}
[echo] ${my.property}
{noformat}

Instead of what it *should be*:

{noformat}
[echo] foo
{noformat}

The workaround is to delegate to a build.xml file with the ant task and 
redefine each property that is needed:

{code}



{code}


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-686) Please, upload JXTA 2.3.6 to the ibiblio repository.

2006-01-31 Thread Loic Lefevre (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-686?page=comments#action_57472 ] 

Loic Lefevre commented on MAVENUPLOAD-686:
--

okay, bundle has just been updated.

Cheers,
Loic

> Please, upload JXTA 2.3.6 to the ibiblio repository.
> 
>
>  Key: MAVENUPLOAD-686
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-686
>  Project: maven-upload-requests
> Type: Task

> Reporter: Loic Lefevre

>
>
> http://lolosav.free.fr/dev/jxta-2.3.6-bundle.jar
> JXTA peers create a virtual network where any peer can interact with other 
> peers and resources directly even when some of the peers and resources are 
> behind firewalls and NATs or are on different network transports.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2

[ http://jira.codehaus.org/browse/MNG-1980?page=comments#action_57467 ] 

Tomislav Stojcevich commented on MNG-1980:
--

I didn't have maven-project updated.  I assumed the change was in 
maven-artifact-ant.  You are correct, the message only appears in the 2.0.3 
version.

After rebuilding and testing, 2.0.3-SNAPSHOT still produces this error, 
2.1-SNAPSHOT seems to have corrected it.

Will it be fixed for 2.0.3 or must we wait until 2.1?  The "Fix Version/s" is 
currently set at 2.0.3 for this issue.

> "Duplicate project ID found" message with maven-artifact-ant-2.0.2
> --
>
>  Key: MNG-1980
>  URL: http://jira.codehaus.org/browse/MNG-1980
>  Project: Maven 2
> Type: Bug

>   Components: Ant tasks
> Versions: 2.0.2
> Reporter: Tomislav Stojcevich
> Assignee: Jason van Zyl
>  Fix For: 2.0.3

>
>
> The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2.
> [artifact:install] An error has occurred while processing the Maven artifact 
> tasks.
> [artifact:install]  Diagnosis:
> [artifact:install]
> [artifact:install] Unable to build project: 
> D:\Projects\Development\app\pom.xml
> [artifact:install] Duplicate project ID found in 
> D:\Projects\Development\app\pom.xml
> [artifact:install]
> BUILD FAILED
> D:\Projects\Development\app\ant\build.xml:166: Unable to build project: 
> D:\Projects\Development\app\pom.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MPDASHBOARD-28) Please sorth the report in alpha order

 [ http://jira.codehaus.org/browse/MPDASHBOARD-28?page=all ]
 
Lukas Theussl closed MPDASHBOARD-28:


 Resolution: Fixed
Fix Version: 1.9

> Please sorth the report in alpha order
> --
>
>  Key: MPDASHBOARD-28
>  URL: http://jira.codehaus.org/browse/MPDASHBOARD-28
>  Project: maven-dashboard-plugin
> Type: Improvement

> Reporter: Jon Strayer
> Priority: Minor
>  Fix For: 1.9

>
>
> When you have a lot of projects on the dashbord report (and currently we have 
> 34) the default sort makes it hard to find a specific project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MEV-319) geronimo-security POM references activeio 2.0-r118, which is not in the repository

 [ http://jira.codehaus.org/browse/MEV-319?page=all ]
 
Carlos Sanchez closed MEV-319:
--

 Assign To: Carlos Sanchez
Resolution: Fixed

It was badly converted from m1

> geronimo-security POM references activeio 2.0-r118, which is not in the 
> repository
> --
>
>  Key: MEV-319
>  URL: http://jira.codehaus.org/browse/MEV-319
>  Project: Maven Evangelism
> Type: Bug

>   Components: Dependencies
> Reporter: Jim Babka
> Assignee: Carlos Sanchez

>
>
> The geronimo-security POM calls for version 2.0-r118 of activeio:activeio, 
> but that version is not in the repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (SCM-84) Develop VSS Provider for Maven-SCM

2006-01-31 Thread Emmanuel Venisse (JIRA)

[ http://jira.codehaus.org/browse/SCM-84?page=comments#action_57460 ] 

Emmanuel Venisse commented on SCM-84:
-

I started the VSS provider with only the changelog command for now. I used 
partially the code provide in this patch.

> Develop VSS Provider for Maven-SCM
> --
>
>  Key: SCM-84
>  URL: http://jira.codehaus.org/browse/SCM-84
>  Project: Maven SCM
> Type: New Feature

>   Components: maven-scm-provider-vss
> Reporter: George Gastaldi
>  Attachments: maven-scm-provider-vss-unfinished.zip, 
> maven-scm-provider-vss.zip
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (MEV-319) geronimo-security POM references activeio 2.0-r118, which is not in the repository

2006-01-31 Thread Mike Perham (JIRA)

[ http://jira.codehaus.org/browse/MEV-319?page=comments#action_57458 ] 

Mike Perham commented on MEV-319:
-

I've just looked on www.ibiblio.org/maven/activeio/jars and there is an 
activeio-2.0-r118.jar in there which matches the version configured for 
geronimo 1.0.

Perhaps the m1 <-> m2 mirroring is broken somehow?



> geronimo-security POM references activeio 2.0-r118, which is not in the 
> repository
> --
>
>  Key: MEV-319
>  URL: http://jira.codehaus.org/browse/MEV-319
>  Project: Maven Evangelism
> Type: Bug

>   Components: Dependencies
> Reporter: Jim Babka

>
>
> The geronimo-security POM calls for version 2.0-r118 of activeio:activeio, 
> but that version is not in the repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MEV-319) geronimo-security POM references activeio 2.0-r118, which is not in the repository

2006-01-31 Thread Jim Babka (JIRA)

geronimo-security POM references activeio 2.0-r118, which is not in the 
repository
--

 Key: MEV-319
 URL: http://jira.codehaus.org/browse/MEV-319
 Project: Maven Evangelism
Type: Bug

  Components: Dependencies  
Reporter: Jim Babka


The geronimo-security POM calls for version 2.0-r118 of activeio:activeio, but 
that version is not in the repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MPCLOVER-50) Add support for span

 [ http://jira.codehaus.org/browse/MPCLOVER-50?page=all ]
 
Lukas Theussl closed MPCLOVER-50:
-

 Resolution: Fixed
Fix Version: 1.11

> Add support for span
> 
>
>  Key: MPCLOVER-50
>  URL: http://jira.codehaus.org/browse/MPCLOVER-50
>  Project: maven-clover-plugin
> Type: Improvement

> Versions: 1.10
> Reporter: Matt Read
> Assignee: Vincent Massol
> Priority: Minor
>  Fix For: 1.11

>
>
> Would it be possible add support for the span attribute of the appropriate 
> ant tasks? Currently I modify plugin.jelly each time I upgrade to a new 
> version by adding span="5h" to all the  tags and the 
>  tag.
> The reason being my Maven project delegates out to a number of legacy ant 
> scripts, each of which may run a clover-enabled task. Without the addition of 
> the span attribute, the reports do not include all of the results I want.
> If you want me to supply a patch to the plugin then please let me know.
> Matt.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2

2006-01-31 Thread Jason van Zyl (JIRA)

[ http://jira.codehaus.org/browse/MNG-1980?page=comments#action_57450 ] 

Jason van Zyl commented on MNG-1980:


It wasn't from the trunk because the code that contains that error messages no 
longer exists. You sure you updated?

Grep the code and you will see the code exists in the branch but does not exist 
in the trunk.

The embedder displays the same problem and is not isolated to the Ant tasks, 
but I'm sure you won't get that exception because the cache that tracks 
duplicates in the project builder is gone.

> "Duplicate project ID found" message with maven-artifact-ant-2.0.2
> --
>
>  Key: MNG-1980
>  URL: http://jira.codehaus.org/browse/MNG-1980
>  Project: Maven 2
> Type: Bug

>   Components: Ant tasks
> Versions: 2.0.2
> Reporter: Tomislav Stojcevich
> Assignee: Jason van Zyl
>  Fix For: 2.0.3

>
>
> The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2.
> [artifact:install] An error has occurred while processing the Maven artifact 
> tasks.
> [artifact:install]  Diagnosis:
> [artifact:install]
> [artifact:install] Unable to build project: 
> D:\Projects\Development\app\pom.xml
> [artifact:install] Duplicate project ID found in 
> D:\Projects\Development\app\pom.xml
> [artifact:install]
> BUILD FAILED
> D:\Projects\Development\app\ant\build.xml:166: Unable to build project: 
> D:\Projects\Development\app\pom.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MPCLOVER-45) Allow specifying the "relative" property for clover-setup

 [ http://jira.codehaus.org/browse/MPCLOVER-45?page=all ]
 
Lukas Theussl closed MPCLOVER-45:
-

 Resolution: Fixed
Fix Version: 1.11

> Allow specifying the "relative" property for clover-setup
> -
>
>  Key: MPCLOVER-45
>  URL: http://jira.codehaus.org/browse/MPCLOVER-45
>  Project: maven-clover-plugin
> Type: Improvement

> Versions: 1.9.1
>  Environment: Maven 1.0.2
> Reporter: Wim Deblauwe
>  Fix For: 1.11

>
>
> When using Clover in a distributed environment, you have several options of 
> instrumenting your class files as presented here: 
> http://www.cenqua.com/clover/doc/adv/distributed.html
> For option 2 you need to be able to specify the "relative" property, but 
> currently this is not possible in the plugin. Please add this as it is very 
> little work to do.
> regards,
> Wim

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MPCLOVER-39) Sources file should not be instrumented when no test file is present

 [ http://jira.codehaus.org/browse/MPCLOVER-39?page=all ]
 
Lukas Theussl closed MPCLOVER-39:
-

Resolution: Won't Fix

See comment above

> Sources file should not be instrumented when no test file is present
> 
>
>  Key: MPCLOVER-39
>  URL: http://jira.codehaus.org/browse/MPCLOVER-39
>  Project: maven-clover-plugin
> Type: Improvement

> Versions: 1.9
>  Environment: mavan 1.0.1 clover plugin 1.9
> Reporter: Julien Kirch

>
>
> I have a project with no test file (it's a set of test classes we want to 
> reuse and NO we don't test the tests)
> when building the project's site :
> ***snip
> [javac] loaded from: 
> C:\maven-1.0.1\repository\clover\jars\clover-1.3.6.jar
> [javac] 30 day Evaluation Version distributed via the Maven Jar 
> Repository.
> [javac] Clover is not free. You have 30 days to evaluate it. After this, 
> please visit http://www.cenqua.com to obtain a licensed version
>  of Clover
> [javac] No coverage database 
> 'C:\yourNameHere\target\clover\database\clover_coverage.db' found. Creating a 
> fresh one.
> [javac] Clover all over. Instrumented 80 file.
> ***snip
> as there's no test to execute, clovering the source is a pure loss of time, 
> the plugin should check it

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Reopened: (MNG-1980) "Duplicate project ID found" message with maven-artifact-ant-2.0.2

 [ http://jira.codehaus.org/browse/MNG-1980?page=all ]
 
Tomislav Stojcevich reopened MNG-1980:
--


Why was this closed?  The problem still exists.  I checkout and rebuild from 
both the trunk and 2.0.3 branches and I still get the same error with both 
versions.

> "Duplicate project ID found" message with maven-artifact-ant-2.0.2
> --
>
>  Key: MNG-1980
>  URL: http://jira.codehaus.org/browse/MNG-1980
>  Project: Maven 2
> Type: Bug

>   Components: Ant tasks
> Versions: 2.0.2
> Reporter: Tomislav Stojcevich
> Assignee: Jason van Zyl
>  Fix For: 2.0.3

>
>
> The same bug that was reported as fixed MNG-1851 still shows up with 2.0.2.
> [artifact:install] An error has occurred while processing the Maven artifact 
> tasks.
> [artifact:install]  Diagnosis:
> [artifact:install]
> [artifact:install] Unable to build project: 
> D:\Projects\Development\app\pom.xml
> [artifact:install] Duplicate project ID found in 
> D:\Projects\Development\app\pom.xml
> [artifact:install]
> BUILD FAILED
> D:\Projects\Development\app\ant\build.xml:166: Unable to build project: 
> D:\Projects\Development\app\pom.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MSUREFIRE-53) Make forked mode console output look the same as non-forked mode console output

2006-01-31 Thread Mike Whittemore (JIRA)

[ http://jira.codehaus.org/browse/MSUREFIRE-53?page=comments#action_57445 ] 

Mike Whittemore commented on MSUREFIRE-53:
--

FYI, once also has the problem.

> Make forked mode console output look the same as non-forked mode console 
> output
> ---
>
>  Key: MSUREFIRE-53
>  URL: http://jira.codehaus.org/browse/MSUREFIRE-53
>  Project: Maven 2.x Surefire Plugin
> Type: Bug

> Reporter: Jason van Zyl
>  Fix For: 2.1.3

>
>
> Right now nothing comes out on the console which is confusing to users.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Re: svn commit: r373872 - in /maven/maven-1/plugins/trunk/pmd: project.xml xdocs/changes.xml

2006-01-31 Thread Arnaud HERITIER

I saw it but there's also an issue open in the tracker for the pmd project.

Arnaud

On 1/31/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> Actually, pmd 3.5 has been released but it's not on ibiblio yet, see
> http://jira.codehaus.org/browse/MPMD-12
>
> -Lukas
>
>
> [EMAIL PROTECTED] wrote:
> > Author: aheritier
> > Date: Tue Jan 31 08:53:29 2006
> > New Revision: 373872
> >
> > URL: http://svn.apache.org/viewcvs?rev=373872&view=rev
> > Log:
> > begin 1.8-SNAPSHOT
> > Upgrade to pmd 3.4
> >
> > Modified:
> > maven/maven-1/plugins/trunk/pmd/project.xml
> > maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml
> >
> > Modified: maven/maven-1/plugins/trunk/pmd/project.xml
> > URL: 
> > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/pmd/project.xml?rev=373872&r1=373871&r2=373872&view=diff
> > ==
> > --- maven/maven-1/plugins/trunk/pmd/project.xml (original)
> > +++ maven/maven-1/plugins/trunk/pmd/project.xml Tue Jan 31 08:53:29 2006
> > @@ -134,7 +134,7 @@
> >  
> >pmd
> >pmd
> > -  3.2
> > +  3.4
> >http://pmd.sourceforge.net
> >  
> >  
> >
> > Modified: maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml
> > URL: 
> > http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml?rev=373872&r1=373871&r2=373872&view=diff
> > ==
> > --- maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml (original)
> > +++ maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml Tue Jan 31 08:53:29 
> > 2006
> > @@ -24,6 +24,9 @@
> >  Vincent Massol
> >
> >
> > +
> > +  Upgrade to pmd-3.4.
> > +
> >  
> >Added ability to 
> > check test sources.
> >Upgrade to 
> > pmd-3.2.
> >
> >
>
>
> -
> 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]

[jira] Commented: (MNG-897) allows use of Ant build files

[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_57444 ] 

Brett Porter commented on MNG-897:
--

when the plugin plugin is released, it can be updated into your existing maven 
install using -U.

> allows use of Ant build files
> -
>
>  Key: MNG-897
>  URL: http://jira.codehaus.org/browse/MNG-897
>  Project: Maven 2
> Type: Improvement

>   Components: Plugin Creation Tools
> Versions: 2.0-alpha-3
> Reporter: Chris Berry
> Assignee: John Casey
>  Fix For: 2.0.1
>  Attachments: antfile.zip
>
> Original Estimate: 8 hours
>Time Spent: 8 hours
> Remaining: 1 hour
>
> Per John Casey, This is logged to that it stays on the radar.
> Please consider incorporating my antfile plugin.
> I have included the following in the ZIP
> maven-antrun-plugin --> the basic antrun w/ a few small mods
> maven-antfile-plugin
> maven-axisant-plugin --> an example plugin using the antfile plugin
> axis-master --> a "grouping" plugin for axis example
> my-app --> an example app using the axisant plugin.
> Cheers,
> -- Chris 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Re: svn commit: r373872 - in /maven/maven-1/plugins/trunk/pmd: project.xml xdocs/changes.xml

2006-01-31 Thread Lukas Theussl


Actually, pmd 3.5 has been released but it's not on ibiblio yet, see
http://jira.codehaus.org/browse/MPMD-12

-Lukas


[EMAIL PROTECTED] wrote:

Author: aheritier
Date: Tue Jan 31 08:53:29 2006
New Revision: 373872

URL: http://svn.apache.org/viewcvs?rev=373872&view=rev
Log:
begin 1.8-SNAPSHOT
Upgrade to pmd 3.4

Modified:
maven/maven-1/plugins/trunk/pmd/project.xml
maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/pmd/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/pmd/project.xml?rev=373872&r1=373871&r2=373872&view=diff
==
--- maven/maven-1/plugins/trunk/pmd/project.xml (original)
+++ maven/maven-1/plugins/trunk/pmd/project.xml Tue Jan 31 08:53:29 2006
@@ -134,7 +134,7 @@
 
   pmd
   pmd
-  3.2
+  3.4
   http://pmd.sourceforge.net
 
 

Modified: maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml?rev=373872&r1=373871&r2=373872&view=diff
==
--- maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/pmd/xdocs/changes.xml Tue Jan 31 08:53:29 2006
@@ -24,6 +24,9 @@
 Vincent Massol
   
   
+
+  Upgrade to pmd-3.4.
+
 
   Added ability to check test 
sources.
   Upgrade to 
pmd-3.2.





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

Re: Specify multiple proxies

2006-01-31 Thread Brett Porter

Thomas Recloux wrote:
> 2006/1/31, Brett Porter <[EMAIL PROTECTED]>:
> 
>> I'd start with the second one as it doesn't requires model changes and
>> can be included in Maven 2.0.3.
> 
> OK, I'll work on it. Should I create a jira issue ? On the MNG project ?

yes, please.

> 
>> I'd also special case https to use the http proxy if none is defined.
> 
> I'm not sure to understand, If no https proxy is specified, use the
> http proxy ? You would manage it in which component ?

That's what I was thinking. I'm not sure if its best in wagon or the
wagon manager (probably easier in the latter for now).

- Brett

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

Re: Specify multiple proxies

2006-01-31 Thread Thomas Recloux

2006/1/31, Brett Porter <[EMAIL PROTECTED]>:

> I'd start with the second one as it doesn't requires model changes and
> can be included in Maven 2.0.3.

OK, I'll work on it. Should I create a jira issue ? On the MNG project ?

> I'd also special case https to use the http proxy if none is defined.

I'm not sure to understand, If no https proxy is specified, use the
http proxy ? You would manage it in which component ?

--
Thomas Recloux

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

Re: Specify multiple proxies

2006-01-31 Thread Brett Porter

Thomas Recloux wrote:
> I see two solutions:
> - Keeping only one active proxy and add a way to specify multiple
> protocols by proxy.
> - Modify the Settings and DefaultMaven objects to add one active proxy
> server by protocol.
> 
> What do you think of this? If you choose one of theses solutions, I
> can post the patch.

I think they are both good solutions and maybe could be used together.
I'd start with the second one as it doesn't requires model changes and
can be included in Maven 2.0.3.

I'd also special case https to use the http proxy if none is defined.

- Brett

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

Specify multiple proxies

2006-01-31 Thread Thomas Recloux

Hello all,

I need to use my office proxy to access two repositories:

- The central repository on Ibibio using the http protocol.
- An enterprise internal repository located in an other country, using
the https protocol.

I submitted a patch on wagon
(http://jira.codehaus.org/browse/WAGONHTTP-6) for it to use the proxy
for the https protocol.

I still have a problem:
- In the settings file, I can specify one protocol by proxy, so I have
to specify one proxy for each protocol. Like this:


  proxy-http
  true
  http
  proxy
  8080


  proxy-https
  true
  https
  proxy
  8080

  

- This configuration is transferred from the Settings object to the
DefaultWagonManager object by the DefaultMaven object. But this object
transfers only the first active proxy which is retrieved by the
getActiveProxy method of the Settings object.

- In my case, only one proxy (the first one) will be added to the
DefaultWagonManager and my https request won't be send to the proxy
server.

I see two solutions:
- Keeping only one active proxy and add a way to specify multiple
protocols by proxy.
- Modify the Settings and DefaultMaven objects to add one active proxy
server by protocol.

What do you think of this? If you choose one of theses solutions, I
can post the patch.

Thomas.

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

[jira] Created: (MAVEN-1741) maven 1.1 fails to run commons-attributes in mutliproject mode on a war project

2006-01-31 Thread nicolas de loof (JIRA)

maven 1.1 fails to run commons-attributes in mutliproject mode on a war project
---

 Key: MAVEN-1741
 URL: http://jira.codehaus.org/browse/MAVEN-1741
 Project: Maven
Type: Bug

Versions: 1.1-beta-2
Reporter: nicolas de loof
Priority: Minor
 Attachments: test_maven11_commons-attributes.zip

Attached zip contains a minimalist multiproject using commons-attributes that 
demonstrates the bug. 

- head (top level project)
- jar (minimalist jar project) : Sample.java has a "java.util.Date" attribute
- war (minimalist war project) : Sample.java has a "java.util.Date" attribute

When runing "maven war:install" on war project, attributes are generated as 
expected.

When running from "head" project using "maven multiproject:install", 
commons-attributes are 
- generated as expected for the jar
- NOT generated in the war (no log from plugin)

I don't know if this is a maven, multiproject-plugin, war-plugin or 
commons-attributes-plugin bug.

Please notice commons-attributes plugin uses a preGoal to automatically 
register itself. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Re: Eclipse plugin

2006-01-31 Thread James Mitchell

It might even be better to let this plugin group a dependency and it's 
transitive dependencies into a reusable user libraryI have no idea how 
to do this from mavenbut it's just a thought.


Thanks for all the hard work even with what we haveyou guys rock!!!



--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017

- Original Message - 
From: "Simon Vos" <[EMAIL PROTECTED]>

Newsgroups: gmane.comp.jakarta.turbine.maven.devel
Sent: Tuesday, January 31, 2006 2:51 AM
Subject: Re: Eclipse plugin


By the way, it would also be nice t have some option to stop the classpaths
to libraries to the maven2 repository to be added to the .classpath file,
the maven2 plugin for eclipse doesn't like this ;).

On 1/30/06, James Mitchell <[EMAIL PROTECTED]> wrote:


+1 -- I would also use this if it were available.

--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017

- Original Message -
From: "Simon" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.jakarta.turbine.maven.devel
Sent: Monday, January 30, 2006 3:07 PM
Subject: Eclipse plugin


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wouldn't it be a good idea to have some option to add include and
> exclude filters to the source and resource classpaths in the
> .classpath file for eclipse? This is something I really miss in the
> current plugin. I've added a quit hack in the code to provide this
> option for myself..
>
> King regards,
>
> Simon
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFD3nHsbAyTrjLX2RkRAsSbAKC8NMuetwTCGOH7SVCpWUnUSKRt9QCgwx3S
> QwhNfPRmlmlPOGrPJMgMMlQ=
> =pPKW
> -END PGP SIGNATURE-

-
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]

[jira] Commented: (MNG-2027) Document POM inheritance

2006-01-31 Thread Stefan H?bner (JIRA)

[ http://jira.codehaus.org/browse/MNG-2027?page=comments#action_57443 ] 

Stefan Hübner commented on MNG-2027:


May I add a request on information about how Maven interpolates scm-locations 
based on scmConnections defined in parent vs. child-pom?

Stefan

> Document POM inheritance
> 
>
>  Key: MNG-2027
>  URL: http://jira.codehaus.org/browse/MNG-2027
>  Project: Maven 2
> Type: Task

>   Components: Documentation:  General
> Reporter: John Casey
>  Fix For: documentation

>
>
> Document in detail how parent POMs are merged with local POM data. In 
> particular:
> * how are lists of things merged
> * how do local POMs override parent data
> * how can one suppress inheritance of a plugin
> * how can one control merge-vs-append in plugin configurations
> * how does the  affect the requirement for a locally 
> specified 
> How does managed information differ??
> Managed info (dependencyManagement, pluginManagement) sets the standard 
> configuration, version, etc for that information. This standard can be used 
> in opt-in fashion by child POMs, BUT WILL ONLY BE APPLIED WHERE IT IS 
> REFERENCED.
> Document the way in which managed info is merged, and how it can be 
> referenced and overridden.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVENUPLOAD-695) Publish new testng release files to ibiblio

2006-01-31 Thread Jesse Kuhnert (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-695?page=comments#action_57442 ] 

Jesse Kuhnert commented on MAVENUPLOAD-695:
---

I'd like to pretend that I understand what you just said but I don't ;) The 
modified surefire patches I submitted in the other jira issue already handle 
including the right version of testng based on the running jvm. I've tested 
this on my local box with seperate maven project builds and everything seems to 
work fine as long as the user at least specifies one of the artifcat id's as a 
depedency (ie testng-14 or testng-1.5).

I'm unsure what this one pom should look like. Does using profiles mean that 
all people using maven with testng will need to configure an additional profile 
config to be able to use it? 

Sorry for all the questions. I've browsed the maven docs as best I could 
(including the plugin dev guide), but am having trouble with this last step. 

All of the testing I did with these jars and the ticket linked to this one was 
based off of installing these two jars with commands like this:

mvn install:install-file -DartifactId=testng-jdk15 -DgroupId=org.testng 
-Dversion=4.4.7 -Dpackaging=jar -Dfile=testng-4.4.7-jdk15.jar
mvn install:install-file -DartifactId=testng-jdk14 -DgroupId=org.testng 
-Dversion=4.4.7 -Dpackaging=jar -Dfile=testng-4.4.7-jdk14.jar

I started creating a parent->module heirarchy but started getting frustrated 
when I realised I needed to share classes in both jars..Not your problem to be 
sure, I think I just need a little more nudging. (Is there any other project's 
pom I can look at doing something similar? ) 




> Publish new testng release files to ibiblio
> ---
>
>  Key: MAVENUPLOAD-695
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-695
>  Project: maven-upload-requests
> Type: Task

> Reporter: Jesse Kuhnert
> Assignee: Carlos Sanchez
>  Attachments: testng-4.4.7-jdk14-bundle.jar, testng-4.4.7-jdk15-bundle.jar
>
>
> This is a new ibiblio addition. The bundle jars aren't actually available on 
> a normal public facing website (yet), but are attached to the issue 
> referenced in the bundle url.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MNG-2027) Document POM inheritance

Document POM inheritance


 Key: MNG-2027
 URL: http://jira.codehaus.org/browse/MNG-2027
 Project: Maven 2
Type: Task

  Components: Documentation:  General  
Reporter: John Casey


Document in detail how parent POMs are merged with local POM data. In 
particular:

* how are lists of things merged
* how do local POMs override parent data
* how can one suppress inheritance of a plugin
* how can one control merge-vs-append in plugin configurations
* how does the  affect the requirement for a locally 
specified 

How does managed information differ??

Managed info (dependencyManagement, pluginManagement) sets the standard 
configuration, version, etc for that information. This standard can be used in 
opt-in fashion by child POMs, BUT WILL ONLY BE APPLIED WHERE IT IS REFERENCED.

Document the way in which managed info is merged, and how it can be referenced 
and overridden.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MNG-2027) Document POM inheritance

 [ http://jira.codehaus.org/browse/MNG-2027?page=all ]

John Casey updated MNG-2027:


Fix Version: documentation

> Document POM inheritance
> 
>
>  Key: MNG-2027
>  URL: http://jira.codehaus.org/browse/MNG-2027
>  Project: Maven 2
> Type: Task

>   Components: Documentation:  General
> Reporter: John Casey
>  Fix For: documentation

>
>
> Document in detail how parent POMs are merged with local POM data. In 
> particular:
> * how are lists of things merged
> * how do local POMs override parent data
> * how can one suppress inheritance of a plugin
> * how can one control merge-vs-append in plugin configurations
> * how does the  affect the requirement for a locally 
> specified 
> How does managed information differ??
> Managed info (dependencyManagement, pluginManagement) sets the standard 
> configuration, version, etc for that information. This standard can be used 
> in opt-in fashion by child POMs, BUT WILL ONLY BE APPLIED WHERE IT IS 
> REFERENCED.
> Document the way in which managed info is merged, and how it can be 
> referenced and overridden.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MNG-2026) Document how parent-child POM relationships, , and works

 [ http://jira.codehaus.org/browse/MNG-2026?page=all ]

John Casey updated MNG-2026:


Fix Version: documentation

> Document how parent-child POM relationships, , and 
>  works
> --
>
>  Key: MNG-2026
>  URL: http://jira.codehaus.org/browse/MNG-2026
>  Project: Maven 2
> Type: Task

>   Components: Documentation:  General
> Reporter: John Casey
>  Fix For: documentation

>
>
> Create a document that will describe how POMs can be related to one another 
> in a multimodule build. Specifically, document:
> * The parent-child relationship - how is this manifest in the POMs
> * How does the  section work
> * How does the  element of the  section work...and 
> what is required in the  section?
> * How to install ONLY the parent POM for a multimodule setup (mvn -N pom.xml 
> at the top level)
> * How to build an entire multimodule setup from one command (tie all of this 
> together into a working example)
> Related to this, but in another document, should be a list of things that are 
> inherited (could be a link to somewhere else, if this documentation exists in 
> other places). Also, the algorithm used to merge inherited and local POM 
> sections should be in this other document.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MNG-2026) Document how parent-child POM relationships, , and works