[jira] Subscription: Outstanding Repository Maintenance: Uploads

[jira]

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


Key Summary
MAVENUPLOAD-997Upload PJL Compression Servlet Filter
http://jira.codehaus.org/browse/MAVENUPLOAD-997
MAVENUPLOAD-989squashfs-0.9-beta
http://jira.codehaus.org/browse/MAVENUPLOAD-989
MAVENUPLOAD-988easyio-0.9-beta
http://jira.codehaus.org/browse/MAVENUPLOAD-988
MAVENUPLOAD-982Relocate jWebUnit and upload 1.3-rc2
http://jira.codehaus.org/browse/MAVENUPLOAD-982
MAVENUPLOAD-978Upload ejb-3.0-public-draft-20060502 (needed for hibernate)
http://jira.codehaus.org/browse/MAVENUPLOAD-978
MAVENUPLOAD-976Please upload SUN Java 1.2 rutime 
http://jira.codehaus.org/browse/MAVENUPLOAD-976
MAVENUPLOAD-789Tomcat 5.5.15 poms for existing jars
http://jira.codehaus.org/browse/MAVENUPLOAD-789


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

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

[jira]

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


Key Summary
MEV-426 Quartz 1.5.2 missing pom and jar. Has source.
http://jira.codehaus.org/browse/MEV-426
MEV-425 plexus-container-default, junit scope compile is bad
http://jira.codehaus.org/browse/MEV-425
MEV-392 bad dependencies in commons-logging-1.1.pom
http://jira.codehaus.org/browse/MEV-392
MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded 
variables
http://jira.codehaus.org/browse/MEV-296
MEV-413 Jaxen has unnecessary and unexpected dependencies (which cause 
problems with JDK 1.5)
http://jira.codehaus.org/browse/MEV-413
MEV-405 pom for cactus:cactus:13-1.7.2
http://jira.codehaus.org/browse/MEV-405
MEV-404 pom for cactus:cactus-ant:13-1.7.2
http://jira.codehaus.org/browse/MEV-404
MEV-401 Incoherences / duplication between javax.xml and com.sun.xml
http://jira.codehaus.org/browse/MEV-401
MEV-334 Stax POM points to an invalid XMLBeans dependency
http://jira.codehaus.org/browse/MEV-334
MEV-384 velocity 1.4 dependencies are wrong
http://jira.codehaus.org/browse/MEV-384
MEV-375 Relocate xpp to xpp3
http://jira.codehaus.org/browse/MEV-375
MEV-364 Fix dependencies of common-lang 1.0 (add test scope for junit)
http://jira.codehaus.org/browse/MEV-364
MEV-352 Relocate cvslib in netbeans groupId to cvsclient in org.netbeans.lib
http://jira.codehaus.org/browse/MEV-352
MEV-356 Missing dep on jboss-common in jbossmq-client & jnp-client 4.0.2
http://jira.codehaus.org/browse/MEV-356
MEV-351 xmlc-xerces-2.2.7.1.jar is unnecessary and  xmlc-apis.jar is 
required.
http://jira.codehaus.org/browse/MEV-351
MEV-337 OJB 1.0.4 has a number of dependencies that should be optional
http://jira.codehaus.org/browse/MEV-337
MEV-330 WebWork 2.2.1 POM should list FreeMarker as a dependency since it's 
required for plain ol' JSPs
http://jira.codehaus.org/browse/MEV-330
MEV-325 Description of jaxb-api 1.0.1 is wrong
http://jira.codehaus.org/browse/MEV-325
MEV-320 Hibernate 3.1.x POMs pull in Sun jars
http://jira.codehaus.org/browse/MEV-320
MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype
http://jira.codehaus.org/browse/MEV-201
MEV-173 xmlpull JARs exist in two different places on ibiblio
http://jira.codehaus.org/browse/MEV-173
MEV-48  openejb poms
http://jira.codehaus.org/browse/MEV-48
MEV-45  Full list of poms that doesn't respect the m2 format
http://jira.codehaus.org/browse/MEV-45
MEV-36  Exo POM(s) missing dependency versions
http://jira.codehaus.org/browse/MEV-36
MEV-33  XOM POM references xercesImpl v.2.2.1 which does not exist in repo
http://jira.codehaus.org/browse/MEV-33
MEV-31  XOM POM references xmlParserAPIs v2.6.1 which is not in the repo
http://jira.codehaus.org/browse/MEV-31
MEV-20  clean up bad IDs in the repository
http://jira.codehaus.org/browse/MEV-20


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

Re: Please review site plugin documentation

[Maria Odea Ching]

Hi Vincent,

Thanks for the review :)
I'll post your comments on jira and revise the docs.

Odea

Vincent Siveton wrote:


Hi Maria,

Thanks for your work! Here is my comments:

usage.html
note => Bold font
add a link to the Jetty server: http://jetty.mortbay.org/jetty/index.html

sitedescriptor.html
"For more references of the site descriptor, here's a link
http://maven.apache.org/site.html"; should be in the introduction.

http://maven.apache.org/site.html is out of date thus to specify it.
(IMHO we need a new page for this, maybe something like
http://maven.apache.org/ref/current/maven-model/maven.html)

"Site Descriptor" part should be renamed to "Publish Date"

templatefile.html
add a link to Velocity: http://jakarta.apache.org/velocity/

moduleexcludes.html
empty 

creatingskins.html
add an example or a link to
http://svn.apache.org/viewvc/maven/skins/trunk/maven-classic-skin/

General comment
i18n link is missing.
Moreover, i18n.xml should be updated with the new bundle.

Cheers,

Vincent

2006/7/19, Maria Odea Ching <[EMAIL PROTECTED]>:


Hi Everyone,

The Site plugin documentation is now ready for review.
A staging site is available at
http://people.apache.org/~oching/maven-site-plugin
.

Thanks,
Odea

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




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




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

Re: [maven2 build trunk - FAILED - update] Thu Jul 20 01:00:00 GMT 2006

[Brett Porter]

Jason - this is because of a missing DOAP plugin. Can you take a look?

- Brett

On 20/07/2006 11:08 AM, [EMAIL PROTECTED] wrote:

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




--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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

Re: Maven1 project converter

[Dion Gillard]

Guys,

what does the plugin do?

On 7/20/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:



Dennis Lundberg a écrit :
> Emmanuel Venisse wrote:
>> Hi,
>>
>> I'm starting to migrate all the code from
>> sandbox/plugins/maven-maven1-plugin to maven-model-converter with some
>> modifications on plugin configuration converter loading.
>>
>> Dennis, do you work actually on maven-maven1-plugin?
>
> Oh sorry Emmanuel, I misread your mail the first time.
>
> I will check out maven-model-converter and see what you have done.

yes, all the code is in maven-model-converter now. I need to merge it in maven 
2.0.x branch, I'll do
it tomorrow morning.

>
> There only seems to be the mojo left in the sandbox. I will have a look
> at moving that to the maven-one-plugin and making it use the code that
> has now moved to maven-model-converter. OK?

The mojo is always in sandbox and we need to modify it, so it will use 
maven-model-converter, and
yes, maven-one-plugin will be a better place for it.

>
> One other thing that I have left on my todo list, besides the stuff I
> wrote about in the other mail, is to make the
> PluginConfigurationConverters into plexus components.

it's done :-)

>
> I have some other stuff that is not yet committed. Will go through it
> and see how much there is and if it's ready to be checked in or not.
>
> Would it be possible for me to get svn write access to
> maven-model-converter or do you prefer if I submit patches?
>

For the moment, you can send a patch and we'll see with the pmc if you can have 
access to
maven-model-converter.

Emmanuel


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





--
http://www.multitask.com.au/people/dion/
"If you even dream of beating me you'd better wake up and apologize" -
Muhammad Ali

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

Re: OutOfMemoryError when compiling with javac

[Brett Porter]

On 20/07/2006 5:20 AM, Graham Leggett wrote:
- Does adding -Xmx2048M to MAVEN_OPTS affect the amount of RAM available 
to javac when it is called by maven, or is there a different option that 
should be used? Does MAVEN_OPTS have any effect on javac at all?


Depends on whether javac is forked. You can change that and the memory 
using the properties here:

http://maven.apache.org/maven-1.x/plugins/java/properties.html

Please send these queries to the users@ list in future - thanks.

Cheers,
Brett

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

Re: [m2] ArtifactHandler and Artifacts.

[Barrie Treloar]

On 7/19/06, Brett Porter <[EMAIL PROTECTED]> wrote:

the plugin manager calls ArtifactResolver (see maven-artifact and
maven-artifact-manager for DefaultArtifactResolver I think).

This uses the ArtifactCollector to find all the artifacts and they'd be
created by an ArtifactFactory.

The addedToClasspath field is probably set on the standard types in the
components.xml of maven-artifact.


Excellent, the components.xml was the spot where addedToClasspath is being set.

Now I need to digest this information.

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

Re: Maven1 project converter

[Emmanuel Venisse]

Dennis Lundberg a écrit :

Emmanuel Venisse wrote:

Hi,

I'm starting to migrate all the code from 
sandbox/plugins/maven-maven1-plugin to maven-model-converter with some 
modifications on plugin configuration converter loading.


Dennis, do you work actually on maven-maven1-plugin?


Oh sorry Emmanuel, I misread your mail the first time.

I will check out maven-model-converter and see what you have done.


yes, all the code is in maven-model-converter now. I need to merge it in maven 2.0.x branch, I'll do 
it tomorrow morning.




There only seems to be the mojo left in the sandbox. I will have a look 
at moving that to the maven-one-plugin and making it use the code that 
has now moved to maven-model-converter. OK?


The mojo is always in sandbox and we need to modify it, so it will use maven-model-converter, and 
yes, maven-one-plugin will be a better place for it.




One other thing that I have left on my todo list, besides the stuff I 
wrote about in the other mail, is to make the 
PluginConfigurationConverters into plexus components.


it's done :-)



I have some other stuff that is not yet committed. Will go through it 
and see how much there is and if it's ready to be checked in or not.


Would it be possible for me to get svn write access to 
maven-model-converter or do you prefer if I submit patches?




For the moment, you can send a patch and we'll see with the pmc if you can have access to 
maven-model-converter.


Emmanuel


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

Re: Maven1 project converter

[Dennis Lundberg]

Emmanuel Venisse wrote:

Hi,

I'm starting to migrate all the code from 
sandbox/plugins/maven-maven1-plugin to maven-model-converter with some 
modifications on plugin configuration converter loading.


Dennis, do you work actually on maven-maven1-plugin?


Oh sorry Emmanuel, I misread your mail the first time.

I will check out maven-model-converter and see what you have done.

There only seems to be the mojo left in the sandbox. I will have a look 
at moving that to the maven-one-plugin and making it use the code that 
has now moved to maven-model-converter. OK?


One other thing that I have left on my todo list, besides the stuff I 
wrote about in the other mail, is to make the 
PluginConfigurationConverters into plexus components.


I have some other stuff that is not yet committed. Will go through it 
and see how much there is and if it's ready to be checked in or not.


Would it be possible for me to get svn write access to 
maven-model-converter or do you prefer if I submit patches?


--
Dennis Lundberg

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

Re: Continuum Security design

[Jesse McConnell]

There was some discussion on irc about the security model so I wrote
up this description for review by everyone.

http://docs.codehaus.org/display/CONTINUUM/Straight+Role+Based+Access+Control

It doesn't have implementation details in it, it is just an attempt at
drawing together the different concepts we have been talking about
together so we can agree on 'what we want' and then we can focus on
'how to do it'.

personally, I think this basic idea could go into plexus (if it isn't
already there with jason's rbac stuff) pretty smoothly and then have
different implementations like carlo's acegi stuff...

but anyway, please review the above and comment

cheers!

jesse

On 7/18/06, Brett Porter <[EMAIL PROTECTED]> wrote:

I've added my comments.

I don't think we need domain ACLs - it's an interesting concept but it
also worries me a little to have security as an afterthought - it's
intrinsic to the design of the code in some ways (surely if you only
want to give one person access to a subset of the data you also want to
avoid going ahead and retrieving the data in the first place). Perhaps I
misunderstand it's intent.

So, where are we at with this? I don't think its healthy to keep a
branch for too long on something so fundamental as it'll become hard to
merge back in, but is Acegi proving to be both non-intrusive and capable
of doing what we need? What state is it in?

- Brett

On 11/07/2006 8:41 AM, Carlos Sanchez wrote:
> http://docs.codehaus.org/display/CONTINUUM/Security
>
> Please take a look and provide feedback on the semantics of what to
> secure and to what level.
>


--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/




--
jesse mcconnell
[EMAIL PROTECTED]

Re: whither jar 2.1?

[Dennis Lundberg]

Mike Perham wrote:

What's holding up jar plugin 2.1?  There's a huge number of
fixes/improvements and the documentation is light-years better.


I went through JIRA the other day with the intention of asking the very 
same question :)


There are 15 unscheduled issues, with 6 bugs, so mostly enhancement 
requests. Most bugs seem like corner cases. And as you said: there's 
enough done to the plugin to warrant a release.


--
Dennis Lundberg

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

Re: Maven1 project converter

[Dennis Lundberg]

Emmanuel Venisse wrote:

Hi,

I'm starting to migrate all the code from 
sandbox/plugins/maven-maven1-plugin to maven-model-converter with some 
modifications on plugin configuration converter loading.


Dennis, do you work actually on maven-maven1-plugin?


Yes, it's pretty much completed. It needs some documentation and really 
should be moved to maven-one-plugin, as someone suggested earlier. There 
are always more stuff to do, but I think it is ready for (at least) a 
beta release. There is one thing that needs to be done first though and 
that is to repackage the source as it is currently in the wrong package.


What are your thoughts on moving this forward?
My suggested plan would be:
1. Repackage source code
2. Move the code from sandbox to maven-one-plugin
3. Write basic documentation
4. Release a beta
5. Wait for user feedback, as it has had minimal testing
6. Fix bugs
7. Release stable version

Any thoughts?

I'll get starting on this. Also need to check the status of the 
maven-one-plugin.


--
Dennis Lundberg

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

Maven2 site generation for module builds with flat directory layout

[Alexander Rau]

Hi all,

I've sent this mail to the users list but did not receive any reply. 
Therefore I'm asking here:



I've had this problem for several weeks now. Anyone has an idea if this
can be worked around or if it's just a bug in the site plugin.

Use case: flat multi module project layout (due to eclipse) - means:


workspace:


  /Project
  /Module1
  /Module2
  /Module3
  ...


/Project/pom.xml is the parent /Project/pom.xml of all modules and 
contains entries like:


../Module(1|2|3)

The parent pom.xml is referenced by all submodules using the
 tag.

mvn site in /Project creates correct sites for each module. However the
site for the parent Project in /Project gets wrong links to the modules
in the left navigation bar. E.g. the link to Module1 from the parent
site gets translated (links to) http://Module1/index.html when deploying
the site - which is obviously wrong.

I just had a quick look on the properties of the site plugin - however
there's no property which could help creating correct links.

I tried to overwrite the distributionManagement property for the site
url - it just seems to get ignored.

Any ideas ?


Tnx in advance

Regards,


Alex


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

OutOfMemoryError when compiling with javac

[Graham Leggett]

Hi all,

I have a maven 1 configuration that builds the IFX and ACORD schemas 
using xmlbeans. This step works, however the second step - compiling the 
generated code - fails with an OutOfMemoryError.


I tried setting the MAVEN_OPTS environment variable to jack up the -Xmx 
to 2GB of RAM, but this has no effect, and the build fails.


The build is failing for one of the following reasons, I am not sure 
which one is the case:


- Does adding -Xmx2048M to MAVEN_OPTS affect the amount of RAM available 
to javac when it is called by maven, or is there a different option that 
should be used? Does MAVEN_OPTS have any effect on javac at all?


- Has anybody ever managed to compile either the IFX or ACORD schemas 
using xmlbeans, or is this a lost cause?


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

Revision number displaying in "Changes"

[Heikki Rauhala]

Hi,

We're using continuum 1.0.3 with subversion and Maven 2 projects set up 
as shell projects (because of the project name changing bug in 1.0.3).


It would be very useful to see the revision numbers of files in the 
"Changes" table on build results page, and also per build # if the SCM 
system supports repository-wide revisions (like subversion does).


Is this feature somewhere on the roadmap?

Are there some obvious obstacles for implementing this?

Cheers,
- Heikki.

Re: whither jar 2.1?

[Brett Porter]

It looks ready - it just needs someone to call a vote!

(I'm notoriously bad at having open ended votes recently, so I'll leave 
it for someone that has the time to do the release...)


Thanks,
Brett

On 19/07/2006 2:02 PM, Mike Perham wrote:

What's holding up jar plugin 2.1?  There's a huge number of
fixes/improvements and the documentation is light-years better.

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




--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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

Re: Please review maven-compiler-plugin

[Vincent Siveton]

Hi Edwin,

A small standardization comment:
remove introduction word in Maven Compiler Plugin: Introduction (index.html)

Cheers,

Vincent

2006/7/19, Edwin Punzalan <[EMAIL PROTECTED]>:

Done, thanks.

Staging site updated.


Dennis Lundberg wrote:
> Edwin Punzalan wrote:
>> Hi,
>>
>>
>> I've just created the staging site for this plugin:
>>
>>http://people.apache.org/~epunzalan/maven-compiler-plugin/
>>
>> and would appreciate your feedback/comments.
>>
>> Thanks in advance.
>
> Here's my review, Edwin
>
> index.html
> - "This Compiler Plugin is Maven 2 version"
>   --> "This Compiler Plugin is the Maven 2 version"
> - "the Maven Lifecycles" --> "the Maven Lifecycle"
>
> compile-mojo.html and testCompile-mojo.html
> - compilerId parameter mentions the default value "javac", but which
> values are allowed?
> - parameters optimize, showDeprecation, showWarnings, staleMillis and
> verbose are missing a period "." at the end of the Javadoc comment.
> This makes it look silly when the "Default value is ..." sentence
> starts right after.
>
> faq.html
> - Question 2: Add a link to the modello-plugin.
>
> compile-with-memory-enhancements.html and
> set-compiler-source-and-target.html
> - Title/Heading of the page is not the same as the texts used of links
> in site.xml and index.html
>
> pass-compiler-arguments.html
> - Shorten the title/heading to "Passing Compiler Arguments"
>
> I'd also like to see a link to Suns javac pages somwhere, so that
> users can read more about the different options that are referred to
> in the mojo pages.
>

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




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

Re: Review of install plugin

[Vincent Siveton]

Hi Allan,

Standardization:
in the index.html, introduction should be replaced by "Maven Install Plugin"

Cheers,

Vincent

2006/7/19, Allan Ramirez <[EMAIL PROTECTED]>:

done.. Thanks

http://people.apache.org/~aramirez/maven-install-plugin/

-allan

Vincent Siveton wrote:
> Hi Allan,
>
> Other comments:
>
> index.html
> (~/.m2/repository) => italic
>
> usage.html
> install:install => italic
>
> FAQ
> add a link to the maven-deploy-plugin.
>
> Good work. Thanks.
>
> Vincent
>
> 2006/7/18, Allan Ramirez <[EMAIL PROTECTED]>:
>> By the way, the staging site can be found here
>> http://people.apache.org/~aramirez/maven-install-plugin/
>>
>> allan
>>
>> Allan Ramirez wrote:
>> > Ready for another review.
>> >
>> > Thanks,
>> > allan
>> >
>> > Dennis Lundberg wrote:
>> >> Allan Ramirez wrote:
>> >>> Hi everyone,
>> >>>
>> >>> Just updated the docs of the install plugin. I hope you dont mind if
>> >>> you take a look and give me some feedback about it. Thanks
>> >>>
>> >>> Cheers,
>> >>> allan
>> >>
>> >> Here are my comments:
>> >>
>> >> site.xml
>> >> - Missing the "Goals" link in the overview section.
>> >>
>> >> **/*.html
>> >> - Remove the text "Maven 2 Install Plugin" from the titles. The title
>> >> is picked up from the project name in site.xml
>> >> - In the example documents, the title and heading are not equal.
>> >>
>> >> index.html
>> >> - Change the title to "Introduction"
>> >>
>> >> usage.html
>> >> - "install:install goal doesnt" -> "the install:install goal doesn't"
>> >> - "overriden" -> "overridden"
>> >> - "Maven assumes the file is the main artifact for the project."
>> >>   Is this the same as packaging then?
>> >>
>> >> faq.html
>> >> - It's empty...
>> >>
>> >> examples/update-release-info.html
>> >> - "Updating the release information changes the project's
>> >> maven-metadata.xml in the local repository, forcing the current
>> >> installed version as the latest release version."
>> >> I'm sorry, but I don't understand what this means :(
>> >>
>> >> install-mojo.html
>> >> - createChecksum param: "Flag whether" -> "Whether"
>> >> - updateReleaseInfo param: No default value? It's a boolean.
>> >>
>> >> install-file-mojo.html
>> >> - All parameters but "file" are optional. Well that's not really
>> >> true. This problem might occur in other plugins as well. IIUC you
>> >> have to use *either* pomFile *or* groupId/artifactId/version. How do
>> >> we document that?
>> >> - generatePom param: No default value? It's a boolean.
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

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




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

Re: Review for maven-rar-plugin

[Vincent Siveton]

Hi Allan,

Other comment (standardization):
in the index.html,
introduction should be replaced by "Maven Rar Plugin"
"How to Use" by "Usage"

Cheers,

Vincent

2006/7/19, Allan Ramirez <[EMAIL PROTECTED]>:

done.. Thanks

staging site: http://people.apache.org/~aramirez/maven-rar-plugin/

-allan

Vincent Siveton wrote:
> Hi Allan,
>
> I was thinking about this:
> http://java.sun.com/j2ee/connector/ (Main page)
>
> Agree with Denis proposal for the faq. Moreover, maybe we could
> provide a sample ra.xml file (the ra.xml in basic-rar-with-descriptor
> is empty) in the site or a link to:
> http://docs.sun.com/source/817-2254-10/Ch_04_sm.html
>
> Cheers,
>
> Vincent
>
> 2006/7/18, Allan Ramirez <[EMAIL PROTECTED]>:
>> Hi Vincent,
>>
>> Im not sure if this is the link you are looking for
>>
>> http://java.sun.com/j2ee/apidocs-1_0-fr/api/index.html
>>
>> Thanks,
>> allan
>>
>> Vincent Siveton wrote:
>> > My comments:
>> >
>> > - faq is empty
>> > - add a link to J2EE Connector API specification for the ra.xml
>> >
>> > Cheers,
>> >
>> > Vincent
>> >
>> > 2006/7/17, Allan Ramirez <[EMAIL PROTECTED]>:
>> >> Hi everyone,
>> >>
>> >>
>> >> Just updated the docs of the rar plugin. I hope you dont mind if you
>> >> take a look and give me some feedback about it. Thanks
>> >>
>> >> staging site can be found here
>> >> http://people.apache.org/~aramirez/maven-rar-plugin/
>> >>
>> >> Thanks,
>> >> allan
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

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




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

Re: Please review site plugin documentation

[Vincent Siveton]

Hi Maria,

Thanks for your work! Here is my comments:

usage.html
note => Bold font
add a link to the Jetty server: http://jetty.mortbay.org/jetty/index.html

sitedescriptor.html
"For more references of the site descriptor, here's a link
http://maven.apache.org/site.html"; should be in the introduction.

http://maven.apache.org/site.html is out of date thus to specify it.
(IMHO we need a new page for this, maybe something like
http://maven.apache.org/ref/current/maven-model/maven.html)

"Site Descriptor" part should be renamed to "Publish Date"

templatefile.html
add a link to Velocity: http://jakarta.apache.org/velocity/

moduleexcludes.html
empty 

creatingskins.html
add an example or a link to
http://svn.apache.org/viewvc/maven/skins/trunk/maven-classic-skin/

General comment
i18n link is missing.
Moreover, i18n.xml should be updated with the new bundle.

Cheers,

Vincent

2006/7/19, Maria Odea Ching <[EMAIL PROTECTED]>:

Hi Everyone,

The Site plugin documentation is now ready for review.
A staging site is available at
http://people.apache.org/~oching/maven-site-plugin
.

Thanks,
Odea

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

Maven1 project converter

[Emmanuel Venisse]

Hi,

I'm starting to migrate all the code from sandbox/plugins/maven-maven1-plugin to 
maven-model-converter with some modifications on plugin configuration converter loading.


Dennis, do you work actually on maven-maven1-plugin?

Emmanuel


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

Re: Please review maven-eclipse-plugin

[Edwin Punzalan]

Updates applied.  Staging site, updated.

Thanks.


^_^


Dennis Lundberg wrote:

Edwin Punzalan wrote:

Ooopps!  I sent the other one to the user list... :(


Here are the changes I've made:

- created three sample usages:
  - attaching library sources
  - preventing module references
  - providing project natures and build commands
- added three FAQ entries
- some fixes to improve site documentation
- docck compliance

Staging site is available here: 
http://people.apache.org/~epunzalan/maven-eclipse-plugin/


Hi Edwin, thanks for working on the plugin documentation!

Here are some comments from me:

site.xml
- Is missing bannerLeft and bannerRight

reactor.html
"2. Open the command line shell and change to the newly created 
workspace directory.
3. From the command line change to newly created step-by-step 
workspace and create a new maven project using the archetype plugin."

- You change into the "newly created workspace" twice.

The link to "Maven as an external tool" is broken. Should go to 
usage.html#...


faq.html
- 3. question:
"runnning" --> "running"
"This is done by using:
   eclipse:add-maven-repo"
Shouldn't that be "mvn eclipse:add-maven-repo", or if you mean the 
goal itself, I would recommend linking it to the goal-page.

- 4. question:
"plugin to download" --> "plugin download"

provide-project-natures-and-build-commands.html
"nature by projects created by" --> "nature for projects created by"
"them in your pom.xml like:" --> "them in your pom.xml like this:"

*.html
- "eclipse" --> "Eclipse" in a lot of places




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

Re: Please review maven-compiler-plugin

[Edwin Punzalan]

Done, thanks.

Staging site updated.


Dennis Lundberg wrote:

Edwin Punzalan wrote:

Hi,


I've just created the staging site for this plugin:

   http://people.apache.org/~epunzalan/maven-compiler-plugin/

and would appreciate your feedback/comments.

Thanks in advance.


Here's my review, Edwin

index.html
- "This Compiler Plugin is Maven 2 version"
  --> "This Compiler Plugin is the Maven 2 version"
- "the Maven Lifecycles" --> "the Maven Lifecycle"

compile-mojo.html and testCompile-mojo.html
- compilerId parameter mentions the default value "javac", but which 
values are allowed?
- parameters optimize, showDeprecation, showWarnings, staleMillis and 
verbose are missing a period "." at the end of the Javadoc comment. 
This makes it look silly when the "Default value is ..." sentence 
starts right after.


faq.html
- Question 2: Add a link to the modello-plugin.

compile-with-memory-enhancements.html and 
set-compiler-source-and-target.html
- Title/Heading of the page is not the same as the texts used of links 
in site.xml and index.html


pass-compiler-arguments.html
- Shorten the title/heading to "Passing Compiler Arguments"

I'd also like to see a link to Suns javac pages somwhere, so that 
users can read more about the different options that are referred to 
in the mojo pages.




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

Re: svn commit: r420933 - in /maven/continuum/branches/continuum-acegi/continuum-webapp/src/main/resources: commons-logging.properties log4j.properties

[Trygve Laugstøl]

Carlos Sanchez wrote:
I don't know how to configure commons-logging and log4j through plexus 
for Acegi


Then you should ask instead of just ignoring the issue. I just saw that 
Kenney did the same thing, I hope that he'll fix it once and for all now.


--
Trygve

Re: svn commit: r422904 - in /maven/continuum/trunk/continuum-webapp/src/main/resources: log4j.xml validators.xml

[Trygve Laugstøl]

[EMAIL PROTECTED] wrote:

Author: kenney
Date: Mon Jul 17 15:31:54 2006
New Revision: 422904

URL: http://svn.apache.org/viewvc?rev=422904&view=rev
Log:
Added a log4j.xml configuration file because JPOX needs it - nice to
see some output for that if something goes wrong. 


Plexus is handling Log4j configuration so add this configuration to 
Plexus instead.


[snip]

--
Trygve

Re: [m2] ArtifactHandler and Artifacts.

[Brett Porter]

the plugin manager calls ArtifactResolver (see maven-artifact and 
maven-artifact-manager for DefaultArtifactResolver I think).


This uses the ArtifactCollector to find all the artifacts and they'd be 
created by an ArtifactFactory.


The addedToClasspath field is probably set on the standard types in the 
components.xml of maven-artifact.


- Brett

On 19/07/2006 6:19 PM, Barrie Treloar wrote:

The DefaultArtifactHandler has no way to set addedToClasspath, yet
MavenArchiver requires this to be true for getRuntimeArtifacts() to
return anything.

I've been trawling to find where Artifacts are resolved and I'm not
having too much luck.
Is anyone able to point me to where an Artifact is created from the
repository and how the meta-data gets populated into the Artifact
object?

Thanks

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




--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

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

[m2] ArtifactHandler and Artifacts.

[Barrie Treloar]

The DefaultArtifactHandler has no way to set addedToClasspath, yet
MavenArchiver requires this to be true for getRuntimeArtifacts() to
return anything.

I've been trawling to find where Artifacts are resolved and I'm not
having too much luck.
Is anyone able to point me to where an Artifact is created from the
repository and how the meta-data gets populated into the Artifact
object?

Thanks

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

Re: Please review maven source plugin documentation

[Maria Odea Ching]

Hi,

I've revised the documentation for the source plugin.
A staging site is now available at 
http://people.apache.org/~oching/maven-source-plugin 
.


Thanks,
Odea

Maria Odea Ching wrote:


Ok, thanks for the comments :) Will post it on jira and revise the docs.

Dennis Lundberg wrote:


Maria Odea Ching wrote:


Hi Everyone,

The documentation for the source plugin is now ready for review :)

Thanks,
Odea




My comments:

faq.html
- "Use the source:test-jar to" -> "Use the source:test-jar goal to"

examples/configureplugin.html
- "To customize the configuration of the plugin" ->
  "To customize the plugin"
- "The generated jar file will hold the value of the" ->
  "The generated jar file will be named by the value of the"
- "It would be generated" -> "It will be generated"
- "The attach parameter specifies that the produced jar file will be 
attached to the project artifact."

What does this mean?

jar-mojo.html
- "This plugin bundles all the generated sources into a jar archive." ->
  "This plugin bundles all the sources into a jar archive."

test-jar-mojo.html
- "This plugin bundles all the generated test sources into a jar 
archive." ->

  "This plugin bundles all the test sources into a jar archive."

jar-mojo.html and test-jar-mojo.html
- executedProject, finalName and outputDirectory params: These must 
have some kind of implicit default values, because I can issue the 
command "mvn source:jar" and it works.





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




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

Re: Maven 2.x Resource Plugin Documentation needs Reviewing

[FA Valencia See]

Good day,

The patch (MRESOURCES-23-maven-resource-plugin-2.2.patch) I submitted to the
MRESOUCES-23 jira issue  for
maven-resources-pluginhave
just been applied. Also, the staging
sitehas
been updated (thanks
again Allan).

In line with this, I would like to ask the community again for help with
regards to reviewing the Maven 2.x Resources Plugin documentation.

Thanks again.

- Franz

PS: Thank you Edwin and Dennis for your reviews.

On 7/18/06, FA Valencia See <[EMAIL PROTECTED]> wrote:


Good day,

Thanks for your review. I've already submitted a
MRESOURCES-23-maven-resources-patch-2.2.patch
to the jira issue  based
from edwin and your inputs, as well as mine.

Btw, although the phases of the goals are already in the
resources-mojo.html and testResources-mojo.html,
I've also added that info in the usage.html.

Thanks again for your review :)

- Franz


On 7/18/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>
> FA Valencia See wrote:
> > Good day,
> >
> > I would like to ask for some help reviewing M2's Resource Plugin
> > Documentation.
> >
> > The documentation can be viewed
> > here< http://people.apache.org/%7Earamirez/maven-resources-plugin/
> >(thanks
> > allan for the stage), while the Jira Issue can be viewed
> > here
> > .
> >
> > Thanks,
> > Franz
>
> Thanks for your efforts on improving the documentation Franz. Here is my
> review:
>
> site.xml
> - project/name="Maven Resources Report" but other documentation says
> "Maven Resources Plugin"
>
> index.html
> - "transfering" --> "transferring"
> - "Resources are categorized into two" --> "Resources come in two
> categories"
> - "resources of the main code" --> "resources for the main code"
> - "resources of the main source" --> "resources for the main source"
> - "resources of the test source" --> "resources for the test source"
> - "the Javadoc Plugin" --> "the Resources Plugin"  oops :)
>
> faq.html
> - "allwos" --> "allows"
>
> filter.html
> - "we can sdo so" --> "we can do so"
>
> include-exclude.html
> - "And to excludes a resource" --> "And to exclude a resource"
> - "need to add an exclude tag" --> "need to add an excludes tag"
> - Excludes example: all non-resource files have #1
>
>
> I am missing info on which phase the plugin is bound to, if any.
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>