Re: main design tasks

[Brett Porter]

Brett Porter wrote:

>Hi,
>
>The following is a summary of all proposed designs, with the addition of
>requirements for the dependency mediation and profiles as have been
>discussed. I'll fill them out tomorrow:
>
>http://docs.codehaus.org/display/MAVEN/Maven+2.0+Design+Documents
>  
>
BTW, feel free to comment on these in advance too!

The topics are:

* Build Profiles 
* Dependeny Mediation and Conflict Resolution
  

* Lifecycle 
* Packaging vs Type - Derived and Attached Artifacts
  
* Plugin and Report Inheritence
  


>I think we need to get these hashed out and finalised next week so they
>can be implemented. I'd like to call a logged meeting on IRC (#maven)
>next week for all interested parties (you don't have to be a developer,
>you just have to be interested - and you don't have to have an opinion,
>you can just listen in). The logs will be posted and finalised docs
>agreed on beyond that. It will probably take a couple of hours, or a
>couple of sessions.
>
>I think the best time is the late afternoon in Europe, which is early
>morning in the US and about 10pm here (but I'm the only one in that
>timezone AFAICT). It's also the same date for everyone then so it is
>easier to plan :)
>
>Any suggested dates? I was thinking Wednesday or Thursday as I am busy
>Monday and Tuesday.
>
>Cheers,
>Brett
>
>
>-
>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]

main design tasks

[Brett Porter]

Hi,

The following is a summary of all proposed designs, with the addition of
requirements for the dependency mediation and profiles as have been
discussed. I'll fill them out tomorrow:

http://docs.codehaus.org/display/MAVEN/Maven+2.0+Design+Documents

I think we need to get these hashed out and finalised next week so they
can be implemented. I'd like to call a logged meeting on IRC (#maven)
next week for all interested parties (you don't have to be a developer,
you just have to be interested - and you don't have to have an opinion,
you can just listen in). The logs will be posted and finalised docs
agreed on beyond that. It will probably take a couple of hours, or a
couple of sessions.

I think the best time is the late afternoon in Europe, which is early
morning in the US and about 10pm here (but I'm the only one in that
timezone AFAICT). It's also the same date for everyone then so it is
easier to plan :)

Any suggested dates? I was thinking Wednesday or Thursday as I am busy
Monday and Tuesday.

Cheers,
Brett


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

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 5 (10 including POMs).
building file list ... done
activemq/distributions/
last-sync.txt
wrote 634673 bytes  read 42 bytes  6509.90 bytes/sec
total size is 2588548108  speedup is 4078.28
building file list ... done
.index.txt
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom.md5
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom.sha1
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip.md5
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip.sha1
last-sync.txt
wrote 25164267 bytes  read 222346 bytes  94198.94 bytes/sec
total size is 3569724060  speedup is 140.61

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

Re: Jelly issues

[Felipe Leme]

Hi Brett,

Yes, I know, but I'm not subscribed there and didn't want to just
subscribe and out of the blue send such message (anyway, I thought many
developers were maven committers too).

-- Felipe


On Fri, 2005-05-20 at 10:52 +1000, Brett Porter wrote:
> Please send this to commons-dev. Most of the Jelly developers are not on
> this list.



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

[jira] Closed: (MAVENUPLOAD-390) Upload request for maven-statcvs-plugin

[Carlos Sanchez (JIRA)]

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

Resolution: Fixed
 Assign To: Carlos Sanchez

> Upload request for maven-statcvs-plugin
> ---
>
>  Key: MAVENUPLOAD-390
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-390
>  Project: maven-upload-requests
> Type: Task
> Reporter: Steffen Pingel
> Assignee: Carlos Sanchez

>
>
> http://statcvs-xml.berlios.de/maven-plugin/
> http://statcvs-xml.berlios.de/maven-plugin/team-list.html
> The statcvs plugin has been updated to depend on the new version of 
> StatCVS-XML and  a new goal has been added for the generation of html reports.

-- 
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-387) upload emma jar to maven repository

[Carlos Sanchez (JIRA)]

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

Resolution: Fixed
 Assign To: Carlos Sanchez

> upload emma jar to maven repository 
> 
>
>  Key: MAVENUPLOAD-387
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-387
>  Project: maven-upload-requests
> Type: Task
> Reporter: Chad Woolley
> Assignee: Carlos Sanchez
>  Attachments: emma-2.0.4217-bundle.jar
>
>
> http://emma.sourceforge.net/
> http://sourceforge.net/project/memberlist.php?group_id=108932

-- 
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: (MPJAVADOC-59) package.html and overview.html are not copied when source modifications are used ...

[Arnaud HERITIER (JIRA)]

package.html and overview.html are not copied when source modifications are 
used ...


 Key: MPJAVADOC-59
 URL: http://jira.codehaus.org/browse/MPJAVADOC-59
 Project: maven-javadoc-plugin
Type: Bug
Versions: 1.7
 Environment: maven 1.0.2
Reporter: Arnaud HERITIER
 Assigned to: Arnaud HERITIER 


>From Steven Caswell on the ML :

I'm having trouble with the javadoc plugin (Maven 1.0.2,
maven-javadoc-plugin-1.7) and source modifications. It looks like if I have a 
source modification defined in the project.xml, the javadoc plugin is not 
including package.html and overview.html when it copies the source tree to the 
alternate location to apply the source mods. The end result is that the javadoc 
does not contain the content of these.

I find it hard to believe this hasn't been reported, but I looked through Jira 
and the users mailing list and didn't see anything about it. Is this really a 
bug in the javadoc plugin or am I missing something?

TIA


-- 
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: Jelly issues

[Brett Porter]

Please send this to commons-dev. Most of the Jelly developers are not on
this list.

- Brett

Felipe Leme wrote:

>Hi all,
>
>
>I had submitted some Jelly patches a couple of weeks ago, but didn't get
>any comments about them
>
>http://issues.apache.org/jira/browse/JELLY-194
>http://issues.apache.org/jira/browse/JELLY-203
>http://issues.apache.org/jira/browse/JELLY-204
>http://issues.apache.org/jira/browse/JELLY-205
>
>
>Except by 194 which is a new feature, the other 3 issues are easy to
>apply (and the patches even include test cases :-). 
>
>So, could some of you with commons karma take a look on them?
>
>-- Felipe
>
>
>
>-
>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]

Jelly issues

[Felipe Leme]

Hi all,


I had submitted some Jelly patches a couple of weeks ago, but didn't get
any comments about them

http://issues.apache.org/jira/browse/JELLY-194
http://issues.apache.org/jira/browse/JELLY-203
http://issues.apache.org/jira/browse/JELLY-204
http://issues.apache.org/jira/browse/JELLY-205


Except by 194 which is a new feature, the other 3 issues are easy to
apply (and the patches even include test cases :-). 

So, could some of you with commons karma take a look on them?

-- Felipe



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

[jira] Closed: (MNG-1) directory and artifact comparison

[Brett Porter (JIRA)]

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

Fix Version: (was: 2.0-alpha-3)
 2.0-alpha-1
 Resolution: Fixed

this was present in alpha-1 (conflict id and others).

When it comes to utilising this in mevenide, we can look more closely at what 
might be needed in the api

> directory and artifact comparison
> -
>
>  Key: MNG-1
>  URL: http://jira.codehaus.org/browse/MNG-1
>  Project: m2
> Type: Improvement
> Reporter: gilles dodinet
> Priority: Minor
>  Fix For: 2.0-alpha-1

>
>
> 1. artifacts
> in mevenide to synchronize pom with ide we need to display artifacts if they 
> are not already added to ide (and vice-versa). for that purpose we need to 
> have a comparison mechanism. so a equals() method is needed, but also other 
> utility methods like (non exhaustive) : 
> o myArtifact.conflicts(myOtherArtifact) and
> o myArtifact.relaxEquals(myOtherArtifact)
> f.i. conflicts would return true if same groupId and sameAritfactId but 
> incompatible version, relaxEquals would return true if version is compatible, 
> etc.. (just some quick thoughts)
> 2. directories 
> although not as needed as artifact comparison it would be util to have 
> utility to compare a Resource with a given path that might be relative or to 
> ${basedir} or absolute.

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

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 17 (34 including POMs).
building file list ... done
./
emma/
emma/jars/
emma/jars/emma-2.0.4217.jar
emma/jars/emma_ant-2.0.4217.jar
emma/licenses/
emma/licenses/emma-2.0.4217.license
emma/licenses/emma_ant-2.0.4217.license
emma/poms/
emma/poms/emma-2.0.4217.pom
emma/poms/emma_ant-2.0.4217.pom
last-sync.txt
mevenide/distributions/
mule/dtds/
mule/dtds/mule-configuration.dtd
mule/jars/
mule/jars/mule-SNAPSHOT.jar
mule/jars/mule-core-SNAPSHOT.jar
mule/jars/mule-email-provider-SNAPSHOT.jar
mule/jars/mule-extras-client-SNAPSHOT.jar
mule/jars/mule-extras-spring-SNAPSHOT.jar
mule/jars/mule-jdbc-provider-SNAPSHOT.jar
mule/jars/mule-tcp-provider-SNAPSHOT.jar
mule/jars/mule-vm-provider-SNAPSHOT.jar
mule/nightly/
mule/nightly/mule-SNAPSHOT.jar
mule/nightly/mule-configuration.dtd
mule/nightly/mule-core-SNAPSHOT.jar
mule/nightly/mule-email-provider-SNAPSHOT.jar
mule/nightly/mule-extras-client-SNAPSHOT.jar
mule/nightly/mule-extras-spring-SNAPSHOT.jar
mule/nightly/mule-jdbc-provider-SNAPSHOT.jar
mule/nightly/mule-ra-SNAPSHOT.rar
mule/nightly/mule-tcp-provider-SNAPSHOT.jar
mule/nightly/mule-vm-provider-SNAPSHOT.jar
mule/rars/
mule/rars/mule-ra-SNAPSHOT.rar
statcvs/jars/
statcvs/jars/statcvs-xml-0.9.6.jar
statcvs/licenses/
statcvs/licenses/maven-statcvs-plugin-2.7.license
statcvs/licenses/statcvs-xml-0.9.6.license
statcvs/plugins/
statcvs/plugins/maven-statcvs-plugin-2.7.jar
statcvs/poms/
statcvs/poms/maven-statcvs-plugin-2.7.pom
statcvs/poms/statcvs-xml-0.9.6.pom
wrote 4865143 bytes  read 72386 bytes  24144.40 bytes/sec
total size is 2588548108  speedup is 524.26
building file list ... done
./
.index.txt
emma/
emma/emma/
emma/emma/2.0.4217/
emma/emma/2.0.4217/emma-2.0.4217.jar
emma/emma/2.0.4217/emma-2.0.4217.jar.md5
emma/emma/2.0.4217/emma-2.0.4217.jar.sha1
emma/emma/2.0.4217/emma-2.0.4217.pom
emma/emma/2.0.4217/emma-2.0.4217.pom.md5
emma/emma/2.0.4217/emma-2.0.4217.pom.sha1
emma/emma_ant/
emma/emma_ant/2.0.4217/
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.jar
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.jar.md5
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.jar.sha1
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.pom
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.pom.md5
emma/emma_ant/2.0.4217/emma_ant-2.0.4217.pom.sha1
last-sync.txt
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.tar.gz
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.tar.gz.md5
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.tar.gz.sha1
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.zip
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.zip.md5
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT-src.zip.sha1
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.pom
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.pom.md5
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.pom.sha1
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.tar.gz
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.tar.gz.md5
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.tar.gz.sha1
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.zip
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.zip.md5
mevenide/mevenide-idea/0.1-SNAPSHOT/mevenide-idea-0.1-SNAPSHOT.zip.sha1
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.jar
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.jar.md5
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.jar.sha1
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.pom
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.pom.md5
mule/mule-core/SNAPSHOT/mule-core-SNAPSHOT.pom.sha1
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.jar
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.jar.md5
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.jar.sha1
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.pom
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.pom.md5
mule/mule-email-provider/SNAPSHOT/mule-email-provider-SNAPSHOT.pom.sha1
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.jar
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.jar.md5
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.jar.sha1
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.pom
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.pom.md5
mule/mule-extras-client/SNAPSHOT/mule-extras-client-SNAPSHOT.pom.sha1
mule/mule-extras-spring/SNAPSHOT/mule-extras-spring-SNAPSHOT.jar
mule/mule-extras-spring/SNAPSHOT/mule-extras-spring-SNAPSHOT.jar.md5
mule/mule-extras-spring/SNAPSHOT/mule-extras-spring-SNAPSHOT.jar.sha1
mule/mule-extras-spring/SNAPSHOT/mule-extras-spring-SNAPSHOT.pom
mule/mule-extras-spring/SNAPSHOT/mule-extras-spring-SNAPSHOT.pom.md5
mule/mule

[jira] Updated: (MNG-397) transitive artifacts may not match pom's repository definition

[Brett Porter (JIRA)]

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

Brett Porter updated MNG-397:
-

Summary: transitive artifacts may not match pom's repository definition  
(was: transitive artifacts may not match repository definition)

> transitive artifacts may not match pom's repository definition
> --
>
>  Key: MNG-397
>  URL: http://jira.codehaus.org/browse/MNG-397
>  Project: m2
> Type: Bug
>   Components: maven-artifact
> Reporter: Brett Porter
>  Fix For: 2.0-beta-1

>
>
> I haven't produced a test case, but I assume this to be true based on a 
> review of the code.
> If a project has a dependency on another project, and that project has a 
> dependency only available in a repository declared in that project, I don't 
> believe those additional repositories are used to search for artifacts. It 
> would appear that the artifact would not be found. 

-- 
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: (MPJAVADOC-59) package.html and overview.html are not copied when source modifications are used ...

[Arnaud HERITIER (JIRA)]

 [ http://jira.codehaus.org/browse/MPJAVADOC-59?page=all ]
 
Arnaud HERITIER closed MPJAVADOC-59:


Fix Version: 1.8
 Resolution: Fixed

Fixed

> package.html and overview.html are not copied when source modifications are 
> used ...
> 
>
>  Key: MPJAVADOC-59
>  URL: http://jira.codehaus.org/browse/MPJAVADOC-59
>  Project: maven-javadoc-plugin
> Type: Bug
> Versions: 1.7
>  Environment: maven 1.0.2
> Reporter: Arnaud HERITIER
> Assignee: Arnaud HERITIER
>  Fix For: 1.8

>
>
> From Steven Caswell on the ML :
> I'm having trouble with the javadoc plugin (Maven 1.0.2,
> maven-javadoc-plugin-1.7) and source modifications. It looks like if I have a 
> source modification defined in the project.xml, the javadoc plugin is not 
> including package.html and overview.html when it copies the source tree to 
> the alternate location to apply the source mods. The end result is that the 
> javadoc does not contain the content of these.
> I find it hard to believe this hasn't been reported, but I looked through 
> Jira and the users mailing list and didn't see anything about it. Is this 
> really a bug in the javadoc plugin or am I missing something?
> TIA

-- 
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-386) jcs update

[Carlos Sanchez (JIRA)]

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

Resolution: Won't Fix
 Assign To: Carlos Sanchez

Apache projects should upload bundles through apache repo
http://www.apache.org/dist/java-repository/

> jcs update
> --
>
>  Key: MAVENUPLOAD-386
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-386
>  Project: maven-upload-requests
> Type: Task
> Reporter: Aaron Smuts
> Assignee: Carlos Sanchez
>  Attachments: jcs-1.2.6-bundle.jar
>
>
> New version of JCS.

-- 
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-388) upload emma_ant jar to maven repository

[Carlos Sanchez (JIRA)]

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

Resolution: Fixed
 Assign To: Carlos Sanchez

> upload emma_ant jar to maven repository 
> 
>
>  Key: MAVENUPLOAD-388
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-388
>  Project: maven-upload-requests
> Type: Task
> Reporter: Chad Woolley
> Assignee: Carlos Sanchez
>  Attachments: emma_ant-2.0.4217-bundle.jar
>
>
> http://emma.sourceforge.net/
> http://sourceforge.net/project/memberlist.php?group_id=108932

-- 
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-389) Upload request for statcvs-xml

[Carlos Sanchez (JIRA)]

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

Resolution: Fixed
 Assign To: Carlos Sanchez

> Upload request for statcvs-xml
> --
>
>  Key: MAVENUPLOAD-389
>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-389
>  Project: maven-upload-requests
> Type: Task
> Reporter: Steffen Pingel
> Assignee: Carlos Sanchez

>
>
> http://statcvs-xml.berlios.de
> http://statcvs-xml.berlios.de/team-list.html
> A new version of StatCVS-XML has been released.

-- 
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 - FAILED] Thu May 19 13:07:00 EDT 2005

[jvanzyl]

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.130700.txt

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

svn commit: r171020 - /maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml

[aheritier]

Author: aheritier
Date: Thu May 19 16:52:09 2005
New Revision: 171020

URL: http://svn.apache.org/viewcvs?rev=171020&view=rev
Log:
remove debug logs

Modified:
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml

Modified: maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml?rev=171020&r1=171019&r2=171020&view=diff
==
--- maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml 
(original)
+++ maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml Thu 
May 19 16:52:09 2005
@@ -42,15 +42,10 @@
 
 
 
-1
 
-2
 
-3
 
-4
 
-5
   
 
 



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

svn commit: r171019 - in /maven/maven-1/plugins/trunk/javadoc: ./ src/plugin-test/test03/ src/plugin-test/test03/src/main/ src/plugin-test/test03/src/main/org/apache/maven/ src/plugin-test/test03/src/main/org/apache/maven2/ src/plugin-test/test03/src/opt/org/apache/maven3/ xdocs/

[aheritier]

Author: aheritier
Date: Thu May 19 16:51:22 2005
New Revision: 171019

URL: http://svn.apache.org/viewcvs?rev=171019&view=rev
Log:
Fix + tests for MPJAVADOC-59
New tests require maven-plugin-plugin 1.6 or more

Added:

maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties   
(with props)

maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/overview.html
   (with props)
Modified:
maven/maven-1/plugins/trunk/javadoc/plugin.jelly
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml

maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven/package.html

maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven2/package.html

maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/opt/org/apache/maven3/package.html
maven/maven-1/plugins/trunk/javadoc/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/javadoc/plugin.jelly
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/plugin.jelly?rev=171019&r1=171018&r2=171019&view=diff
==
--- maven/maven-1/plugins/trunk/javadoc/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/javadoc/plugin.jelly Thu May 19 16:51:22 2005
@@ -125,6 +125,7 @@
 
   
 
+
 
 
 
@@ -506,6 +507,7 @@
 
 
   
+  
 
   
 

Modified: maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml?rev=171019&r1=171018&r2=171019&view=diff
==
--- maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml 
(original)
+++ maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/maven.xml Thu 
May 19 16:51:22 2005
@@ -41,6 +41,16 @@
 
 
 
+
+1
+
+2
+
+3
+
+4
+
+5
   
 
 

Added: 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties?rev=171019&view=auto
==
--- 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties 
(added)
+++ 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties 
Thu May 19 16:51:22 2005
@@ -0,0 +1 @@
+maven.javadoc.overview=${pom.build.sourceDirectory}/overview.html
\ No newline at end of file

Propchange: 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/project.properties
--
svn:eol-style = native

Modified: 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven/package.html
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven/package.html?rev=171019&r1=171018&r2=171019&view=diff
==
--- 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven/package.html
 (original)
+++ 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven/package.html
 Thu May 19 16:51:22 2005
@@ -1,6 +1,7 @@
 
 
 
+package.html file content. 
 Package documentation. 
 example.txt in doc-files directory.
 

Modified: 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven2/package.html
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven2/package.html?rev=171019&r1=171018&r2=171019&view=diff
==
--- 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven2/package.html
 (original)
+++ 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/org/apache/maven2/package.html
 Thu May 19 16:51:22 2005
@@ -1,6 +1,7 @@
 
 
 
+package.html file content. 
 Package documentation. 
 example.txt in doc-files directory.
 

Added: 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/overview.html
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/overview.html?rev=171019&view=auto
==
--- 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/overview.html
 (added)
+++ 
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test03/src/main/overview.html
 Thu May 19 16:51:22 2005
@@ -0,0 +1,6 @@
+
+
+
+overview.

svn commit: r171018 - /maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test06

[aheritier]

Author: aheritier
Date: Thu May 19 16:49:48 2005
New Revision: 171018

URL: http://svn.apache.org/viewcvs?rev=171018&view=rev
Log:
ignore log files

Modified:
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test06/   (props 
changed)

Propchange: maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test06/
--
--- svn:ignore (original)
+++ svn:ignore Thu May 19 16:49:48 2005
@@ -1 +1,2 @@
 target
+*.log



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

svn commit: r171017 - /maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test09

[aheritier]

Author: aheritier
Date: Thu May 19 16:49:13 2005
New Revision: 171017

URL: http://svn.apache.org/viewcvs?rev=171017&view=rev
Log:
ignore target directory

Modified:
maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test09/   (props 
changed)

Propchange: maven/maven-1/plugins/trunk/javadoc/src/plugin-test/test09/
--
--- svn:ignore (added)
+++ svn:ignore Thu May 19 16:49:13 2005
@@ -0,0 +1 @@
+target



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

Beanshell support in plugins

[Brett Porter]

Hi,

This was implemented earlier in the week. I've drafted up a brief
explanation here if people want to see how it works:

http://blogs.codehaus.org/people/brett/archives/001090_writing_beanshell_plugins_for_maven_20.html

Any additional thoughts on the implementation?

- Brett

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

Re: and m2

[Brett Porter]

Dan Diephouse wrote:

>
> Requiring the user to override/exclude dependencies in their pom
> somehow would be kind of a pain. 

Ok, but the alternative is just to turn it off (still needing to be
specified), which I feel like is too much of an easy out. We're in early
days here, we can make the metadata get better. We do need to make it
simple though.

> But, what if m2 made it simple for a user to change this. Ie m2 would
> iterate through the dependency conflicts and allow you to select
> different options.

I don't feel like this type of prompting is appropriate in most cases,
especially for something as common as dependency resolution. I think we
should definitely have tools to help setup the previously mentioned
configurations though. What you are proposing sounds exactly like
http://deputy.sourceforge.net/

> I guess I'm just thinking how to make it easier for the user, because
> I believe that ease of entry will be a real barrier to use the way
> things are now.
>
I agree - though you have bitten off probably the hardest one of all
given all your sun spec dependencies :)

- Brett


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

[maven2 build - FAILED] Thu May 19 15:07:00 EDT 2005

[jvanzyl]

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.150700.txt

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

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 29 (58 including POMs).
building file list ... done
ant/jars/
ant/jars/ant-1.6.4.jar
ant/jars/ant-1.6.4.jar.md5
ant/jars/ant-1.6.4.jar.sha1
ant/jars/ant-antlr-1.6.4.jar
ant/jars/ant-antlr-1.6.4.jar.md5
ant/jars/ant-antlr-1.6.4.jar.sha1
ant/jars/ant-apache-bcel-1.6.4.jar
ant/jars/ant-apache-bcel-1.6.4.jar.md5
ant/jars/ant-apache-bcel-1.6.4.jar.sha1
ant/jars/ant-apache-bsf-1.6.4.jar
ant/jars/ant-apache-bsf-1.6.4.jar.md5
ant/jars/ant-apache-bsf-1.6.4.jar.sha1
ant/jars/ant-apache-log4j-1.6.4.jar
ant/jars/ant-apache-log4j-1.6.4.jar.md5
ant/jars/ant-apache-log4j-1.6.4.jar.sha1
ant/jars/ant-apache-oro-1.6.4.jar
ant/jars/ant-apache-oro-1.6.4.jar.md5
ant/jars/ant-apache-oro-1.6.4.jar.sha1
ant/jars/ant-apache-regexp-1.6.4.jar
ant/jars/ant-apache-regexp-1.6.4.jar.md5
ant/jars/ant-apache-regexp-1.6.4.jar.sha1
ant/jars/ant-apache-resolver-1.6.4.jar
ant/jars/ant-apache-resolver-1.6.4.jar.md5
ant/jars/ant-apache-resolver-1.6.4.jar.sha1
ant/jars/ant-commons-logging-1.6.4.jar
ant/jars/ant-commons-logging-1.6.4.jar.md5
ant/jars/ant-commons-logging-1.6.4.jar.sha1
ant/jars/ant-commons-net-1.6.4.jar
ant/jars/ant-commons-net-1.6.4.jar.md5
ant/jars/ant-commons-net-1.6.4.jar.sha1
ant/jars/ant-icontract-1.6.4.jar
ant/jars/ant-icontract-1.6.4.jar.md5
ant/jars/ant-icontract-1.6.4.jar.sha1
ant/jars/ant-jai-1.6.4.jar
ant/jars/ant-jai-1.6.4.jar.md5
ant/jars/ant-jai-1.6.4.jar.sha1
ant/jars/ant-javamail-1.6.4.jar
ant/jars/ant-javamail-1.6.4.jar.md5
ant/jars/ant-javamail-1.6.4.jar.sha1
ant/jars/ant-jdepend-1.6.4.jar
ant/jars/ant-jdepend-1.6.4.jar.md5
ant/jars/ant-jdepend-1.6.4.jar.sha1
ant/jars/ant-jmf-1.6.4.jar
ant/jars/ant-jmf-1.6.4.jar.md5
ant/jars/ant-jmf-1.6.4.jar.sha1
ant/jars/ant-jsch-1.6.4.jar
ant/jars/ant-jsch-1.6.4.jar.md5
ant/jars/ant-jsch-1.6.4.jar.sha1
ant/jars/ant-junit-1.6.4.jar
ant/jars/ant-junit-1.6.4.jar.md5
ant/jars/ant-junit-1.6.4.jar.sha1
ant/jars/ant-launcher-1.6.4.jar
ant/jars/ant-launcher-1.6.4.jar.md5
ant/jars/ant-launcher-1.6.4.jar.sha1
ant/jars/ant-netrexx-1.6.4.jar
ant/jars/ant-netrexx-1.6.4.jar.md5
ant/jars/ant-netrexx-1.6.4.jar.sha1
ant/jars/ant-nodeps-1.6.4.jar
ant/jars/ant-nodeps-1.6.4.jar.md5
ant/jars/ant-nodeps-1.6.4.jar.sha1
ant/jars/ant-starteam-1.6.4.jar
ant/jars/ant-starteam-1.6.4.jar.md5
ant/jars/ant-starteam-1.6.4.jar.sha1
ant/jars/ant-stylebook-1.6.4.jar
ant/jars/ant-stylebook-1.6.4.jar.md5
ant/jars/ant-stylebook-1.6.4.jar.sha1
ant/jars/ant-swing-1.6.4.jar
ant/jars/ant-swing-1.6.4.jar.md5
ant/jars/ant-swing-1.6.4.jar.sha1
ant/jars/ant-trax-1.6.4.jar
ant/jars/ant-trax-1.6.4.jar.md5
ant/jars/ant-trax-1.6.4.jar.sha1
ant/jars/ant-vaj-1.6.4.jar
ant/jars/ant-vaj-1.6.4.jar.md5
ant/jars/ant-vaj-1.6.4.jar.sha1
ant/jars/ant-weblogic-1.6.4.jar
ant/jars/ant-weblogic-1.6.4.jar.md5
ant/jars/ant-weblogic-1.6.4.jar.sha1
ant/jars/ant-xalan1-1.6.4.jar
ant/jars/ant-xalan1-1.6.4.jar.md5
ant/jars/ant-xalan1-1.6.4.jar.sha1
ant/jars/ant-xslp-1.6.4.jar
ant/jars/ant-xslp-1.6.4.jar.md5
ant/jars/ant-xslp-1.6.4.jar.sha1
last-sync.txt
nanocontainer/poms/
nanocontainer/poms/nanocontainer-nanowar-sample-1.0-SNAPSHOT.pom
picocontainer/jars/
picocontainer/jars/picocontainer-tck-1.2-SNAPSHOT.jar
wrote 2816523 bytes  read 1424 bytes  60601.01 bytes/sec
total size is 2588167826  speedup is 918.46
building file list ... done
.index.txt
ant/ant/
ant/ant-antlr/
ant/ant-antlr/1.6.4/
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.jar
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.jar.md5
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.jar.sha1
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.pom
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.pom.md5
ant/ant-antlr/1.6.4/ant-antlr-1.6.4.pom.sha1
ant/ant-apache-bcel/
ant/ant-apache-bcel/1.6.4/
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.jar
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.jar.md5
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.jar.sha1
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.pom
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.pom.md5
ant/ant-apache-bcel/1.6.4/ant-apache-bcel-1.6.4.pom.sha1
ant/ant-apache-bsf/
ant/ant-apache-bsf/1.6.4/
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.jar
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.jar.md5
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.jar.sha1
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.pom
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.pom.md5
ant/ant-apache-bsf/1.6.4/ant-apache-bsf-1.6.4.pom.sha1
ant/ant-apache-log4j/
ant/ant-apache-log4j/1.6.4/
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.jar
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.jar.md5
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.jar.sha1
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.pom
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.pom.md5
ant/ant-apache-log4j/1.6.4/ant-apache-log4j-1.6.4.pom.sha1
ant/ant-apache-oro/
ant/ant-apache-oro/1.6.4/
ant/ant-apache-oro/1.6.4/ant-apache-oro-1.6.4.jar
a

[ANN] Maven Dashboard Plugin 1.8 released

[Vincent Massol]

The maven team is pleased to announce the Maven Dashboard Plugin 1.8 release! 

http://maven.apache.org/reference/plugins/dashboard/

Generate a dashboard containing global statistics about other maven reports 

Changes in this version include:

  New Features:

o Added aggregator totals to the HTML report. Issue: MPDASHBOARD-22. Thanks 
  to Morten Kristiansen. 

  Fixed bugs:

o Prevent failure in junitpassrate.jellydue to a division by zero when there 
  is a unit test source directory defined but no tests are executed. Issue: 
  MPDASHBOARD-17. Thanks to Philippe Kernevez. 

  Changes:

o Default values for maven.dashboard.basedir, maven.dashboard.includes, 
  maven.dashboard.excludesand maven.dashboard.ignoreFailuresare copied from 
  the equivalent Multiproject properties. This should reduce the number of 
  properties you have to set to get going as you need now only set the 
  Multiproject properties.  

To automatically install the plugin, type the following on a single line:

maven plugin:download 
  -DgroupId=maven 
  -DartifactId=maven-dashboard-plugin
  -Dversion=1.8

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.8.jar
 

Have fun!
-The maven team
  

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

Re: [m2] artifact handlers

[Brett Porter]

Gilles Dodinet wrote:

> ive tried to build from trunk but encountered some problems with
> bootstrap : i had to build core-it-verifier by hand (using alpha-2),
> but then all it-tests failed because of file not found (however the
> files were actually present). i remember having encountered such issue
> a while back when bootstrapping (as far as i can recall that was a
> basedir issue). i havent investigated this very far and downloaded the
> last snapshot instead.

This is a bit weird. I'd like to work this through with you if possible
(as you can see, our clean build is working on the integration machine -
so I'd need to see what in your environment is causing it).

>
> but yet im still not sure how to register an artifact handler. 

maven-artifact/src/main/resources/META-INF/plexus/components.xml lists them

> i also wonder how i can specify non defualt artifact name mapping.
> indeed even though it is to handle assembly name like any other
> artifact, assemblies generally don't include version in the name (no
> judgement nor appreciation here). on the other hand m2 default
> repository layout has a folder per version so i guess it should be
> possible to locate a dependency even if its name doesn't make the
> version explicit, not ? (although i understand this make it not
> backward compatible)

In the repository, the naming format is quite strict - the handler only
has control over the extension used (And the subdirectory in the old
style repo). I don't quite understand the use case - you can bundle/save
without versions locally, but the repository artifacts should still have
a version. Can you explain more about this?

>
> concerning the lifecycle i'm not sure how to map it to a specific
> packaging type. it's tempting though to use the artifact handler for
> this. but handlers seem to only define packageGoal(). so how to
> instruct m2 that a project  that has a 'foo' packaging type should be
> compiled with foo-compiler. 

This would be the responsibility of the compiler mojo. However, you may
need to alter the lifecycle more - there has been a thread of discussion
about how to do this recently, but is not yet implemented.

> i'm not sure either to understand the directory() method. is this 
> method present to support m1 repository-style ?

correct.

> what i have so far is pretty simplistic as you can see at
> http://codehaus.org/~gdodinet/csharp.png. 

ok, I was thinking that you should be able to use the same compiler
mojo, and have an alternate configuration element for csharp (and we
could possibly put the java compiler options into a separate nested
element too). I'm not sure about this - maybe it is better to have a
separate mojo. How much do they differ?

I agree we could rename classpath elements to dependencyFiles, however.

> concerning the ant task i would have been happier without it (not
> mentionning that it needs an ant project - however i use 1.5.4,
> perhaps that changed in 1.6+) but for now i didn't wnat to rewrite
> something similar.

That's fine to get started. I think a good goal is to get some of the
ant compiler code into commons-jci, without the ant
project/types/listener bindings if that's possible. I'm going to try and
kickstart that soon.

- Brett


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

Re: build failures -> m2 versioning clarification?

[Brett Porter]

Kenney Westerhof wrote:

>Hi there,
>
>Just tried to bootstrap m2 HEAD (r170983) (with clean repo) and it failed.
>Didn't want to make this a JIRA issue (yet).. Below a description,
>and a question about m2 versioning. Sorry if this is supposed to be posted
>to the users@ list..
>  
>
Nope, this is correct.

>First the compilation error:
>maven-site-plugin depends on maven-reporting-api 2.0-alpha-2,
>which does not have 2 methods defined in MavenReportConfiguration;
>the output (see http://rafb.net/paste/results/N8VhdB30.html)
>didn't clarify much - only after loading it in eclipse the error
>became evident (probably an issue on it's own :)).
>After updating the version to 2.0-SNAPSHOT it compiled fine.
>  
>
This seems to have been an error during the last change - as you'll see
the CI build failed because of this too.

>Now for my question:
>I've asked this before on #maven, but never got a straight answer:
>How do you approach the versioning of modules in m2?
>
>The current versioning of modules is unclear to me: plugins have
>the following versions:
>
>1.0-alpha-2-SNAPSHOT
>1.0-SNAPSHOT
>2.0-alpha-2-SNAPSHOT
>2.0-alpha-3-SNAPSHOT
>
>whereas for example maven-reporting(-api) lack versions and use the
>2.0-SNAPSHOT version defined in the parent pom.
>  
>
The use of 2.0-SNAPSHOT in our POMs is because I've been lazy. I've
agreed to update this after the next release (but right now, it'd just
be busy work...). So the policy is "XXX-SNAPSHOT means development
progressing towards version XXX". So, Maven should have version
2.0-alpha-3-SNAPSHOT right now. After the next release, it will be
2.0-beta-1-SNAPSHOT.

>Maven-site-plugin depends on maven-reporting-api 2.0-alpha-2,
>and I can't find that that version was ever assigned to that module
>in the svn history. 
>
It's there:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0-alpha-2

I made the version change as I did the svn copy. In hindsight, this is
confusing, so I won't do it again.

>- How did maven-reporting-api 2.0-alpha-2 get on ibiblio when all I can
>find is versioning 2.0 in the source tree?
>  
>
see above.

>- If you want to separate plugin development from the core development,
>why not use separate repositories? Doing so prevents programming against
>api's in the current checkout, which does not match the version the module
>depends on..
>  
>
will do (there is a JIRA to shuffle things around)

>- If not, why not use SNAPSHOT everywhere?
>  
>
As you guessed abve, its because the plugins aren't tied to the Maven
release.

>- Why are there different versions used througout the repository (and I'm
>not only talking about core/plugin separation).
>
>  
>
the versions are ok - each plugin can have a different one. I'm just not
following our own conventions with 2.0-SNAPSHOT.

>Either you guys make a mess of versions in the repository, or I'm
>completely missing something here..
>  
>
Bit of both :)

>I know it's not really my concern (I should just stick to whatever you
>officially release) but i'd like to learn about how a big project like
>this is organized..
>  
>
Not at all, its great to see you taking this level of interest.

Cheers,
Brett


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

[maven2 build - SUCCESS] Thu May 19 17:07:00 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050519.170700.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.170700.txt

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

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
maven/plugins/
maven/plugins/maven-dashboard-plugin-1.8.jar
maven/plugins/maven-dashboard-plugin-1.8.jar.md5
maven/poms/
maven/poms/maven-dashboard-plugin-1.8.pom
maven/poms/maven-dashboard-plugin-1.8.pom.md5
wrote 681448 bytes  read 106 bytes  3148.06 bytes/sec
total size is 2588214958  speedup is 3797.52
building file list ... done
.index.txt
last-sync.txt
wrote 1088018 bytes  read 70 bytes  1890.68 bytes/sec
total size is 3569457872  speedup is 3280.49

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

[maven2 build - FAILED] Thu May 19 14:07:01 EDT 2005

[jvanzyl]

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.140701.txt

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

build failures -> m2 versioning clarification?

[Kenney Westerhof]

Hi there,

Just tried to bootstrap m2 HEAD (r170983) (with clean repo) and it failed.
Didn't want to make this a JIRA issue (yet).. Below a description,
and a question about m2 versioning. Sorry if this is supposed to be posted
to the users@ list..

First the compilation error:
maven-site-plugin depends on maven-reporting-api 2.0-alpha-2,
which does not have 2 methods defined in MavenReportConfiguration;
the output (see http://rafb.net/paste/results/N8VhdB30.html)
didn't clarify much - only after loading it in eclipse the error
became evident (probably an issue on it's own :)).
After updating the version to 2.0-SNAPSHOT it compiled fine.

Now for my question:
I've asked this before on #maven, but never got a straight answer:
How do you approach the versioning of modules in m2?

The current versioning of modules is unclear to me: plugins have
the following versions:

1.0-alpha-2-SNAPSHOT
1.0-SNAPSHOT
2.0-alpha-2-SNAPSHOT
2.0-alpha-3-SNAPSHOT

whereas for example maven-reporting(-api) lack versions and use the
2.0-SNAPSHOT version defined in the parent pom.

Maven-site-plugin depends on maven-reporting-api 2.0-alpha-2,
and I can't find that that version was ever assigned to that module
in the svn history. Even worse, it uses features not present
in 2.0-alpha-2, but that are present in the svn head.

As you might understand, all this is rather confusing.

So the following questions arise:

- How did maven-reporting-api 2.0-alpha-2 get on ibiblio when all I can
find is versioning 2.0 in the source tree?

- If you want to separate plugin development from the core development,
why not use separate repositories? Doing so prevents programming against
api's in the current checkout, which does not match the version the module
depends on..

- If not, why not use SNAPSHOT everywhere?

- Why are there different versions used througout the repository (and I'm
not only talking about core/plugin separation).

Either you guys make a mess of versions in the repository, or I'm
completely missing something here..

I know it's not really my concern (I should just stick to whatever you
officially release) but i'd like to learn about how a big project like
this is organized..

Thanks for reading this far! :)

Comments really appreciated!

Greetings,

Kenney Westerhof

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

svn commit: r170928 - /maven/maven-1/core/trunk/project.xml

[brett]

Author: brett
Date: Thu May 19 07:05:49 2005
New Revision: 170928

URL: http://svn.apache.org/viewcvs?rev=170928&view=rev
Log:
must use fixed xml tag library, rolling back util due to javadoc issue

Modified:
maven/maven-1/core/trunk/project.xml

Modified: maven/maven-1/core/trunk/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/project.xml?rev=170928&r1=170927&r2=170928&view=diff
==
--- maven/maven-1/core/trunk/project.xml (original)
+++ maven/maven-1/core/trunk/project.xml Thu May 19 07:05:49 2005
@@ -507,13 +507,14 @@
 
   commons-jelly
   commons-jelly-tags-util
-  1.1
+  
+  1.0
   http://jakarta.apache.org/commons/jelly/tags/util/
 
 
   commons-jelly
   commons-jelly-tags-xml
-  1.0
+  1.1-SNAPSHOT
   http://jakarta.apache.org/commons/jelly/tags/xml/
 
 



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

svn commit: r170969 - /maven/components/trunk/pom.xml

[evenisse]

Author: evenisse
Date: Thu May 19 10:05:48 2005
New Revision: 170969

URL: http://svn.apache.org/viewcvs?rev=170969&view=rev
Log:
Add more modules

Modified:
maven/components/trunk/pom.xml

Modified: maven/components/trunk/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/pom.xml?rev=170969&r1=170968&r2=170969&view=diff
==
--- maven/components/trunk/pom.xml (original)
+++ maven/components/trunk/pom.xml Thu May 19 10:05:48 2005
@@ -102,17 +102,22 @@
 
   
   
+maven-archetype
 maven-archiver
 maven-artifact
+maven-artifact-ant
 maven-artifact-test
+maven-core
 maven-model
 maven-monitor
 maven-plugin-api
 maven-plugin-descriptor
+maven-plugins
+maven-plugin-tools
 maven-project
-maven-core
+maven-reporting
+maven-reports
 maven-settings
 maven-script
-maven-reporting
   
 



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

[jira] Created: (MAVENUPLOAD-390) Upload request for maven-statcvs-plugin

[Steffen Pingel (JIRA)]

Upload request for maven-statcvs-plugin
---

 Key: MAVENUPLOAD-390
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-390
 Project: maven-upload-requests
Type: Task
Reporter: Steffen Pingel


http://statcvs-xml.berlios.de/maven-plugin/
http://statcvs-xml.berlios.de/maven-plugin/team-list.html

The statcvs plugin has been updated to depend on the new version of StatCVS-XML 
and  a new goal has been added for the generation of html reports.

-- 
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: (MAVENUPLOAD-389) Upload request for statcvs-xml

[Steffen Pingel (JIRA)]

Upload request for statcvs-xml
--

 Key: MAVENUPLOAD-389
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-389
 Project: maven-upload-requests
Type: Task
Reporter: Steffen Pingel


http://statcvs-xml.berlios.de
http://statcvs-xml.berlios.de/team-list.html

A new version of StatCVS-XML has been released.


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

svn commit: r170965 - in /maven/components/trunk/maven-reports: maven-checkstyle-plugin/pom.xml maven-pmd-plugin/pom.xml maven-project-info-reports-plugin/pom.xml pom.xml

[evenisse]

Author: evenisse
Date: Thu May 19 09:52:47 2005
New Revision: 170965

URL: http://svn.apache.org/viewcvs?rev=170965&view=rev
Log:
o Add a report parent pom
o Reduce dependencies declaration

Added:
maven/components/trunk/maven-reports/pom.xml
Modified:
maven/components/trunk/maven-reports/maven-checkstyle-plugin/pom.xml
maven/components/trunk/maven-reports/maven-pmd-plugin/pom.xml

maven/components/trunk/maven-reports/maven-project-info-reports-plugin/pom.xml

Modified: maven/components/trunk/maven-reports/maven-checkstyle-plugin/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-checkstyle-plugin/pom.xml?rev=170965&r1=170964&r2=170965&view=diff
==
--- maven/components/trunk/maven-reports/maven-checkstyle-plugin/pom.xml 
(original)
+++ maven/components/trunk/maven-reports/maven-checkstyle-plugin/pom.xml Thu 
May 19 09:52:47 2005
@@ -1,9 +1,9 @@
 
   4.0.0
   
-maven-plugin-parent
+maven-report-parent
 org.apache.maven.plugins
-2.0-alpha-2
+2.0-SNAPSHOT
   
   maven-checkstyle-plugin
   2.0-alpha-1-SNAPSHOT
@@ -11,26 +11,6 @@
   Maven Checkstyle Plugin
   2005
   
-
-  org.apache.maven
-  maven-project
-  2.0-alpha-2
-
-
-  doxia
-  doxia-core
-  1.0-alpha-2
-
-
-  org.apache.maven.reporting
-  maven-reporting-api
-  2.0-alpha-2
-
-
-  plexus
-  plexus-utils
-  1.0-alpha-2
-
 
   checkstyle
   checkstyle

Modified: maven/components/trunk/maven-reports/maven-pmd-plugin/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-pmd-plugin/pom.xml?rev=170965&r1=170964&r2=170965&view=diff
==
--- maven/components/trunk/maven-reports/maven-pmd-plugin/pom.xml (original)
+++ maven/components/trunk/maven-reports/maven-pmd-plugin/pom.xml Thu May 19 
09:52:47 2005
@@ -1,9 +1,9 @@
 
   4.0.0
   
-maven-plugin-parent
+maven-report-parent
 org.apache.maven.plugins
-2.0-alpha-2
+2.0-SNAPSHOT
   
   maven-pmd-plugin
   2.0-alpha-1-SNAPSHOT
@@ -12,21 +12,6 @@
   2005
   
 
-  org.apache.maven
-  maven-project
-  2.0-alpha-2
-
-
-  doxia
-  doxia-core
-  1.0-alpha-2
-
-
-  org.apache.maven.reporting
-  maven-reporting-api
-  2.0-alpha-2
-
-
   pmd
   pmd
   3.0
@@ -41,11 +26,6 @@
   saxpath
   saxpath
   1.0-FCS
-
-
-  plexus
-  plexus-utils
-  1.0-alpha-2
 
   
 

Modified: 
maven/components/trunk/maven-reports/maven-project-info-reports-plugin/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-project-info-reports-plugin/pom.xml?rev=170965&r1=170964&r2=170965&view=diff
==
--- 
maven/components/trunk/maven-reports/maven-project-info-reports-plugin/pom.xml 
(original)
+++ 
maven/components/trunk/maven-reports/maven-project-info-reports-plugin/pom.xml 
Thu May 19 09:52:47 2005
@@ -1,35 +1,13 @@
 
   4.0.0
   
-maven-plugin-parent
+maven-report-parent
 org.apache.maven.plugins
-2.0-alpha-2
+2.0-SNAPSHOT
   
   maven-project-info-reports-plugin
   2.0-alpha-1-SNAPSHOT
   maven-plugin
   Maven Project Info Reports Plugin
   2005
-  
-
-  org.apache.maven
-  maven-project
-  2.0-alpha-2
-
-
-  doxia
-  doxia-core
-  1.0-alpha-2
-
-
-  org.apache.maven.reporting
-  maven-reporting-api
-  2.0-alpha-2
-
-
-  org.apache.maven
-  maven-model
-  2.0-alpha-2
-
-  
 

Added: maven/components/trunk/maven-reports/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/pom.xml?rev=170965&view=auto
==
--- maven/components/trunk/maven-reports/pom.xml (added)
+++ maven/components/trunk/maven-reports/pom.xml Thu May 19 09:52:47 2005
@@ -0,0 +1,31 @@
+
+  4.0.0
+  
+maven-plugin-parent
+org.apache.maven.plugins
+2.0-SNAPSHOT
+  
+  maven-report-parent
+  pom
+  2.0-SNAPSHOT
+  Maven Reports
+  Maven report parent
+  
+
+  org.apache.maven.reporting
+  maven-reporting-api
+  2.0-SNAPSHOT
+
+  
+  
+maven-checkstyle-plugin
+maven-javadoc-plugin
+maven-pmd-plugin
+maven-project-info-reports-plugin
+  
+  
+
scm:svn:http://svn.apache.org/repos/asf/maven/components/trunk/maven-reports/
+
scm:svn:https://svn.apache.org/repos/asf/maven/components/trunk/maven-reports/
+
http://svn.apache.org/viewcvs.cgi/maven/components/maven-reports/
+  
+



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

[jira] Closed: (CONTINUUM-105) better input for SCM URL

[Jason van Zyl (JIRA)]

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

Resolution: Won't Fix

> better input for SCM URL
> 
>
>  Key: CONTINUUM-105
>  URL: http://jira.codehaus.org/browse/CONTINUUM-105
>  Project: Continuum
> Type: Improvement
>   Components: continuum-web
> Reporter: Brett Porter
> Assignee: Jason van Zyl
> Priority: Trivial
>  Fix For: 1.0-alpha-2

>
>
> this should not require scm:, and the type should be a dropdown of 
> CVS|SVN|etc. The text input would then just be CVSROOT, SVN URL, etc.

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

Re: [m2] artifact handlers

[Gilles Dodinet]

Brett Porter wrote:
Is there any chance you'd build the plugin tracking the m2 trunk? 

ive tried to build from trunk but encountered some problems with 
bootstrap : i had to build core-it-verifier by hand (using alpha-2), but 
then all it-tests failed because of file not found (however the files 
were actually present). i remember having encountered such issue a while 
back when bootstrapping (as far as i can recall that was a basedir 
issue). i havent investigated this very far and downloaded the last 
snapshot instead.


That
way you could add in a new artifact handler now, and be an additional
guinea pig for configurable handlers and the full lifecycle <-> type
mapping for which we don't have a test for yet.
 

but yet im still not sure how to register an artifact handler. i also 
wonder how i can specify non defualt artifact name mapping. indeed even 
though it is to handle assembly name like any other artifact, assemblies 
generally don't include version in the name (no judgement nor 
appreciation here). on the other hand m2 default repository layout has a 
folder per version so i guess it should be possible to locate a 
dependency even if its name doesn't make the version explicit, not ? 
(although i understand this make it not backward compatible)

concerning the lifecycle i'm not sure how to map it to a specific 
packaging type. it's tempting though to use the artifact handler for 
this. but handlers seem to only define packageGoal(). so how to instruct 
m2 that a project  that has a 'foo' packaging type should be compiled 
with foo-compiler. i'm not sure either to understand the directory() 
method. is this  method present to support m1 repository-style ?

What we have for compilers is in plexus-compilers. It is a generic API
which was developed from a similar base as something at Apache, and I am
actually going to fold that back in to Jakarta Commons JCI for the next
release of the compiler plugin. So we could provide a VS.Net CSharp
implementation and a Mono implementation that people could configure
locally. The goal should remain compiler:compile - though we might need
to look at a better way of configuring the compilers as currently it is
quite java specific.
 

what i have so far is pretty simplistic as you can see at 
http://codehaus.org/~gdodinet/csharp.png. i kinda mimic the java 
compiler and register several (non exhaustive) options through the 
Compiler config. seems more or less enough, however concerning 
references i suppose something more general than classpathElements could 
be nice - very java centric indeed. concerning the ant task i would have 
been happier without it (not mentionning that it needs an ant project - 
however i use 1.5.4, perhaps that changed in 1.6+) but for now i didn't 
wnat to rewrite something similar.

thanks for any comment.
regards,
-- gd
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r170966 - in /maven/components/trunk/maven-reports/maven-javadoc-plugin: ./ src/ src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/ src/main/java/org/apache/maven/ src/main/java/org/apache/maven/plugin/ src/main/java/org/apache/maven/plugin/javadoc/

[evenisse]

Author: evenisse
Date: Thu May 19 09:53:27 2005
New Revision: 170966

URL: http://svn.apache.org/viewcvs?rev=170966&view=rev
Log:
Add a little javadoc report

Added:
maven/components/trunk/maven-reports/maven-javadoc-plugin/
maven/components/trunk/maven-reports/maven-javadoc-plugin/pom.xml
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java

maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReportMojo.java

Added: maven/components/trunk/maven-reports/maven-javadoc-plugin/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-javadoc-plugin/pom.xml?rev=170966&view=auto
==
--- maven/components/trunk/maven-reports/maven-javadoc-plugin/pom.xml (added)
+++ maven/components/trunk/maven-reports/maven-javadoc-plugin/pom.xml Thu May 
19 09:53:27 2005
@@ -0,0 +1,23 @@
+
+  4.0.0
+  
+org.apache.maven.plugins
+maven-report-parent
+2.0-SNAPSHOT
+  
+  maven-javadoc-plugin
+  2.0-SNAPSHOT
+  maven-plugin
+  Maven Javadoc Plugin
+  
+
+  evenisse
+  Emmanuel Venisse
+  [EMAIL PROTECTED]
+  Apache Software Foundation
+  
+Creator
+  
+
+  
+

Added: 
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java?rev=170966&view=auto
==
--- 
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
 (added)
+++ 
maven/components/trunk/maven-reports/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocReport.java
 Thu May 19 09:53:27 2005
@@ -0,0 +1,188 @@
+package org.apache.maven.plugin.javadoc;
+
+/*
+ * Copyright 2004-2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import java.io.File;
+import java.util.Calendar;
+import java.util.Iterator;
+
+import org.apache.maven.reporting.AbstractMavenReport;
+import org.apache.maven.reporting.MavenReportException;
+import org.codehaus.doxia.sink.Sink;
+import org.codehaus.plexus.util.FileUtils;
+import org.codehaus.plexus.util.cli.CommandLineUtils;
+import org.codehaus.plexus.util.cli.Commandline;
+import org.codehaus.plexus.util.cli.DefaultConsumer;
+
+/**
+ * @author mailto:[EMAIL PROTECTED]">Emmanuel Venisse
+ * @version $Id: DependenciesReport.java,v 1.2 2005/02/23 00:08:02 brett Exp $
+ */
+public class JavadocReport
+extends AbstractMavenReport
+{
+
+/**
+ * @see 
org.apache.maven.reporting.AbstractMavenReport#generate(org.codehaus.doxia.sink.Sink)
+ */
+public void generate( Sink sink )
+throws MavenReportException
+{
+if ( getConfiguration() == null )
+{
+throw new MavenReportException( "You must specify a report 
configuration." );
+}
+
+execute();
+}
+
+/**
+ * @see org.apache.maven.reporting.AbstractMavenReport#execute()
+ */
+protected void execute()
+throws MavenReportException
+{
+try
+{
+File outputDir = new File( 
getConfiguration().getReportOutputDirectory().getAbsolutePath() + "/apidocs" );
+outputDir.mkdirs();
+
+int actualYear = Calendar.getInstance().get( Calendar.YEAR );
+String year;
+if ( getConfiguration().getModel().getInceptionYear() != null
+ 

svn commit: r170964 - /maven/maven-1/plugins/tags/MAVEN_DASHBOARD_1_8

[vmassol]

Author: vmassol
Date: Thu May 19 09:43:48 2005
New Revision: 170964

URL: http://svn.apache.org/viewcvs?rev=170964&view=rev
Log:
Prepare for release 1.8 of the Dashboard plugin

Added:
maven/maven-1/plugins/tags/MAVEN_DASHBOARD_1_8/
  - copied from r170963, maven/maven-1/plugins/trunk/dashboard/


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

[jira] Commented: (CONTINUUM-19) Deal with signalled projects on startup

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-19?page=comments#action_39339 ]
 
Jason van Zyl commented on CONTINUUM-19:


What affect does this have really? Are these projects that are scheduled to 
build when Continuum shuts down? Won't they just get picked up by the scheduler 
again? Do we even have signalled projects now?

How about just flushing the queue before shutting down and let the scheduler 
pick them back up for now?

> Deal with signalled projects on startup
> ---
>
>  Key: CONTINUUM-19
>  URL: http://jira.codehaus.org/browse/CONTINUUM-19
>  Project: Continuum
> Type: Improvement
>   Components: continuum-core
> Reporter: Trygve Laugstol
> Assignee: Trygve Laugstol
>  Fix For: 1.0-alpha-2

>
>
> Either
>  - enqueue all signalled projects
>  - remove them
>- Set to the old state?
>- Remove the build request?

-- 
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] Updated: (CONTINUUM-30) Project grouping features

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-30?page=all ]

Jason van Zyl updated CONTINUUM-30:
---

Fix Version: (was: 1.0-alpha-2)
 1.0-alpha-3
Version: 1.0-alpha-3
Environment: 

> Project grouping features
> -
>
>  Key: CONTINUUM-30
>  URL: http://jira.codehaus.org/browse/CONTINUUM-30
>  Project: Continuum
> Type: New Feature
> Versions: 1.0-alpha-3
> Reporter: Jason van Zyl
>  Fix For: 1.0-alpha-3

>
>
> It would be nice to start incorporating some functionality based on groupIds. 
> Sorting by groupId, or a separate page for projects with the same groupId, or 
> reports for a whole groupId. Say a summary failure report with links to 
> details instead of 10 different emails.

-- 
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: (CONTINUUM-30) Project grouping features

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-30?page=comments#action_39341 ]
 
Jason van Zyl commented on CONTINUUM-30:


This is another case where we are not storing the information on the 
ContinuumProject level which we will need to do first. 

> Project grouping features
> -
>
>  Key: CONTINUUM-30
>  URL: http://jira.codehaus.org/browse/CONTINUUM-30
>  Project: Continuum
> Type: New Feature
> Versions: 1.0-alpha-3
> Reporter: Jason van Zyl
>  Fix For: 1.0-alpha-3

>
>
> It would be nice to start incorporating some functionality based on groupIds. 
> Sorting by groupId, or a separate page for projects with the same groupId, or 
> reports for a whole groupId. Say a summary failure report with links to 
> details instead of 10 different emails.

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

[maven2 build - SUCCESS] Thu May 19 16:07:01 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050519.160701.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.160701.txt

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

svn commit: r170961 - /maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8

[vmassol]

Author: vmassol
Date: Thu May 19 09:37:14 2005
New Revision: 170961

URL: http://svn.apache.org/viewcvs?rev=170961&view=rev
Log:
wrong tag redoing it

Removed:
maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8/


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

svn commit: r170960 - /maven/maven-1/plugins/trunk/dashboard/project.xml

[vmassol]

Author: vmassol
Date: Thu May 19 09:34:48 2005
New Revision: 170960

URL: http://svn.apache.org/viewcvs?rev=170960&view=rev
Log:
fix wrong tag... sorry... doing too many things at once :-)

Modified:
maven/maven-1/plugins/trunk/dashboard/project.xml

Modified: maven/maven-1/plugins/trunk/dashboard/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/dashboard/project.xml?rev=170960&r1=170959&r2=170960&view=diff
==
--- maven/maven-1/plugins/trunk/dashboard/project.xml (original)
+++ maven/maven-1/plugins/trunk/dashboard/project.xml Thu May 19 09:34:48 2005
@@ -78,7 +78,7 @@
 
   1.8
   1.8
-  MAVEN_CLOVER_1_8
+  MAVEN_DASHBOARD_1_8
 
   
   



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

[jira] Commented: (CONTINUUM-127) Try using a series of incorrect data in the integration tests

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-127?page=comments#action_39338 
]
 
Jason van Zyl commented on CONTINUUM-127:
-

If we start using the validators at the model level how are we going to deal 
with returning the right messages to the XMLRPC interface and the SOAP 
interface?


> Try using a series of incorrect data in the integration tests
> -
>
>  Key: CONTINUUM-127
>  URL: http://jira.codehaus.org/browse/CONTINUUM-127
>  Project: Continuum
> Type: Task
> Versions: 1.0-alpha-2
> Reporter: Jason van Zyl
> Assignee: Trygve Laugstol
> Priority: Critical
>  Fix For: 1.0-alpha-2

>
>
> We need to trap any incorrect data being thrown at continuum coming from any 
> interface. The best place to try this is the integration tests that we run 
> from python. I accidentally used some bad POMs using the xmlrpc interface and 
> in the web interface the projects seems to stay perpetually in the "Checking 
> Out" state.

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

svn commit: r170954 - /maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia /maven/components/trunk/maven-reporting/maven-reporting-api /maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting /maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle /maven/components/trunk/maven-reports/maven-pmd-plugin/src/main/java/org/apache/maven/plugin/pmd /maven/components/trunk/maven-reports/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo

[evenisse]

Author: evenisse
Date: Thu May 19 09:27:00 2005
New Revision: 170954

URL: http://svn.apache.org/viewcvs?rev=170954&view=rev
Log:
o clean import
o Use MavenProject instead of Model for obtain more informations

Modified:

maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReport.java

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReportConfiguration.java

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReportRenderer.java

maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java

maven/components/trunk/maven-reports/maven-pmd-plugin/src/main/java/org/apache/maven/plugin/pmd/PmdReportMojo.java

maven/components/trunk/maven-reports/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ProjectReportsMojo.java

Modified: 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java?rev=170954&r1=170953&r2=170954&view=diff
==
--- 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
 (original)
+++ 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
 Thu May 19 09:27:00 2005
@@ -124,7 +124,9 @@
 
 MavenReportConfiguration config = new MavenReportConfiguration();
 
-config.setModel( project.getModel() );
+config.setProject( project );
+
+config.setReportOutputDirectory( new File( outputDirectory ) );
 
 //Generate reports
 if ( reports != null )

Modified: maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml?rev=170954&r1=170953&r2=170954&view=diff
==
--- maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml 
(original)
+++ maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml Thu May 
19 09:27:00 2005
@@ -9,7 +9,7 @@
   
 
   org.apache.maven
-  maven-model
+  maven-project
   2.0-SNAPSHOT
 
 

Modified: 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java?rev=170954&r1=170953&r2=170954&view=diff
==
--- 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java
 (original)
+++ 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenReport.java
 Thu May 19 09:27:00 2005
@@ -17,10 +17,7 @@
  */
 
 import org.codehaus.doxia.sink.Sink;
-import org.codehaus.doxia.module.xdoc.XdocSink;
 
-import java.io.File;
-import java.io.FileWriter;
 import java.io.IOException;
 
 /**

Modified: 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReport.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReport.java?rev=170954&r1=170953&r2=170954&view=diff
==
--- 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReport.java
 (original)
+++ 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReport.java
 Thu May 19 09:27:00 2005
@@ -18,7 +18,6 @@
 
 import org.codehaus.doxia.sink.Sink;
 
-import java.io.File;
 import java.io.IOException;
 
 /**

Modified: 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReportConfiguration.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/MavenReportConfiguration.java?rev=170954&r1=170953&r2=170954&view=diff
=

svn commit: r170958 - in /maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8/dashboard: ./ project.xml xdocs/changes.xml

[vmassol]

Author: vmassol
Date: Thu May 19 09:30:30 2005
New Revision: 170958

URL: http://svn.apache.org/viewcvs?rev=170958&view=rev
Log:
[maven-scm] copy for tag MAVEN_CLOVER_1_8

Added:
maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8/dashboard/
  - copied from r170952, maven/maven-1/plugins/trunk/dashboard/
maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8/dashboard/project.xml
  - copied unchanged from r170957, 
maven/maven-1/plugins/trunk/dashboard/project.xml
maven/maven-1/plugins/tags/MAVEN_CLOVER_1_8/dashboard/xdocs/changes.xml
  - copied unchanged from r170957, 
maven/maven-1/plugins/trunk/dashboard/xdocs/changes.xml


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

[jira] Updated: (CONTINUUM-39) build in the correct order

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-39?page=all ]

Jason van Zyl updated CONTINUUM-39:
---

Fix Version: (was: 1.0-alpha-2)
 1.0-alpha-3
Version: (was: 1.0-alpha-2)
 1.0-alpha-3

> build in the correct order
> --
>
>  Key: CONTINUUM-39
>  URL: http://jira.codehaus.org/browse/CONTINUUM-39
>  Project: Continuum
> Type: Improvement
> Versions: 1.0-alpha-3
> Reporter: Brett Porter
> Assignee: Trygve Laugstol
> Priority: Critical
>  Fix For: 1.0-alpha-3

>
>
> I'm unsure if this is already the case - it didn't appear to be.
> If a project is going to depend on the output of another scheduled continuum 
> build (ie dependency id including version matches that of the other project's 
> id), then they should be built in the correct order, as in the reactor.

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

svn commit: r170957 - in /maven/maven-1/plugins/trunk/dashboard: project.xml xdocs/changes.xml

[vmassol]

Author: vmassol
Date: Thu May 19 09:30:06 2005
New Revision: 170957

URL: http://svn.apache.org/viewcvs?rev=170957&view=rev
Log:
[maven-scm-plugin] prepare release 1.8

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

Modified: maven/maven-1/plugins/trunk/dashboard/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/dashboard/project.xml?rev=170957&r1=170956&r2=170957&view=diff
==
--- maven/maven-1/plugins/trunk/dashboard/project.xml (original)
+++ maven/maven-1/plugins/trunk/dashboard/project.xml Thu May 19 09:30:06 2005
@@ -23,7 +23,7 @@
   3
   maven-dashboard-plugin
   Maven Dashboard Plugin
-  1.8-SNAPSHOT
+  1.8
   Generate a dashboard containing global statistics about other 
maven reports
   Generate a statistic dashboard
   http://maven.apache.org/reference/plugins/dashboard/
@@ -74,6 +74,11 @@
   1.7
   1.7
   MAVEN_DASHBOARD_1_7
+
+
+  1.8
+  1.8
+  MAVEN_CLOVER_1_8
 
   
   

Modified: maven/maven-1/plugins/trunk/dashboard/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/dashboard/xdocs/changes.xml?rev=170957&r1=170956&r2=170957&view=diff
==
--- maven/maven-1/plugins/trunk/dashboard/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/dashboard/xdocs/changes.xml Thu May 19 09:30:06 
2005
@@ -24,22 +24,16 @@
 Vincent Massol
   
   
-
-  
-Added aggregator totals to the HTML report.
+
+  Added aggregator totals to the HTML report.
+  Default values for
+maven.dashboard.basedir,
+maven.dashboard.includes,
+maven.dashboard.excludesand
+maven.dashboard.ignoreFailuresare copied from the 
equivalent Multiproject properties. This should reduce the number of properties 
you have to set to get going as you need now only set the Multiproject 
properties.
   
-  
-Default values for maven.dashboard.basedir,
-maven.dashboard.includes, 
maven.dashboard.excludes
-and maven.dashboard.ignoreFailures are copied from
-the equivalent Multiproject properties. This should reduce the number 
of
-properties you have to set to get going as you need now only set the
-Multiproject properties.
-  
-  
-Prevent failure in junitpassrate.jelly due to a division 
-by zero when there is a unit test source directory defined but no 
tests 
-are executed.
+  Prevent failure in
+junitpassrate.jellydue to a division by zero when there 
is a unit test source directory defined but no tests are executed.
   
 
 



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

[jira] Reopened: (CONTINUUM-105) better input for SCM URL

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-105?page=all ]
 
Jason van Zyl reopened CONTINUUM-105:
-


> better input for SCM URL
> 
>
>  Key: CONTINUUM-105
>  URL: http://jira.codehaus.org/browse/CONTINUUM-105
>  Project: Continuum
> Type: Improvement
>   Components: continuum-web
> Reporter: Brett Porter
> Assignee: Jason van Zyl
> Priority: Trivial
>  Fix For: 1.0-alpha-2

>
>
> this should not require scm:, and the type should be a dropdown of 
> CVS|SVN|etc. The text input would then just be CVSROOT, SVN URL, etc.

-- 
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] Closed: (CONTINUUM-105) better input for SCM URL

[Jason van Zyl (JIRA)]

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

Resolution: Fixed

I thought about and we are dealing with Maven SCM internally so I'm just going 
to link to provide examples and point to a reference on Maven SCM urls. The SCM 
URL is great for capturing the differences in the SCMs in one input. If this is 
actually something users complain about (and I don't think it's that big a 
deal) then I'll create a wizard for each SCM because they all have quirks and 
different ways of specifying things which is why the scm url is great.

> better input for SCM URL
> 
>
>  Key: CONTINUUM-105
>  URL: http://jira.codehaus.org/browse/CONTINUUM-105
>  Project: Continuum
> Type: Improvement
>   Components: continuum-web
> Reporter: Brett Porter
> Assignee: Jason van Zyl
> Priority: Trivial
>  Fix For: 1.0-alpha-2

>
>
> this should not require scm:, and the type should be a dropdown of 
> CVS|SVN|etc. The text input would then just be CVSROOT, SVN URL, etc.

-- 
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] Created: (MPARTIFACT-48) jar:deploy fails if project.xml is not in the current directory

[Jean-Luc Wasmer (JIRA)]

jar:deploy fails if project.xml is not in the current directory
---

 Key: MPARTIFACT-48
 URL: http://jira.codehaus.org/browse/MPARTIFACT-48
 Project: maven-artifact-plugin
Type: Bug
Versions: 1.4.1
 Environment: Windows XP Pro SP2 - Java 1.5.0
Reporter: Jean-Luc Wasmer


When I call maven from a batch file and the project.xml file is not in the 
current directory, the jar:deploy goal fails because it doesn't give the right 
path to scp:

Executing command: scp project.xml [EMAIL 
PROTECTED]:/home/htdocs/maven/profilium-util/poms/profilium-util-0.5-SNAPSHOT.pom
ERROR>project.xml: No such file or directory

Relevant commands in the batch file:

set repodir=D:\development
call maven -X -p "%repodir%\profilium-util\project.xml" %1

The site:deploy goal works fine.

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

svn commit: r170989 - in /maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact: Artifact.java metadata/ArtifactMetadata.java repository/ArtifactRepository.java resolver/ArtifactResolver.java transform/AbstractVersionTransformation.java

[evenisse]

Author: evenisse
Date: Thu May 19 13:23:45 2005
New Revision: 170989

URL: http://svn.apache.org/viewcvs?rev=170989&view=rev
Log:
Clean imports

Modified:

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/Artifact.java

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/metadata/ArtifactMetadata.java

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepository.java

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolver.java

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/transform/AbstractVersionTransformation.java

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/Artifact.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/Artifact.java?rev=170989&r1=170988&r2=170989&view=diff
==
--- 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/Artifact.java
 (original)
+++ 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/Artifact.java
 Thu May 19 13:23:45 2005
@@ -19,7 +19,6 @@
 import org.apache.maven.artifact.metadata.ArtifactMetadata;
 import org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException;
 import org.apache.maven.artifact.repository.ArtifactRepository;
-import org.apache.maven.artifact.repository.layout.ArtifactPathFormatException;
 
 import java.io.File;
 import java.util.List;

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/metadata/ArtifactMetadata.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/metadata/ArtifactMetadata.java?rev=170989&r1=170988&r2=170989&view=diff
==
--- 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/metadata/ArtifactMetadata.java
 (original)
+++ 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/metadata/ArtifactMetadata.java
 Thu May 19 13:23:45 2005
@@ -19,9 +19,6 @@
 import org.apache.maven.artifact.Artifact;
 import org.apache.maven.artifact.repository.ArtifactRepository;
 
-import java.io.File;
-import java.util.Date;
-
 /**
  * Contains metadata about an artifact, and methods to retrieve/store it from 
an artifact repository.
  *

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepository.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepository.java?rev=170989&r1=170988&r2=170989&view=diff
==
--- 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepository.java
 (original)
+++ 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/ArtifactRepository.java
 Thu May 19 13:23:45 2005
@@ -20,7 +20,6 @@
 import org.apache.maven.artifact.metadata.ArtifactMetadata;
 import org.apache.maven.artifact.repository.layout.ArtifactPathFormatException;
 import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout;
-import org.apache.maven.wagon.authentication.AuthenticationInfo;
 import org.apache.maven.wagon.repository.Repository;
 
 /**

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolver.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolver.java?rev=170989&r1=170988&r2=170989&view=diff
==
--- 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolver.java
 (original)
+++ 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolver.java
 Thu May 19 13:23:45 2005
@@ -18,7 +18,6 @@
 
 import org.apache.maven.artifact.Artifact;
 import org.apache.maven.artifact.metadata.ArtifactMetadataSource;
-import org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException;
 import org.apache.maven.artifact.repository.ArtifactRepository;
 import org.apache.maven.artifact.resolver.filter.ArtifactFilter;
 

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/transform/AbstractVersionTransformation.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/transform/AbstractVersionTransformation.java?rev=170989&r1=170988&r2=170989&view=diff

[jira] Created: (CONTINUUM-137) Store dependency information at the ContinuumProject level

[Jason van Zyl (JIRA)]

Store dependency information at the ContinuumProject level
--

 Key: CONTINUUM-137
 URL: http://jira.codehaus.org/browse/CONTINUUM-137
 Project: Continuum
Type: New Feature
Versions: 1.0-alpha-3
Reporter: Jason van Zyl
 Fix For: 1.0-alpha-3


In order to be able to build in any deterministic order we need dependency 
information on all the projects entered into the system.

-- 
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: (CONTINUUM-39) build in the correct order

[Jason van Zyl (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-39?page=comments#action_39334 ]
 
Jason van Zyl commented on CONTINUUM-39:


This would effect scheduled builds where all, or a group of, projects are built 
and when the "Build All" button is used.

This would require us storing dependency information for each of the continuum 
projects which we currently do not have.

We would need to make forms to input the dependency data for Ant and Shell 
projects. This is making me wonder if we're not just going to end up with 
pseudo POMs for all project types anyway.

We do not currently have support for dependencies amongst the builds so I have 
entered a new issues for this and will link it. But this will have to go to 
alpha-3.

> build in the correct order
> --
>
>  Key: CONTINUUM-39
>  URL: http://jira.codehaus.org/browse/CONTINUUM-39
>  Project: Continuum
> Type: Improvement
> Versions: 1.0-alpha-2
> Reporter: Brett Porter
> Assignee: Trygve Laugstol
> Priority: Critical
>  Fix For: 1.0-alpha-2

>
>
> I'm unsure if this is already the case - it didn't appear to be.
> If a project is going to depend on the output of another scheduled continuum 
> build (ie dependency id including version matches that of the other project's 
> id), then they should be built in the correct order, as in the reactor.

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

svn commit: r170987 - in /maven/components/trunk/maven-core/src/main/java/org/apache/maven: Maven.java usability/ArtifactResolverDiagnoser.java

[evenisse]

Author: evenisse
Date: Thu May 19 13:14:08 2005
New Revision: 170987

URL: http://svn.apache.org/viewcvs?rev=170987&view=rev
Log:
Clean imports

Modified:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/Maven.java

maven/components/trunk/maven-core/src/main/java/org/apache/maven/usability/ArtifactResolverDiagnoser.java

Modified: 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/Maven.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-core/src/main/java/org/apache/maven/Maven.java?rev=170987&r1=170986&r2=170987&view=diff
==
--- maven/components/trunk/maven-core/src/main/java/org/apache/maven/Maven.java 
(original)
+++ maven/components/trunk/maven-core/src/main/java/org/apache/maven/Maven.java 
Thu May 19 13:14:08 2005
@@ -19,8 +19,6 @@
 import org.apache.maven.execution.MavenExecutionRequest;
 import org.apache.maven.execution.MavenExecutionResponse;
 import org.apache.maven.reactor.ReactorException;
-import org.apache.maven.project.ProjectBuildingException;
-import org.apache.maven.artifact.resolver.ArtifactResolutionException;
 
 /**
  * @author mailto:[EMAIL PROTECTED]">Jason van Zyl 

Modified: 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/usability/ArtifactResolverDiagnoser.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-core/src/main/java/org/apache/maven/usability/ArtifactResolverDiagnoser.java?rev=170987&r1=170986&r2=170987&view=diff
==
--- 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/usability/ArtifactResolverDiagnoser.java
 (original)
+++ 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/usability/ArtifactResolverDiagnoser.java
 Thu May 19 13:14:08 2005
@@ -18,11 +18,7 @@
 
 import org.apache.maven.artifact.resolver.ArtifactResolutionException;
 import 
org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException;
-import org.apache.maven.artifact.repository.ArtifactRepository;
 import org.apache.maven.project.ProjectBuildingException;
-
-import java.util.List;
-import java.util.Iterator;
 
 public class ArtifactResolverDiagnoser
 implements ErrorDiagnoser



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

Re: and m2

[Steve Loughran]

Brett Porter wrote:
(bringing over to maven dev as Steve suggested)
On 5/19/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
A key issue w/ transitive dependencies is that I may not want a library,
just because it was used in a library I want. Certainly I need the right
to override versions. This is why dependency declarations in JAR file
manifests is so broken; the builder of the jar is telling the deployer
what files they MUST use, not what files they SHOULD use.

Right - this is the direction we are pushing. To get dependencies to
specify the versions they recommend, but because we still have
"nearest wins", you always get to veto that if necessary.

One thing I've felt might be good in dependency declarations (or in the
POM) would be for something to declare what well-known-APIs they
implement. So that if one version of JAX-RPC is declared, you don't need
another.

http://docs.codehaus.org/display/MAVEN/specification+dependencies
got it. yes, JAXP is the case in point. you dont care what people built 
against, as long as it is the same version of the spec. Maybe projects 
need to declare they were built against an API for xml, just like 
commons-logging-api.


In my mind it was bettter to leave this for a later Maven 2.1 feature
release, after we were confident with the versioning aspects of normal
dependencies, because this adds an extra level of complexity on top of
that. And a lot of specifications have found their way into the JDK so
become specified explicitly less.
yes, it is just that I cant currently import Xom, for example, because 
it pulls in jaxen which pulls in dom4j. I now have a private release 
with a dependency-free POM in my local cache.


Maybe the version policy could be pluggable
policy=none   //no transitiveness
   newest-wins  //newest matters
   nearest-wins //closest declaration matters
   fail //fail on conflict
though I think I'm mixing policy of transitive on/off with conflict
resolution here. hmm.
yeah, I think they are separate. the rest sound like the conflict
strategies I'd envisage. There may be others as well (eg, deploying to
a particular appserver, so make sure you get version X of all these
because they'll be forced on you).
aah, and then there are endorsed directories, worst case of all 'we know 
better' overrides.

I'm not sure "no transitiveness" is a good idea. I think it's
something that once available, people will use as the quick fix to a
problem rather than figuring out a real cause, and miss an opportunity
to improve the overall quality of the data. Which would be ironic,
given how long people asked for transitive deps - to turn it off so
quickly - but I knew that it would come because as you said earlier,
version management isn't a trivial problem. If you are the one
building the libraries, it requires discipline to keep compatibility,
consistent naming, etc.
I'd prefer to be able to filter out unwanted dependencies as an
alternative to turning it off.
yes, a block would work.

I've just subscribed to maven dev; I will discuss it there.

welcome :) I've been planning to take a pass at this design for
alpha-3 tomorrow, so I'll reply to anything else in the morning.
ok. one more troublespot is that no pom should be a warning, not an 
error. there are things on the site without poms, and it is easier to 
pull third party libs in to shape without writing pom files. That said, 
it'd be nice to have a set of .pom files to go with the various java 
libraries, maybe even some client program to do the 
retrieve/clickthrough/version-tag/save processing to bring them into the 
repository structure.

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

Re: [jira] Commented: (MNG-415) allow exclusion of certain depend encies from inclusion in an archive

[Brett Porter]

my comments inline. To me, you seem to be viewing all of dependency
management through the eyes of a single use case (being war exclusions),
which is where we are disagreeing.

Maczka Michal wrote:

>And it indeed requires some amount of extra work in a very limited set of
>cases ( "triples what needs to be specified " is not really accurate - see
>below).  
>
To allow for multiple values:
foo
becomes

  foo

if we are to retain the conventions used so far.

>But if you compare this to amount of work needed in any other
>solution I can think of it actually reduces that amount by much larger
>factor (probably more then 10).  
>
Actaully, your example adds 3 lines instead of 1, so its a factor of 3,
not 10 - exactly the same - but for the other example each additional
dependency is only one more on top of that, instead of 3 or 4 again as
you are proposing :)

But, really, I didn't intend to nitpick about the number of lines
needed. That's not the point I was getting at.

>So if you look for simplicity - this is
>probaly the simplest solution. Just to exclude serlvletapi from war you will
>have to change:
>  
>
Or for simplicity, let's make servletapi a default exclude for WAR and
not configure anything. It's not worth changing the defiition of the
dependencies for a single JAR.

>Sure. But war is an assembling plugin and if you have project packaging set
>to "war" you are actually not likely going to use the same pom for creating
>other assemblies and you definitly know something about environment in which
>this artifact will be used (servlet container). It is just a question if
>standard attributes of dependencies are sufficient or not and if they are
>not sufficient how it can be done in the other way. 
>Anyway scope tag (scope=test) is already used for filtering out artifacts
>from assemblies so I don't see what's actually the problem with that.
>
>  
>
I'm probably missing something, but I can't see how what you are saying
here is related to my point at all. I'm saying you can't change the
definition of scope for the entire system to fit the war use case.

>>From a pure point of view a compile time dependency is always needed at
>runtime (unless the code is never hit, or the server provides the jar, all
>of which is environmental, not by >definition) 
>
>Not true. For example servletapi is a jar agaist which you want to compile
>but most servlet containers have classes from that jar bundled in their own
>jars which have completely different names. 
>  
>
Read what I wrote again. The servletapi, needed at compile time, is also
needed at runtime. You've just said so yourself. Just because the
container happens to provide it, doesn't change anything.

Since we seem to be stuck on servletapi, let's go to a practical
example. You run some tests using a mock library that calls your code,
which utilises the servletapi. No container. What scope does the
servletapi have in your proposal? You'll probably answer "compile, test"
which in this example is valid. What if these tests were not junit
tests, but some other set using the "runtime" classpath? So you add
runtime to servletapi and now it is automatically included in the war -
exactly what you didn't want.

We can't mix concepts. scope != bundling, so we can't try and abuse it
to make it the same. It will give you the right default 99% of the time,
the other 1% you need to configure it, under the war plugin in terms of
bundling.

>I think this case qualifies for such change :) 
>  
>
That's much easier for you to say since you aren't doing the work :)

You can't argue the point in terms of one use case. You need to address
how all the counter examples raised would work under your scheme too.
Then, if there are others who agree that is better, we can look into it.
But I think the confusion here is just how it is being communicated, not
that the concept is broken.

- Brett


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

svn commit: r170986 - /maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install /maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release /maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia

[evenisse]

Author: evenisse
Date: Thu May 19 13:07:49 2005
New Revision: 170986

URL: http://svn.apache.org/viewcvs?rev=170986&view=rev
Log:
Clean imports

Modified:

maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java

maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release/PrepareReleaseMojo.java

maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/ScpSiteDeployMojo.java

Modified: 
maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java?rev=170986&r1=170985&r2=170986&view=diff
==
--- 
maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java
 (original)
+++ 
maven/components/trunk/maven-plugins/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java
 Thu May 19 13:07:49 2005
@@ -19,10 +19,7 @@
 import org.apache.maven.artifact.Artifact;
 import org.apache.maven.artifact.DefaultArtifact;
 import org.apache.maven.artifact.installer.ArtifactInstallationException;
-import org.apache.maven.artifact.installer.ArtifactInstaller;
 import org.apache.maven.artifact.metadata.ArtifactMetadata;
-import org.apache.maven.artifact.repository.ArtifactRepository;
-import org.apache.maven.plugin.AbstractMojo;
 import org.apache.maven.plugin.MojoExecutionException;
 import org.apache.maven.project.artifact.ProjectArtifactMetadata;
 

Modified: 
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release/PrepareReleaseMojo.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release/PrepareReleaseMojo.java?rev=170986&r1=170985&r2=170986&view=diff
==
--- 
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release/PrepareReleaseMojo.java
 (original)
+++ 
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugin/release/PrepareReleaseMojo.java
 Thu May 19 13:07:49 2005
@@ -31,9 +31,6 @@
 import org.codehaus.plexus.components.inputhandler.InputHandler;
 import org.codehaus.plexus.util.StringUtils;
 
-import java.io.BufferedReader;
-import java.io.IOException;
-import java.io.InputStreamReader;
 import java.util.ArrayList;
 import java.util.Collections;
 import java.util.Iterator;

Modified: 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/ScpSiteDeployMojo.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/ScpSiteDeployMojo.java?rev=170986&r1=170985&r2=170986&view=diff
==
--- 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/ScpSiteDeployMojo.java
 (original)
+++ 
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/ScpSiteDeployMojo.java
 Thu May 19 13:07:49 2005
@@ -9,9 +9,7 @@
 import org.apache.maven.plugin.MojoExecutionException;
 import org.apache.maven.project.MavenProject;
 import org.apache.maven.wagon.ConnectionException;
-import org.apache.maven.wagon.WagonUtils;
 import org.apache.maven.wagon.observers.Debug;
-import org.apache.maven.wagon.providers.ssh.ScpWagon;
 import org.apache.maven.wagon.providers.ssh.SshCommandExecutor;
 import org.apache.maven.wagon.repository.Repository;
 import org.codehaus.plexus.util.FileUtils;



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

svn commit: r170985 - /maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle

[evenisse]

Author: evenisse
Date: Thu May 19 13:07:46 2005
New Revision: 170985

URL: http://svn.apache.org/viewcvs?rev=170985&view=rev
Log:
Clean imports

Modified:

maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReport.java

maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java

Modified: 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReport.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReport.java?rev=170985&r1=170984&r2=170985&view=diff
==
--- 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReport.java
 (original)
+++ 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReport.java
 Thu May 19 13:07:46 2005
@@ -18,7 +18,6 @@
 
 import org.apache.maven.reporting.AbstractMavenReport;
 import org.apache.maven.reporting.MavenReportException;
-import org.codehaus.doxia.sink.Sink;
 import org.codehaus.plexus.util.FileUtils;
 import org.codehaus.plexus.util.StringUtils;
 

Modified: 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java?rev=170985&r1=170984&r2=170985&view=diff
==
--- 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java
 (original)
+++ 
maven/components/trunk/maven-reports/maven-checkstyle-plugin/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleReportMojo.java
 Thu May 19 13:07:46 2005
@@ -21,7 +21,6 @@
 import org.apache.maven.project.MavenProject;
 import org.apache.maven.reporting.MavenReport;
 import org.apache.maven.reporting.MavenReportConfiguration;
-import org.apache.maven.reporting.MavenReportException;
 import org.codehaus.doxia.module.xhtml.XhtmlSink;
 import org.codehaus.doxia.site.renderer.SiteRenderer;
 import org.codehaus.plexus.util.FileUtils;



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

svn commit: r170984 - /maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml

[evenisse]

Author: evenisse
Date: Thu May 19 12:57:09 2005
New Revision: 170984

URL: http://svn.apache.org/viewcvs?rev=170984&view=rev
Log:
Use new reporting-api dependency

Modified:
maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml

Modified: maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml?rev=170984&r1=170983&r2=170984&view=diff
==
--- maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml (original)
+++ maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml Thu May 19 
12:57:09 2005
@@ -11,14 +11,9 @@
   Maven Site plugin
   
 
-  org.apache.maven
-  maven-project
-  2.0-alpha-2
-
-
   org.apache.maven.reporting
   maven-reporting-api
-  2.0-alpha-2
+  2.0-SNAPSHOT
 
 
   doxia



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

Re: and m2

[Dan Diephouse]

Brett Porter wrote:
I'm not sure "no transitiveness" is a good idea. I think it's
something that once available, people will use as the quick fix to a
problem rather than figuring out a real cause, and miss an opportunity
to improve the overall quality of the data. Which would be ironic,
given how long people asked for transitive deps - to turn it off so
quickly - but I knew that it would come because as you said earlier,
version management isn't a trivial problem. If you are the one
building the libraries, it requires discipline to keep compatibility,
consistent naming, etc.
I'd prefer to be able to filter out unwanted dependencies as an
alternative to turning it off.
I've been thinking about this because this annoys me a lot :-). As Steve 
so excellently put it, a lot of times dependencies are a SHOULD not a 
MUST. But transitive dependencies do give us a degree of power.

Requiring the user to override/exclude dependencies in their pom somehow 
would be kind of a pain. But, what if m2 made it simple for a user to 
change this. Ie m2 would iterate through the dependency conflicts and 
allow you to select different options.

For example:
$ m2 dosomething
You have 3 different versions of xerces in your classpath. Please select 
which one you would like to use:
(1) 2.4.1
(2) 2.6.0
(3) 2.6.2
> ?

One could imagine a similar interface which allowed users to exclude 
dependencies from different child poms as well.  It would then write out 
the information to the pom or another file. Would this work for the ant 
tasks too?

I guess I'm just thinking how to make it easier for the user, because I 
believe that ease of entry will be a real barrier to use the way things 
are now. 

- Dan
--
Dan Diephouse
Envoi Solutions LLC
http://netzooid.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 8 (16 including POMs).
building file list ... done
last-sync.txt
nanocontainer/jars/
nanocontainer/jars/nanocontainer-1.0-SNAPSHOT.jar
nanocontainer/jars/nanocontainer-deployer-1.0-SNAPSHOT.jar
nanocontainer/jars/nanocontainer-nanowar-1.0-SNAPSHOT.jar
nanocontainer/jars/nanocontainer-remoting-1.0-SNAPSHOT.jar
nanocontainer/jars/nanocontainer-swing-1.0-SNAPSHOT.jar
nanocontainer/poms/
nanocontainer/poms/nanocontainer-1.0-SNAPSHOT.pom
nanocontainer/poms/nanocontainer-nanowar-1.0-SNAPSHOT.pom
nanocontainer/poms/nanocontainer-persistence-1.0-SNAPSHOT.pom
nanocontainer/poms/nanocontainer-remoting-1.0-SNAPSHOT.pom
picocontainer/jars/
picocontainer/jars/picocontainer-1.2-SNAPSHOT.jar
picocontainer/jars/picocontainer-gems-1.2-SNAPSHOT.jar
picocontainer/jars/picocontainer-tck-1.2-SNAPSHOT.jar
picocontainer/poms/
picocontainer/poms/picocontainer-1.2-SNAPSHOT.pom
picocontainer/poms/picocontainer-gems-1.2-SNAPSHOT.pom
wrote 938057 bytes  read 5396 bytes  2361.58 bytes/sec
total size is 2585989299  speedup is 2740.98
building file list ... done
.index.txt
last-sync.txt
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.jar
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.jar.md5
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.jar.sha1
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.pom
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.pom.md5
nanocontainer/nanocontainer-deployer/1.0-SNAPSHOT/nanocontainer-deployer-1.0-SNAPSHOT.pom.sha1
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.jar
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.jar.md5
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.jar.sha1
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.pom
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.pom.md5
nanocontainer/nanocontainer-nanowar/1.0-SNAPSHOT/nanocontainer-nanowar-1.0-SNAPSHOT.pom.sha1
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.jar
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.jar.md5
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.jar.sha1
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.pom
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.pom.md5
nanocontainer/nanocontainer-remoting/1.0-SNAPSHOT/nanocontainer-remoting-1.0-SNAPSHOT.pom.sha1
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.jar
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.jar.md5
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.jar.sha1
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.pom
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.pom.md5
nanocontainer/nanocontainer-swing/1.0-SNAPSHOT/nanocontainer-swing-1.0-SNAPSHOT.pom.sha1
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.jar
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.jar.md5
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.jar.sha1
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.pom
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.pom.md5
nanocontainer/nanocontainer/1.0-SNAPSHOT/nanocontainer-1.0-SNAPSHOT.pom.sha1
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.jar
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.jar.md5
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.jar.sha1
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.pom
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.pom.md5
picocontainer/picocontainer-gems/1.2-SNAPSHOT/picocontainer-gems-1.2-SNAPSHOT.pom.sha1
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.jar
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.jar.md5
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.jar.sha1
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.pom
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.pom.md5
picocontainer/picocontainer-tck/1.2-SNAPSHOT/picocontainer-tck-1.2-SNAPSHOT.pom.sha1
picocontainer/picocontainer/1.2-SNAPSHOT/picocontainer-1.2-SNAPSHOT.jar
picocontainer/

Re: Converting plugins from M1 to M2

[Dennis Lundberg]

Jason van Zyl wrote:
On Tue, 2005-05-17 at 09:08 +0200, Dennis Lundberg wrote:
Hello
I'm thinking about trying to convert the tasklist plugin from Maven 1 to
Maven 2. Are there any good (not that complicated) plugins to look at,
that has been converted to M2? I need some example to look at, to get to
grips with what needs to be done.

How about I give you the stub of a tasklist plugin and then you take it
from there? I have todos all over the place and would really like that
plugin done so I'd be willing you do up a feature lean version if you
want to take it over.
That would be great!
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: and m2

[Brett Porter]

(bringing over to maven dev as Steve suggested)

On 5/19/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
> A key issue w/ transitive dependencies is that I may not want a library,
> just because it was used in a library I want. Certainly I need the right
> to override versions. This is why dependency declarations in JAR file
> manifests is so broken; the builder of the jar is telling the deployer
> what files they MUST use, not what files they SHOULD use.

Right - this is the direction we are pushing. To get dependencies to
specify the versions they recommend, but because we still have
"nearest wins", you always get to veto that if necessary.

> One thing I've felt might be good in dependency declarations (or in the
> POM) would be for something to declare what well-known-APIs they
> implement. So that if one version of JAX-RPC is declared, you don't need
> another.

http://docs.codehaus.org/display/MAVEN/specification+dependencies

In my mind it was bettter to leave this for a later Maven 2.1 feature
release, after we were confident with the versioning aspects of normal
dependencies, because this adds an extra level of complexity on top of
that. And a lot of specifications have found their way into the JDK so
become specified explicitly less.

> > The final project should use the most recent
> > version allowed by all of the definitions (on the assumption that the
> > most recent is backwards compatible and has less bugs than earlier
> > versions :)
> 
> That's one assumption, but I take the view is that If I explicitly ask
> for an older version, I should get that (albeit maybe with a warning).

Absolutely. I was just suggesting an algorithm that would determine
the best version unaided, but when it comes down to it the final
project has to decide. In a lot of cases, an older version might work
just fine because several other projects have overstated their needs,
but a warning is still a good idea.

> Maybe the version policy could be pluggable
> 
> policy=none   //no transitiveness
> newest-wins  //newest matters
> nearest-wins //closest declaration matters
> fail //fail on conflict
> 
> though I think I'm mixing policy of transitive on/off with conflict
> resolution here. hmm.

yeah, I think they are separate. the rest sound like the conflict
strategies I'd envisage. There may be others as well (eg, deploying to
a particular appserver, so make sure you get version X of all these
because they'll be forced on you).

I'm not sure "no transitiveness" is a good idea. I think it's
something that once available, people will use as the quick fix to a
problem rather than figuring out a real cause, and miss an opportunity
to improve the overall quality of the data. Which would be ironic,
given how long people asked for transitive deps - to turn it off so
quickly - but I knew that it would come because as you said earlier,
version management isn't a trivial problem. If you are the one
building the libraries, it requires discipline to keep compatibility,
consistent naming, etc.

I'd prefer to be able to filter out unwanted dependencies as an
alternative to turning it off.

> I've just subscribed to maven dev; I will discuss it there.

welcome :) I've been planning to take a pass at this design for
alpha-3 tomorrow, so I'll reply to anything else in the morning.

Cheers,
Brett

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

svn commit: r170922 - in /maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css: maven-classic.css print.css

[brett]

Author: brett
Date: Thu May 19 06:19:44 2005
New Revision: 170922

URL: http://svn.apache.org/viewcvs?rev=170922&view=rev
Log:
remove tabs

Modified:
maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/maven-classic.css
maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/print.css

Modified: 
maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/maven-classic.css
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/maven-classic.css?rev=170922&r1=170921&r2=170922&view=diff
==
--- maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/maven-classic.css 
(original)
+++ maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/css/maven-classic.css 
Thu May 19 06:19:44 2005
@@ -133,742 +133,742 @@
   padding-left: 10px;
 }
 /* $Id$
-   
-   This file defines basic default formatting for HTML conforming to 
Tigris application style. To extend or override these rules for your instance, 
edit inst.css instead of this file. */
+  
+  This file defines basic default formatting for HTML conforming to Tigris 
application style. To extend or override these rules for your instance, edit 
inst.css instead of this file. */
 
 /* colors, backgrounds, borders, link indication */
 .contentBox h2, .contentBox h3, .tabs td, .tabs th, .functnbar {
-   background-image: url(../images/nw_maj_rond.gif);
-   background-repeat: no-repeat;
+  background-image: url(../images/nw_maj_rond.gif);
+  background-repeat: no-repeat;
 }
 
 .functnbar, .functnbar2 {
-   background-color: #aaa;
+  background-color: #aaa;
 }
 
 .functnbar2, .functnbar3 {
-   background-color: #aaa;
-   background-image: url(../images/sw_maj_rond.gif);
-   background-repeat: no-repeat;
-   background-position: bottom left;
+  background-color: #aaa;
+  background-image: url(../images/sw_maj_rond.gif);
+  background-repeat: no-repeat;
+  background-position: bottom left;
 }
 
 .functnbar3 {
-   background-color: #ddd;
-   background-image: url(../images/sw_med_rond.gif);
+  background-color: #ddd;
+  background-image: url(../images/sw_med_rond.gif);
 }
 
 .functnbar, .functnbar2, .functnbar3 {
-   color: #000;
+  color: #000;
 }
 
 .functnbar a, .functnbar2 a, .functnbar3 a {
-   color: #000;
-   text-decoration: underline;
+  color: #000;
+  text-decoration: underline;
 }
 
 #navcolumn .body div, body.docs #toc li li {
-   background-image: url(../images/strich.gif);
-   background-repeat: no-repeat;
-   background-position: .5em .5em;
+  background-image: url(../images/strich.gif);
+  background-repeat: no-repeat;
+  background-position: .5em .5em;
 }
 
 #searchbox .body div, #navcolumn .body .heading {
-   background-image: none;
+  background-image: none;
 }
 
 a:link.selfref, a:visited.selfref {
-   text-decoration: none;
+  text-decoration: none;
 }
 
 #leftColumn a, #breadcrumbs a {
-   text-decoration: none;
+  text-decoration: none;
 }
 
 /* Unsure of this. TODO */
 .contentBox h2 a:link, .contentBox h2 a:visited, .contentBox h3 a:link, 
.contentBox h3 a:visited {
-   color: #fff !important;
-   text-decoration: underline;
+  color: #fff !important;
+  text-decoration: underline;
 }
 
 table, th, td {
-   border: none;
+  border: none;
 }
 
 div.colbar {
-   background: #eee;
-   border-color: #999 #EEE #EEE #999;
-   border-width: 1px;
-   border-style: solid;
+  background: #eee;
+  border-color: #999 #EEE #EEE #999;
+  border-width: 1px;
+  border-style: solid;
 }
 
 .toolgroup {
-   background: #efefef;
+  background: #efefef;
 }
 
 .toolgroup .label {
-   border-bottom: 1px solid #666;
-   border-right: 1px solid #666;
-   background: #ddd;
-   color: #555;
+  border-bottom: 1px solid #666;
+  border-right: 1px solid #666;
+  background: #ddd;
+  color: #555;
 }
 
 .toolgroup .body {
-   border-right: 1px solid #aaa;
-   border-bottom: 1px solid #aaa;
+  border-right: 1px solid #aaa;
+  border-bottom: 1px solid #aaa;
 }
 
 #main {
-   border-top: 1px solid #999;
+  border-top: 1px solid #999;
 }
 
 #rightcol div.www, #rightcol div.help {
-   border: 1px solid #ddd;
+  border: 1px solid #ddd;
 }
 
 body.docs div.docs {
-   background-color: #fff;
-   border-left: 1px solid #ddd;
-   border-top: 1px solid #ddd;
+  background-color: #fff;
+  border-left: 1px solid #ddd;
+  border-top: 1px solid #ddd;
 }
 
 #helptext .label {
-   background-image: url(../images/icon_help_sml.gif);
-   background-repeat: no-repeat;
-   background-position: 97%;
+  background-image: url(../images/icon_help_sml.gif);
+  background-repeat: no-repeat;
+  background-position: 97%;
 }
 
 body.docs {
-   background: #eee url(../images/help_logo.gif) top right no-repeat 
!important;
+  background: #eee url(../images/help_logo.gif) top right no-repeat !important;
 }
 
 .doc

svn commit: r170921 - /maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl

[brett]

Author: brett
Date: Thu May 19 06:19:28 2005
New Revision: 170921

URL: http://svn.apache.org/viewcvs?rev=170921&view=rev
Log:
fix nbsp references

Modified:
maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl

Modified: maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl?rev=170921&r1=170920&r2=170921&view=diff
==
--- maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl (original)
+++ maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl Thu May 19 
06:19:28 2005
@@ -172,7 +172,7 @@
 
  
  
- ${pom.name} > ${docTitle}   
+ ${pom.name} > ${docTitle}   

 
  
@@ -384,7 +384,7 @@
   

   ${_name}
-   > 
+   > 
 
   
   



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

RE: [jira] Commented: (MNG-415) allow exclusion of certain depend encies from inclusion in an archive

[Maczka Michal]

 

> -Original Message-
> From: Brett Porter (JIRA) [mailto:[EMAIL PROTECTED] 

>  
>to your point, however - making your change: 
>a) triples what needs to be specified for most compile dependencies - you'd
also need to specify test, and hope we never add anything else implied from
compile. This violates the rule we're 
>following of making the defaults work most of the time, and the amount of
configuration needed minimal. 

How does it violates this rule?
The defaults will remain the same - if you don't give provide dependency
scope (as far as I see it now this will be a case for most of the non test
dependencies) dependencies will be visible in all classpaths.
Only when you will want to have one of them  excluded  from some classpaths
you will want to use scope tags. both compile time and runtime dependecies
can be also still visible in test class path.

And it indeed requires some amount of extra work in a very limited set of
cases ( "triples what needs to be specified " is not really accurate - see
below).  But if you compare this to amount of work needed in any other
solution I can think of it actually reduces that amount by much larger
factor (probably more then 10).  So if you look for simplicity - this is
probaly the simplest solution. Just to exclude serlvletapi from war you will
have to change:

from:

 ..
servletapi
..


to:

 ..
servletapi
compile  (you just need to add this single line to
excluded dependency from "runtime" classpath)
..


I don't see how does it "triples what needs to be specified" and how it can
get any simpler :)


>b) is not actually scope any more. Excluding something from runtime, but
including it compile assumes something about the end environment, which the
dependencies should not do - that's the job of the >assembling plugin. 

Sure. But war is an assembling plugin and if you have project packaging set
to "war" you are actually not likely going to use the same pom for creating
other assemblies and you definitly know something about environment in which
this artifact will be used (servlet container). It is just a question if
standard attributes of dependencies are sufficient or not and if they are
not sufficient how it can be done in the other way. 
Anyway scope tag (scope=test) is already used for filtering out artifacts
from assemblies so I don't see what's actually the problem with that.


>From a pure point of view a compile time dependency is always needed at
runtime (unless the code is never hit, or the server provides the jar, all
of which is environmental, not by >definition) 

Not true. For example servletapi is a jar agaist which you want to compile
but most servlet containers have classes from that jar bundled in their own
jars which have completely different names. 


> So unless there is something else missing, the scope will 
> remain as it is. We can't go breaking backwards compatibility 
> unless it is a really serious problem that we can't take forward.
> 

I think this case qualifies for such change :) 
 
regards

michal

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

[jira] Created: (MNG-419) Setting Automatic Plugin Update to never throws a NullPointerException

[Malcolm Wong Ho (JIRA)]

Setting Automatic Plugin Update to never throws a NullPointerException
--

 Key: MNG-419
 URL: http://jira.codehaus.org/browse/MNG-419
 Project: m2
Type: Bug
Versions: 2.0-alpha-2
Reporter: Malcolm Wong Ho


Setting snapshotPolicy to 'never' for the central pluginRepository in pom.xml, 
then executing an m2 comman eg. m2 clean:clean

Sample pom.xml :


central
central
http://repo1.maven.org/maven2
never
default



Exception :

java.lang.NullPointerException
at 
org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:140)
at 
org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:52)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:99)
at 
org.codehaus.plexus.DefaultArtifactEnabledContainer.addComponent(DefaultArtifactEnabledContainer.java:104)
at 
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:285)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:241)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:389)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.configureMojo(DefaultLifecycleExecutor.java:337)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:135)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
at org.codehaus.classworlds.Launcher.main(Launcher.java:363)



-- 
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: (CONTINUUM-136) Add Continuum to the CI Server Matrix

[Trygve Laugstol (JIRA)]

Add Continuum to the CI Server Matrix
-

 Key: CONTINUUM-136
 URL: http://jira.codehaus.org/browse/CONTINUUM-136
 Project: Continuum
Type: Task
Reporter: Trygve Laugstol
 Assigned to: Trygve Laugstol 


http://damagecontrol.codehaus.org/Continuous+Integration+Server+Feature+Matrix


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

svn commit: r170909 - /maven/maven-1/plugins/trunk/xdoc/project.xml

[brett]

Author: brett
Date: Thu May 19 03:31:38 2005
New Revision: 170909

URL: http://svn.apache.org/viewcvs?rev=170909&view=rev
Log:
use consistent versions with core

Modified:
maven/maven-1/plugins/trunk/xdoc/project.xml

Modified: maven/maven-1/plugins/trunk/xdoc/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/project.xml?rev=170909&r1=170908&r2=170909&view=diff
==
--- maven/maven-1/plugins/trunk/xdoc/project.xml (original)
+++ maven/maven-1/plugins/trunk/xdoc/project.xml Thu May 19 03:31:38 2005
@@ -146,12 +146,7 @@
 
   dom4j
   dom4j
-  1.5.2
-
-
-  jaxen
-  jaxen
-  1.1-beta-4
+  1.4
 
 
   commons-jelly
@@ -176,7 +171,7 @@
 
   commons-jelly
   commons-jelly-tags-xml
-  1.0
+  1.1-SNAPSHOT
   http://jakarta.apache.org/commons/jelly/libs/xml/
 
 
@@ -194,11 +189,10 @@
   maven-model
   3.0.0-SNAPSHOT
 
-
 
   velocity
   velocity
-  1.4-dev
+  1.4
 
 
   velocity-dvsl



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

svn commit: r170908 - /maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml

[brett]

Author: brett
Date: Thu May 19 03:31:13 2005
New Revision: 170908

URL: http://svn.apache.org/viewcvs?rev=170908&view=rev
Log:
fix typo

Modified:
maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml

Modified: maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml?rev=170908&r1=170907&r2=170908&view=diff
==
--- maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml (original)
+++ maven/maven-1/plugins/trunk/xdoc/xdocs/navigation.xml Thu May 19 03:31:13 
2005
@@ -27,7 +27,7 @@
   http://maven.apache.org/reference/plugins/index.html"/>
 
 
-  http://jakarta.apache.org/site/jakarta-site2.html"/>
+  http://jakarta.apache.org/site/jakarta-site2.html"/>
 
 
  



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

svn commit: r170905 - /maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl

[brett]

Author: brett
Date: Thu May 19 03:28:06 2005
New Revision: 170905

URL: http://svn.apache.org/viewcvs?rev=170905&view=rev
Log:
fix spacing

Modified:
maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl

Modified: maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl?rev=170905&r1=170904&r2=170905&view=diff
==
--- maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl (original)
+++ maven/maven-1/plugins/trunk/xdoc/src/plugin-resources/site.jsl Thu May 19 
03:28:06 2005
@@ -172,7 +172,7 @@
 
  
  
- ${pom.name} > ${docTitle}   
+ ${pom.name} > ${docTitle}   

 
  
@@ -384,7 +384,7 @@
   

   ${_name}
-  >   
+   > 
 
   
   



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

[jira] Closed: (MAVEN-1345) Upgrade to dom4j 1.4

[Brett Porter (JIRA)]

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

Resolution: Fixed

> Upgrade to dom4j 1.4
> 
>
>  Key: MAVEN-1345
>  URL: http://jira.codehaus.org/browse/MAVEN-1345
>  Project: maven
> Type: Bug
>   Components: core
> Versions: 1.0-rc3
> Reporter: Paul Libbrecht
> Assignee: Brett Porter
> Priority: Critical
>  Fix For: 1.1-beta-1

>
>
> Currently, Maven relies on dom4j beta 8.
> This is bad in many respects, the worst being that the XML output, for 
> example provided by Jelly XML plugin, has wrong xmlns attributes.
> At least the 1.5 betas of dom4j all fix this, they also fix the html output 
> which was, otherwise, inserting random (kind-of) spaces in the text.

-- 
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-415) allow exclusion of certain dependencies from inclusion in an archive

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39288 ]
 
Brett Porter commented on MNG-415:
--

Hugo - if you make "runtime" imply "compile" you can never have a runtime only 
dependency, which is a valid and common use case (ie anything where you only 
call into it via reflection - like a JCE provider, etc).

I'm happy to hear ways to make it less confusing, but the behaviour is 
absolutely correct.

This is not a BUG, and this issue really has little to do with scope. It is 
about the archive plugins not being configurable enough about what they bundle.

I'll keep replying here if there are comments for the sake of keeping it 
together, but I'd really appreciate taking it to the dev list.

> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

-- 
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-415) allow exclusion of certain dependencies from inclusion in an archive

[Hugo Palma (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39287 ]
 
Hugo Palma commented on MNG-415:


I find the names "compile" and "runtime" dependencies misleading. If i didn't 
read the documentation my guess would be that "compile" dependencies are used 
for compiling only and are never included in a package and that "runtime" 
dependencies would be used for compiling and would be packaged. I find the 
choice that was made very confusing.

Is there any reason why it's not donne the way i've described ? If it was it 
would solve this particular BUG and i think it would make it's use much more 
obvious. 

> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

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

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
wrote 632637 bytes  read 42 bytes  4962.19 bytes/sec
total size is 2586204283  speedup is 4087.70
building file list ... done
.index.txt
last-sync.txt
wrote 1085126 bytes  read 64 bytes  1908.87 bytes/sec
total size is 3567497970  speedup is 3287.44

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

[jira] Commented: (MNG-415) allow exclusion of certain dependencies from inclusion in an archive

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39286 ]
 
Brett Porter commented on MNG-415:
--

(in future - please don't use jira for design discussions - that's what the dev 
list is for).

to your point, however - making your change:
a) triples what needs to be specified for most compile dependencies - you'd 
also need to specify test, and hope we never add anything else implied from 
compile. This violates the rule we're following of making the defaults work 
most of the time, and the amount of configuration needed minimal.
b) is not actually scope any more. Excluding something from runtime, but 
including it compile assumes something about the end environment, which the 
dependencies should not do - that's the job of the assembling plugin. From a 
pure point of view a compile time dependency is always needed at runtime 
(unless the code is never hit, or the server provides the jar, all of which is 
environmental, not by definition)

So unless there is something else missing, the scope will remain as it is. We 
can't go breaking backwards compatibility unless it is a really serious problem 
that we can't take forward.

If you feel the description of scope in the doc above is unclear, please 
propose alternate wording or point out the sections that don't make sense... 
thanks.


> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

-- 
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-415) allow exclusion of certain dependencies from inclusion in an archive

[Michal Maczka (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39285 ]
 
Michal Maczka commented on MNG-415:
---

I understood how the scopes work and that why I am proposing is to change it as 
this seems to be the simplest
solution for this problem.

Really what you want to bundle in wars, ears and such  artifacts are only 
runtime dependecies.
servletapi is compile time only dependency but __it is not__ a runtime 
dependecy so it should not be bundled in wars. 

This seems to be natural for me and apparently for some other people.
Look at the subject of the thread:

"how to exclude compile time only jars from .war?"




> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

-- 
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-418) Add non-interactive mode

[Brett Porter (JIRA)]

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

Brett Porter updated MNG-418:
-

Fix Version: 2.0-beta-1

> Add non-interactive mode
> 
>
>  Key: MNG-418
>  URL: http://jira.codehaus.org/browse/MNG-418
>  Project: m2
> Type: Improvement
> Versions: 2.0-alpha-2
> Reporter: Trygve Laugstol
>  Fix For: 2.0-beta-1

>
>
> When embedding Maven 2 in Continuum the build log is full of lines like these:
> 2/1585K
> 3/1585K
> 5/1585K
> Having a "non-interactive" mode would not continuously write out these status 
> messages.

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

svn commit: r170893 - /maven/maven-1/core/trunk/project.xml

[brett]

Author: brett
Date: Thu May 19 00:56:09 2005
New Revision: 170893

URL: http://svn.apache.org/viewcvs?rev=170893&view=rev
Log:
back to dom4j 1.4 - links broken, will investigate

Modified:
maven/maven-1/core/trunk/project.xml

Modified: maven/maven-1/core/trunk/project.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/project.xml?rev=170893&r1=170892&r2=170893&view=diff
==
--- maven/maven-1/core/trunk/project.xml (original)
+++ maven/maven-1/core/trunk/project.xml Thu May 19 00:56:09 2005
@@ -455,14 +455,10 @@
   
 
   dom4j
-  1.6
+  1.4
   http://www.dom4j.org/
 
 
-  jaxen
-  1.1-beta-6
-
-
   ant
   1.6.3
   http://ant.apache.org/
@@ -511,7 +507,7 @@
 
   commons-jelly
   commons-jelly-tags-util
-  1.0
+  1.1
   http://jakarta.apache.org/commons/jelly/tags/util/
 
 
@@ -685,9 +681,7 @@
 maven-jxr-plugin
 maven-junit-report-plugin
 maven-license-plugin
-
 maven-tasklist-plugin
 maven-pmd-plugin
 maven-simian-plugin



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

[jira] Created: (MNG-418) Add non-interactive mode

[Trygve Laugstol (JIRA)]

Add non-interactive mode


 Key: MNG-418
 URL: http://jira.codehaus.org/browse/MNG-418
 Project: m2
Type: Improvement
Versions: 2.0-alpha-2
Reporter: Trygve Laugstol


When embedding Maven 2 in Continuum the build log is full of lines like these:

2/1585K
3/1585K
5/1585K

Having a "non-interactive" mode would not continuously write out these status 
messages.

-- 
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-415) allow exclusion of certain dependencies from inclusion in an archive

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39284 ]
 
Brett Porter commented on MNG-415:
--

Michal, you've misunderstood how scopes work - please read 
http://maven.apache.org/maven2/dependencies.html. Only test is excluded from 
the war, and this is how it already works. Additional measures are needed, 
because servletapi is a valid compile/runtime jar but should not be bundled 
because the container always provides it.

The EAR stuff such as context roots was already being discussed in the linked 
issue, MNG-148.

> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

-- 
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-415) allow exclusion of certain dependencies from inclusion in an archive

[Michal Maczka (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-415?page=comments#action_39283 ]
 
Michal Maczka commented on MNG-415:
---

EAR is a different case then WAR as not only you must decide what will be 
included in the archive 
but also attach some information to some dependencies (e.g. context roots for 
wars)

The decison of what gets included and what not can be based on artifact's type 
and scope.
For wars in particular only all runtime dependecies should be included and 
nothing else (compile and test dependecies should be skipped). So one of the 
possible solutons would be to enable to enumerate dependency scopes rather then 
assume that all compile time dependecies are also runtime dependecies.

To give an example


  
   runtime  (will be included in the war)




  
   runtime  (will be included in the war)
   compile  




  
 
   compile  (will not be included in the war)




   
   test  (will not be included in the war)


This approch seems to be the most natural and simple one and covers in a 
generic way all the cases I can think of. 

Note the artifact scope given at the top level affects also dependencies of 
dependencies.





> allow exclusion of certain dependencies from inclusion in an archive
> 
>
>  Key: MNG-415
>  URL: http://jira.codehaus.org/browse/MNG-415
>  Project: m2
> Type: Improvement
>   Components: maven-plugins, maven-archiver
> Versions: 2.0-alpha-2
> Reporter: Brett Porter
>  Fix For: 2.0-alpha-3

>
>
> this has been requested for WAR, but it should apply to all archives that 
> include dependencies.

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

svn commit: r170890 - /maven/maven-1/core/trunk/xdocs/reference/index.xml

[brett]

Author: brett
Date: Thu May 19 00:49:01 2005
New Revision: 170890

URL: http://svn.apache.org/viewcvs?rev=170890&view=rev
Log:
fix typo

Modified:
maven/maven-1/core/trunk/xdocs/reference/index.xml

Modified: maven/maven-1/core/trunk/xdocs/reference/index.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/reference/index.xml?rev=170890&r1=170889&r2=170890&view=diff
==
--- maven/maven-1/core/trunk/xdocs/reference/index.xml (original)
+++ maven/maven-1/core/trunk/xdocs/reference/index.xml Thu May 19 00:49:01 2005
@@ -64,7 +64,7 @@
 The Maven Jelly Tag Library can be used from a Jelly based
 application to perform the tasks of any of the 
 tags.
   
-
+
 
   Command Line Reference
   



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

[jira] Created: (MPXDOC-144) property to control navigation.xml

[=?ANSI_X3.4-1968?Q?Thomas_Kvalv=3Fg_=28JIRA=29?=]

property to control navigation.xml
--

 Key: MPXDOC-144
 URL: http://jira.codehaus.org/browse/MPXDOC-144
 Project: maven-xdoc-plugin
Type: Wish
Versions: 1.8
Reporter: Thomas Kvalvåg
 Assigned to: Arnaud HERITIER 


Hi

I would like to be able to override the navigation.xml file to a site.xml since 
this seems to be the standard in M2. Add a property maven.xdoc.navigation, 
default shold be navigation.xml

regards
Thomas

-- 
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 - SUCCESS] Thu May 19 03:07:01 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050519.030701.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050519.030701.txt

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

svn commit: r170885 - in /maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting: AbstractMavenMultiPageReport.java sink/ sink/SinkFactory.java

[evenisse]

Author: evenisse
Date: Thu May 19 00:02:19 2005
New Revision: 170885

URL: http://svn.apache.org/viewcvs?rev=170885&view=rev
Log:
Add multipage support.

Added:

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenMultiPageReport.java

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/

maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/SinkFactory.java

Added: 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenMultiPageReport.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenMultiPageReport.java?rev=170885&view=auto
==
--- 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenMultiPageReport.java
 (added)
+++ 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/AbstractMavenMultiPageReport.java
 Thu May 19 00:02:19 2005
@@ -0,0 +1,72 @@
+package org.apache.maven.reporting;
+
+import java.io.InputStream;
+
+import org.apache.maven.reporting.sink.SinkFactory;
+import org.codehaus.doxia.sink.Sink;
+
+/*
+ * Copyright 2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+/**
+ * @author Emmanuel Venisse
+ * @version $Id: MavenReport.java 163376 2005-02-23 00:06:06Z brett $
+ */
+public abstract class AbstractMavenMultiPageReport
+extends AbstractMavenReport
+{
+SinkFactory factory;
+
+public void setSinkFactory( SinkFactory factory )
+{
+this.factory = factory;
+
+if ( getFlavour() != null )
+{
+factory.setFlavour( getFlavour() );
+}
+
+if ( !useDefaultSiteDescriptor() )
+{
+factory.setSiteDescriptor( getSiteDescriptor() );
+}
+}
+public SinkFactory getSinkFactory()
+{
+return factory;
+}
+
+public String getFlavour()
+{
+return null;
+}
+
+public InputStream getSiteDescriptor()
+{
+return null;
+}
+
+public boolean useDefaultSiteDescriptor()
+{
+return true;
+}
+
+public Sink getSink( String outputName )
+throws Exception
+{
+return factory.getSink( outputName );
+}
+}
\ No newline at end of file

Added: 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/SinkFactory.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/SinkFactory.java?rev=170885&view=auto
==
--- 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/SinkFactory.java
 (added)
+++ 
maven/components/trunk/maven-reporting/maven-reporting-api/src/main/java/org/apache/maven/reporting/sink/SinkFactory.java
 Thu May 19 00:02:19 2005
@@ -0,0 +1,79 @@
+package org.apache.maven.reporting.sink;
+
+import java.io.File;
+import java.io.InputStream;
+
+import org.codehaus.doxia.sink.Sink;
+import org.codehaus.doxia.site.renderer.SiteRenderer;
+import org.codehaus.plexus.util.StringInputStream;
+
+/*
+ * Copyright 2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+/**
+ * @author Emmanuel Venisse
+ * @version $Id: MavenReport.java 163376 2005-02-23 00:06:06Z brett $
+ */
+public class SinkFactory
+{
+private String outputDirectory;
+
+private String siteDirectory;
+
+private SiteRenderer siteRenderer;
+
+private InputStream siteDescriptor;