[jira] Created: (MCHECKSTYLE-123) remove use of Serviceable (to be compatible wih maven 3.x)
remove use of Serviceable (to be compatible wih maven 3.x) -- Key: MCHECKSTYLE-123 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-123 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Olivier Lamy Priority: Critical the current version use interface Serviceable which won't work with maven 3.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
[jira] Updated: (MCHECKSTYLE-123) remove use of Serviceable (to be compatible wih maven 3.x)
[ http://jira.codehaus.org/browse/MCHECKSTYLE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCHECKSTYLE-123: - Assignee: Olivier Lamy Fix Version/s: 2.4 > remove use of Serviceable (to be compatible wih maven 3.x) > -- > > Key: MCHECKSTYLE-123 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-123 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Critical > Fix For: 2.4 > > > the current version use interface Serviceable which won't work with maven 3.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
[jira] Commented: (MCHECKSTYLE-123) remove use of Serviceable (to be compatible wih maven 3.x)
[ http://jira.codehaus.org/browse/MCHECKSTYLE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189991#action_189991 ] Olivier Lamy commented on MCHECKSTYLE-123: -- reverting MCHECKSTYLE-101 ? In fact I don't really understand why people attached checkstyle check in a normal build. IMHO this must be only in a dedicated reporting profile. > remove use of Serviceable (to be compatible wih maven 3.x) > -- > > Key: MCHECKSTYLE-123 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-123 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Critical > Fix For: 2.4 > > > the current version use interface Serviceable which won't work with maven 3.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
[jira] Updated: (MSHADE-54) not respected when generating the package
[ http://jira.codehaus.org/browse/MSHADE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MSHADE-54: Testcase included: yes Fix Version/s: 1.2.2 > not respected when generating the package > - > > Key: MSHADE-54 > URL: http://jira.codehaus.org/browse/MSHADE-54 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.2.1 >Reporter: Sean McRae >Assignee: Mark Struberg > Fix For: 1.2.2 > > > Specifying the final name of the package is not respected by the plugin, > instead the default name for the package is always used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-54) not respected when generating the package
[ http://jira.codehaus.org/browse/MSHADE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MSHADE-54. --- Resolution: Fixed > not respected when generating the package > - > > Key: MSHADE-54 > URL: http://jira.codehaus.org/browse/MSHADE-54 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.2.1 >Reporter: Sean McRae >Assignee: Mark Struberg > Fix For: 1.2.2 > > > Specifying the final name of the package is not respected by the plugin, > instead the default name for the package is always used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-255) Cannot suppress reports
[
http://jira.codehaus.org/browse/MJAVADOC-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-255.
Resolution: Not A Bug
To exclude all reports you need to use:
{noformat}
{noformat}
> Cannot suppress reports
> ---
>
> Key: MJAVADOC-255
> URL: http://jira.codehaus.org/browse/MJAVADOC-255
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Benson Margulies
>
> I wanted to suppress javadoc aggregation for mvn site:site.
> So, I tried
>
> No effect. it goes ahead and runs the aggregate report. help:effectivePom
> does not show the empty reportSets element.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-123) remove use of Serviceable (to be compatible wih maven 3.x)
[ http://jira.codehaus.org/browse/MCHECKSTYLE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190007#action_190007 ] Olivier Lamy commented on MCHECKSTYLE-123: -- The question is : Restoring this in plexus ? or reverting MCHECKSTYLE-101 ? > remove use of Serviceable (to be compatible wih maven 3.x) > -- > > Key: MCHECKSTYLE-123 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-123 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Critical > Fix For: 2.4 > > > the current version use interface Serviceable which won't work with maven 3.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
[jira] Created: (MCHANGES-176) Make ConversionTool available in the VelocityContext
Make ConversionTool available in the VelocityContext Key: MCHANGES-176 URL: http://jira.codehaus.org/browse/MCHANGES-176 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.1 Reporter: Antonin Stefanutti It would be very useful to have access to an instance of ConversionTool in the Velocity templace so that one can convert String to List for example. See : http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/generic/ConversionTool.html In my special case, I want to pass a list of packages as a comma-separated String in the announceParameters as configuration of the changes plugin and convert this comma-separated String as a List in the Velocity template to iterate over to send e-mails containing the packages I deployed in addition to the changes report. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANT-60) Generated "package" task for EAR/WAR is missing transitive dependencies
Generated "package" task for EAR/WAR is missing transitive dependencies
---
Key: MANT-60
URL: http://jira.codehaus.org/browse/MANT-60
Project: Maven 2.x Ant Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Benjamin Bentmann
The generated {{maven-build.xml}} only copies direct dependencies of the
project to the {{lib}} directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANT-60) Generated "package" task for EAR/WAR is missing transitive dependencies
[
http://jira.codehaus.org/browse/MANT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MANT-60.
-
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.2.1
Fixed in [r811830|http://svn.apache.org/viewvc?view=rev&revision=811830].
> Generated "package" task for EAR/WAR is missing transitive dependencies
> ---
>
> Key: MANT-60
> URL: http://jira.codehaus.org/browse/MANT-60
> Project: Maven 2.x Ant Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 2.2.1
>
>
> The generated {{maven-build.xml}} only copies direct dependencies of the
> project to the {{lib}} directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
We need an element - to TRULY exclude classes from resulting jar --- Key: MSHADE-62 URL: http://jira.codehaus.org/browse/MSHADE-62 Project: Maven 2.x Shade Plugin Issue Type: New Feature Reporter: Paul Hammant 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch. I want to totally exclude some packages or classes from the resulting jar. As in leave them out, or kill them, or don't have them at all in the resulting jar. Neither as their original class name nor their potential new class name. Perforce has an 'obliterate' concept, given exclude is already used in shade, maybe obliterate is the new element for this essential feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
[ http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190010#action_190010 ] Benjamin Bentmann commented on MSHADE-62: - Paul, can you be more specific why the "fine-grained control of which classes from the selected dependencies are included" from the example [Selecting Contents for Uber JAR|http://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html] does not work? > We need an element - to TRULY exclude classes from resulting > jar > --- > > Key: MSHADE-62 > URL: http://jira.codehaus.org/browse/MSHADE-62 > Project: Maven 2.x Shade Plugin > Issue Type: New Feature >Reporter: Paul Hammant > > 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch. > I want to totally exclude some packages or classes from the resulting jar. > As in leave them out, or kill them, or don't have them at all in the > resulting jar. Neither as their original class name nor their potential new > class name. > Perforce has an 'obliterate' concept, given exclude is already used in shade, > maybe obliterate is the new element for this essential feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
[
http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190011#action_190011
]
Paul Hammant commented on MSHADE-62:
I thought I could exclude classes that would never be used by PicoContainer
like so :-
{noformat}
org.apache.maven.plugins
maven-shade-plugin
1.2.1
package
shade
picocontainer
javax.annotation:jsr250-api
com.thoughtworks.paranamer
org.picocontainer.paranamer
com.thoughtworks.paranamer.JavadocParanamer
{noformat}
Unfortunately, exclude does not mean exclude it means "don't re-package" .
{noformat}
ph-mbp:container paul$ jar -tvf target/picocontainer-2.9-SNAPSHOT.jar | grep
paranamer
0 Sun Sep 06 11:06:50 CDT 2009 org/picocontainer/paranamer/
3150 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/AdaptiveParanamer.class
809 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer$1.class
7803 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer$ClassReader.class
2977 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer$MethodCollector.class
4662 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer$Type.class
6262 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer$TypeCollector.class
6198 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/BytecodeReadingParanamer.class
2535 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/CachingParanamer.class
5336 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/DefaultParanamer.class
0 Sun Sep 06 11:06:50 CDT 2009 com/thoughtworks/paranamer/
10630 Sun Sep 06 11:06:50 CDT 2009
com/thoughtworks/paranamer/JavadocParanamer.class
1432 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/NullParanamer.class
964 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/ParameterNamesNotFoundException.class
762 Sun Sep 06 11:06:50 CDT 2009 org/picocontainer/paranamer/Paranamer.class
549 Sun Sep 06 11:06:50 CDT 2009
org/picocontainer/paranamer/ParanamerConstants.class
0 Sun Sep 06 11:06:50 CDT 2009 META-INF/maven/com.thoughtworks.paranamer/
0 Sun Sep 06 11:06:50 CDT 2009
META-INF/maven/com.thoughtworks.paranamer/paranamer/
1290 Sun Sep 06 11:06:50 CDT 2009
META-INF/maven/com.thoughtworks.paranamer/paranamer/pom.xml
127 Sun Sep 06 11:06:50 CDT 2009
META-INF/maven/com.thoughtworks.paranamer/paranamer/pom.properties
{noformat}
Specifically, its these two lines that I'd rather were left out completely (not
in the jar, not in the jar in re-packaged form) ..
{noformat}
0 Sun Sep 06 11:06:50 CDT 2009 com/thoughtworks/paranamer/
10630 Sun Sep 06 11:06:50 CDT 2009
com/thoughtworks/paranamer/JavadocParanamer.class
{noformat}
Also, I'd rather do without the pom.xml stuff for paranamer too, but that's a
different issue.
- Paul
> We need an element - to TRULY exclude classes from resulting
> jar
> ---
>
> Key: MSHADE-62
> URL: http://jira.codehaus.org/browse/MSHADE-62
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
>Reporter: Paul Hammant
>
> 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch.
> I want to totally exclude some packages or classes from the resulting jar.
> As in leave them out, or kill them, or don't have them at all in the
> resulting jar. Neither as their original class name nor their potential new
> class name.
> Perforce has an 'obliterate' concept, given exclude is already used in shade,
> maybe obliterate is the new element for this essential feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
[
http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190012#action_190012
]
Benjamin Bentmann commented on MSHADE-62:
-
Paul, did you try the example I pointed at, e.g. something like
{code:xml}
org.apache.maven.plugins
maven-shade-plugin
1.2.1
package
shade
com.thoughtworks.paranamer:paranamer
com/thoughtworks/paranamer/**
{code}
> We need an element - to TRULY exclude classes from resulting
> jar
> ---
>
> Key: MSHADE-62
> URL: http://jira.codehaus.org/browse/MSHADE-62
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
>Reporter: Paul Hammant
>
> 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch.
> I want to totally exclude some packages or classes from the resulting jar.
> As in leave them out, or kill them, or don't have them at all in the
> resulting jar. Neither as their original class name nor their potential new
> class name.
> Perforce has an 'obliterate' concept, given exclude is already used in shade,
> maybe obliterate is the new element for this essential feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-123) remove use of Serviceable (to be compatible wih maven 3.x)
[
http://jira.codehaus.org/browse/MCHECKSTYLE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190015#action_190015
]
Benjamin Bentmann commented on MCHECKSTYLE-123:
---
The Velocity component appears to be used only for generation of RSS however
the generation of RSS is surely not needed for the {{checkstyle:check}} goal.
I.e. the issue reported in MCHECKSTYLE-101 could be addressed by some
refactoring of the plugin, that would need to aim at removing {...@execute
goal="checkstyle"}} from the {{check}} goal.
> remove use of Serviceable (to be compatible wih maven 3.x)
> --
>
> Key: MCHECKSTYLE-123
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-123
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Critical
> Fix For: 2.4
>
>
> the current version use interface Serviceable which won't work with maven 3.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
[jira] Created: (MNG-4339) Add a --show command line option that list all possible targets
Add a --show command line option that list all possible targets Key: MNG-4339 URL: http://jira.codehaus.org/browse/MNG-4339 Project: Maven 2 Issue Type: Improvement Components: Command Line Reporter: Christian Hammers Priority: Minor Hello It would be nice if maven had a "--show" command line option that could be used to figure out which individual targets can be called: $ mvn --show The following goals can be called directly: compile deploy site : :javadoc :doxia jaxws :wsgen :wsimport ant :run release :prepare :perform This would help newbies like me to figure out how I can just recreate the apidocs wihout haven to run "mvn site" and wait for the whole unit test to complete etc bye, -christian- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
[
http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190014#action_190014
]
Paul Hammant commented on MSHADE-62:
You're right Ben, the following was what I wanted ...
{noformat}
org.apache.maven.plugins
maven-shade-plugin
1.2.1
package
shade
picocontainer
com.thoughtworks.paranamer:paranamer
com/thoughtworks/paranamer/Javadoc*
com.thoughtworks.paranamer
org.picocontainer.paranamer
{noformat}
This bug can be closed - sorry for wasting your time
> We need an element - to TRULY exclude classes from resulting
> jar
> ---
>
> Key: MSHADE-62
> URL: http://jira.codehaus.org/browse/MSHADE-62
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
>Reporter: Paul Hammant
>
> 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch.
> I want to totally exclude some packages or classes from the resulting jar.
> As in leave them out, or kill them, or don't have them at all in the
> resulting jar. Neither as their original class name nor their potential new
> class name.
> Perforce has an 'obliterate' concept, given exclude is already used in shade,
> maybe obliterate is the new element for this essential feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHADE-62) We need an element - to TRULY exclude classes from resulting jar
[ http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MSHADE-62. --- Assignee: Benjamin Bentmann Resolution: Won't Fix > We need an element - to TRULY exclude classes from resulting > jar > --- > > Key: MSHADE-62 > URL: http://jira.codehaus.org/browse/MSHADE-62 > Project: Maven 2.x Shade Plugin > Issue Type: New Feature >Reporter: Paul Hammant >Assignee: Benjamin Bentmann > > 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch. > I want to totally exclude some packages or classes from the resulting jar. > As in leave them out, or kill them, or don't have them at all in the > resulting jar. Neither as their original class name nor their potential new > class name. > Perforce has an 'obliterate' concept, given exclude is already used in shade, > maybe obliterate is the new element for this essential feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-367) Exception while parsing .apt (probably due to snippet macro)
Exception while parsing .apt (probably due to snippet macro) Key: DOXIA-367 URL: http://jira.codehaus.org/browse/DOXIA-367 Project: Maven Doxia Issue Type: Bug Components: Maven plugin Reporter: Christian Hammers Hello I got the following: $ mvn site ... [INFO] Generating "Issue Tracking" report. [INFO] Generating "Surefire Report" report. [WARNING] Unable to locate Test Source XRef to link to - DISABLED [INFO] Generating "Project License" report. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] 1 [INFO] [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.apt.AptParser$MacroBlock.traverse(AptParser.java:2689) at org.apache.maven.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:358) at org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:304) at org.apache.maven.doxia.module.apt.AptParser.traverseBody(AptParser.java:255) at org.apache.maven.doxia.module.apt.AptParser.parse(AptParser.java:181) at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:376) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:52) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) 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:597) 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) I guess it's due to my first attempt to write an .apt file. Still, it would be nice if the error message could be slightly improved... The offending examples.apt is below. As file:// is not further documented I tried to try out which path is expected. -- Apache log4php Examples -- -- -- Apache Log4php Examples The source contains ready to run examples for most appenders and major concepts in the src/ex
[jira] Closed: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
[
http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-257.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.6.1
I created an IT and fixed the pb as discuss here in
[r811825|http://svn.apache.org/viewvc?rev=811825&view=rev], snap deployed.
> maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
> --
>
> Key: MJAVADOC-257
> URL: http://jira.codehaus.org/browse/MJAVADOC-257
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Apache Maven 2.2.0
> Java version: 1.6.0_11
>Reporter: jcrouvi
>Assignee: Vincent Siveton
> Fix For: 2.6.1
>
> Attachments: MJAVADOC-257.diff
>
>
> Using maven-javadoc-plugin Version 2.5 or 2.6 for a project of type
> *maven-plugin* leads to the following error message,
> even if the aggregation is not set:
> {{Error extracting plugin descriptor: 'Goal: ... already exists in the plugin
> descriptor ...}}
> *Using maven-javadoc-plugin Version 2.2 solves this problem.*
> Structure of the project:
> {code:none}
> [INFO] Reactor build order:
> [INFO] Service
> [INFO] Service: Common Dependencies
> [INFO] Service: API
> [INFO] Service: Test Fixture
> [INFO] Service: Implementation
> [INFO] Service: DI
> [INFO] Service: auth-maven-plugin
> [INFO] Service: Config
> [INFO] Service: Interceptors
> [INFO] Service: Client Module
> [INFO] Service: Web Components
> [INFO] Service: Example
> {code}
> Configuration in {{service/pom.xml}}
> {code:xml}
>
> full-site
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
>
> analyze-report
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.5
>
> true
> protected
>
> http://java.sun.com/javase/6/docs/api/
> http://java.sun.com/javaee/5/docs/api/
>
>
>
> ...
> {code}
> Also see: [http://jira.codehaus.org/browse/MJAVADOC-224]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems
[ http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190050#action_190050 ] Petter Måhlén commented on SCM-444: --- The way we use it at work, we do have a central repository so for us I would say pushing (of + to the current branch only) is desirable or at least ok. Off the top of my head, I can't think of any real issues with not pushing - we could just do that manually. Even for more truly distributed source management, though, I would say that the nature of making a release involves publishing the artifacts, so it would make some sort of sense to also publish the source code (in a better way than a jarball Maven artifact). But I guess that part of it could be seen as a separate thing - if somebody wants the tag that corresponds to the released code, you just have to pull it from whoever happened to make that release. So from my perspective, Brett's suggestion about not pushing sounds fine. On another note, I would hate to work on a combination of Maven + completely distributed source. :) Handling SNAPSHOT releases would be hell, or at least, you couldn't do it using a shared repo. Even without a central repo for snapshots, conflicts where my project A version depends on a project B 1.2-SNAPSHOT that is completely different from somebody else's project B 1.2-SNAPSHOT are likely and hard to troubleshoot. I guess some addition to Maven's snapshot concept would be required for that to work. > Git provider does 'git push' during 'mvn release:prepare' which causes > unwanted problems > > > Key: SCM-444 > URL: http://jira.codehaus.org/browse/SCM-444 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.1 >Reporter: Petter Måhlén >Priority: Minor > > When doing 'mvn release:prepare' with a Git provider, a 'git push' command is > executed. This is not ideal because the push command can fail or push things > from the local repository that are not needed/wanted in the remote > repository. Some examples are: > 1. The local repository has two branches: master (tracking origin/master) and > dummy (tracking origin/dummy). The release is being made on the master > branch, and the dummy and origin/dummy branches have diverged. Running > 'release:prepare' causes a 'git push', which will succeed for the master > branch (assuming that the release preparation has been made correctly) and > fail for the dummy branch (the two branches have diverged and need to be > merged or rebased). The release preparation aborts and the directory is left > in a somewhat inconsistent state where manual cleaning up is needed (removing > pom.xml.next files, changing versions to -SNAPSHOT, etc.) > 2. The local repository has two branches: master (tracking origin/master) and > localtest (not in the origin repository). The localtest branch shouldn't be > published because it is just used for some temporary testing and doesn't even > work. It will be pushed during 'release:prepare'. > Suggested behaviour: use 'git push origin :', > or even better, query for which remote repository to push to (found in > .git/config) and which branch to push from and to. For me, it would be great > to have a 'confirm push' before doing it so as to keep things clean, but > maybe that is quite complex. -- 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
