[jira] Closed: (MWAR-132) dependencies with same artifactId and != groupId result is conflicts in WEB-INF/lib
[ http://jira.codehaus.org/browse/MWAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MWAR-132. Resolution: Duplicate > dependencies with same artifactId and != groupId result is conflicts in > WEB-INF/lib > --- > > Key: MWAR-132 > URL: http://jira.codehaus.org/browse/MWAR-132 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: nicolas de loof >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.1 > > > as discussed on dev mailing list (groupId/artifactId mapping for Eclipse > jars) the War plugin may fail creating the webapp WEB-INF/lib if multiple > dependencies use the same artifactId, but different groupIds. > This is not the case now as many libs are created with maven1 "Id" in mind, > for example all apache commons having "commons-" as artifactId prefix. In > future, some libs may start using simplier names and rely more on maven > groupId. For such case, the war plugin MAY provide and option to add groupIds > to artifacts copied to WEB-INF/lib. -- 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: (DOXIA-208) standardize link/anchor handling: remove usage of StructureSinkUtils
[ http://jira.codehaus.org/browse/DOXIA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-208: Fix Version/s: 1.0-beta-2 Component/s: Module - Docbook Simple Module - Apt Core Summary: standardize link/anchor handling: remove usage of StructureSinkUtils (was: change the default link from an anchor to a relative page in the apt format) The two methods in StructureSink are apt-specific but they are used in HtmlTools, XhtmlBaseSink, DocbookSink and XdocSink. Eg the isExternalLink() method returns true for links that start with "./" but this is only necessary for apt, see my comment above. > standardize link/anchor handling: remove usage of StructureSinkUtils > > > Key: DOXIA-208 > URL: http://jira.codehaus.org/browse/DOXIA-208 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Module - Apt, Module - Docbook Simple, Module - > Xhtml >Affects Versions: 1.0-alpha-10 >Reporter: Andrew Williams > Fix For: 1.0-beta-2 > > > To be inline with wikis and other formats the APT link "MyLink" should be a > relative link whereas "#MyLink" would link to an anchor. > This is a deviation from the apt format, but would remove confusion for new > users and those working on supporting multiple formats. > Edit: this is an issue with the XHTML sink, not the apt parser - anything > link "MyLink" will be spat out as "#MyLink" -- 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: (DOXIA-56) clean up doxia api and code
[ http://jira.codehaus.org/browse/DOXIA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-56. -- Assignee: Lukas Theussl Resolution: Fixed I grepped through the code and only found "throws Exception"s in tests, not in the main code. Closing as too generic, please indicate any specific issues if I missed anything. > clean up doxia api and code > --- > > Key: DOXIA-56 > URL: http://jira.codehaus.org/browse/DOXIA-56 > Project: Maven Doxia > Issue Type: Task > Components: Core >Reporter: Brett Porter >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > there is a lot of "throws Exception" and uncertainty in the API. It needs a > clean up before 1.0 -- 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: (DOXIA-144) Review signature methods
[ http://jira.codehaus.org/browse/DOXIA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123983 ] Lukas Theussl commented on DOXIA-144: - Vincent, can you specify what methods you had in mind exactly? > Review signature methods > > > Key: DOXIA-144 > URL: http://jira.codehaus.org/browse/DOXIA-144 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Modules >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Siveton > Fix For: 1.0-beta-1 > > > Severals methods are public instead of private -- 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: (DOXIA-59) Doxia creates files with inconsistent new lines
[ http://jira.codehaus.org/browse/DOXIA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-59. -- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: (was: 1.0) 1.0-beta-2 Added Napoleon's snippet to AbstractSink. For now only XhtmlBaseSink uses it, which is probably the most important one, but in principle every sink should filter its text output through this method. > Doxia creates files with inconsistent new lines > --- > > Key: DOXIA-59 > URL: http://jira.codehaus.org/browse/DOXIA-59 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Carlos Sanchez >Assignee: Lukas Theussl > Fix For: 1.0-beta-2 > > Attachments: DOXIA-59-nramirez.patch > > > It uses \n instead of System.getProperty( line.separator ); -- 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: (MSITE-301) Schedule and release maven-doxia-tools 1.0
[ http://jira.codehaus.org/browse/MSITE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-301: Fix Version/s: 2.0-beta-7 > Schedule and release maven-doxia-tools 1.0 > -- > > Key: MSITE-301 > URL: http://jira.codehaus.org/browse/MSITE-301 > Project: Maven 2.x Site Plugin > Issue Type: Task > Components: doxia integration >Reporter: Lukas Theussl > Fix For: 2.0-beta-7 > > -- 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: (MPA-57) migrate all Maven projects to the Basic Issue Creation Scheme in JIRA
[ http://jira.codehaus.org/browse/MPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MPA-57. -- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2008-q1 I've changed this for all Maven projects, except maven-proxy and those who's name begins with "Maven 1" . > migrate all Maven projects to the Basic Issue Creation Scheme in JIRA > - > > Key: MPA-57 > URL: http://jira.codehaus.org/browse/MPA-57 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Affects Versions: 2006-q3 >Reporter: Brett Porter >Assignee: Dennis Lundberg > Fix For: 2008-q1 > > -- 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: (MSITE-301) Schedule and release maven-doxia-tools 1.0
Schedule and release maven-doxia-tools 1.0 -- Key: MSITE-301 URL: http://jira.codehaus.org/browse/MSITE-301 Project: Maven 2.x Site Plugin Issue Type: Task Components: doxia integration Reporter: Lukas Theussl Fix For: 2.0-beta-7 -- 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: (MPA-103) Freshmeat entry of maven is not up to date
[ http://jira.codehaus.org/browse/MPA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPA-103: Fix Version/s: (was: 2007-q2) > Freshmeat entry of maven is not up to date > -- > > Key: MPA-103 > URL: http://jira.codehaus.org/browse/MPA-103 > Project: Maven Project Administration > Issue Type: Wish >Reporter: Raphaël Piéroni >Priority: Trivial > > The maven freshmeat is not up to date : > http://freshmeat.net/projects/maven > Please take any action. > extract from irc > 18:07 < rafale> Hi, I talk about maven to a friend last WE, he tried the > freshmeat site and we both see that the maven page on freshmeat wasn't > updated since maven was at jakarta/turbine/maven. > 18:07 < rafale> should i raise a jira for that ? > 18:10 < jvanzyl> we should just erase that page -- 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: (MSITE-261) Local Parent POM not found if specifies a directory
[
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-261.
---
Assignee: Lukas Theussl
Resolution: Fixed
Patch applied in maven-doxia-tools, thanks!
> Local Parent POM not found if specifies a directory
> --
>
> Key: MSITE-261
> URL: http://jira.codehaus.org/browse/MSITE-261
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>Reporter: Benjamin Bentmann
>Assignee: Lukas Theussl
>Priority: Minor
> Fix For: 2.0-beta-7
>
> Attachments: site-parent-pom.patch, site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the element
> in a module POM to locate the parent POM, e.g.{code:xml}
> ...
> ../parent
> {code}will properly find the parent POM in "../parent/pom.xml".
> However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a
> different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is
> not already included somewhere in the Maven core (where is belongs IMHO).
--
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-8) The generated "get-deps" target uses the "get" target - would be better to use Maven Ant Tasks
[ http://jira.codehaus.org/browse/MANT-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MANT-8. -- Resolution: Won't Fix I agree with Robert. The Ant Plugin should create a build.xml that requires only Ant to run. > The generated "get-deps" target uses the "get" target - would be better to > use Maven Ant Tasks > -- > > Key: MANT-8 > URL: http://jira.codehaus.org/browse/MANT-8 > Project: Maven 2.x Ant Plugin > Issue Type: Improvement >Reporter: Matt Raible > > It seems like it would be much better (and cleaner) to use Maven's own Ant > Tasks rather than the task. The task takes a lot longer to run > and often spits out useless logging to the end user. -- 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: (DOXIA-59) Doxia creates files with inconsistent new lines
[ http://jira.codehaus.org/browse/DOXIA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-59: --- Fix Version/s: (was: 1.0-beta-2) 1.0-beta-1 > Doxia creates files with inconsistent new lines > --- > > Key: DOXIA-59 > URL: http://jira.codehaus.org/browse/DOXIA-59 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Carlos Sanchez >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-59-nramirez.patch > > > It uses \n instead of System.getProperty( line.separator ); -- 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: (MNG-3397) [RFC] change the POM to use attributes
[ http://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123993 ] nicolas de loof commented on MNG-3397: -- I tried to enable the "flat" modello format for collections, to change : xx xx xx .. to the more convice : xx but this didn't worked : the modello generated parser still search the "executions" in XML stream. Not investigated more yet on this. > [RFC] change the POM to use attributes > -- > > Key: MNG-3397 > URL: http://jira.codehaus.org/browse/MNG-3397 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 2.0.8 >Reporter: Brett Porter > -- 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: (MWAR-132) dependencies with same artifactId and != groupId result is conflicts in WEB-INF/lib
[ http://jira.codehaus.org/browse/MWAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MWAR-132: - Fix Version/s: (was: 2.1) 2.1-alpha-2 > dependencies with same artifactId and != groupId result is conflicts in > WEB-INF/lib > --- > > Key: MWAR-132 > URL: http://jira.codehaus.org/browse/MWAR-132 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: nicolas de loof >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.1-alpha-2 > > > as discussed on dev mailing list (groupId/artifactId mapping for Eclipse > jars) the War plugin may fail creating the webapp WEB-INF/lib if multiple > dependencies use the same artifactId, but different groupIds. > This is not the case now as many libs are created with maven1 "Id" in mind, > for example all apache commons having "commons-" as artifactId prefix. In > future, some libs may start using simplier names and rely more on maven > groupId. For such case, the war plugin MAY provide and option to add groupIds > to artifacts copied to WEB-INF/lib. -- 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: (MWAR-143) War Overlays and resources filtering
[
http://jira.codehaus.org/browse/MWAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MWAR-143:
-
Affects Version/s: (was: 2.1-alpha-2)
(was: 2.0.2)
> War Overlays and resources filtering
>
>
> Key: MWAR-143
> URL: http://jira.codehaus.org/browse/MWAR-143
> Project: Maven 2.x War Plugin
> Issue Type: Improvement
>Affects Versions: 2.1-alpha-1
> Environment: maven 2.0.7
>Reporter: Rémy Sanlaville
>Assignee: Olivier Lamy
> Fix For: 2.1-alpha-2
>
> Attachments: reactor-war-overlay-filter.zip, war-overlays-filter.zip
>
>
> I have multiple web applications who share common resources.
> So I use the [war overlays
> mechanism|http://maven.apache.org/plugins/maven-war-plugin/overlays.html].
> All seems ok except for common properties files that I want to filter when
> creating the web applications.
> For instance (see war-overlays-filter.zip in attachment):
> My war-common war
> war-common.war
>|-- WEB-INF\classes\filter.properties (which contains for instance
> title.main=Prototype ${pom.name})
> I would like to create the war-filter-overlay web application
> war-filter-overlay.war
>|-- WEB-INF\classes\filter.properties (which contains the filtering
> property title.main=Prototype war-filter-overlay)
> [As suggested by Olivier
> Lamy|http://www.nabble.com/War-Overlays-and-resources-filtering-td15272334s177.html#a15272334]
> it tried this configuration
> {code:xml}
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1-alpha-2-SNAPSHOT
>
>
>
>
>
> debug.war
> common-overlay
>
> true
>
>
>
>
> {code}
> Unfortunately it's not working.
--
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: (DOXIA-144) Review signature methods
[ http://jira.codehaus.org/browse/DOXIA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123996 ] Vincent Siveton commented on DOXIA-144: --- Some public methods in the following classes need to be review: - AbstractParser - AbstractXmlSink Also in specific modules: - AptParser - ConfluenceParser - FoAggregateSink - FoSink Maybe others > Review signature methods > > > Key: DOXIA-144 > URL: http://jira.codehaus.org/browse/DOXIA-144 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Modules >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Siveton > Fix For: 1.0-beta-1 > > > Severals methods are public instead of private -- 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-216) Linkcheck broken
Linkcheck broken Key: DOXIA-216 URL: http://jira.codehaus.org/browse/DOXIA-216 Project: Maven Doxia Issue Type: Bug Components: Doxia Tools Reporter: Lukas Theussl Priority: Critical Checking the current Doxia site I noticed that we have an invalid link: the page references/apt-format.html (in paragraph 'Paragraph') has a link to #Document_structure which does not exist. However, linkcheck does not report this. -- 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: (DOXIA-138) Review and clarify the APT guide
[ http://jira.codehaus.org/browse/DOXIA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-138. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: (was: 1.0) 1.0-beta-1 Documented the points above on the doxia site. > Review and clarify the APT guide > > > Key: DOXIA-138 > URL: http://jira.codehaus.org/browse/DOXIA-138 > Project: Maven Doxia > Issue Type: Task > Components: Documentation, Module - Apt >Affects Versions: 1.0-alpha-8 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > Our current apt guide is a copy of > http://www.xmlmind.com/_aptconvert/docs/userguide2.html, but there are > several issues that need clarification, eg > * case sensitivity and white space handling in anchors > * anchors for section titles > * figure handling, esp extensions > * tables: is the first line always a header row? > Some of these depend on how things are going to be implemented. > We also decided to remove the apt guide at > http://maven.apache.org/guides/mini/guide-apt-format.html and only keep the > one on the doxia site. -- 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: (MWAR-137) Site's Overlays section doesn't reflect the correct configuration for zip overlays
[ http://jira.codehaus.org/browse/MWAR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MWAR-137. Resolution: Fixed Fix Version/s: 2.1-alpha-2 Fixed in HEAD. > Site's Overlays section doesn't reflect the correct configuration for zip > overlays > -- > > Key: MWAR-137 > URL: http://jira.codehaus.org/browse/MWAR-137 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-1 >Reporter: Marcio Silva >Assignee: Stephane Nicoll >Priority: Minor > Fix For: 2.1-alpha-2 > > > The section in overlays.apt that describes zip overlay configuration omits > the needed zip element required by the final implementation of > zip overlays. > The file was edited as part of the zip overlay implementation issue MWAR-104 > , but the implementation was changed to require the type element (rev 584631) > after the overlay documentation was edited (rev 582805). For non-war overlay > types, the type element must be present. -- 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-218) AbstractSink needs to have a default protected constructor
AbstractSink needs to have a default protected constructor
---
Key: DOXIA-218
URL: http://jira.codehaus.org/browse/DOXIA-218
Project: Maven Doxia
Issue Type: Improvement
Affects Versions: 1.0-alpha-10
Reporter: Vincent Siveton
Something like:
{noformat}
private Writer writer;
protected AbstractSink( Writer writer )
{
this.writer = writer;
}
{noformat}
Maybe adding another one with OutputStream.
--
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-219) Bump to new release of plexus-utils
Bump to new release of plexus-utils --- Key: DOXIA-219 URL: http://jira.codehaus.org/browse/DOXIA-219 Project: Maven Doxia Issue Type: Task Components: Decoration Model Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton Fix For: 1.0-beta-1 -- 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: (DOXIA-219) Bump to new release of plexus-utils
[ http://jira.codehaus.org/browse/DOXIA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-219: -- Fix Version/s: 1.0-beta-1 > Bump to new release of plexus-utils > --- > > Key: DOXIA-219 > URL: http://jira.codehaus.org/browse/DOXIA-219 > Project: Maven Doxia > Issue Type: Task > Components: Decoration Model >Affects Versions: 1.0-alpha-10 >Reporter: Vincent Siveton > Fix For: 1.0-beta-1 > > -- 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: (DOXIA-218) AbstractSink needs to have a default protected constructor
[
http://jira.codehaus.org/browse/DOXIA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated DOXIA-218:
--
Component/s: Core
> AbstractSink needs to have a default protected constructor
> ---
>
> Key: DOXIA-218
> URL: http://jira.codehaus.org/browse/DOXIA-218
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.0-alpha-10
>Reporter: Vincent Siveton
>
> Something like:
> {noformat}
> private Writer writer;
> protected AbstractSink( Writer writer )
> {
> this.writer = writer;
> }
> {noformat}
> Maybe adding another one with OutputStream.
--
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: (DOXIA-99) Figures require extension in APT and they should not
[ http://jira.codehaus.org/browse/DOXIA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-99. -- Assignee: Lukas Theussl (was: Jason van Zyl) Resolution: Won't Fix Documented on doxia site. > Figures require extension in APT and they should not > > > Key: DOXIA-99 > URL: http://jira.codehaus.org/browse/DOXIA-99 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Apt >Affects Versions: 1.0-alpha-5, 1.0-alpha-6, 1.0-alpha-7, 1.0-alpha-8 >Reporter: Greg Luck >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > Figures require extension in APT and they should not. > For example, http://ehcache.sourceforge.net/nameandlogo.html shows a broken > image. The APT for this page is: > [images/ehcache_logo] > Now, if I change it to [images/ehcache_logo.gif] it works. However this > breaks aptconvert. The reason is that it is illegal in APT to specify the > figure extension. I use aptconvert to create a pdf and single HTML page. -- 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-217) Make default impl classes
Make default impl classes - Key: DOXIA-217 URL: http://jira.codehaus.org/browse/DOXIA-217 Project: Maven Doxia Issue Type: Improvement Components: Module - Confluence, Module - Rtf, Module - Twiki Affects Versions: 1.0-alpha-10 Reporter: Vincent Siveton Fix For: 1.0-beta-1 doxia-module-rtf doxia-module-confluence doxia-module-twiki -- 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: (DOXIA-217) Make default impl classes
[ http://jira.codehaus.org/browse/DOXIA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-217: -- Fix Version/s: 1.0-beta-1 > Make default impl classes > - > > Key: DOXIA-217 > URL: http://jira.codehaus.org/browse/DOXIA-217 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Confluence, Module - Rtf, Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Vincent Siveton > Fix For: 1.0-beta-1 > > > doxia-module-rtf > doxia-module-confluence > doxia-module-twiki -- 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: (DOXIA-135) Handle SSI in xdoc
[
http://jira.codehaus.org/browse/DOXIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated DOXIA-135:
--
Fix Version/s: (was: 1.0)
1.0-beta-1
> Handle SSI in xdoc
> --
>
> Key: DOXIA-135
> URL: http://jira.codehaus.org/browse/DOXIA-135
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - Xdoc
>Affects Versions: 1.0-alpha-8
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> SSI (server side includes) are eliminated from xdoc.
> In ASF, we could use it to include ads:
> {noformat}
>
> {noformat}
--
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: (DOXIA-119) How to deal with encoding and documentation
[ http://jira.codehaus.org/browse/DOXIA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-119: -- Fix Version/s: (was: 1.0) 1.0-beta-1 > How to deal with encoding and documentation > --- > > Key: DOXIA-119 > URL: http://jira.codehaus.org/browse/DOXIA-119 > Project: Maven Doxia > Issue Type: Task > Components: Core, Documentation >Reporter: Jason van Zyl > Fix For: 1.0-beta-1 > > > Show how people can use different encodings with APT. This can probably be > added to the guide-site.apt. -- 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: (MCHANGES-102) Fix case-insensitive string handling
[ http://jira.codehaus.org/browse/MCHANGES-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-102. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0 Patch applied in r628327. Thanks! > Fix case-insensitive string handling > > > Key: MCHANGES-102 > URL: http://jira.codehaus.org/browse/MCHANGES-102 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.0-beta-3 >Reporter: Benjamin Bentmann >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0 > > Attachments: case-insensitive-strings.patch > > > Please see [Common > Bugs|http://www.nabble.com/Common-Bugs-to14783703s177.html#a14931921] for an > explanation. -- 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: (MCHANGES-101) Consider changing log outputs to debug
[
http://jira.codehaus.org/browse/MCHANGES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-101.
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0
Patch applied with the following modifications.
{code}
[INFO] Downloading from JIRA at:
http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=11216
&statusIds=6&resolutionIds=1&sorter/field=fixVersions&sorter/order=DESC&tempMax=100&reset=true&decorator=none
> This is an aggregated string resulting from all configurations made. I prefer
> to keep it at info level.
[INFO] The JIRA Report will contain issues only for the current version.
> This configuration can conflict with other configurations, so I want it to be
> shown to the user.
{code}
> Consider changing log outputs to debug
> --
>
> Key: MCHANGES-101
> URL: http://jira.codehaus.org/browse/MCHANGES-101
> Project: Maven 2.x Changes Plugin
> Issue Type: Wish
> Components: jira-report
>Affects Versions: 2.0-beta-3
>Reporter: Benjamin Bentmann
>Assignee: Dennis Lundberg
>Priority: Trivial
> Fix For: 2.0
>
> Attachments: jira-debug-logs.patch
>
>
> Log levels are quite controversial but I would like to see some less output
> from the report generation on the INFO level. Currently, one gets:
> {noformat}
> [INFO] Generating "JIRA Report" report.
> [INFO] JIRA lives at: http://jira.codehaus.org
> > I know, that where it was configured in the POM
> [INFO] The JIRA URL http://jira.codehaus.org/browse/MJAVACC doesn't include a
> pid, trying to extract it from JIRA.
> > Well, I know this as well
> [INFO] Successfully reached JIRA.
> > Hopefully
> [INFO] Downloading from JIRA at:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=11216
> &statusIds=6&resolutionIds=1&sorter/field=fixVersions&sorter/order=DESC&tempMax=100&reset=true&decorator=none
> > Wow, that's a pretty URL to read
> [INFO] Downloading from JIRA was successful
> > I'm an optimist so I expected that. Better tell me things that suprise me.
> [INFO] The JIRA Report will contain issues only for the current version.
> > Cool, it's honoring my configuration again!
> {noformat}
> As my not so serious comments shall indicate, I consider most of the current
> INFO ouput quite uninteresting during a regular build. It either reports back
> the plugin configuration or the expected behavior. Therefore, I personally
> would be fine with just "Generating "JIRA Report" 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] Closed: (MCHANGES-103) Allow suffix "ASC" for sort columns
[
http://jira.codehaus.org/browse/MCHANGES-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-103.
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.0
Patch applied in r628332. Thanks!
I also added documentation for this in the mojo.
> Allow suffix "ASC" for sort columns
> ---
>
> Key: MCHANGES-103
> URL: http://jira.codehaus.org/browse/MCHANGES-103
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira-report
>Reporter: Benjamin Bentmann
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.0
>
> Attachments: asc-sorting.patch
>
>
> As a matter of consistency, it would be good if the plugin accepted the
> suffix "ASC" to denote ascending sorting as well. When somebody sees a plugin
> configuration like
> {code:xml}
> Key DESC
> {code}
> I argue most peoply would expect that "Key ASC" is a valid input, too.
--
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-64) Allow inclusion of javadoc source path in check
[ http://jira.codehaus.org/browse/MCHECKSTYLE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124007 ] Benjamin Bentmann commented on MCHECKSTYLE-64: -- bq. The package.html files in src/main/javadoc do get copied to the build output directory, don't they? No, these files are only copied to the report output directory. If they were copied to the build output directory, they would end up in the JAR which is not intended. > Allow inclusion of javadoc source path in check > --- > > Key: MCHECKSTYLE-64 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-64 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Johan Vanbockryck >Priority: Minor > > According to the documentation of the maven-javadoc-plugin, the Javadoc > resources (like package.html) should be placed in src/main/javadoc. This will > cause a checkstyle error for missing package.html files however when enabling > the PackageHtml module, since this directory is not included in the > checkstyle source path. > See also: http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html -- 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: (MCHECKSTYLE-86) Lock down encoding used to read source files
Lock down encoding used to read source files Key: MCHECKSTYLE-86 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-86 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Benjamin Bentmann Priority: Minor Attachments: fixed-charset.patch Since [version 3.5|http://checkstyle.sourceforge.net/releasenotes.html#Release%203.5], Checkstyle allows to configure the encoding used to read source files (somehow weird, they included this setting in the XML config which limits reusability among unrelated projects). Unless this is specified by the user via the [charset property|http://checkstyle.sourceforge.net/config.html#TreeWalker], it defaults to the system property "file.encoding". This makes the checks platform-dependent and possibly fail. For reproducible builds, the encoding should be locked down. -- 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: (MECLIPSE-388) Correct classpath ordering in .classpath
[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124006
]
Siarhei Dudzin commented on MECLIPSE-388:
-
I agree, forcing to maven 2.0.9 would be a bit extreme... What about having an
option or something like that (a disadvantage is that too many options isn't
nice)? That about performing sorting based on maven version (also not very nice
but no extra complexity in configuration for the end user)?
> Correct classpath ordering in .classpath
>
>
> Key: MECLIPSE-388
> URL: http://jira.codehaus.org/browse/MECLIPSE-388
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
>Affects Versions: 2.4
>Reporter: Siarhei Dudzin
>Priority: Critical
>
> Currently plugin sorts artifacts on its own (alphabetic order???) because the
> order of dependencies that comes from maven is not reliable (random?). This
> breaks tests that use JBoss Embedded which works under maven surefire plugin
> because it still puts dependencies that came first at the beginning of the
> classpath). Apparently not all classpath elements are put in random order. At
> least I get the first ones listed in dependencies also first in the classpath
> (can be seen as ${surefire.test.class.path} and in
> target/surefire-reports/TEST-TestSuite.xml).
> While there is not much we can do for maven eclipse plugin a solution is on
> the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
> revert back to the default classpath order.
> Can we somehow schedule this?
> Another question: is there anyway to put certain dependencies in the first
> place except for renaming them so that alphabetic order does the job?
--
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: (MWAR-144) Custom filter list does not work
[
http://jira.codehaus.org/browse/MWAR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124008
]
Trygve Laugstol commented on MWAR-144:
--
No, I haven't. If the latest SNAPSHOT fixes is, consider this a documentation
bug as it should be specified with a "since" description.
Also, if ${basedir} really is required (if it is a File[] array it isn't), that
is also a bug. All file references are *always* relative to the project itself.
> Custom filter list does not work
>
>
> Key: MWAR-144
> URL: http://jira.codehaus.org/browse/MWAR-144
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Trygve Laugstol
>Assignee: Olivier Lamy
> Fix For: 2.1-alpha-2
>
>
> When specifying filters on the plugin (not inside ) like this:
> {code}
>
>
> polopoly-resources/config_ptest
> WEB-INF/config
>
> ptest
> target/ptest-work
>
> src/main/filters/filter.ptest.properties
>
>
>
> src/main/resources
> WEB-INF/classes
> true
>
>
> {code}
> the list of filters is ignored. If I move the list to inside the
> they work as expected. The documentation explicitly say that this
> is possible under the section "Filtering webResources".
--
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: (MCHECKSTYLE-86) Lock down encoding used to read source files
[ http://jira.codehaus.org/browse/MCHECKSTYLE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-86. -- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.2 Patch applied in r628373. Thanks! > Lock down encoding used to read source files > > > Key: MCHECKSTYLE-86 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-86 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Benjamin Bentmann >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.2 > > Attachments: fixed-charset.patch > > > Since [version > 3.5|http://checkstyle.sourceforge.net/releasenotes.html#Release%203.5], > Checkstyle allows to configure the encoding used to read source files > (somehow weird, they included this setting in the XML config which limits > reusability among unrelated projects). Unless this is specified by the user > via the [charset > property|http://checkstyle.sourceforge.net/config.html#TreeWalker], it > defaults to the system property "file.encoding". This makes the checks > platform-dependent and possibly fail. For reproducible builds, the encoding > should be locked down. -- 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: (MCOMPILER-64) "mvn clean install" crashes with java.lang.OutOfMemoryError: PermGen space after update to java 1.6.0_04
[ http://jira.codehaus.org/browse/MCOMPILER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124010 ] Michael Semb Wever commented on MCOMPILER-64: - I get this too. Know of no workaround. > "mvn clean install" crashes with java.lang.OutOfMemoryError: PermGen space > after update to java 1.6.0_04 > > > Key: MCOMPILER-64 > URL: http://jira.codehaus.org/browse/MCOMPILER-64 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug > Environment: Maven version: 2.0.8 > Java version: 1.6.0_04 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Joern Huxhorn >Priority: Critical > > After upgrading to java 1.6.0_04 i can't build a big multi-module project > anymore. > java.exe keeps allocating more and more memory (ca. 260MB) until it crashes > with an error like the following: > Failure executing javac, but could not parse the error: > The system is out of resources. > Consult the following stack trace for details. > java.lang.OutOfMemoryError: PermGen space > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$000(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at > org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:56) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.javac.comp.Annotate.(Annotate.java:52) > at com.sun.tools.javac.comp.Annotate.instance(Annotate.java:36) > at com.sun.tools.javac.jvm.ClassReader.(ClassReader.java:215) > at com.sun.tools.javac.jvm.ClassReader.instance(ClassReader.java:168) > at com.sun.tools.javac.main.JavaCompiler.(JavaCompiler.java:293) > at > com.sun.tools.javac.main.JavaCompiler.instance(JavaCompiler.java:72) > at com.sun.tools.javac.main.Main.compile(Main.java:340) > at com.sun.tools.javac.main.Main.compile(Main.java:279) > at com.sun.tools.javac.main.Main.compile(Main.java:270) > at com.sun.tools.javac.Main.compile(Main.java:87) > 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.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420) > at > org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141) > at > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493) > at > org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > Executing the same command with this setup > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > works perfectly. java.exe allocates at most 110MB. > Increasing the PermGen space using -XX:MaxPermSize=512M didn't help, either... > This is probably a java regression introduced with j6u4 but it could also be > a problem in org.codehaus.plexus.compiler.javac.IsolatedClassLoader. > I didn't experience any other problems with the new java version, so far. -- 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: (SUREFIRE-459) Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4
Integration test using Jetty and JSP 2.1 fails after update to maven-surefire-plugin 2.4 Key: SUREFIRE-459 URL: http://jira.codehaus.org/browse/SUREFIRE-459 Project: Maven Surefire Issue Type: Bug Components: classloading, plugin Affects Versions: 2.4.1, 2.4 Environment: Maven 2.0.8, Windows XP Reporter: Nils-Helge Garli We have an integration test running in a Struts 2 sample application, and after the maven-surefire-plugin was updated from 2.3 to 2.4, the test is failing. There's an issue registered in the Struts 2 JIRA explaining the error: https://issues.apache.org/struts/browse/WW-2494 I have no idea what's causing the error, but I suspect it has something to do witn classloader configuration, as aparently no tld files are found inside the jar files on the classpath. It should be pretty easy to reproduce. Just checkout the Struts 2 code and run 'mvn test' on the portlet example application. -- 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: (MECLIPSE-332) mvn-eclipse-cache.properties is never filled
[ http://jira.codehaus.org/browse/MECLIPSE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124014 ] Arnaud Heritier commented on MECLIPSE-332: -- The 2.5 isn't yet released :-( But we deployed several snapshots on the dedicated repository. > mvn-eclipse-cache.properties is never filled > > > Key: MECLIPSE-332 > URL: http://jira.codehaus.org/browse/MECLIPSE-332 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Wouter de Vaal > Fix For: 2.5 > > > See summary, the file is writen, but no data is in it, resulting in very long > builds each time the eclipse update is needed. -- 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: (MCHANGELOG-80) support selecting of changes by revision-range for subversion
support selecting of changes by revision-range for subversion - Key: MCHANGELOG-80 URL: http://jira.codehaus.org/browse/MCHANGELOG-80 Project: Maven 2.x Changelog Plugin Issue Type: New Feature Reporter: Simon Kitching Currently, only selecting by-date is supported for Subversion. However subversion has a problem with date-selection in some cases. In particular, when CVS projects are imported into subversion, and the original commit date info is preserved during import, then all subversion select-by-date operations are broken for the repository. This is a known issue with subversion, and not likely to be fixed in the near future. The basic issue is that subversion maps a date to a revision-number by doing a binary-search across all its revisions, and assumes that the commit-date for revision N is before the commit-date for revision N+M. This is not true when external repos (CVS or other) are imported into subversion with original commit dates preserved. One example of a repository where this is a problem is *svn.apache.org*; all select-by-date is completely broken for the apache repo; always has been and will be until (if) a subversion release is made that has an additional "committed on" attribute for each commit, and changes made to svn to use an index on this property rather than its existing binary-search. It would therefore be *very* nice to be able to specify a subversion revision range, eg "from r10 to HEAD" as the input to the 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: (MPLUGIN-73) PluginXdocGenerator fails to decode javadoc inline tags
PluginXdocGenerator fails to decode javadoc inline tags
---
Key: MPLUGIN-73
URL: http://jira.codehaus.org/browse/MPLUGIN-73
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: API
Affects Versions: 2.3
Reporter: Benjamin Bentmann
Priority: Minor
Attachments: javadoc-inline-tags.patch
Javadoc descriptions may contain certain inline tags that javadoc expands into
HTML. For example, Javadoc 1.5 introduces [EMAIL PROTECTED] text}}} as a
superior notation to {{text}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-220) Fix project name for doxia-logging-api
Fix project name for doxia-logging-api -- Key: DOXIA-220 URL: http://jira.codehaus.org/browse/DOXIA-220 Project: Maven Doxia Issue Type: Task Reporter: Benjamin Bentmann Priority: Trivial Attachments: logging-api-project-name.patch Copy&Paste BTW, maybe create a component for this project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-220) Fix project name for doxia-logging-api
[ http://jira.codehaus.org/browse/DOXIA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIA-220: -- Component/s: Logging API > Fix project name for doxia-logging-api > -- > > Key: DOXIA-220 > URL: http://jira.codehaus.org/browse/DOXIA-220 > Project: Maven Doxia > Issue Type: Task > Components: Logging API >Reporter: Benjamin Bentmann >Priority: Trivial > Attachments: logging-api-project-name.patch > > > Copy&Paste > BTW, maybe create a component for this project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPLUGIN-74) Explicitly control layout of tables generated for parameters of mojo description
Explicitly control layout of tables generated for parameters of mojo description
Key: MPLUGIN-74
URL: http://jira.codehaus.org/browse/MPLUGIN-74
Project: Maven 2.x Plugin Tools
Issue Type: Task
Components: API
Affects Versions: 2.3
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: table-style.patch
The handling for the {{}} element in [commit 578469 to
doxia-module-xdoc|http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-xdoc/src/main/java/org/apache/maven/doxia/module/xdoc/XdocParser.java?r1=571451&r2=578469&pathrev=578469]
will cause a change for the current output of the PluginXdocGenerator (i.e.
table cells get centered instead of left aligned and a border will be
rendered). Updating the XDoc generator now should allow a smooth transition to
doxia 1.0-beta-1.
--
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: (MNG-3397) [RFC] change the POM to use attributes
[ http://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124017 ] Brett Porter commented on MNG-3397: --- what change did you make to the model to enable this? > [RFC] change the POM to use attributes > -- > > Key: MNG-3397 > URL: http://jira.codehaus.org/browse/MNG-3397 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 2.0.8 >Reporter: Brett Porter > -- 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-221) Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
---
Key: DOXIA-221
URL: http://jira.codehaus.org/browse/DOXIA-221
Project: Maven Doxia
Issue Type: Bug
Components: Module - Xdoc
Affects Versions: 1.0-beta-1
Reporter: Benjamin Bentmann
Attachments: cell-justify.patch
Attempt to render a multi column table using XDoc:
{noformat}
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.sink.XhtmlBaseSink.tableCell(XhtmlBaseSink.java:807)
at
org.apache.maven.doxia.sink.XhtmlBaseSink.tableCell(XhtmlBaseSink.java:780)
at
org.apache.maven.doxia.sink.XhtmlBaseSink.tableHeaderCell(XhtmlBaseSink.java:768)
at
org.apache.maven.doxia.parser.XhtmlBaseParser.baseStartTag(XhtmlBaseParser.java:300)
at
org.apache.maven.doxia.module.xdoc.XdocParser.handleStartTag(XdocParser.java:213)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:103)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:54)
at
org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:93)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:345)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:272)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:102)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:137)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
{noformat}
The XDocParser/XHtmlBaseParser calls sink.tableRows() always with a
single-element array. This is usually not enough to describe all columns of the
table individually. Hence, XHtmlBaseSink should be prepared to render a table
cell that does not have a corresponding cellJustif entry. The patch simply
repeats the justification of the last array element.
Last but not least, it might be worth to consider changing the default cell
alignment to left alignment to match the default behavior of HTML for table
body cells. Additionally, left-alignment seems to be the current behavior of
the xdoc module in the alpha branch.
--
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: (MDEP-145) Outputting dependency resolution/tree in a well known _machine readable_ output format
Outputting dependency resolution/tree in a well known _machine readable_ output
format
--
Key: MDEP-145
URL: http://jira.codehaus.org/browse/MDEP-145
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: resolve, tree
Affects Versions: 2.0
Reporter: Samuel Le Berrigaud
Assignee: Brian Fox
Currently (at least on trunk) one can output the dependencies in a file.
However the file output doesn't follow any specific format, except from being
the exact same output than on the console.
I would be nice to have an easily parse-able, format so that tools could
leverage the dependency resolution/tree. I am thinking for example of
continuous integration tools that could report on added/removed/updated
dependencies on modules.
The format could be xml, json or something else. I've been playing with the
current output to make it so that:
* the first line describes the current module for which dependency resolution
is done, formatted as such: {{:::}}
* every following line is a dependency (indented by 2 or more spaces),
formatted as such: {{}}
This already is easy to parse.
What do you think?
--
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: (WAGON-101) Allow use of streams for get, getIfNewer and put
Allow use of streams for get, getIfNewer and put Key: WAGON-101 URL: http://jira.codehaus.org/browse/WAGON-101 Project: wagon Issue Type: New Feature Components: wagon-provider-api Affects Versions: 1.0 Reporter: James William Dumay Allow the use of Streams with get, getIfNewer and put. -- 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: (WAGON-101) Allow use of streams for get, getIfNewer and put
[ http://jira.codehaus.org/browse/WAGON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay updated WAGON-101: -- Attachment: wagon-streaming.patch Patch includes testcases > Allow use of streams for get, getIfNewer and put > > > Key: WAGON-101 > URL: http://jira.codehaus.org/browse/WAGON-101 > Project: wagon > Issue Type: New Feature > Components: wagon-provider-api >Affects Versions: 1.0 >Reporter: James William Dumay > Attachments: wagon-streaming.patch > > > Allow the use of Streams with get, getIfNewer and put. -- 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: (DOXIA-220) Fix project name for doxia-logging-api
[ http://jira.codehaus.org/browse/DOXIA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-220. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Fixed thanks! I'm not sure about the need of a component, maybe open a specific issue or discuss on the dev list? > Fix project name for doxia-logging-api > -- > > Key: DOXIA-220 > URL: http://jira.codehaus.org/browse/DOXIA-220 > Project: Maven Doxia > Issue Type: Task > Components: Logging API >Reporter: Benjamin Bentmann >Assignee: Lukas Theussl >Priority: Trivial > Fix For: 1.0-beta-1 > > Attachments: logging-api-project-name.patch > > > Copy&Paste > BTW, maybe create a component for this project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-221) Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
[
http://jira.codehaus.org/browse/DOXIA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed DOXIA-221.
---
Assignee: Lukas Theussl
Resolution: Fixed
Fix Version/s: 1.0-beta-1
Fixed, thanks! Also switched to left default justification in XhtmlBaseParser.
> Fix ArrayIndexOutOfBoundsException in XhtmlBaseSink
> ---
>
> Key: DOXIA-221
> URL: http://jira.codehaus.org/browse/DOXIA-221
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
>Affects Versions: 1.0-beta-1
>Reporter: Benjamin Bentmann
>Assignee: Lukas Theussl
> Fix For: 1.0-beta-1
>
> Attachments: cell-justify.patch
>
>
> Attempt to render a multi column table using XDoc:
> {noformat}
> java.lang.ArrayIndexOutOfBoundsException: 1
> at
> org.apache.maven.doxia.sink.XhtmlBaseSink.tableCell(XhtmlBaseSink.java:807)
> at
> org.apache.maven.doxia.sink.XhtmlBaseSink.tableCell(XhtmlBaseSink.java:780)
> at
> org.apache.maven.doxia.sink.XhtmlBaseSink.tableHeaderCell(XhtmlBaseSink.java:768)
> at
> org.apache.maven.doxia.parser.XhtmlBaseParser.baseStartTag(XhtmlBaseParser.java:300)
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.handleStartTag(XdocParser.java:213)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:103)
> at
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:54)
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:93)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:345)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:272)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:102)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:137)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> {noformat}
> The XDocParser/XHtmlBaseParser calls sink.tableRows() always with a
> single-element array. This is usually not enough to describe all columns of
> the table individually. Hence, XHtmlBaseSink should be prepared to render a
> table cell that does not have a corresponding cellJustif entry. The patch
> simply repeats the justification of the last array element.
> Last but not least, it might be worth to consider changing the default cell
> alignment to left alignment to match the default behavior of HTML for table
> body cells. Additionally, left-alignment seems to be the current behavior of
> the xdoc module in the alpha branch.
--
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
