Re: The Maven PMC welcomes Deng Ching

[allan ramirez]

Deng!!! Congratz :D

On 8/21/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
>
> Thanks everyone!  :-)
>
> -Deng
>
> Henry Isidro wrote:
> > Wow! Congratulations Deng!
> >
> > On 8/21/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> >> Welcome, Deng!
> >>
> >> Congrats - it's great to have you on board.
> >>
> >> Cheers,
> >> Brett
> >>
> >> On 21/08/2007, at 9:19 AM, Wendy Smoak wrote:
> >>
> >>
> >>> I'm pleased to announce that the Maven PMC has voted to add Deng Ching
> >>> to the PMC. Please join me in welcoming her!
> >>>
> >>> --
> >>> Wendy
> >>>
> >>> -
> >>> 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]
>
>


-- 
==
- alramirez

Re: [vote] release maven-changelog-plugin 2.0

[allan ramirez]

+1

-allan

On 1/21/07, Rahul Thakur <[EMAIL PROTECTED]> wrote:


+1

Rahul

- Original Message -
From: "Dennis Lundberg" <[EMAIL PROTECTED]>
To: "Maven Developers List" 
Sent: Saturday, January 20, 2007 12:08 PM
Subject: [vote] release maven-changelog-plugin 2.0


> Hi,
>
> I'd like to release the changelog. It has not had a release since it
> moved from Codehaus, so this will be the first release at Apache.
>
> A lot of issues have been resolved for 2.0 as can be seen in JIRA:
>
>
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11211&fixfor=12471
>
> There are still 2 open issues, but I don't think they should hold back
> a release:
>
>
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11211&fixfor=-1
>
> Revision: 497994
>
> A snapshot has been deployed to the Apache snapshot repo:
>
>
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-changelog-plugin/2.0-SNAPSHOT/maven-changelog-plugin-2.0-20070119.230232-7.jar
>
> The one thing left to do is to decide which parent pom to use.
> Currently maven-plugins-8-SNAPSHOT is used as a parent. Either we go
> back to maven-plugins-7 or release maven-plugins-8. WDYT?
>
>
> The vote will be open for 72 hours.
>
>
> Here is my +1
>
> --
> Dennis Lundberg
>
> -
> 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]





--
==
- alramirez

Re: Unable to checkout maven and plugin source code

[allan ramirez]

Hi drekka,

what component did you checked out? I tried the /plugins/trunk and it was
fine.

On 1/17/07, drekka <[EMAIL PROTECTED]> wrote:



Yes I did have a https connection. I turned it off and tried again. This
time
I got:

REPORT request failed on '/repos/asf/!svn/vcc/default'
Corrupt GZIP trailer

...and another attempt:

REPORT request failed on '/repos/asf/!svn/vcc/default'
invalid block type

After about 6 minutes of work. Looks likes it's always this file that is
causing the problem.

ciao
Derek


baerrach wrote:
>
> On 1/17/07, drekka <[EMAIL PROTECTED]> wrote:
>>
>> Hello everyone,
>>
>> I've tried several times to checkout the source code so I can have a
look
>> through it, and perhaps contribute back. However every time I try to do
>> it,
>> the checkout process dies after about five minutes, returning the
>> following
>> error:
>>
>> REPORT request failed on '/repos/asf/!svn/vcc/default'
>> Connection has been shutdown: javax.net.ssl.SSLException: SSL peer shut
>> down
>> incorrectly
>>
>> I'm using the Eclipse subversion plugin to manage svn. Does anyone have
>> any
>> idea what the issue is ?
>
> What is the connection URL you are attempting.
> The error message appears to indicate you are using SSL.
> The anonymous user connection is plain HTTP not SSL.
>
> I assume you looked at
> http://maven.apache.org/guides/development/guide-building-m2.html as
> this is the only docs I could find that list the SVN repository.
>
> I am using the following URL
> http://svn.apache.org/repos/asf/maven
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

--
View this message in context:
http://www.nabble.com/Unable-to-checkout-maven-and-plugin-source-code-tf3024802s177.html#a8405043
Sent from the Maven Developers mailing list archive at Nabble.com.


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





--
==
- alramirez

Re: Unable to checkout maven and plugin source code

[allan ramirez]

I just checked out the source a while ago using svn command and I did not
encountered any problems with it.


On 1/17/07, Barrie Treloar <[EMAIL PROTECTED]> wrote:


On 1/17/07, drekka <[EMAIL PROTECTED]> wrote:
>
> Hello everyone,
>
> I've tried several times to checkout the source code so I can have a
look
> through it, and perhaps contribute back. However every time I try to do
it,
> the checkout process dies after about five minutes, returning the
following
> error:
>
> REPORT request failed on '/repos/asf/!svn/vcc/default'
> Connection has been shutdown: javax.net.ssl.SSLException: SSL peer shut
down
> incorrectly
>
> I'm using the Eclipse subversion plugin to manage svn. Does anyone have
any
> idea what the issue is ?

What is the connection URL you are attempting.
The error message appears to indicate you are using SSL.
The anonymous user connection is plain HTTP not SSL.

I assume you looked at
http://maven.apache.org/guides/development/guide-building-m2.html as
this is the only docs I could find that list the SVN repository.

I am using the following URL
http://svn.apache.org/repos/asf/maven

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





--
==
- alramirez

Re: [discuss] A new name for the repository manager?

[Allan Ramirez]

I like Maven Curator.

nhb wrote:

Hi,

Brett invited me to post an idea or two I had to the list:

Maven Curator

# The person responsible for developing and maintaining collections.
http://www.lib.unc.edu/instruct/manuscripts/glossary/

# A person who catalogs and cares for artifacts after they are removed
during excavation.
http://www.nps.gov/colo/TEACHERS/SG_Act/ArchGlossary.html

# one that manages or oversees, a museum collection or a library
http://collections.ic.gc.ca/peh/teachers/Glossary.html

Maven Exchequer - (only loosely analogous, but has neat ring to it)

Maven Archiva (like Doxia - it is latin root of archive, which is related to
repository))

  


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

Re: Review surefire plugin documentation

[Allan Ramirez]

Thanks for all the comments of the reviewers.

Updated docs is still available here 
http://people.apache.org/~aramirez/maven-surefire-plugin/


Cheers,
allan

Allan Ramirez wrote:

Hi everyone,

Just updated the docs of the surefire 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-surefire-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]

Re: Review of maven-dependency-plugin documentation

[Allan Ramirez]

Done in updating the docs. Thanks for all the comments of reviewers.

Site is still available at 
http://people.apache.org/~aramirez/maven-dependency-plugin/


Cheers,
allan

Allan Ramirez wrote:

Hi Everyone,

The plugin docs for maven-dependency-plugin is now ready for review.
Staging site can be found here.

http://people.apache.org/~aramirez/maven-dependency-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]

Re: Review surefire plugin documentation

[Allan Ramirez]

Hi Simon,

Thanks for all of your comments. By the way, what do you mean by 
"environment variable configuration"?

Is that different with the System Properties example?

Regards,
allan

Simon Kitching wrote:

On Tue, 2006-08-01 at 11:52 +1200, Simon Kitching wrote:
  

On Tue, 2006-08-01 at 11:15 +1200, Simon Kitching wrote:


On Fri, 2006-07-28 at 20:05 +0200, Dennis Lundberg wrote:
      

Allan Ramirez wrote:


Hi everyone,

Just updated the docs of the surefire 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-surefire-plugin/
  

BTW, my reading of the surefire-plugin code is that the "test"
configuration attribute can be a comma-separated list of classes to
execute. The docs indicate that only one test class can be listed. See
method SurefirePlugin.constructSurefireBooter().




Oh, and is there any chance of an example of the use of "environment
variable" configuration? I'm experimenting with this at the moment, and
can't get it working. Probably my fault, but there is definitely a lack
of documentation about this.

Cheers,

Simon



-
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 maven-dependency-plugin documentation

[Allan Ramirez]

Applied, and with regards in the terms used, I added a link to 
dependency mechanism for more information about dependencies


Cheers,
allan

Franz Allan Valencia See wrote:

Good day,

Here are my reviews,

in general
dependency and other related terms were not explained (since this is the
dependency plugin, i guess there should be an explanation as to what
dependency and the other related terms are, or at least a reference to 
where

one can find out more about it)
* transitive dependency
* resolve (what does it mean by "resolve")

in index.html
change "usecases" to "use-cases"

in site.xml
Change the link named "Maven 2" to just "Maven"

in usage.html
Apply monospace font on the following words:
* ArtifactItem
* outputDirectoryField
* dependencyManagement
* artifactItem.overWrite
* overWriteReleases
* overWriteSnapshots
* resolve (wherein by "resolve", you meant the "resolve" goal)

in FAQ.html
remove "most" from the phrase "...the most recommended plugin to use..."

Thanks a bunch ^_^
Franz

On 8/1/06, Allan Ramirez <[EMAIL PROTECTED]> wrote:


Hi Everyone,

The plugin docs for maven-dependency-plugin is now ready for review.
Staging site can be found here.

http://people.apache.org/~aramirez/maven-dependency-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]

Re: Review of maven-dependency-plugin documentation

[Allan Ramirez]

changed. Thanks for that.

allan

Matt Brozowski wrote:


On Aug 1, 2006, at 7:18 PM, Allan Ramirez wrote:


Hi Everyone,

The plugin docs for maven-dependency-plugin is now ready for review.
Staging site can be found here.

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



Most of the examples still reference the plugin as 
'dependency-maven-plugin' rather than 'maven-dependency-plugin'



Matt Brozowski


___ 


Matt Brozowski, OpenNMS MaintainerMain:+1 919 812 4984
The OpenNMS Group, Inc.Fax:+1 503 961 7746
Email: [EMAIL PROTECTED]URL:
http://www.opennms.com






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

Review of maven-antrun-plugin documentation

[Allan Ramirez]

maven-antrun-plugin documentation is now ready for review.
Staging site can be found here:

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

jira issue:
http://jira.codehaus.org/browse/MANTRUN-55

Thank you very much Franz See for your great work here.

Cheers,
allan



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

Review of maven-dependency-plugin documentation

[Allan Ramirez]

Hi Everyone,

The plugin docs for maven-dependency-plugin is now ready for review.
Staging site can be found here.

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


Thanks,
allan

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

Re: Contribution to the Plugin Documentation

[Allan Ramirez]

Hi Pete,

I deployed your staging site on the following link:

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

Thanks,
allan

Allan Ramirez wrote:

Hi pete,

I can do that. I will mail you after I deployed it.

Cheers,
allan

Pete Marvin King wrote:

 Hello All,

I have contributed some plugin documentations for the ejb plugin and
scm plugin. I don't have anyplace to stage
the documentation patches if anyone is interested in staging these,
the patch can be accessed in :

  http://jira.codehaus.org/browse/MEJB-17  
http://jira.codehaus.org/browse/SCM-218


I'd be happy to fix and apply any comments and suggestions, feedback
will be highly appreciated. =)  Thanx!


cheers,
pete marvin
 
-

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: Contribution to the Plugin Documentation

[Allan Ramirez]

Hi pete,

I can do that. I will mail you after I deployed it.

Cheers,
allan

Pete Marvin King wrote:

 Hello All,

I have contributed some plugin documentations for the ejb plugin and
scm plugin. I don't have anyplace to stage
the documentation patches if anyone is interested in staging these,
the patch can be accessed in :

  http://jira.codehaus.org/browse/MEJB-17
  http://jira.codehaus.org/browse/SCM-218


I'd be happy to fix and apply any comments and suggestions, feedback
will be highly appreciated. =)  Thanx!


cheers,
pete marvin
  


-
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 Archetype Plugin Documentation needs Reviewing

[Allan Ramirez]

Hi Franz,

Nice work with the plugin. Here are my comments

++

index.html

+ work in progress -> currently under development

Under Goals Overview section:

+ Once the archetype is retrieve it is process -> Once the archetype is 
retrieved it is processed

+ against a st of user -> Typo for "st" It should be "set"


Under Usage section:

+ Change the Resources Plugin to Archetype Plugin

Under Examples

+ examples show how to use the Javadoc Plugin -> examples show how to 
use the Archetype Plugin



usage.html

+ I think the statement "The Archetype Plugin has two goals: create and 
create-from-project" should be removed, since

 it is already mentioned in the Goals Overview section.

+ specific directory structure -> maven recommended directory structure

+ I think you also need to mention that by calling the said command, by 
default, maven will use the

maven-archetype-quickstart (wdyt?)


remote-repositories.html

+ use the remoteRepositories -D expression -> use the remoteRepositories 
property/parameter (in italic or monospace

font)

site.html

+ and it will generate a maven projecct  -> and it will generate a maven 
project
+ This would then create a maven proect -> This would then create a 
maven project
+ you could also add a link to the guide to apt 
format(http://maven.apache.org/guides/mini/guide-apt-format.html) from

here

j2ee-simple.html

+ This would then create a maven proect - >This would then create a 
maven project


webapp.html

+ This would then create a maven proect - >This would then create a 
maven project


portlet.html

+ This would then create a maven proect - >This would then create a 
maven project


mojo.html

+ you can ues -> you can use
+ This would then create a maven proect - >This would then create a 
maven project



Cheers,
allan

Maria Odea Ching wrote:

Hi Everyone,

I've moved the archetype plugin staging site to 
http://people.apache.org/~oching/maven-archetype-plugin 
.

There seems to be a problem with the geocities site.

Thanks,
Odea

Franz Allan Valencia See wrote:


Good day,

I would like to ask for some help reviewing the Maven Archetype Plugin
Documentation.

The documentation can be viewed
here, 


while the Jira Issue can be viewed
here
.

Btw, I assumed that archetypes profiles and simple are still work in
progress. I am not really sure what the purpose of 
maven-archetype-profiles
is, but as of the moment, the results of archetype:create for 
profiles is

the same as that of quickstart. And as for maven-archetype-simple, the
source code seems to be in archetype:create-from-project format, 
which is

also a work in progress.

Moreover, maven-archetype-portlet still has a bug when this 
documentation

was created. However, I've already submitted a patch in its jira
issueto make it work
again.

Also, I would like to suggest that the Apache Maven's Guide to Creating
Archetypesand 


Introduction
to 
Archetypesbe 


transfered in the Maven
Archetype Plugin
Documentation(under 

examplesand 

FAQrespectivelly). 



Thanks,
Franz




-
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: svn commit: r425406 - in /maven/plugins/trunk/maven-surefire-plugin: ./ src/main/java/org/apache/maven/plugin/surefire/ src/site/ src/site/apt/ src/site/apt/examples/ src/site/fml/

[Allan Ramirez]

Hi Trygve,

done. Thanks!

allan

Trygve Laugstøl wrote:

[EMAIL PROTECTED] wrote:

Author: aramirez
Date: Tue Jul 25 07:49:28 2006
New Revision: 425406

URL: http://svn.apache.org/viewvc?rev=425406&view=rev
Log: (empty)


Please make sure you always include a log message. It is impossible to 
follow the development unless you tell what you're doing.


You can change the log message for the revision using svn.

[snip]

--
Trygve

-
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 the documentation for the maven-one-plugin

[Allan Ramirez]

oopss sorry it should be one:deploy-maven-one-repository  *NOT* 
one:install-maven-one-repository


allan

Allan Ramirez wrote:

Hi Dennis,

Nice work! But got confused with the difference between 
one:install-maven-one-repository goal and the deploy:deploy-file with 
repositoryLayout as legacy 
(http://people.apache.org/~aramirez/maven-deploy-plugin/examples/deploying-in-legacy-layout.html). 
Are they the same?


Thanks,
allan

Dennis Lundberg wrote:

Hi all

I have finished going over the documentation for the
maven-one-plugin and adapting it to the plugin documentation standard.

Please take a moment and read through it. There is a JIRA issue for
this:
  http://jira.codehaus.org/browse/MONE-4

Feel free to post your comments to the mailing list or to that issue.

There are a couple of mojo parameters left to write Javadoc for. I 
just don't know what they do. Perhaps Brett, as the original author, 
can shed some light on those. I've added @todos for them in the code.


A staged site is available for browsing here:
  http://people.apache.org/~dennisl/maven-one-plugin/



-
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 the documentation for the maven-one-plugin

[Allan Ramirez]

Hi Dennis,

Nice work! But got confused with the difference between 
one:install-maven-one-repository goal and the deploy:deploy-file with 
repositoryLayout as legacy 
(http://people.apache.org/~aramirez/maven-deploy-plugin/examples/deploying-in-legacy-layout.html). 
Are they the same?


Thanks,
allan

Dennis Lundberg wrote:

Hi all

I have finished going over the documentation for the
maven-one-plugin and adapting it to the plugin documentation standard.

Please take a moment and read through it. There is a JIRA issue for
this:
  http://jira.codehaus.org/browse/MONE-4

Feel free to post your comments to the mailing list or to that issue.

There are a couple of mojo parameters left to write Javadoc for. I 
just don't know what they do. Perhaps Brett, as the original author, 
can shed some light on those. I've added @todos for them in the code.


A staged site is available for browsing here:
  http://people.apache.org/~dennisl/maven-one-plugin/



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

Review surefire plugin documentation

[Allan Ramirez]

Hi everyone,

Just updated the docs of the surefire 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-surefire-plugin/


Thanks,
allan

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

Re: Review surefire-report-plugin documentation

[Allan Ramirez]

Hi Dennis,

Applied comments. Thanks again

Cheers,
-allan

Dennis Lundberg wrote:

Allan Ramirez wrote:

Hi everyone,


Just updated the docs of the surefire-report 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-surefire-report-plugin/


Thanks,
allan

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



Thanks for your work Allan. It's looking good. I just found a couple 
of small details:


index.html
- Change the heading "Introduction" to be the plugin name.

surefire-report.html
- Parameter outputName:
  "The default filename to use" --> "The filename to use"
- Parameter reportsDirectory:
  "that must be parsed" --> "that will be parsed"
- Parameter showSuccess:
  "If set to false"
  It seems that you have used html-entities for the '<' and '>'
  characters.

examples/show-failures.html
- "test result satus(success" --> "test result status (success"
- "In able to show" --> "To be able to show"

examples/changing-report-name.html
- "file name is changed to newname.html" -->
  "file is named newname.html"

examples/report-custom-location.html
- Under the heading "Configuring the Output Location using standalone 
goal" there is a pom and commandline example. Shouldn't the pom be 
removed from there and the commandline be changed to add 
-DoutputDirectory...


examples/cross-referencing.html
- "There are times that we need to" -->
  "There are times when we need to"
- "In able to activate it" --> "To be able to activate it"
- "be declared to" --> "be declared in"




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

Re: Review surefire-report-plugin documentation

[Allan Ramirez]

Hi,

Applied comments, and thanks for your review

Cheers,
allan

Cabasson Denis wrote:

This is great work!

As far as I'm concerned, everything needed is there.

You have got a deadlink on your index page, your mojo page entry is
report-mojo.html rather than surefire-report-mojo.html 


The only other thing that could be improved (but that's really details, when
you see how much more information you get from your page than the current
documentation) are the screenchots. They are good, but I find it hard to see
the limits between the documentation and the screenshots. Maybe some border
would help?

Anyway, this documentation is great.

Can't wait to have all this brand new documentation set into place, to
really be able to fully use the maven plugins (at least the apache ones).

Cheers.

Denis.

-Message d'origine-
De : Allan Ramirez [mailto:[EMAIL PROTECTED] 
Envoyé : samedi 22 juillet 2006 03:45

À : Maven Developers List
Objet : Review surefire-report-plugin documentation

Hi everyone,


Just updated the docs of the surefire-report 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-surefire-report-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]

Review surefire-report-plugin documentation

[Allan Ramirez]

Hi everyone,


Just updated the docs of the surefire-report 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-surefire-report-plugin/


Thanks,
allan

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

Re: Review of install plugin

[Allan Ramirez]

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]

Re: Review for maven-rar-plugin

[Allan Ramirez]

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]

Re: Review for maven-rar-plugin

[Allan Ramirez]

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]

Re: Review of install plugin

[Allan Ramirez]

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]

Re: Review of install plugin

[Allan Ramirez]

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]

Review for maven-rar-plugin

[Allan Ramirez]

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]

Re: Review of install plugin

[Allan Ramirez]

Hi Dennis,

Thanks for the comments. will fix immediately.

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]

Review of install plugin

[Allan Ramirez]

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

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

Re: deploy:deploy-file

[Allan Ramirez]

Hi Rinku,

There is an open issue for it.. please see 
http://jira.codehaus.org/browse/MNG-1712


regards,
allan

Rinku wrote:

Hi,

I have meant to ask this everytime I run into similar error with wagon 
providers.


Why is it that the wagon provider lib needs to be copied to under M2 
Home? Shouldn't this be downloaded to local repo and used from there? 
Is it something to do with Classworlds' realms.


Cheers,
Rahul

- Original Message ----- From: "Allan Ramirez" <[EMAIL PROTECTED]>
To: "Maven Developers List" 
Sent: Tuesday, July 11, 2006 3:15 AM
Subject: Re: deploy:deploy-file



Hi,

This should be on the users mailing list. anyway, to answer your 
question,


When using deploy-deploy-file goal and encountered this error

"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find 
wagon which supports the requested protocol: ftp"


You only have to place the appropriate wagon provider to your 
%M2_HOME%/lib.
In this case the provider needed is ftp, so we have to place the 
wagon-ftp jar to the lib of your m2 installation.


If the error description is something like

"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find 
wagon which supports the requested protocol: ftp

org/apache/commons/net/ftp/FTP"

Place also the commons-net jar to %M2_HOME%/lib.


You can find the wagon-ftp here 
http://www.ibiblio.org/maven2/org/apache/maven/wagon/wagon-ftp/


Cheers,
allan

Marcin Maciukiewicz wrote:

Hi!

I want to deploy my artifact via ftp. So this is my command:
mvn -e -Durl=file://ftp://some-server/root-dir/
-Dfile=com.company.models.util_1.2.0.jar
-DrepositoryId=ftp-company-snapshot -DgroupId=com.company.models
-DartifactId=com.company.models.util -Dversion=1.2.0-SNAPSHOT
-Dpackaging=jar -DgeneratePom=true deploy:deploy-file

This the result:
...
[INFO] 
 


[ERROR] BUILD ERROR
[INFO] 
 


[INFO] Error deploying artifact: Unsupported Protocol: 'ftp': Cannot
find wagon which supports the requested protocol: ftp
...

How to register wagon for ftp transport when using command line
deployment as shown above?

Thanks,
Marcin.

-
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: deploy:deploy-file

[Allan Ramirez]

Hi,

This should be on the users mailing list. anyway, to answer your question,

When using deploy-deploy-file goal and encountered this error

"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find 
wagon which supports the requested protocol: ftp"


You only have to place the appropriate wagon provider to your %M2_HOME%/lib.
In this case the provider needed is ftp, so we have to place the 
wagon-ftp jar to the lib of your m2 installation.


If the error description is something like

"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find 
wagon which supports the requested protocol: ftp

org/apache/commons/net/ftp/FTP"

Place also the commons-net jar to %M2_HOME%/lib.


You can find the wagon-ftp here 
http://www.ibiblio.org/maven2/org/apache/maven/wagon/wagon-ftp/


Cheers,
allan

Marcin Maciukiewicz wrote:

Hi!

I want to deploy my artifact via ftp. So this is my command:
mvn -e -Durl=file://ftp://some-server/root-dir/
-Dfile=com.company.models.util_1.2.0.jar
-DrepositoryId=ftp-company-snapshot -DgroupId=com.company.models
-DartifactId=com.company.models.util -Dversion=1.2.0-SNAPSHOT
-Dpackaging=jar -DgeneratePom=true deploy:deploy-file

This the result:
...
[INFO] 


[ERROR] BUILD ERROR
[INFO] 


[INFO] Error deploying artifact: Unsupported Protocol: 'ftp': Cannot
find wagon which supports the requested protocol: ftp
...

How to register wagon for ftp transport when using command line
deployment as shown above?

Thanks,
Marcin.

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



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

Re: MRM Build Broken

[Allan Ramirez]

Build your maven-jar-plugin from svn then try to build mrm again.

-allan

David Beckedorff wrote:

What is the fix for this?  I'm using maven-2.0.4.

 

  

 


[INFO] Installing
D:\MRM\maven-repository-manager-site\maven-repository-application\target\m

aven-repository-application-1.0-SNAPSHOT.jar to C:\Documents and
Settings\dbeckedorff\.m2\re

pository\org\apache\maven\repository\maven-repository-application\1.0-SNAPSH
OT\maven-reposit

ory-application-1.0-SNAPSHOT.jar

[INFO]


[INFO] Building Maven Repository Manager Artifact Applet

[INFO]task-segment: [install]

[INFO]


[INFO]


[ERROR] BUILD ERROR

[INFO]


[INFO] 'sign' was specified in an execution, but not found in the plugin

[INFO]


[INFO] Trace

org.apache.maven.lifecycle.LifecycleExecutionException: 'sign' was specified
in an execution

, but not found in the plugin

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle
(Defa

ultLifecycleExecutor.java:1337)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(De
fault

LifecycleExecutor.java:1238)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappin
gs(De

faultLifecycleExecutor.java:982)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleE

xecutor.java:453)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(

DefaultLifecycleExecutor.java:306)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLi

fecycleExecutor.java:273)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Execu

tor.java:140)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)

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:315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

[INFO]


[INFO] Total time: 37 seconds

[INFO] Finished at: Mon Jun 12 13:43:29 EDT 2006

[INFO] Final Memory: 9M/17M

[INFO]


 

 

<<< 

 

 


___

 


David Beckedorff

Senior Developer

CellExchange, Inc.

[EMAIL PROTECTED]

Office: (617)528-2196

Cell:   (781)820-0567

 

 



  


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

Re: svn commit: r407769 - /maven/plugins/trunk/maven-deploy-plugin/src/main/java/org/apache/maven/plugin/deploy/DeployFileMojo.java

[Allan Ramirez]

Kenney Westerhof wrote:


On Fri, 19 May 2006, Brett Porter wrote:


 


[EMAIL PROTECTED] wrote:
   


/**
+ * Description passed to a generated POM file (in case of generatePom=true)
+ *
+ * @parameter expression="${generatePom.description}"
+ */
+private String description = "POM was created from deploy:deploy-file";
 


Wouldn't ${description} be more consistent?
   



If it's a  element, yes; if it's specified on the
commandline then I'm in favor of prefixing property names with something
so you can call multiple goals at once without risking overlapping.
Although in this case the goal would probably always be the only one
specified at the command line.
 


I agree with Kenney for the property name. Im going to leave it as is.


I don't think there should be a default (and besides, defaults should be
in default-value).
   



True.
 


Yeah, You're both right. I'll change it right away. Thanks

-allan


-- Kenney
 


- Brett

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

   



--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

-
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: What is in assembly's FileItem

[Allan Ramirez]

Hi Dan,

It is like the  of resources where the expression in resource 
files such as LICENSE.txt can be interpolated.


Hope this helps,
allan

dan tran wrote:

Hello, I am trying to fix 
http://jira.codehaus.org/browse/MASSEMBLY-100  and

having trouble
understanding the purpose of  element in FileItem if the
descriptor.

Could someone or the owner of that feature explains what it really means?

Thanks

-Dan



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

Re: [vote] Fabrice Bellingard as a plugins committer

[Allan Ramirez]

+ 1

Brett Porter wrote:


Hi,

Fabrice worked on the JXR plugin, fixed a number of bugs in the original
library and improved the mojo. Active on the users list, with a
particular interest in the site plugin, I believe would be a good
addition to the project.

Please vote:
[ ] +1
[ ] +0 abstain
[ ] -1

Vote is open for 72 hours.

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

Re: [vote] Brian Fox as a plugins committer

[Allan Ramirez]

+ 1

Brett Porter wrote:


Hi,

Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugin there, which we previously indicated
we'd like to have as a part of the Maven plugin artillery.

He has also actively helped on the users list and participated on the
dev@ list.

Please vote:
[ ] +1
[ ] +0 abstain
[ ] -1

Vote is open for 72 hours.

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

How to resolve a project jar if it is not yet installed in the repo?

[Allan Ramirez]

Hi everyone,

Is there a way to resolve a project jar of project modules if it is not 
yet installed in the repo?


I tried the reactorProject.getArtifact().getFile() but it is returning a 
null value.


Thanks in advance,
-allan

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

[jira] Closed: (MASSEMBLY-46) artifact classifier not used in outputFileNameMapping

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MASSEMBLY-46?page=all ]
 
Allan Ramirez closed MASSEMBLY-46:
--

Resolution: Fixed

Fixed in svn. 

> artifact   classifier  not used in  outputFileNameMapping
> -
>
>  Key: MASSEMBLY-46
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-46
>  Project: Maven 2.x Assembly Plugin
> Type: Bug

>  Environment: Linux
> Reporter: M. van der Plas
> Assignee: Allan Ramirez
>  Fix For: 2.1

>
>
> The classifier field of an artifact cannot be specified in the 
> outputFileNameMapping. 
> This means that  attached Artifacts with the same type cannot  be 
> distinguished. 
> I have a native code libraries attached to a java jar. Next, I have 
> documentation etc attached to the artifact. All files have type .tgz.
> When I specify a depencySet I end up with only one file, instead of several. 
> This is caused by the fact that classifier is removed from the name of the 
> the original input artifact file. 
> The workaround is to rename attached artifacts to a different type (rename 
> .tgz to  .tar.gz...).

-- 
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: (MJAVADOC-36) Would like a way to get default javadoc behavior

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-36?page=all ]
 
Allan Ramirez closed MJAVADOC-36:
-

Resolution: Fixed

Applied odea's patch. Thanks

> Would like a way to get default javadoc behavior
> 
>
>  Key: MJAVADOC-36
>  URL: http://jira.codehaus.org/browse/MJAVADOC-36
>  Project: Maven 2.x Javadoc Plugin
> Type: Wish

>  Environment: Windows XP
> Reporter: Martin Desruisseaux
> Assignee: Maria Odea Ching
> Priority: Minor
>  Fix For: 2.0-beta-4
>  Attachments: MJAVADOC-36-maven-javadoc-plugin.patch, 
> no_default_stylesheet.diff
>
>
> The javadoc plugin overrides some Sun's javadoc default options with its own 
> default. This is quite nice for options like -bottom, since Maven has 
> informations that Sun's javadoc doesn't have. The -package option (which 
> default to 'true' in maven-javadoc-plugin, while the default was 'false' in 
> Sun's javadoc) sound a little bit more surprising to me, since it lead us to 
> a situation where we have two set of default values to keep in mind: the 
> Sun's ones, and the Maven ones.
> It is not a real problem for options like -package and -use. It is a little 
> bit more disturbing for -stylesheet, since it seems hard to tell to Maven to 
> not use the Maven's stylesheet, but to keep the Sun's default stylesheet 
> instead. I understand that we can provide our own stylesheet with the 
>  parameter, but in this case I have no file to point; I would 
> just like to keep Sun's default stylesheet.
> I would like a way to disable completly the "-stylesheet" option in the 
> javadoc plugin. Or alternatively, the plugin may use the Maven's stylesheet 
> only when explicitly required.

-- 
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: (MJAVADOC-57) empty target/site/apidocs/apidocs/index.html created

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-57?page=all ]
 
Allan Ramirez closed MJAVADOC-57:
-

Resolution: Fixed

Applied patch.. Thanks

> empty target/site/apidocs/apidocs/index.html created
> 
>
>  Key: MJAVADOC-57
>  URL: http://jira.codehaus.org/browse/MJAVADOC-57
>  Project: Maven 2.x Javadoc Plugin
> Type: Bug

> Reporter: Brett Porter
> Assignee: Maria Odea Ching
>  Fix For: 2.0-beta-4
>  Attachments: MJAVADOC-57-maven-javadoc-plugin.patch
>
>
> this seems to be because of the getOutputName(), but setting that to "index" 
> would likely overwrite the correct version.

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


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

[jira] Commented: (MASSEMBLY-33) document assembly descriptoir in more detail

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MASSEMBLY-33?page=comments#action_60292 ] 

Allan Ramirez commented on MASSEMBLY-33:


Already fixed in SVN.

> document assembly descriptoir in more detail
> 
>
>  Key: MASSEMBLY-33
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-33
>  Project: Maven 2.x Assembly Plugin
> Type: Bug

> Reporter: Brett Porter
>  Fix For: 2.1

>
>
> fill out the mdo descriptions, and enhance the standard descriptor doc to 
> explain what each does.

-- 
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: (MASSEMBLY-56) Refactor DirectoryMojo so it can be run either stand-alone or attached

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MASSEMBLY-56?page=comments#action_60175 ] 

Allan Ramirez commented on MASSEMBLY-56:


Does somebody already came up with a good name for this? ;)

> Refactor DirectoryMojo so it can be run either stand-alone or attached
> --
>
>  Key: MASSEMBLY-56
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-56
>  Project: Maven 2.x Assembly Plugin
> Type: Improvement

> Versions: 2.1
> Reporter: John Didion
>  Fix For: 2.1
>  Attachments: MASSEMBLY-56.patch
>
>
> Pretty straight-forward. Just make the directory goal into two goals (like 
> assembly and attached), one that can be run stand-alone and one that can be 
> run attached to a lifecycle phase.

-- 
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: (MASSEMBLY-11) In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MASSEMBLY-11?page=all ]
 
Allan Ramirez closed MASSEMBLY-11:
--

Resolution: Fixed

Fixed in SVN, usage of expressions are now allowed in the assembly descriptor. 

> In a multi-module build, assembly descriptor paths are not project-relative, 
> but erraneously relative to the parent project directory
> -
>
>  Key: MASSEMBLY-11
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-11
>  Project: Maven 2.x Assembly Plugin
> Type: Bug

>  Environment: WinXP SP2
> Maven 2
> Reporter: Michael Böckling
> Assignee: Allan Ramirez
>  Fix For: 2.1

>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> When I try to perform a multi-module build executed in a build-only 
> (packaging=pom) parent project ("AAH-1-Genius-Build"), assembly fails. I 
> defined an assembly:assembly execution bound to the "install" phase in the 
> "AAH-1-Genius-TpmMonitor" sub-project using my own descriptor. Maven finds 
> the descriptor, but the (relative) paths in the descriptor are not expanded 
> against the "AAH-1-Genius-TpmMonitor" sub-project, but against the 
> "AAH-1-Genius-Build" parent-project, which of course stops the build.
> The last line of the error log below shouldnt be 
> "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern", it should 
> be "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-TpmMonitor\src\extern"!
> I also tried using ${basedir} and such, but unfortunately those variables 
> don't get expanded. I also tried activating "includeBaseDirectory" in the 
> descriptor, hoping it would prepend the current project path to the 
> descriptor paths (I had to guess since its not documented...), but no luck.
> Beside the obvious bug concerning project directory, I really think maven 
> vars should be expanded.
> Error log:
> [INFO] [assembly:assembly {execution: prepare-assembly}]
> [INFO] Expanding: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-BusinessLib\target\aah-genius-business-lib-1.0-SNAPSHOT.jar into 
> C:\DEVE
> LOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target
> \assembly\work\aah-genius-business-lib-1.0-SNAPSHOT
> [INFO] Expanding: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-MappingLib\target\aah-genius-mapping-lib-1.0-SNAPSHOT.jar into 
> C:\DEVELO
> PMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target\a
> ssembly\work\aah-genius-mapping-lib-1.0-SNAPSHOT
> [INFO] 
> -
> ---
> [ERROR] BUILD ERROR
> [INFO] 
> -
> ---
> [INFO] Error creating assembly
> Embedded error: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern
>  isn't a directory.
> [INFO] 
> -

-- 
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: (MASSEMBLY-11) In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MASSEMBLY-11?page=all ]

Allan Ramirez updated MASSEMBLY-11:
---

Remaining Estimate: 4 hours
 Original Estimate: 4 hours

> In a multi-module build, assembly descriptor paths are not project-relative, 
> but erraneously relative to the parent project directory
> -
>
>  Key: MASSEMBLY-11
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-11
>  Project: Maven 2.x Assembly Plugin
> Type: Bug

>  Environment: WinXP SP2
> Maven 2
> Reporter: Michael Böckling
> Assignee: Allan Ramirez
>  Fix For: 2.1

>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> When I try to perform a multi-module build executed in a build-only 
> (packaging=pom) parent project ("AAH-1-Genius-Build"), assembly fails. I 
> defined an assembly:assembly execution bound to the "install" phase in the 
> "AAH-1-Genius-TpmMonitor" sub-project using my own descriptor. Maven finds 
> the descriptor, but the (relative) paths in the descriptor are not expanded 
> against the "AAH-1-Genius-TpmMonitor" sub-project, but against the 
> "AAH-1-Genius-Build" parent-project, which of course stops the build.
> The last line of the error log below shouldnt be 
> "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern", it should 
> be "C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-TpmMonitor\src\extern"!
> I also tried using ${basedir} and such, but unfortunately those variables 
> don't get expanded. I also tried activating "includeBaseDirectory" in the 
> descriptor, hoping it would prepend the current project path to the 
> descriptor paths (I had to guess since its not documented...), but no luck.
> Beside the obvious bug concerning project directory, I really think maven 
> vars should be expanded.
> Error log:
> [INFO] [assembly:assembly {execution: prepare-assembly}]
> [INFO] Expanding: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-BusinessLib\target\aah-genius-business-lib-1.0-SNAPSHOT.jar into 
> C:\DEVE
> LOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target
> \assembly\work\aah-genius-business-lib-1.0-SNAPSHOT
> [INFO] Expanding: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1
> -Genius-MappingLib\target\aah-genius-mapping-lib-1.0-SNAPSHOT.jar into 
> C:\DEVELO
> PMENT\Workspaces\Standard\AAH-1-Genius-Build\..\AAH-1-Genius-TpmMonitor\target\a
> ssembly\work\aah-genius-mapping-lib-1.0-SNAPSHOT
> [INFO] 
> -
> ---
> [ERROR] BUILD ERROR
> [INFO] 
> -
> ---
> [INFO] Error creating assembly
> Embedded error: 
> C:\DEVELOPMENT\Workspaces\Standard\AAH-1-Genius-Build\src\extern
>  isn't a directory.
> [INFO] 
> -

-- 
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: (MJAVADOC-47) Javadoc plugin ignores destDir when used in reporting section

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-47?page=all ]
 
Allan Ramirez closed MJAVADOC-47:
-

Resolution: Fixed

Applied Patch. Thanks

> Javadoc plugin ignores destDir when used in reporting section
> -
>
>  Key: MJAVADOC-47
>  URL: http://jira.codehaus.org/browse/MJAVADOC-47
>  Project: Maven 2.x Javadoc Plugin
> Type: Bug

> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
>  Fix For: 2.0-beta-4
>  Attachments: MJAVADOC-47-maven-javadoc-plugin.patch
>
>
> When used in the reporting section of the pom and 'mvn site', output always 
> goes to target/apidocs, even if you specify an outputDir.  
> Having outputDir work correctly would by useful with alternate doclets, for 
> example sending the output of the UMLGraph doclet to target/uml so that it 
> can be further transformed.
> This seems to be the code that's doing it:
> if ( !javadocDirectory.getAbsolutePath().equals( getOutputDirectory() 
> ) )
> {
> // we're in site-embedded report mode, so Doxia has set the
> // reportOutputDirectory to the basedir of the site.
> // Append 'apidocs'.
> javadocDirectory = new File( javadocDirectory, "apidocs" );
> }

-- 
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: (MJAVADOC-40) javadoc:jar doesn't work if destDir was changed in javadoc:javadoc

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-40?page=all ]
 
Allan Ramirez closed MJAVADOC-40:
-

Resolution: Fixed

Applied patch. Thanks

> javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
> --
>
>  Key: MJAVADOC-40
>  URL: http://jira.codehaus.org/browse/MJAVADOC-40
>  Project: Maven 2.x Javadoc Plugin
> Type: Bug

> Reporter: Brian Fox
> Assignee: Maria Odea Ching
>  Fix For: 2.0-beta-4
>  Attachments: MJAVADOC-40-maven-javadoc-plugin.patch, javadoc-jar.patch
>
>
> The following configuration will cause jar to fail. This is major because it 
> stops release:perform from completing on what otherwise should be a valid 
> config
> 
> 
>   
> maven-javadoc-plugin
> 
>   1.4
>   ${project.build.directory}/site/javadoc
> 
>   
> 
>   

-- 
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: (MJAVADOC-46) Allow -docletpath to be specified as an artifact

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-46?page=all ]
 
Allan Ramirez closed MJAVADOC-46:
-

Resolution: Fixed

Applied Patch.. Thanks Wendy and Odea

> Allow -docletpath to be specified as an artifact
> 
>
>  Key: MJAVADOC-46
>  URL: http://jira.codehaus.org/browse/MJAVADOC-46
>  Project: Maven 2.x Javadoc Plugin
> Type: New Feature

> Reporter: Wendy Smoak
> Assignee: Allan Ramirez
> Priority: Minor
>  Fix For: 2.0-beta-4
>  Attachments: javadoc-docletArtifact.diff
>
>
> As suggested (and written!) by Brett Porter on [EMAIL PROTECTED], in this 
> thread:
>http://marc.theaimsgroup.com/?l=turbine-maven-dev&m=113694865002748&w=2 
> Allow the doclet path to be specified as an artifact with .  
> Currently the only option is  which must be the local path to the 
> jar file and is not portable.
> Comments welcome, I'm happy to rework it if necessary.

-- 
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: (MASSEMBLY-40) Evaluate project variables within assembly descriptors

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MASSEMBLY-40?page=all ]
 
Allan Ramirez closed MASSEMBLY-40:
--

Resolution: Fixed

Fixed in SVN. 

> Evaluate project variables within assembly descriptors
> --
>
>  Key: MASSEMBLY-40
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-40
>  Project: Maven 2.x Assembly Plugin
> Type: Bug

> Reporter: Travis Carlson
> Assignee: Allan Ramirez
>  Fix For: 2.1

>
>   Time Spent: 10 hours
>Remaining: 0 minutes
>
> Currently any project variables (for example ${basedir}, ${artifact}, etc.) 
> are ignored within the assembly descriptor.

-- 
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: (MASSEMBLY-71) Allow an archive base directory that accepts variables

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MASSEMBLY-71?page=all ]
 
Allan Ramirez closed MASSEMBLY-71:
--

Resolution: Fixed

Applied Patch. Thanks

> Allow an archive base directory that accepts variables
> --
>
>  Key: MASSEMBLY-71
>  URL: http://jira.codehaus.org/browse/MASSEMBLY-71
>  Project: Maven 2.x Assembly Plugin
> Type: New Feature

> Versions: 2.0.1, 2.0
> Reporter: Gary Murphy
> Assignee: Allan Ramirez
>  Fix For: 2.1
>  Attachments: MASSEMBLY-71-maven-assembly-plugin.patch
>
>
> Much like the request in MASSEMBLY-40, I wanted to be able to use profile 
> variables in the specification of the location of items to include in the 
> assembly.  I also wanted to be able to specify the base directory when 
> constructing the assembly.  That is, I was getting:
> Archive:  commons-bin.zip
>  Length   MethodSize  Ratio   Date   Time   CRC-32Name
>   --  --- -         --
>0  Stored0   0%  02-17-06 07:19    c:/
>0  Stored0   0%  09-24-05 15:47    c:/home/
>0  Stored0   0%  02-17-06 16:40    c:/home/glm/
>0  Stored0   0%  11-18-05 09:23    c:/home/glm/develop/
> .
> .
> .
>21798  Defl:N19746   9%  02-18-06 08:22  a9ca0394  
> c:/home/glm/develop/jar/commons-1.2-SNAPSHOT.jar
>   ---  ------
>2179819746   9%12 files
> in the archive, but I wanted:
> Archive:  commons-bin.zip
>  Length   MethodSize  Ratio   Date   Time   CRC-32Name
>   --  --- -         --
>0  Stored0   0%  02-18-06 08:51    jar/
>21798  Defl:N19745   9%  02-18-06 08:51  1232e35d  
> jar/commons-1.2-SNAPSHOT.jar
>   ---  ------
>2179819745   9%2 files
> I took an approach that achieves both of these goals.   I added a 
> archiveBaseDirectory property to the AssemblyMojo that allows the base of the 
> archive to be specified as a parameter as the example shows:
> 
>.
>.
>.
>   
> org.apache.maven.plugins  
> maven-assembly-plugin
> 2.1-SNAPSHOT
> 
>${basedir}/assembly.xml
>${artifactId}
> 
> ${buildPath}/${artifactId}
>
> ${assemblyPath}/assembly/${artifactId}
>
> ${assemblyPath}/tmp/assembly/${artifactId}
> 
>  
>.
>.
>.
> 
> where ${buildpath} comes from my profile:
>   
> 
>   
> true
>   
>   aentendre
>   
> /home/glm/develop
>   
> 
> 
> I will attach the patch after I get the JIRA number.

-- 
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: (MDEPLOY-7) deploy plugin leaves unnecessary information in the deployed pom.xml

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-7?page=all ]
 
Allan Ramirez closed MDEPLOY-7:
---

Resolution: Fixed

I closed this issue because it seems to me that it is already deploying an 
uninherited, uninjected, uninterpolated POM to the remote repository

> deploy plugin leaves unnecessary information in the deployed pom.xml
> 
>
>  Key: MDEPLOY-7
>  URL: http://jira.codehaus.org/browse/MDEPLOY-7
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Reporter: Jorg Heymans
> Assignee: Allan Ramirez

>
>
> ideally, during deployment, the deployed pom should be stripped of elements 
> like  and 
> IRC log :
> jorg  Can someone enlighten me here : when i "deploy" an artifact (m2), why 
> does the deployed plugin contain the  and  
> elements ?
> jorg  s/plugin/artifact/
> jorg  surely these elements are only relevant to the deployer ?
> jesse in the pom that is in the jar?
> jorg  no the one that is deployed alongside the jar
> jorg  shall I jira this ?
> jesse hm, I think that is a bug similar to the one with stuff in the 
> META-INF/maven file too
> jorg  yeah that's what i figured too
> jesse might as well bug it
> jdcasey   jorg: we're not cleaning up that pom at all, just sending it 
> on...but it's a good point
> jorg  jdcasey: you mean about the maven version ?
> jdcasey   I mean about the build/distributionManagement stuff...or 
> anything that makes it into the POM that's deployed
> jorg  oh ok , yup i think the pom should be stripped of anything not 
> dependency related
> jorg  i'm using deploy plugin v2.0
> jdcasey   I think I agree that it should be stripped of the functional 
> parts of the POM, but not the informational stuff...it will allow us to make 
> a richer map of project info if we leave that stuff in
> jorg  jdcasey: yes thinking of it that's what i meant .. anything build or 
> deploy related can go
> jdcasey   "don't ask *how" this got here, it just did." ;-)
> jorg  hehe exactly

-- 
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: [vote] Release Maven 2.0.3

[Allan Ramirez]

+ 1 for me

John Casey wrote:


Hi,

I think it's time to release Maven 2.0.3. This release will 
incorporate 21 resolved JIRA issues, including some critical fixes for 
Continuum and users of the embedder. The full listing of fixes can be 
found here:


http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=12107 



The remaining open issues are reminders for the site publishing 
process which should accompany this binary release.


If you're interested, you can take the current release candidate for a 
test drive. The RC tarball is at:


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



I'll leave the vote open for the customary 72 hours before 
summarizing. Please cast your vote as:


[ ] +1 Yes, release
[ ]  0 No opinion
[ ] -1 No, don't release

Here's my +1.

Cheers,

John

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



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

[jira] Closed: (MDEPLOY-24) Plugin lacks documentation

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-24?page=all ]
 
Allan Ramirez closed MDEPLOY-24:


Resolution: Fixed

Added docs in SVN. Thanks

> Plugin lacks documentation
> --
>
>  Key: MDEPLOY-24
>  URL: http://jira.codehaus.org/browse/MDEPLOY-24
>  Project: Maven 2.x Deploy Plugin
> Type: Improvement

> Versions: 2.1
> Reporter: Jerome Lacoste
> Assignee: Allan Ramirez
>  Fix For: 2.2
>  Attachments: MDEPLOY24.diff
>
>
> Attached the doc. To apply after MDEPLOY-23 and MDEPLOY-19.

-- 
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: (MDEPLOY-19) Ability to deploy-file as classifier

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-19?page=all ]
 
Allan Ramirez closed MDEPLOY-19:


Resolution: Fixed

Fixed in SVN. Thanks Jerome

> Ability to deploy-file as classifier
> 
>
>  Key: MDEPLOY-19
>  URL: http://jira.codehaus.org/browse/MDEPLOY-19
>  Project: Maven 2.x Deploy Plugin
> Type: New Feature

> Versions: 2.1
>  Environment: xp
> Reporter: Dan Tran
> Assignee: Allan Ramirez
>  Attachments: MDEPLOY19.diff
>
>
> deploy-file currently does not support this option

-- 
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: (MDEPLOY-25) deploy:deploy-file installs the file in the local repository too (but it should not do that)

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-25?page=all ]
 
Allan Ramirez closed MDEPLOY-25:


Resolution: Fixed

-added the document in the maven-site "guide-deploying-3rd-party-jars.apt" 
-mentioned that the artifact would be installed both on local and remote 
repository

> deploy:deploy-file installs the file in the local repository too (but it 
> should not do that)
> 
>
>  Key: MDEPLOY-25
>  URL: http://jira.codehaus.org/browse/MDEPLOY-25
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.1
> Reporter: Geoffrey De Smet
> Assignee: Allan Ramirez
> Priority: Minor

>
>
> deploy:deploy-file installs a jar in a remote repository, but currently also 
> installs it in the local repository.
> I believe this is a bug, because it makes you wrongly believe that the remote 
> repository is ok when you run local tests afterwards.
> If this is the desired behaviour, please notify it on the command line and 
> the documentation of deploy:deploy-file
> When I installed a simple hello.jar in my remote repository, I also found it 
> in my local repository (in my user dir) after this command:
> $ mvn deploy:deploy-file -Dfile=hello.jar -DgroupId=org.hello 
> -DartifactId=hello -Dversion=0.7 -Dpackaging=jar -Dreposi
> toryId=springRichclientRepository 
> -Durl=file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repositor
> y
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO] 
> 
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO] 
> 
> [INFO] [deploy:deploy-file]
> Uploading: 
> file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repository/org/hello/hello/0.7/hello-0.
> 7.jar
> 6b uploaded
> [INFO] Retrieving previous metadata from springRichclientRepository
> [INFO] Uploading repository metadata for: 'artifact org.hello:hello'
> [INFO] Retrieving previous metadata from springRichclientRepository
> [INFO] Uploading project information for hello 0.7
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 1 second
> [INFO] Finished at: Sun Feb 19 19:38:12 CET 2006
> [INFO] Final Memory: 2M/4M
> [INFO] 
> 

-- 
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: (MDEPLOY-25) deploy:deploy-file installs the file in the local repository too (but it should not do that)

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MDEPLOY-25?page=comments#action_59171 ] 

Allan Ramirez commented on MDEPLOY-25:
--

Ok.. I 'll document it.

> deploy:deploy-file installs the file in the local repository too (but it 
> should not do that)
> 
>
>  Key: MDEPLOY-25
>  URL: http://jira.codehaus.org/browse/MDEPLOY-25
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.1
> Reporter: Geoffrey De Smet
> Priority: Minor

>
>
> deploy:deploy-file installs a jar in a remote repository, but currently also 
> installs it in the local repository.
> I believe this is a bug, because it makes you wrongly believe that the remote 
> repository is ok when you run local tests afterwards.
> If this is the desired behaviour, please notify it on the command line and 
> the documentation of deploy:deploy-file
> When I installed a simple hello.jar in my remote repository, I also found it 
> in my local repository (in my user dir) after this command:
> $ mvn deploy:deploy-file -Dfile=hello.jar -DgroupId=org.hello 
> -DartifactId=hello -Dversion=0.7 -Dpackaging=jar -Dreposi
> toryId=springRichclientRepository 
> -Durl=file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repositor
> y
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO] 
> 
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO] 
> 
> [INFO] [deploy:deploy-file]
> Uploading: 
> file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repository/org/hello/hello/0.7/hello-0.
> 7.jar
> 6b uploaded
> [INFO] Retrieving previous metadata from springRichclientRepository
> [INFO] Uploading repository metadata for: 'artifact org.hello:hello'
> [INFO] Retrieving previous metadata from springRichclientRepository
> [INFO] Uploading project information for hello 0.7
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 1 second
> [INFO] Finished at: Sun Feb 19 19:38:12 CET 2006
> [INFO] Final Memory: 2M/4M
> [INFO] 
> 

-- 
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: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-21?page=all ]
 
Allan Ramirez closed MDEPLOY-21:


Resolution: Fixed

Fixed in SVN. This time its for sure :)

> Deploying an artifact from the local directory failed if the associated pom 
> file is not renamed
> ---
>
>  Key: MDEPLOY-21
>  URL: http://jira.codehaus.org/browse/MDEPLOY-21
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.0
>  Environment: PowerBook G4, Mac OS X 10.4.4, J2SDK1.5, Maven 2.0.2
> Reporter: Romain Rouvoy
> Assignee: Allan Ramirez

>
> Original Estimate: 5 hours
> Remaining: 5 hours
>
> mvn deploy:deploy-file -Dfile=fractal-2.0.1.jar - DpomFile=fractal-2.0.1.pom 
> -Durl=... -DrepositoryId=objectweb-release
> These files have been previously successfully copied to my local repository 
> using a mvn install:install-file command. I execute the deploy command from 
> the local repository.
> But I obdtain the following error:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO]
> --
> --
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
> --
> --
> [INFO] [deploy:deploy-file]
> Uploading: scp://forge.objectweb.org/var/lib/gforge/chroot/home/
> groups/maven/htdocs/maven2/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.jar
> 11K uploaded
> [INFO] Retrieving previous metadata from objectweb-release [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] Error installing artifact's metadata: Error installing
> metadata: Error rewriting POM
> /Users/rouvoy/.m2/repository/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.pom (No such file or directory) [INFO]
> --
> --
> [INFO] For more information, run Maven with the -e switch [INFO]
> --
> --
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Fri Jan 20 17:09:51 CET 2006 [INFO] Final Memory: 3M/5M 
> [INFO]
> --
> --
> And my local pom file has been deleted by the mvn command :'-(
> In fact I can not use the default pom file generated by install-file to 
> deploy. I need to rename it before deploying ... otherwise the rewriting of 
> the pom file will failed :-(

-- 
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: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-21?page=all ]

Allan Ramirez updated MDEPLOY-21:
-

Remaining Estimate: 5 hours
 Original Estimate: 5 hours

> Deploying an artifact from the local directory failed if the associated pom 
> file is not renamed
> ---
>
>  Key: MDEPLOY-21
>  URL: http://jira.codehaus.org/browse/MDEPLOY-21
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.0
>  Environment: PowerBook G4, Mac OS X 10.4.4, J2SDK1.5, Maven 2.0.2
> Reporter: Romain Rouvoy
> Assignee: Allan Ramirez

>
> Original Estimate: 5 hours
> Remaining: 5 hours
>
> mvn deploy:deploy-file -Dfile=fractal-2.0.1.jar - DpomFile=fractal-2.0.1.pom 
> -Durl=... -DrepositoryId=objectweb-release
> These files have been previously successfully copied to my local repository 
> using a mvn install:install-file command. I execute the deploy command from 
> the local repository.
> But I obdtain the following error:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO]
> --
> --
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
> --
> --
> [INFO] [deploy:deploy-file]
> Uploading: scp://forge.objectweb.org/var/lib/gforge/chroot/home/
> groups/maven/htdocs/maven2/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.jar
> 11K uploaded
> [INFO] Retrieving previous metadata from objectweb-release [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] Error installing artifact's metadata: Error installing
> metadata: Error rewriting POM
> /Users/rouvoy/.m2/repository/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.pom (No such file or directory) [INFO]
> --
> --
> [INFO] For more information, run Maven with the -e switch [INFO]
> --
> --
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Fri Jan 20 17:09:51 CET 2006 [INFO] Final Memory: 3M/5M 
> [INFO]
> --
> --
> And my local pom file has been deleted by the mvn command :'-(
> In fact I can not use the default pom file generated by install-file to 
> deploy. I need to rename it before deploying ... otherwise the rewriting of 
> the pom file will failed :-(

-- 
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: [vote] Release maven-clean-plugin 2.1

[Allan Ramirez]

+ 1

Carlos Sanchez wrote:


+1

On 2/14/06, John Casey (mergere) <[EMAIL PROTECTED]> wrote:
 


Hi,

I wanted to call a vote to see if we can release a new version of the
maven-clean-plugin for Maven 2. I've just added two features which were
covered by two of the three outstanding jira issues - the final jira
issue will have to wait for a new version of plexus-utils, and
consequently, Maven (since the plexus-utils artifact is filtered out of
the plugin's dependency list, and provided by maven's core).

The two issues were:

* MCLEAN-2: Allow configuration of  beyond the three main
directories that are cleaned.

* MCLEAN-4: Provide a flag and behavior to handle symbolic links
(followSymLinks = true|false)

Anyway, these are the only issues in the MCLEAN jira project, so if
there have been other fixes, we have no record of them.

I'll summarize in 72 hours. Please vote +1/0/-1.

Here's my +1.

Thanks,

John

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


   




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

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


 



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

[jira] Reopened: (MNG-2000) Create comprehensive profiles documentation

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-2000?page=all ]
 
Allan Ramirez reopened MNG-2000:


 Assign To: John Casey  (was: Allan Ramirez)

For review/edits

> Create comprehensive profiles documentation
> ---
>
>  Key: MNG-2000
>  URL: http://jira.codehaus.org/browse/MNG-2000
>  Project: Maven 2
> Type: Task

>   Components: Documentation: Guides
> Reporter: John Casey
> Assignee: John Casey
> Priority: Critical
>  Fix For: documentation

>
> Original Estimate: 16 hours
>Time Spent: 1 day
> Remaining: 0 minutes
>
> This document should draw from the mailing list, FAQ wiki, MNGFAQ jira 
> project (on codehaus), existing site documentation, project source code, and 
> any IRC conversations necessary.
> It should include:
> * How can I tell which profiles are in effect during a build?
> * What are the different types of profile? Where is each defined?
> * Which areas of a POM can be customized by each type of profile? Why?
> - settings-defined and profiles.xml-defined only modify properties, 
> repositories, and pluginRepositories. This is necessary to preserve the 
> portability of the pom as much as possible, since these two locations are not 
> installed/deployed to the repository system.
> * How can a profile be triggered? How does this vary according to the type of 
> profile being used?
> * Profiles are not inherited, but their effects are, because they are applied 
> to the POM before it's used for inheritance. This means a parent POM will 
> have its profiles triggered and applied before it is used to calculate the 
> inherited values for the current POM. Please include this in the 
> documentation as well.
> There's probably more, but I can't think of it off the top of my head. We 
> need to make this another one of those definitive documents for POM 
> configuration.

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


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

[jira] Closed: (MNG-1996) Enhance "Guide to Configuring Plug-ins" to include effects of configuration inside/outside executions section

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-1996?page=all ]
 
Allan Ramirez closed MNG-1996:
--

Resolution: Fixed

Applied Patch with small modification.. Thanks

> Enhance "Guide to Configuring Plug-ins" to include effects of configuration 
> inside/outside executions section
> -
>
>  Key: MNG-1996
>  URL: http://jira.codehaus.org/browse/MNG-1996
>  Project: Maven 2
> Type: Task

>   Components: Documentation: Guides
>     Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation
>  Attachments: MNG-1996.patch
>
>
> we need to add a section or two to the Guide to Configuring Plug-ins 
> (http://maven.apache.org/guides/mini/guide-configuring-plugins.html) which 
> will describe what happens when you configure a plugin at the 
>  level, and how that differs from the configuration 
> put in .
> In particular, what will happen if the plugin is called directly from the 
> command-line in each scenario? What about when the plugin is executed as part 
> of a phase in the lifecycle? What if there are multiple executions, bound to 
> different phases?

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


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

[jira] Closed: (MNG-1778) Guide to sun jars points jca to javax.jca but is not in ibiblio

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-1778?page=all ]
 
Allan Ramirez closed MNG-1778:
--

Resolution: Fixed

Applied Patch.. Thanks 

> Guide to sun jars points jca to javax.jca but is not in ibiblio
> ---
>
>  Key: MNG-1778
>  URL: http://jira.codehaus.org/browse/MNG-1778
>  Project: Maven 2
> Type: Bug

>   Components: Documentation: Guides
> Versions: 2.0
> Reporter: Edwin Punzalan
> Assignee: Edwin Punzalan
>  Fix For: documentation
>  Attachments: MNG-1778-maven-site.patch
>
>
> According to carlos, it should be javax.resource:connector... will attach a 
> patch in a while.

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


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

[jira] Closed: (MNG-1953) src/main/webapp should be added to "Introduction to the Standard Directory Layout" page

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-1953?page=all ]
 
Allan Ramirez closed MNG-1953:
--

Resolution: Fixed

Applied. Thanks

> src/main/webapp should be added to "Introduction to the Standard Directory 
> Layout" page
> ---
>
>  Key: MNG-1953
>  URL: http://jira.codehaus.org/browse/MNG-1953
>  Project: Maven 2
> Type: Bug

>   Components: Documentation: Introductions
> Reporter: Stephen Duncan Jr
> Assignee: Allan Ramirez
> Priority: Minor
>  Fix For: documentation
>  Attachments: MNG-1953-documentation-introductions.patch
>
>
> "Introduction to the Standard Directory Layout" at 
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>  should add an entry for src/main/webapp as the standard for web app sources.

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


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

[jira] Closed: (MNG-2047) doc. "Philosophy of Maven": Typo

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-2047?page=all ]
 
Allan Ramirez closed MNG-2047:
--

Resolution: Fixed

Sure thing :)

> doc. "Philosophy of Maven": Typo
> 
>
>  Key: MNG-2047
>  URL: http://jira.codehaus.org/browse/MNG-2047
>  Project: Maven 2
> Type: Bug

>   Components: Documentation: Guides
> Versions: 2.0.2
> Reporter: Rainer Wasserfuhr
> Assignee: Allan Ramirez
> Priority: Trivial
>  Fix For: documentation

>
>
> http://svn.apache.org/viewcvs.cgi/maven/site/trunk/src/site/apt/background/?rev=375610
> typo: "resuability" -> "reusability"

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


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

[jira] Closed: (MNG-2000) Create comprehensive profiles documentation

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-2000?page=all ]
 
Allan Ramirez closed MNG-2000:
--

Resolution: Fixed

Modified in svn

> Create comprehensive profiles documentation
> ---
>
>  Key: MNG-2000
>  URL: http://jira.codehaus.org/browse/MNG-2000
>  Project: Maven 2
> Type: Task

>   Components: Documentation: Guides
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation

>
> Original Estimate: 16 hours
>Time Spent: 1 day
> Remaining: 0 minutes
>
> This document should draw from the mailing list, FAQ wiki, MNGFAQ jira 
> project (on codehaus), existing site documentation, project source code, and 
> any IRC conversations necessary.
> It should include:
> * How can I tell which profiles are in effect during a build?
> * What are the different types of profile? Where is each defined?
> * Which areas of a POM can be customized by each type of profile? Why?
> - settings-defined and profiles.xml-defined only modify properties, 
> repositories, and pluginRepositories. This is necessary to preserve the 
> portability of the pom as much as possible, since these two locations are not 
> installed/deployed to the repository system.
> * How can a profile be triggered? How does this vary according to the type of 
> profile being used?
> * Profiles are not inherited, but their effects are, because they are applied 
> to the POM before it's used for inheritance. This means a parent POM will 
> have its profiles triggered and applied before it is used to calculate the 
> inherited values for the current POM. Please include this in the 
> documentation as well.
> There's probably more, but I can't think of it off the top of my head. We 
> need to make this another one of those definitive documents for POM 
> configuration.

-- 
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-2000) Create comprehensive profiles documentation

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-2000:
---

Remaining Estimate: 16 hours
 Original Estimate: 16 hours

> Create comprehensive profiles documentation
> ---
>
>  Key: MNG-2000
>  URL: http://jira.codehaus.org/browse/MNG-2000
>  Project: Maven 2
> Type: Task

>   Components: Documentation: Guides
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation

>
> Original Estimate: 16 hours
> Remaining: 16 hours
>
> This document should draw from the mailing list, FAQ wiki, MNGFAQ jira 
> project (on codehaus), existing site documentation, project source code, and 
> any IRC conversations necessary.
> It should include:
> * How can I tell which profiles are in effect during a build?
> * What are the different types of profile? Where is each defined?
> * Which areas of a POM can be customized by each type of profile? Why?
> - settings-defined and profiles.xml-defined only modify properties, 
> repositories, and pluginRepositories. This is necessary to preserve the 
> portability of the pom as much as possible, since these two locations are not 
> installed/deployed to the repository system.
> * How can a profile be triggered? How does this vary according to the type of 
> profile being used?
> * Profiles are not inherited, but their effects are, because they are applied 
> to the POM before it's used for inheritance. This means a parent POM will 
> have its profiles triggered and applied before it is used to calculate the 
> inherited values for the current POM. Please include this in the 
> documentation as well.
> There's probably more, but I can't think of it off the top of my head. We 
> need to make this another one of those definitive documents for POM 
> configuration.

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


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

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

[Allan Ramirez (JIRA)]

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

Resolution: Fixed

Added to SVN

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

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

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


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

[jira] Commented: (MDEPLOY-19) Ability to deploy-file as classifier

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_57814 ] 

Allan Ramirez commented on MDEPLOY-19:
--

It is not considered as a patch.

> Ability to deploy-file as classifier
> 
>
>  Key: MDEPLOY-19
>  URL: http://jira.codehaus.org/browse/MDEPLOY-19
>  Project: Maven 2.x Deploy Plugin
> Type: New Feature

> Versions: 2.1
>  Environment: xp
> Reporter: Dan Tran
>  Attachments: MDEPLOY19.diff
>
>
> deploy-file currently does not support this option

-- 
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: (MDEPLOY-19) Ability to deploy-file as classifier

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_57724 ] 

Allan Ramirez commented on MDEPLOY-19:
--

Hi Jerome,

Could you make another copy of that diff file, I think It is broken. Thanks

Allan

> Ability to deploy-file as classifier
> 
>
>  Key: MDEPLOY-19
>  URL: http://jira.codehaus.org/browse/MDEPLOY-19
>  Project: Maven 2.x Deploy Plugin
> Type: New Feature

> Versions: 2.1
>  Environment: xp
> Reporter: Dan Tran
>  Attachments: MDEPLOY19.diff
>
>
> deploy-file currently does not support this option

-- 
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: (MDEPLOY-23) deploy:file favors parent groupId over the child's one

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-23?page=all ]
 
Allan Ramirez closed MDEPLOY-23:


Resolution: Fixed

Applied patch. Thanks

> deploy:file favors parent groupId over the child's one
> --
>
>  Key: MDEPLOY-23
>  URL: http://jira.codehaus.org/browse/MDEPLOY-23
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.2
> Reporter: Jerome Lacoste
> Assignee: Allan Ramirez
> Priority: Critical
>  Attachments: MDEPLOY23.diff, fix.diff
>
> Original Estimate: 0 minutes
> Remaining: 0 minutes
>
> Fix attached.

-- 
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-1984) document optional dependencies and dependency exclusions

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: guide-optional-and-exclusions.apt

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

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

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: dependency-D.apt

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

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

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


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

[jira] Closed: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MDEPLOY-21?page=all ]
 
Allan Ramirez closed MDEPLOY-21:


 Assign To: Allan Ramirez
Resolution: Fixed

Fixed in SVN. I added the validation if there is no protocol provided for the 
url.

> Deploying an artifact from the local directory failed if the associated pom 
> file is not renamed
> ---
>
>  Key: MDEPLOY-21
>  URL: http://jira.codehaus.org/browse/MDEPLOY-21
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.0
>  Environment: PowerBook G4, Mac OS X 10.4.4, J2SDK1.5, Maven 2.0.2
> Reporter: Romain Rouvoy
> Assignee: Allan Ramirez

>
>
> mvn deploy:deploy-file -Dfile=fractal-2.0.1.jar - DpomFile=fractal-2.0.1.pom 
> -Durl=... -DrepositoryId=objectweb-release
> These files have been previously successfully copied to my local repository 
> using a mvn install:install-file command. I execute the deploy command from 
> the local repository.
> But I obdtain the following error:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO]
> --
> --
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
> --
> --
> [INFO] [deploy:deploy-file]
> Uploading: scp://forge.objectweb.org/var/lib/gforge/chroot/home/
> groups/maven/htdocs/maven2/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.jar
> 11K uploaded
> [INFO] Retrieving previous metadata from objectweb-release [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] Error installing artifact's metadata: Error installing
> metadata: Error rewriting POM
> /Users/rouvoy/.m2/repository/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.pom (No such file or directory) [INFO]
> --
> --
> [INFO] For more information, run Maven with the -e switch [INFO]
> --
> --
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Fri Jan 20 17:09:51 CET 2006 [INFO] Final Memory: 3M/5M 
> [INFO]
> --
> --
> And my local pom file has been deleted by the mvn command :'-(
> In fact I can not use the default pom file generated by install-file to 
> deploy. I need to rename it before deploying ... otherwise the rewriting of 
> the pom file will failed :-(

-- 
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: (MDEPLOY-21) Deploying an artifact from the local directory failed if the associated pom file is not renamed

[Allan Ramirez (JIRA)]

[ http://jira.codehaus.org/browse/MDEPLOY-21?page=comments#action_57095 ] 

Allan Ramirez commented on MDEPLOY-21:
--

Did you execute your command with the url parameter as "..." or you just hide 
your real url? I can only replicate the issue when there is no protocol 
provided in the url parameter.

> Deploying an artifact from the local directory failed if the associated pom 
> file is not renamed
> ---
>
>  Key: MDEPLOY-21
>  URL: http://jira.codehaus.org/browse/MDEPLOY-21
>  Project: Maven 2.x Deploy Plugin
> Type: Bug

> Versions: 2.0
>  Environment: PowerBook G4, Mac OS X 10.4.4, J2SDK1.5, Maven 2.0.2
> Reporter: Romain Rouvoy

>
>
> mvn deploy:deploy-file -Dfile=fractal-2.0.1.jar - DpomFile=fractal-2.0.1.pom 
> -Durl=... -DrepositoryId=objectweb-release
> These files have been previously successfully copied to my local repository 
> using a mvn install:install-file command. I execute the deploy command from 
> the local repository.
> But I obdtain the following error:
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [INFO]
> --
> --
> [INFO] Building Maven Default Project
> [INFO]task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO]
> --
> --
> [INFO] [deploy:deploy-file]
> Uploading: scp://forge.objectweb.org/var/lib/gforge/chroot/home/
> groups/maven/htdocs/maven2/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.jar
> 11K uploaded
> [INFO] Retrieving previous metadata from objectweb-release [INFO]
> --
> --
> [ERROR] BUILD ERROR
> [INFO]
> --
> --
> [INFO] Error installing artifact's metadata: Error installing
> metadata: Error rewriting POM
> /Users/rouvoy/.m2/repository/org/objectweb/fractal/fractal/2.0.1/
> fractal-2.0.1.pom (No such file or directory) [INFO]
> --
> --
> [INFO] For more information, run Maven with the -e switch [INFO]
> --
> --
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Fri Jan 20 17:09:51 CET 2006 [INFO] Final Memory: 3M/5M 
> [INFO]
> --
> --
> And my local pom file has been deleted by the mvn command :'-(
> In fact I can not use the default pom file generated by install-file to 
> deploy. I need to rename it before deploying ... otherwise the rewriting of 
> the pom file will failed :-(

-- 
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-1984) document optional dependencies and dependency exclusions

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: dependency-C.apt

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

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

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


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

[jira] Closed: (MNG-804) maven.jar.override usage in m2

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-804?page=all ]
 
Allan Ramirez closed MNG-804:
-

Resolution: Fixed

> maven.jar.override usage in m2
> --
>
>  Key: MNG-804
>  URL: http://jira.codehaus.org/browse/MNG-804
>  Project: Maven 2
> Type: Sub-task

>   Components: documentation - general
> Reporter: Natalie Burdick
> Assignee: Allan Ramirez
> Priority: Minor
>  Fix For: documentation
>  Attachments: m1-m2-changes (revised).txt, m1-m2-changes-b.apt, 
> m1-m2-changes-c.apt, m1-m2-changes.JPG, m1-m2-changes.apt
>
>
> refer to:
> http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL 
> PROTECTED]
> to document that unlike m1, m2 no longer allow jar overrides via the 
> maven.jar.override property

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


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

[jira] Closed: (MNG-1301) Document test inclusions and exclusions using the surefire plugin

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-1301?page=all ]
 
Allan Ramirez closed MNG-1301:
--

Resolution: Fixed

added in the SVN,  in howto.apt of surefire plugin. 

> Document test inclusions and exclusions using the surefire plugin
> -
>
>  Key: MNG-1301
>  URL: http://jira.codehaus.org/browse/MNG-1301
>  Project: Maven 2
> Type: Improvement

>   Components: documentation - general
> Reporter: Jason van Zyl
> Assignee: Allan Ramirez
>  Fix For: documentation

>
>


-- 
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-1984) document optional dependencies and dependency exclusions

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: (was: dependency-B.apt)

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

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

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: dependency-B.apt

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

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

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: dependency-B.apt

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

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

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Attachment: dependency.apt

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

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

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez commented on MNG-1984:


I cant seem to find enough info/questions regarding optional dependencies dated 
december 2005 to january 2006.

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

>   Components: documentation - guides
> Versions: 2.0.2
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation

>
> Original Estimate: 8 hours
>Time Spent: 5 hours
> Remaining: 3 hours
>
> assemble questions and problems from the users list, and create documentation 
> for managing bad POM dependency data using optional dependencies and 
> dependency exclusions.
> Document in depth how these two features work, and how they impact users of 
> POMs (even if the exclusion is in a transitive dependency).

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


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

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

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1984:
---

Remaining Estimate: 8 hours
 Original Estimate: 8 hours

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

>   Components: documentation - guides
> Versions: 2.0.2
> Reporter: John Casey
> Assignee: Allan Ramirez
> Priority: Critical
>  Fix For: documentation

>
> Original Estimate: 8 hours
> Remaining: 8 hours
>
> assemble questions and problems from the users list, and create documentation 
> for managing bad POM dependency data using optional dependencies and 
> dependency exclusions.
> Document in depth how these two features work, and how they impact users of 
> POMs (even if the exclusion is in a transitive dependency).

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


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

[jira] Updated: (MNG-1940) In maven-core-it, all integration test projects should have unique artifactId

[Allan Ramirez (JIRA)]

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

Allan Ramirez updated MNG-1940:
---

Attachment: MNG-1940.patch

> In maven-core-it, all integration test projects should have unique artifactId
> -
>
>  Key: MNG-1940
>  URL: http://jira.codehaus.org/browse/MNG-1940
>  Project: Maven 2
> Type: Bug

>   Components: integration tests
> Versions: 2.0.2
> Reporter: Allan Ramirez
>  Attachments: MNG-1940.patch
>
>
> The artifact Id of it0038 is the same with it0037 and it0052 to it0051

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


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

[jira] Created: (MNG-1940) In maven-core-it, all integration test projects should have unique artifactId

[Allan Ramirez (JIRA)]

In maven-core-it, all integration test projects should have unique artifactId
-

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

  Components: integration tests  
Versions: 2.0.2
Reporter: Allan Ramirez


The artifact Id of it0038 is the same with it0037 and it0052 to it0051

-- 
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] Deleted: (MNG-1631) FAQ: why there are no dependency properties in Maven 2

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-1631?page=all ]
 
Allan Ramirez deleted MNG-1631:
---


> FAQ: why there are no dependency properties in Maven 2
> --
>
>  Key: MNG-1631
>  URL: http://jira.codehaus.org/browse/MNG-1631
>  Project: Maven 2
> Type: Task

> Reporter: Brett Porter

>
>
> They were removed because they aren't reliable in a transitive
> environment. It implies that the dependency knows something about the
> environment of the dependee, which is back to front. In most cases,
> granted, the value for war bundle will be the same for a particular
> dependency - but that relies on the dependency specifying it.
> In the end, we give control to the actual POM doing the building,
> trying to use sensible defaults that minimise what needs to be
> specified, and allowing the use of artifact filters in the
> configuration of plugins.

-- 
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] Moved: (MPH-8) rename to help plugin

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-8?page=all ]

Allan Ramirez moved MNG-1285 to MPH-8:
--

Fix Version: (was: 2.0.1)
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-8  (was: MNG-1285)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> rename to help plugin
> -
>
>  Key: MPH-8
>  URL: http://jira.codehaus.org/browse/MPH-8
>  Project: Maven 2.x Project Help Plugin
> Type: Task

> Reporter: Brett Porter
> Assignee: John Casey
>  Attachments: MNG-1285-maven-plugins.patch
>
>   Time Spent: 1 hour
>Remaining: 0 minutes
>


-- 
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] Moved: (MPH-6) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-6?page=all ]

Allan Ramirez moved MNG-1531 to MPH-6:
--

Fix Version: (was: 2.0.3)
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-6  (was: MNG-1531)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> add a report mojo to create a an effective pom and effective settings report 
> (to be used in site generation)
> 
>
>  Key: MPH-6
>  URL: http://jira.codehaus.org/browse/MPH-6
>  Project: Maven 2.x Project Help Plugin
> Type: New Feature

> Reporter: John Allen

>
>
> add a report mojo so that we can include the effective pom and effective 
> settings in a project's site 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] Moved: (MPH-4) add mojo to projecthelp to describe supported plugin parameter expressions

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-4?page=all ]

Allan Ramirez moved MNG-1077 to MPH-4:
--

Version: (was: 2.0-beta-2)
Fix Version: (was: 2.0.3)
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-4  (was: MNG-1077)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> add mojo to projecthelp to describe supported plugin parameter expressions
> --
>
>  Key: MPH-4
>  URL: http://jira.codehaus.org/browse/MPH-4
>  Project: Maven 2.x Project Help Plugin
> Type: New Feature

> Reporter: John Casey

>
>
> People wanting to develop mojos need some help determining what plugin 
> parameter expressions Maven will support. The projecthelp plugin would be a 
> good place for this type of mojo, which would simply read the plugin 
> parameter documentation used to diagnose plugin configuration errors 
> (paramdoc files), and do some simple pattern matching on the expressions 
> before outputting information about expressions and how to affect their 
> values, not to mention descriptions of what they do.
> This will depend on more complete paramdoc information.

-- 
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] Moved: (MPH-3) NPE in describe mojo goal when plugin=install

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-3?page=all ]

Allan Ramirez moved MNG-1080 to MPH-3:
--

Fix Version: (was: 2.0 (RC))
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-3  (was: MNG-1080)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> NPE in describe mojo goal when plugin=install
> -
>
>  Key: MPH-3
>  URL: http://jira.codehaus.org/browse/MPH-3
>  Project: Maven 2.x Project Help Plugin
> Type: Bug

> Reporter: Brett Porter
> Assignee: John Casey

>
> Original Estimate: 2 hours
>Time Spent: 1 hour
> Remaining: 0 minutes
>
> not sure if the plugin name is correct syntax (I tried a prefix), but the 
> error handling could be improved :)

-- 
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] Moved: (MPH-7) document projecthelp plugin classes/parameters

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-7?page=all ]

Allan Ramirez moved MNG-1082 to MPH-7:
--

Fix Version: (was: 2.0 (RC))
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-7  (was: MNG-1082)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> document projecthelp plugin classes/parameters
> --
>
>  Key: MPH-7
>  URL: http://jira.codehaus.org/browse/MPH-7
>  Project: Maven 2.x Project Help Plugin
> Type: Task

> Reporter: Brett Porter
> Assignee: John Casey

>
> Original Estimate: 2 hours
>Time Spent: 10 minutes
> Remaining: 0 minutes
>


-- 
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] Moved: (MPH-5) add describe mojo to projecthelp plugin

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-5?page=all ]

Allan Ramirez moved MNG-698 to MPH-5:
-

Version: (was: 2.0-alpha-3)
Fix Version: (was: 2.0 (RC))
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-5  (was: MNG-698)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> add describe mojo to projecthelp plugin
> ---
>
>  Key: MPH-5
>  URL: http://jira.codehaus.org/browse/MPH-5
>  Project: Maven 2.x Project Help Plugin
> Type: New Feature

> Reporter: John Casey
> Assignee: John Casey
> Priority: Minor

>
> Original Estimate: 2 hours
>Time Spent: 2 hours
> Remaining: 0 minutes
>
> these will replace the -g functionality of maven 1.x

-- 
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] Moved: (MPH-2) projecthelp plugin always returns TODO! for each mojo

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-2?page=all ]

Allan Ramirez moved MNG-1236 to MPH-2:
--

  Version: (was: 2.0 (RC))
Component: (was: maven-projecthelp-plugin)
 Workflow: jira  (was: Maven)
  Key: MPH-2  (was: MNG-1236)
  Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> projecthelp plugin always returns TODO! for each mojo
> -
>
>  Key: MPH-2
>  URL: http://jira.codehaus.org/browse/MPH-2
>  Project: Maven 2.x Project Help Plugin
> Type: Bug

>  Environment: winxp sp2, java 1.4.2_08
> Reporter: Brian Bonner
> Assignee: Brett Porter

>
>
> Running:
> m2 -e projecthelp:describe 
> -Dplugin=org.apache.maven.plugins:maven-eclipse-plugin
> returns:
> Group Id:  org.apache.maven.plugins
> Artifact Id: maven-eclipse-plugin
> Version: 2.0-beta-2
> Goal Prefix: eclipse
> Mojos:
> ---
> TODO!
> ---
> TODO!
> ---
> TODO!
> ---
> No matter what plugin I try, I always get TODO!
> I think this is a bug.

-- 
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] Moved: (MPH-1) describe mojo should not require a project

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPH-1?page=all ]

Allan Ramirez moved MNG-1081 to MPH-1:
--

Fix Version: (was: 2.0 (RC))
  Component: (was: maven-projecthelp-plugin)
   Workflow: jira  (was: Maven)
Key: MPH-1  (was: MNG-1081)
Project: Maven 2.x Project Help Plugin  (was: Maven 2)

> describe mojo should not require a project
> --
>
>  Key: MPH-1
>  URL: http://jira.codehaus.org/browse/MPH-1
>  Project: Maven 2.x Project Help Plugin
> Type: Bug

> Reporter: Brett Porter
> Assignee: John Casey

>
> Original Estimate: 1 hour
>Time Spent: 10 minutes
> Remaining: 0 minutes
>


-- 
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] Moved: (MPIR-8) project-team goal incorrectly formats developers'

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-8?page=all ]

Allan Ramirez moved MNG-1040 to MPIR-8:
---

Version: (was: 2.0-beta-2)
Fix Version: (was: 2.0 (RC))
  Component: (was: maven-project-info-reports-plugin)
   Workflow: jira  (was: Maven)
Key: MPIR-8  (was: MNG-1040)
Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> project-team goal incorrectly formats developers' 
> ---
>
>  Key: MPIR-8
>  URL: http://jira.codehaus.org/browse/MPIR-8
>  Project: Maven 2.x Project Info Reports Plugin
> Type: Bug

> Reporter: Matthew Beermann
> Assignee: Johnny R. Ruiz III
> Priority: Minor
>  Attachments: MNG-1040-maven-reporting.patch
>
>
> If you have a developer with the attribute "http://foo", on the 
> project team page this will come out looking like "{http://foo, http://foo}";.
> While I'm here, I'm not sure what the column "Actual Time (GMT)" is for - 
> it's going to be the same for all developers, after all. I think you meant 
> "Local TIme"; as in, flexed off their timezone.

-- 
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] Moved: (MPIR-16) Create link in subscribe/unscribe field if field starts with http:// in mailinglist report.

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-16?page=all ]

Allan Ramirez moved MNG-1431 to MPIR-16:


Version: (was: 2.0)
Fix Version: (was: 2.0.1)
  Component: (was: maven-project-info-reports-plugin)
   Workflow: jira  (was: Maven)
Key: MPIR-16  (was: MNG-1431)
Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> Create link in subscribe/unscribe field if field starts with http:// in 
> mailinglist report.
> ---
>
>  Key: MPIR-16
>  URL: http://jira.codehaus.org/browse/MPIR-16
>  Project: Maven 2.x Project Info Reports Plugin
> Type: Improvement

>  Environment: OpenSuSE 10, Maven 2.0, maven-project-info-reports-plugin 
> 2.0--beta-3
> Reporter: Rohnny Moland (JIRA)
> Assignee: Brett Porter
> Priority: Minor

>
>
> When pom subscribe/unsubscribe field starts with http:// , should create a 
> link and hide the full url in the mailing list report. 
> Not all subscription systems can use a direct mailto: address in those fields.

-- 
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] Moved: (MPIR-11) improved dependency report

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-11?page=all ]

Allan Ramirez moved MNG-1013 to MPIR-11:


Component: (was: maven-project-info-reports-plugin)
 Workflow: jira  (was: Maven)
  Key: MPIR-11  (was: MNG-1013)
  Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> improved dependency report
> --
>
>  Key: MPIR-11
>  URL: http://jira.codehaus.org/browse/MPIR-11
>  Project: Maven 2.x Project Info Reports Plugin
> Type: New Feature

> Reporter: Brett Porter

>
>
> it'd be great to have a dependencies report based on the listener in 
> maven-artifact:
> - report on scopes
> - report on versions considered by not selected
> - show structure of dependency tree
> I think it would be best to tabulate each dependencies info in multiple rows 
> at the bottom (as the description currently gets squashed into the table), 
> and present a tree at the top that links to it. (indented lists here, we have 
> a graphing tool we can use later).
> we should make some of this configurable, of course.

-- 
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] Moved: (MPIR-9) Project Mailing Lists reports bad URL, post and archive

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-9?page=all ]

Allan Ramirez moved MNG-1046 to MPIR-9:
---

Version: (was: 2.0-beta-2)
Fix Version: (was: 2.0 (RC))
  Component: (was: maven-project-info-reports-plugin)
   Workflow: jira  (was: Maven)
Key: MPIR-9  (was: MNG-1046)
Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> Project Mailing Lists reports bad URL, post and archive
> ---
>
>  Key: MPIR-9
>  URL: http://jira.codehaus.org/browse/MPIR-9
>  Project: Maven 2.x Project Info Reports Plugin
> Type: Bug

> Reporter: David DIDIER
> Assignee: Vincent Siveton
>  Attachments: maven-reporting-impl.diff
>
>
> Here is my pom :
> 
> 
> NDD Development
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> generates (with site:site) in "mailing lists" the array :
> NDD Development  |||  {Subscribe, [EMAIL PROTECTED]  |||  {Unsubscribe, 
> [EMAIL PROTECTED]  |||  {Post, }  |||  {???UNKWOWN???, }

-- 
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] Moved: (MPIR-15) the issue management report should handle more issue management systems

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-15?page=all ]

Allan Ramirez moved MNG-1336 to MPIR-15:


Version: (was: 2.0 (RC))
Fix Version: (was: 2.0.1)
  Component: (was: maven-project-info-reports-plugin)
   Workflow: jira  (was: Maven)
Key: MPIR-15  (was: MNG-1336)
Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> the issue management report should handle more issue management systems
> ---
>
>  Key: MPIR-15
>  URL: http://jira.codehaus.org/browse/MPIR-15
>  Project: Maven 2.x Project Info Reports Plugin
> Type: Improvement

>  Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
>  Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this 
> report to reflect that choice. Before I get into that though, one tiny 
> grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management 
> System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven 
> was not grabbing the system I specified in the pom and making the proper 
> substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at 
> all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should 
> one need to specify a valid system in code, and then in the properties file? 
> And then make my customized version of the plugin available to the team? Just 
> so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a 
> change in the POM, so if Mantis can simply be added to the list of valid IM 
> systems: 
> report.issuetracking.mantis.intro=This project uses {Mantis, 
> http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.

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


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

[jira] Moved: (MPIR-14) Accept absolute license files as well as file URLs [PATCH]

[Allan Ramirez (JIRA)]

 [ http://jira.codehaus.org/browse/MPIR-14?page=all ]

Allan Ramirez moved MNG-1321 to MPIR-14:


Version: (was: 2.0)
Fix Version: (was: 2.0.1)
  Component: (was: maven-project-info-reports-plugin)
   Workflow: jira  (was: Maven)
Key: MPIR-14  (was: MNG-1321)
Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2)

> Accept absolute license files as well as file URLs [PATCH]
> --
>
>  Key: MPIR-14
>  URL: http://jira.codehaus.org/browse/MPIR-14
>  Project: Maven 2.x Project Info Reports Plugin
> Type: Improvement

> Reporter: Bruno Essmann
> Assignee: Brett Porter
> Priority: Trivial
>  Attachments: maven-project-info-reports-plugin-license-report.patch
>
>
> Included is a small patch that works around the inability of UrlValidator 
> (jakarta-commons/validator) to accept URLs without valid authority (i.e. 
> file:// URLs).
> The patch also allows definition of absolute file license file locations 
> (i.e. when using locations such as ${basedir}/license.txt).
> I'm still looking for a way to define a license file location relative to the 
> topmost project, i.e. when using the following structure:
>   TopProj
>   |_ license.txt
>   |_ SubProj
>  |_ SubSubProj
> I'd like to define the license file in the POM of the TopProj in such a way 
> that it is a) relative to the location of TopProj and b) valid for all sub 
> projects, including SubProj and SubSubProj.
> I presume I could achieve this using a variable (similar to ${basedir}) that 
> I'm not aware of at the moment...

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