[jira] Commented: (DOXIA-295) doxia-module-fo fails with a division by 0 error when using FoSink
[
http://jira.codehaus.org/browse/DOXIA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167968#action_167968
]
Lukas Theussl commented on DOXIA-295:
-
It would be good to know how you arrived at this problem, are you using a Doxia
parser or the Sink directly? The point is that a table without cells is not
really a table, e.g. a html table without a element leads to invalid
xhtml.
I think it's logical to require a table to have at least one cell. The javadocs
for table in Sink.java [1] specifies the canonical sequence of events, and
explicitly mentions only tableCaption to be optional.
I am hesitant to fix this as you suggest, as it could potentially hide bugs in
parsers.
[1] http://maven.apache.org/doxia/doxia/doxia-sink-api/apidocs/index.html
> doxia-module-fo fails with a division by 0 error when using FoSink
> --
>
> Key: DOXIA-295
> URL: http://jira.codehaus.org/browse/DOXIA-295
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - FO
>Affects Versions: 1.2
> Environment: Linux / Solairs jdk 1.5
> Build from svn check out Revsion: 749805
>Reporter: Dean Murphy
>
> When using the FoSink to convert from documents containing a table, I am
> running into a division by 0 error on line: 703 in
> org.apache.maven.doxia.module.fo.FoSink.java:
> int percent = 100 / cellCount;
> for ( int i = 0; i < cellCount; i++ )
> {
> sb.append( " "%\"/>" );
> sb.append( EOL );
> }
> Simple fix would be to check if cellCount != 0:
> if ( cellCount != 0 ) {
> int percent = 100 / cellCount;
> for ( int i = 0; i < cellCount; i++ )
> {
> sb.append( " "%\"/>" );
> sb.append( EOL );
> }
> }
--
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-294) Problems with Doxia
[ http://jira.codehaus.org/browse/DOXIA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167969#action_167969 ] Lukas Theussl commented on DOXIA-294: - I don't see anything unusual in dump.txt, what exactly are you referring to? See also MNG-3402, (maven always uses the embedded doxia version). The attached zip is empty, can you update it? > Problems with Doxia > --- > > Key: DOXIA-294 > URL: http://jira.codehaus.org/browse/DOXIA-294 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Apt, Site Renderer >Affects Versions: 1.0-alpha-11, 1.0 > Environment: Max OS X (Leopard), Sun Java 1.5.0_16. Maven 2.0.10 >Reporter: Jakob Vad Nielsen > Attachments: dump.txt, proof.zip > > > It seems to me that there are a mess on what Doxia packages versions that are > chosen when rendering a site with mvn site:site. See the attached dump.txt. > It seems to me that version 1.0 of doxia is not chosen. And that older > versions are used. > I have added this to my pom.xml > plugin> > org.apache.maven.doxia > doxia-maven-plugin >1.0 > > I discovered this when trying to find out why verbatime text doesn't work > like it did before from an apt file. > - > Verbatime > - > gives thes same markup as > +--+ > Verbatime 2 > +--+ > Both are converted into Verbatime. This > is a new bug that I haven't seen before. > I have attached a small maven project that demonstrates this. demo.html > generated with site:site demonstrates the problem. -- 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: (MPIR-151) Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license'
[ http://jira.codehaus.org/browse/MPIR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167971#action_167971 ] Martin West commented on MPIR-151: -- I assume you mean 2.0.10 I tried but maven dies silently in a antrun task, so reverting back to 2.0.9 I cant use 2.0.8 either because of other bugs. siggg > Unable to find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' > -- > > Key: MPIR-151 > URL: http://jira.codehaus.org/browse/MPIR-151 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Affects Versions: 2.1.1 > Environment: all >Reporter: Martin West > > This started happening yesterday after it downloaded a new version of the > plugin ... > Downloading: > http://mirrors.dotsrc.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.pom > Downloading: > http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > 205K downloaded > - > this realm = > app0.child-container[org.apache.maven.plugins:maven-project-info-reports-plugin] > urls[0] = > file:/var/maven2/repo/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > urls[1] = > file:/var/maven2/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > this realm = plexus.core > urls[0] = file:/opt/maven2/lib/maven-2.1.0-M1-uber.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > - > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1': Unable to > find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in > the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' > org.apache.maven.reporting.AbstractMavenReport -- 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-294) Problems with Doxia
[ http://jira.codehaus.org/browse/DOXIA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167972#action_167972 ] Jakob Vad Nielsen commented on DOXIA-294: - It might be me that do not understand the dependencies correctly. But why are older versions of Doxia used? e.g.: [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:6 for project: org.apache.maven.doxia:doxia:pom:1.0-alpha-10 from the repository. [DEBUG] Adding managed dependencies for unknown:doxia-core [DEBUG] org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-10 [DEBUG] org.apache.maven.doxia:doxia-core:jar:1.0-alpha-10 [DEBUG] org.apache.maven.doxia:doxia-core:jar:tests:1.0-alpha-10 Or am I reading it wrong? But the important issue for me here is that I do not get different markup for --- ad + --- + anymore. Up until last week I was able to separate these verbatims from eachother via my special maven theme. Now it gives me the exact same output. > Problems with Doxia > --- > > Key: DOXIA-294 > URL: http://jira.codehaus.org/browse/DOXIA-294 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Apt, Site Renderer >Affects Versions: 1.0-alpha-11, 1.0 > Environment: Max OS X (Leopard), Sun Java 1.5.0_16. Maven 2.0.10 >Reporter: Jakob Vad Nielsen > Attachments: dump.txt, proof.zip > > > It seems to me that there are a mess on what Doxia packages versions that are > chosen when rendering a site with mvn site:site. See the attached dump.txt. > It seems to me that version 1.0 of doxia is not chosen. And that older > versions are used. > I have added this to my pom.xml > plugin> > org.apache.maven.doxia > doxia-maven-plugin >1.0 > > I discovered this when trying to find out why verbatime text doesn't work > like it did before from an apt file. > - > Verbatime > - > gives thes same markup as > +--+ > Verbatime 2 > +--+ > Both are converted into Verbatime. This > is a new bug that I haven't seen before. > I have attached a small maven project that demonstrates this. demo.html > generated with site:site demonstrates the problem. -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
On 2.0.10 antrun execution dies silently Key: MANTRUN-108 URL: http://jira.codehaus.org/browse/MANTRUN-108 Project: Maven 2.x Antrun Plugin Issue Type: Bug Affects Versions: 1.3 Environment: Maven version: 2.0.10 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" Reporter: Martin West Attachments: mvn-2.0.10.log The title says it all. Ive attached a log of running with -X -e -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167973#action_167973 ] Martin West commented on MANTRUN-108: - PS runs fine on 2.0.9 > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MEV-618) Seems like POM for colt-1.2.0 identified itself as 1.0.3
Seems like POM for colt-1.2.0 identified itself as 1.0.3 Key: MEV-618 URL: http://jira.codehaus.org/browse/MEV-618 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Richard Gomes Seems like POM for colt-1.2.0 identified itself as 1.0.3 http://repo1.maven.org/maven2/colt/colt/1.2.0/colt-1.2.0.pom colt colt 1.0.3 -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167975#action_167975 ] Benjamin Bentmann commented on MANTRUN-108: --- How about a minimal test project to help us reproduce the issue? > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[
http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin West updated MANTRUN-108:
Attachment: MANTRUN-108.zip
minimal project, well as minimal as I make it.
You just need to specify mysql root password, either in .m2/settings.xml or in
the pom.xml
Should get something like:
[10:41:04][MANTRUN-108]$ ../mvn-2.0.10
[INFO] Scanning for projects...
[INFO]
[INFO] Building MANTRUN-108
[INFO]task-segment: [install]
[INFO]
[INFO] [antrun:run {execution: validate}]
[INFO] Executing tasks
validate:
[INFO] Executed tasks
[INFO] [antrun:run {execution: generate-resources}]
[INFO] Executing tasks
generate-resources:
[INFO] Executed tasks
[INFO] [resources:resources]
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/Users/martinwest/workspaces/hattrick-ws-1.0.1/net.helixsys.tis/MANTRUN-108/src/main/resources
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [antrun:run {execution: generate-test-resources}]
[INFO] Executing tasks
createdb:
[execsql] Executing resource:
/Users/martinwest/workspaces/hattrick-ws-1.0.1/net.helixsys.tis/MANTRUN-108/target/drop_tis_db.sql
[execsql] Executing resource:
/Users/martinwest/workspaces/hattrick-ws-1.0.1/net.helixsys.tis/MANTRUN-108/target/create_tis_db.sql
= dies here ===
normally carries on with
generate-test-resources:
[INFO] Executed tasks
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
/Users/martinwest/workspaces/hattrick-ws-1.0.1/net.helixsys.tis/MANTRUN-108/target/MANTRUN-108-test.jar
[INFO] [install:install]
[INFO] Installing
/Users/martinwest/workspaces/hattrick-ws-1.0.1/net.helixsys.tis/MANTRUN-108/target/MANTRUN-108-test.jar
to /var/maven2/MANTRUN-108/MANTRUN-108/test/MANTRUN-108-test.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Mar 05 10:51:11 GMT 2009
[INFO] Final Memory: 10M/17M
> On 2.0.10 antrun execution dies silently
>
>
> Key: MANTRUN-108
> URL: http://jira.codehaus.org/browse/MANTRUN-108
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: Maven version: 2.0.10
> Java version: 1.5.0_16
> OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix"
>Reporter: Martin West
> Attachments: MANTRUN-108.zip, mvn-2.0.10.log
>
>
> The title says it all.
> Ive attached a log of running with -X -e
--
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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167980#action_167980 ] Martin West commented on MANTRUN-108: - also fails in this env Maven version: 2.0.10 Java version: 1.6.0_10-beta OS name: "linux" version: "2.6.24-23-generic" arch: "amd64" Family: "unix" > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167981#action_167981 ] Brett Porter commented on MANTRUN-108: -- the zip appears to be empty > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MPIR-151) Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license'
[ http://jira.codehaus.org/browse/MPIR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MPIR-151. - Assignee: Brett Porter Resolution: Not A Bug you are using a bad mirror. You should have received this file: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.pom Without the POM, dependencies are not loaded, causing the no class def found error (we've improved that message for 2.1.0). > Unable to find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' > -- > > Key: MPIR-151 > URL: http://jira.codehaus.org/browse/MPIR-151 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Affects Versions: 2.1.1 > Environment: all >Reporter: Martin West >Assignee: Brett Porter > > This started happening yesterday after it downloaded a new version of the > plugin ... > Downloading: > http://mirrors.dotsrc.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.pom > Downloading: > http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > 205K downloaded > - > this realm = > app0.child-container[org.apache.maven.plugins:maven-project-info-reports-plugin] > urls[0] = > file:/var/maven2/repo/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > urls[1] = > file:/var/maven2/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > this realm = plexus.core > urls[0] = file:/opt/maven2/lib/maven-2.1.0-M1-uber.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > - > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1': Unable to > find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in > the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' > org.apache.maven.reporting.AbstractMavenReport -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin West updated MANTRUN-108: Attachment: MANTRUN-108.zip DOH missed -r off, apologies. > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-108) On 2.0.10 antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167993#action_167993 ] Brett Porter commented on MANTRUN-108: -- confirmed (very bizarre - it looks like a stray System.exit, but not sure what behaviour changed yet) > On 2.0.10 antrun execution dies silently > > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-108) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MANTRUN-108: - Summary: [regression] antrun execution dies silently (was: On 2.0.10 antrun execution dies silently) > [regression] antrun execution dies silently > --- > > Key: MANTRUN-108 > URL: http://jira.codehaus.org/browse/MANTRUN-108 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MNG-4067) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MNG-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4067: -- Fix Version/s: 2.1.0 2.0.11 affects 2.1.0-SNAPSHOT as well > [regression] antrun execution dies silently > --- > > Key: MNG-4067 > URL: http://jira.codehaus.org/browse/MNG-4067 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.10, 2.1.0 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Fix For: 2.0.11, 2.1.0 > > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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] Moved: (MNG-4067) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MNG-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MANTRUN-108 to MNG-4067: --- Affects Version/s: (was: 1.3) 2.1.0 2.0.10 Complexity: Intermediate Key: MNG-4067 (was: MANTRUN-108) Project: Maven 2 (was: Maven 2.x Antrun Plugin) > [regression] antrun execution dies silently > --- > > Key: MNG-4067 > URL: http://jira.codehaus.org/browse/MNG-4067 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.10, 2.1.0 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Fix For: 2.0.11, 2.1.0 > > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MNG-4062) Evaluate possibility to cache parents during multi module build
[
http://jira.codehaus.org/browse/MNG-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-4062:
--
Fix Version/s: 3.0-alpha-5
> Evaluate possibility to cache parents during multi module build
> ---
>
> Key: MNG-4062
> URL: http://jira.codehaus.org/browse/MNG-4062
> Project: Maven 2
> Issue Type: Task
> Components: Performance
>Affects Versions: 3.0-alpha-3
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-5
>
>
> From a breakpoint in {{DefaultMavenProjectBuilder.build(File,
> ProjectBuilderConfiguration)}} it seems that the parent of a multi-module
> project is rebuild for each child in the reactor. Given the likelihood of the
> modules in the reactor having the same parent, it could be a good opportunity
> for optimization to cache the parents (or projects in general).
--
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: (MNG-4055) wrong error on mvn install in folder without pom.xml
[ http://jira.codehaus.org/browse/MNG-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4055: -- Fix Version/s: 3.0-alpha-5 > wrong error on mvn install in folder without pom.xml > - > > Key: MNG-4055 > URL: http://jira.codehaus.org/browse/MNG-4055 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 3.0-alpha-2 >Reporter: Milos Kleint > Fix For: 3.0-alpha-5 > > > a folder without maven's pom.xml file. running mvn install there-> > [mkle...@localhost glassfish]$ ~/javatools/apache-maven-3.0-alpha-2/bin/mvn > install > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Default Project > [INFO] > [INFO] Id: org.apache.maven:super-pom:jar:3.0-SNAPSHOT > [INFO] task-segment: [install] > [INFO] > > [ERROR] > Internal error in the plugin manager executing goal > 'org.apache.maven.plugins:maven-resources-plugin:2.2:resources': Cannot > execute mojo: resources. It requires a project with an existing pom.xml, but > the build is not using one. > While building project with id: org.apache.maven:super-pom:jar:3.0-SNAPSHOT -- 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-4067) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MNG-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167996#action_167996 ] Brett Porter commented on MNG-4067: --- it dies in the second transaction of the call in the ant script, which takes considerably longer to run than the successful one from 2.1.0-M1/2.0.9 before failing I ran with -verbose:gc to see if it was an OOME, but that did not indicate any GC at the time > [regression] antrun execution dies silently > --- > > Key: MNG-4067 > URL: http://jira.codehaus.org/browse/MNG-4067 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.10, 2.1.0 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Fix For: 2.0.11, 2.1.0 > > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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-4063) Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.4:jar.
[
http://jira.codehaus.org/browse/MNG-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167998#action_167998
]
Brett Porter commented on MNG-4063:
---
running site in the package cycle should work (but not a good idea, correct).
> Component descriptor cannot be found in the component repository:
> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.4:jar.
>
>
> Key: MNG-4063
> URL: http://jira.codehaus.org/browse/MNG-4063
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9
> Environment: Linux 2.6.28-8-generic #26-Ubuntu SMP x86_64 GNU/Linux,
> Java: 64bit (IcedTea6 1.4) (6b14-0ubuntu17)
>Reporter: Martin Vysny
>
> When I try to build a project against a completely clean local .m2 repository
> with Nexus cache the build fails with this exception. I have to run it again
> to remove the exception.
> [INFO]
>
> [INFO] Building LSABPM: Escrow complete package
> [INFO]
>
> [INFO] No goals needed for project - skipping
> [INFO] Preparing javadoc:test-javadoc
> [INFO] No goals needed for project - skipping
> [INFO] Preparing cobertura:cobertura
> [INFO] [cobertura:instrument]
> [INFO] Not executing cobertura:instrument as the project is not a Java
> classpath-capable package
> [INFO] Preparing findbugs:findbugs
> [INFO] No goals needed for project - skipping
> [INFO] Preparing surefire-report:report
> [INFO] No goals needed for project - skipping
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/org/apache/maven/wagon/wagon-file/1.0-alpha-5/wagon-file-1.0-alpha-5.jar
> 4/5K
> 5/5K
> 5K downloaded
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/org/apache/maven/wagon/wagon-http-lightweight/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.jar
> 4/7K
> 7/7K
> 7K downloaded
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/org/apache/maven/wagon/wagon-ssh/1.0-alpha-5/wagon-ssh-1.0-alpha-5.jar
> 4/32K
> 8/32K
> 12/32K
> 16/32K
> 20/32K
> 24/32K
> 28/32K
> 32/32K
> 32/32K
> 32K downloaded
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/com/jcraft/jsch/0.1.23/jsch-0.1.23.jar
> 4/113K
> 8/113K
> 12/113K
> 16/113K
> 20/113K
> 24/113K
> 28/113K
> 32/113K
> 36/113K
> 40/113K
> 44/113K
> 48/113K
> 52/113K
> 56/113K
> 60/113K
> 64/113K
> 68/113K
> 72/113K
> 76/113K
> 80/113K
> 84/113K
> 88/113K
> 92/113K
> 96/113K
> 100/113K
> 104/113K
> 108/113K
> 112/113K
> 113/113K
> 113K downloaded
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [site:site {execution: assembly-site}]
> [ERROR] The Trac Report only supports Trac. No Trac Report will be generated.
> [ERROR] The JIRA Report only supports JIRA. No JIRA Report will be generated.
> [INFO] Not executing cobertura:report as the cobertura data file
> (/home/sdktest/lsabpm-escrow/lsabpm-src/lsabpm-escrow/lsabpm-escrow-all/target/cobertura/cobertura.ser)
> could not be found
> [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport -
> AbstractMethodError: canGenerateReport()
> [WARNING] Error loading report org.codehaus.mojo.surefire.SurefireReportMojo
> - AbstractMethodError: canGenerateReport()
> [WARNING] Unable to load parent project from repository: Could not find the
> model file '/home/sdktest/lsabpm-escrow/lsabpm-src/../pom.xml'. for project
> unknown
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/com/whitestein/lsabpm/lsabpm-parent/1.30/lsabpm-parent-1.30-site_en.xml
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/com/whitestein/lsabpm/lsabpm-parent/1.30/lsabpm-parent-1.30-site.xml
> [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for
> updates from central
> Downloading:
> http://magi.dynip:8081/nexus/content/repositories/central/org/apache/maven/skins/maven-default-skin/1.0/maven-default-skin-1.0.jar
> 4/7K
> 7/7K
> 7K downloaded
> [INFO] Generate "PMD Report" report.
> [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
> [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
> [INFO] Generate "CPD Report" report.
> [INFO] Generate "Dependencies" report.
> [INFO] Generate "Dependency Convergence" report.
> [INFO] Gene
[jira] Commented: (MNG-4067) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MNG-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167999#action_167999 ] Martin West commented on MNG-4067: -- yes, I notice the time problem, is timing out on something? > [regression] antrun execution dies silently > --- > > Key: MNG-4067 > URL: http://jira.codehaus.org/browse/MNG-4067 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.10, 2.1.0 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Fix For: 2.0.11, 2.1.0 > > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-109) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168001#action_168001 ] Brett Porter commented on MANTRUN-109: -- my mistake - 2.0.10 upgraded the antrun plugin, I just missed that in the first place I looked. This is a regression between 1.2 and 1.3. If you set the version to either 1.1 or 1.2 in the POM you will avoid the problem under 2.0.10. > [regression] antrun execution dies silently > --- > > Key: MANTRUN-109 > URL: http://jira.codehaus.org/browse/MANTRUN-109 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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] Moved: (MANTRUN-109) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MNG-4067 to MANTRUN-109: --- Affects Version/s: (was: 2.1.0) (was: 2.0.10) 1.3 Fix Version/s: (was: 2.1.0) (was: 2.0.11) Complexity: (was: Intermediate) Key: MANTRUN-109 (was: MNG-4067) Project: Maven 2.x Antrun Plugin (was: Maven 2) > [regression] antrun execution dies silently > --- > > Key: MANTRUN-109 > URL: http://jira.codehaus.org/browse/MANTRUN-109 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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: (MANTRUN-109) [regression] antrun execution dies silently
[ http://jira.codehaus.org/browse/MANTRUN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168005#action_168005 ] Martin West commented on MANTRUN-109: - Thanks for the fast response. > [regression] antrun execution dies silently > --- > > Key: MANTRUN-109 > URL: http://jira.codehaus.org/browse/MANTRUN-109 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_16 > OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix" >Reporter: Martin West > Attachments: MANTRUN-108.zip, MANTRUN-108.zip, mvn-2.0.10.log > > > The title says it all. > Ive attached a log of running with -X -e -- 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-3004) Allow build lifecycle to execute tasks in parallel
[ http://jira.codehaus.org/browse/MNG-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168006#action_168006 ] Nigel Magnay commented on MNG-3004: --- If A, B or C all rely on a downloadable artifact X (or, X-SNAPSHOT), then building them in parallel may result in a parallel update of X. You need to be able to fix it in place for the duration of your build. > Allow build lifecycle to execute tasks in parallel > -- > > Key: MNG-3004 > URL: http://jira.codehaus.org/browse/MNG-3004 > Project: Maven 2 > Issue Type: Improvement > Components: Bootstrap & Build, General, Performance >Affects Versions: 2.0.6 >Reporter: Nigel Magnay > Fix For: 2.2.0-M1 > > Attachments: parallel-builds.patch > > > One of the great advantages with maven over scripted build environments is > that it can calculate the dependencies of the build, and it could execute > items that are independent of each other in parallel. > Unfortunately it currently doesn't do this, which would be a big win over > tools such as 'ant'. It also means that multicore machines have lots of idle > capacity when running a serial build that could be utilised. > I had a quick shot at seeing what might be required. Bear in mind this is the > first time I have looked at maven internally, and I was just trying to feel > my way around and build a POC. I got some of the way there, but my build > threads don't seem to have the correct classpath - I think this is something > to do with plexus / classworlds - but I don't know enough. > It'd be great to get this feature in a future version, or a way of running my > hack (figuring out why in a thread has not the plexus stuff) in the interim. -- 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: (MECLIPSE-531) eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking
eclipse:to-maven uses version ranges in pom.xmls created, which fail version checking - Key: MECLIPSE-531 URL: http://jira.codehaus.org/browse/MECLIPSE-531 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.5.1 Environment: Windows XP SP3, Maven 2.0.9, Java 1.6.0.11 Reporter: Costin Caraivan If you use eclipse:to-maven, the resulting artifacts have poms containing versions like these, for dependencies: [3.2.0,4.0.0). End result => Couldn't find a version in [3.2.0-v3232o] to match range [3.2.0,4.0.0) I believe that to-maven needs an option like make-artifacts, to resolveVersionRanges, because stripping qualifiers means that we lose information (Eclipse 3.4 has some 3.2.0 plugins for example, but with a different qualifier than the original 3.2 Eclipse plugins). Or the version ranges need to be fixed, something like this: [3.2.0-, 4.0.0-). Thank you. -- 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: (SCM-442) Incorrect SCM URL constructed when using parent POM that is not in the parent directory
Incorrect SCM URL constructed when using parent POM that is not in the parent directory --- Key: SCM-442 URL: http://jira.codehaus.org/browse/SCM-442 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.1 Reporter: Petter Måhlén We have a parent corporate POM that is not in the parent folder of each project. When running release:perform, the correct (as specified) GIT SCM URL is not used, but instead a URL is created by appending the Maven artifact name to the SCM URL of the parent corporate POM project. Which doesn't make sense at all to me: 1. There is no requirement (and in fact bad practice in a lot of cases) that the POM hierarchy should map exactly to the folder hierarchy. So a parent POM doesn't have to reside in a parent directory. 2. There is no requirement (but maybe good practice) to have folder names in SCM be the same as the artifact names. In our case, we have a bad artifact name that we want to keep so as not to have to modify a lot of POMs, but we wanted a clearer repository name for the new Git repository. This is the error message from the 'mvn release:perform' command. INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sponsoredlinks-client/target && git clone git://git.shopzilla.com/java/common.mvn.git/slg_client /Users/pettermahlen/git/sponsoredlinks-client/target/checkout [INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/target [ERROR] The git-clone command failed. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to checkout from SCM Provider message: The git-clone command failed. Command output: fatal: The remote end hung up unexpectedly The SCM configuration from the 'slg_client' pom.xml is; scm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client The workaround that I have found is to manually edit the release.properties file and change to using the correct SCM URL. -- 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-3553) cannot resolve dependency with scope import
[
http://jira.codehaus.org/browse/MNG-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168011#action_168011
]
Jacques Morel commented on MNG-3553:
That is great news.
I have really be struggling with this. Apparently I found that if you have a
local proxy server and it proxies central, you may be able to work around some
of these problem here by explicitly mirroring 'central' in your settings.xml.
So maybe it is why you haven't been able to reproduce it.
I am playing with it as we speak because I thought the mirroring central was
working for both release and snapshots. But now I am trying to build on another
machine it does not work anymore for at least snapshots. Very frustrating.
In any case, ask me anything to help you solve this. We really need this fixed
as soon as possible.
Thanks again.
Jacques
> cannot resolve dependency with scope import
> ---
>
> Key: MNG-3553
> URL: http://jira.codehaus.org/browse/MNG-3553
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
> Fix For: 2.0.11
>
> Attachments: mng-3553.zip
>
>
> This pom when added as a dependency of another project does not see
> repository http://snapshots.jboss.org/maven2
>
>
>
>
> org.jboss.jbossas
> jboss-as-component-matrix
> ${jboss.version}
> pom
> import
>
>
>
> with effective settings
> [tdies...@tddell trunk]$ mvn help:effective-settings
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] JBoss Web Services - Stack CXF
> [INFO] JBoss Web Services - Stack CXF Management
> [INFO] JBoss Web Services - Stack CXF Runtime Server
> [INFO] JBoss Web Services - Stack CXF Runtime Client
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
>
> [INFO] Building JBoss Web Services - Stack CXF
> [INFO]task-segment: [help:effective-settings] (aggregator-style)
> [INFO]
>
> [INFO] [help:effective-settings]
> [INFO]
> Effective settings:
>
> /home/tdiesler/.m2/repository
>
>
>
>
> !jboss.repository.off
>
>
>
>
>
> snapshots.jboss.org
> http://snapshots.jboss.org/maven2
>
>
>
> false
>
> repository.jboss.org
> http://repository.jboss.org/maven2
>
>
> jboss.repository
>
>
>
> user-profile
>
>
> org.jboss.maven.plugins
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Billard reopened MAVENUPLOAD-2361: -- Sorry, the bundle was wrong, jar file was not taken into account correctly, my fault. Here is a correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- 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] Issue Comment Edited: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168019#action_168019 ] Olivier Billard edited comment on MAVENUPLOAD-2361 at 3/5/09 10:24 AM: --- This one is the correct one (443 Ko) was (Author: obillard): This one is the correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar, > hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- 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: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Billard updated MAVENUPLOAD-2361: - Attachment: hibernate-search-3.1.0.GA-bundle.jar This one is the correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar, > hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- 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: (MRELEASE-421) overwriting property in version tag, rather than updating property
overwriting property in version tag, rather than updating property
--
Key: MRELEASE-421
URL: http://jira.codehaus.org/browse/MRELEASE-421
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-8
Reporter: Max Powers
I have a multimodule project that has the following dependency setup in one of
the poms
1.0.2-SNAPSHOT
org.sonatype.nexus.plugins
nexus-lvo-plugin
${nexus-lvo-plugin.version}
this nexus-lvo-plugin is in the same reactor build as the module above.
In 2.0-beta-8, rather than simply updating the property w/ the release version,
the tag in the dependency is updated
leaving
org.sonatype.nexus.plugins
nexus-lvo-plugin
1.0.2
which causes me to have to update the pom after release is done. this didn't
happen in previous release plugin versions
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: maven-war-plugin problem with RSA- HELP
Can someonw help me out to resolve this.. From: Vineet Kumar Gautam Sent: Wednesday, March 04, 2009 2:58 PM To: Vineet Kumar Gautam; 'issues@maven.apache.org' Subject: RE: maven-war-plugin problem with RSA Also if I do mvn install from DOS prompt, it says success. After if I try again form RSA. It gives error as follow:- Note that this is the case only with packaging type war i.e with web projects... com.thoughtworks.xstream.converters.ConversionException: dependenciesInfo : dependenciesInfo Debugging information message : dependenciesInfo : dependenciesInfo cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : dependenciesInfo : dependenciesInfo class : org.apache.maven.plugin.war.util.WebappStructure required-type : org.apache.maven.plugin.war.util.WebappStructure path : /webapp-structure/dependenciesInfo line number : 32 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller. java:63) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(Abst ractReferenceUnmarshaller.java:45) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmars haller.java:46) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.ja va:117) at com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.unmars hal(ReferenceByXPathMarshallingStrategy.java:29) at com.thoughtworks. From: Vineet Kumar Gautam Sent: Wednesday, March 04, 2009 2:56 PM To: issues@maven.apache.org Subject: maven-war-plugin problem with RSA Hi, When I try to do mvn install for web project from RSA( Rational Software Architect) we get following error:- [ERROR] The following mojo encountered an error while executing: Group-Id: org.apache.maven.plugins Artifact-Id: maven-war-plugin Version: 2.1-alpha-1 Mojo: war brought in via: packaging: war While building project: Group-Id: com.wellpoint.ebiz.middletier.benefit Artifact-Id: BenefitWebServiceV1 Version: 1.0-SNAPSHOT From file: C:\views\ss\AB77681_member_09.1.0_r10_dev\eBiz_Business_src\biz.ws.benef it\BenefitWebServiceV1\pom.xml Reason: Failed to copy file for artifact[com.wellpoint.ebiz.middletier.benefit:BenefitBusinessService:ja r:1.0-SNAPSHOT:compile] I am totally stucked. Wht is the solution. Regards VIneet IMPORTANT WARNING: This e-mail is intended for the use of the person to whom it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. Dissemination, distribution or copying of this information in an unauthorized manner is strictly prohibited. Sender accepts no liability for any damage caused by any virus transmitted by this e-mail. If you receive this in error, please notify the sender. ==
[jira] Reopened: (MAVENUPLOAD-2028) Sync Compass maven repository with the central maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shay Banon reopened MAVENUPLOAD-2028: - I think I managed to get it to work, can you please try again with rsync over ssh? > Sync Compass maven repository with the central maven repository > --- > > Key: MAVENUPLOAD-2028 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2028 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Shay Banon >Assignee: Carlos Sanchez > > "org.compass-project","rsync://repo.compass-project.org","rsync","Shay > Banon","kim...@gmail.com",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (MECLIPSE-529) File not found - target/classes access denied
antd wrote: > > I believe I hit the same problem with 0.9.7 that wasn't present in the > previous release. The error occurs in a project dependent upon another > one. Is there a work-around? > I face exactly the same problem using Eclipse 3.4.1 and m2eclipse 0.9.7. I gave Eclipse 3.4.2 a try, but the problem remains. My current workaround: invoke maven out of eclipse and hit refresh. Though this is very ugly, it works. I'd like to try m2eclipse 0.9.6 but there seems to be no way to install an older version than 0.9.7. Does somebody know how to get the old version? -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28MECLIPSE-529%29-File-not-found---target-classes-access-denied-tp22311019p22359545.html Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Created: (MNG-4068) Use proper id for mirrored repository
Use proper id for mirrored repository - Key: MNG-4068 URL: http://jira.codehaus.org/browse/MNG-4068 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0-alpha-3 Reporter: Benjamin Bentmann [r750570|http://svn.eu.apache.org/viewvc?view=rev&revision=750570] introduced a regression for authenticated mirrors since the effective repository id must be the id of the mirror to have auth lookup work. Also, a quick seach showed that we currently have no IT for this scenario. -- 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: (MNG-4068) [regression] Use proper id for mirrored repository
[ http://jira.codehaus.org/browse/MNG-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4068: --- Assignee: Benjamin Bentmann Fix Version/s: 3.0-alpha-3 Summary: [regression] Use proper id for mirrored repository (was: Use proper id for mirrored repository) > [regression] Use proper id for mirrored repository > -- > > Key: MNG-4068 > URL: http://jira.codehaus.org/browse/MNG-4068 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > > [r750570|http://svn.eu.apache.org/viewvc?view=rev&revision=750570] introduced > a regression for authenticated mirrors since the effective repository id must > be the id of the mirror to have auth lookup work. Also, a quick seach showed > that we currently have no IT for this scenario. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: maven-war-plugin problem with RSA- HELP
This is a mailing list for automated e-mails from our issue tracker. It is not meant to be used for asking questions. Please use the users mailing list instead: us...@maven.apache.org Vineet Kumar Gautam wrote: > Can someonw help me out to resolve this.. > > > > From: Vineet Kumar Gautam > Sent: Wednesday, March 04, 2009 2:58 PM > To: Vineet Kumar Gautam; 'issues@maven.apache.org' > Subject: RE: maven-war-plugin problem with RSA > > > Also if I do mvn install from DOS prompt, it says success. > After if I try again form RSA. It gives error as follow:- > Note that this is the case only with packaging type war i.e with web > projects... > > > com.thoughtworks.xstream.converters.ConversionException: > dependenciesInfo : dependenciesInfo > > Debugging information > > message : dependenciesInfo : dependenciesInfo > > cause-exception : > com.thoughtworks.xstream.mapper.CannotResolveClassException > > cause-message : dependenciesInfo : dependenciesInfo > > class : org.apache.maven.plugin.war.util.WebappStructure > > required-type : org.apache.maven.plugin.war.util.WebappStructure > > path : /webapp-structure/dependenciesInfo > > line number : 32 > > --- > > at > com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller. > java:63) > > at > com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(Abst > ractReferenceUnmarshaller.java:45) > > at > com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmars > haller.java:46) > > at > com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.ja > va:117) > > at > com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.unmars > hal(ReferenceByXPathMarshallingStrategy.java:29) > > at com.thoughtworks. > > > > > From: Vineet Kumar Gautam > Sent: Wednesday, March 04, 2009 2:56 PM > To: issues@maven.apache.org > Subject: maven-war-plugin problem with RSA > > > Hi, > When I try to do mvn install for web project from RSA( Rational > Software Architect) we get following error:- > > > > [ERROR] > > The following mojo encountered an error while executing: > > Group-Id: org.apache.maven.plugins > > Artifact-Id: maven-war-plugin > > Version: 2.1-alpha-1 > > Mojo: war > > brought in via: packaging: war > > While building project: > > Group-Id: com.wellpoint.ebiz.middletier.benefit > > Artifact-Id: BenefitWebServiceV1 > > Version: 1.0-SNAPSHOT > > From file: > C:\views\ss\AB77681_member_09.1.0_r10_dev\eBiz_Business_src\biz.ws.benef > it\BenefitWebServiceV1\pom.xml > > Reason: Failed to copy file for > artifact[com.wellpoint.ebiz.middletier.benefit:BenefitBusinessService:ja > r:1.0-SNAPSHOT:compile] > > > > > > I am totally stucked. > > Wht is the solution. > > > > Regards > > VIneet > > > IMPORTANT WARNING: > This e-mail is intended for the use of the person to whom it is addressed and > may contain information that is privileged and confidential, the disclosure > of which is governed by applicable law. Dissemination, distribution or > copying of this information in an unauthorized manner is strictly prohibited. > Sender accepts no liability for any damage caused by any virus transmitted by > this e-mail. If you receive this in error, please notify the sender. > == > -- Dennis Lundberg
[jira] Created: (MPLUGIN-148) PluginXdocGenerator generates poorly formed output when default values contain XML
PluginXdocGenerator generates poorly formed output when default values contain
XML
--
Key: MPLUGIN-148
URL: http://jira.codehaus.org/browse/MPLUGIN-148
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: API
Affects Versions: 2.5, 2.4.3
Reporter: Brent N Atkinson
Due to changes made in revision 684062, PluginXDocGenerator no longer handles
defalultValues properly. Before, the routines depended on
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter's method writeText (which
escaped XML). Since the change to using pure ResourceBundle interpolation, the
values are no longer escaped. The following excerpt shows the offending changes:
---
maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
2008/08/08 19:24:21 684061
+++
maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
2008/08/08 19:28:52 684062
...
@@ -532,15 +526,13 @@
}
else
{
-description = getBundle( locale ).getString(
"pluginxdoc.nodescription" );
+description = getString( "pluginxdoc.nodescription" );
}
w.writeMarkup( description + "" );
if ( StringUtils.isNotEmpty( parameter.getDefaultValue() ) )
{
-w.writeMarkup( "" + getBundle( locale ).getString(
"pluginxdoc.mojodescriptor.parameter.defaultValue" ) + ": " );
-w.writeText( parameter.getDefaultValue() );
-w.writeMarkup( "." );
+w.writeMarkup( format(
"pluginxdoc.mojodescriptor.parameter.defaultValue", parameter.getDefaultValue()
) );
}
w.endElement();//td
w.endElement(); //tr
--
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: (MNG-4068) [regression] Use proper id for mirrored repository
[ http://jira.codehaus.org/browse/MNG-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4068. -- Resolution: Fixed Fixed in [r750613|http://svn.eu.apache.org/viewvc?view=rev&revision=750613]. > [regression] Use proper id for mirrored repository > -- > > Key: MNG-4068 > URL: http://jira.codehaus.org/browse/MNG-4068 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > > [r750570|http://svn.eu.apache.org/viewvc?view=rev&revision=750570] introduced > a regression for authenticated mirrors since the effective repository id must > be the id of the mirror to have auth lookup work. Also, a quick seach showed > that we currently have no IT for this scenario. -- 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: (MPLUGIN-148) PluginXdocGenerator generates poorly formed output when default values contain XML
[
http://jira.codehaus.org/browse/MPLUGIN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168070#action_168070
]
Brent N Atkinson commented on MPLUGIN-148:
--
Sorry about the formatting, from the UI I couldn't tell how to achieve the
formatting.
> PluginXdocGenerator generates poorly formed output when default values
> contain XML
> --
>
> Key: MPLUGIN-148
> URL: http://jira.codehaus.org/browse/MPLUGIN-148
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 2.4.3, 2.5
>Reporter: Brent N Atkinson
>
> Due to changes made in revision 684062, PluginXDocGenerator no longer handles
> defalultValues properly. Before, the routines depended on
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter's method writeText (which
> escaped XML). Since the change to using pure ResourceBundle interpolation,
> the values are no longer escaped. The following excerpt shows the offending
> changes:
>
> ---
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:24:21 684061
> +++
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:28:52 684062
> ...
> @@ -532,15 +526,13 @@
> }
> else
> {
> -description = getBundle( locale ).getString(
> "pluginxdoc.nodescription" );
> +description = getString( "pluginxdoc.nodescription" );
> }
> w.writeMarkup( description + "" );
>
> if ( StringUtils.isNotEmpty( parameter.getDefaultValue() ) )
> {
> -w.writeMarkup( "" + getBundle( locale ).getString(
> "pluginxdoc.mojodescriptor.parameter.defaultValue" ) + ": " );
> -w.writeText( parameter.getDefaultValue() );
> -w.writeMarkup( "." );
> +w.writeMarkup( format(
> "pluginxdoc.mojodescriptor.parameter.defaultValue",
> parameter.getDefaultValue() ) );
> }
> w.endElement();//td
> w.endElement(); //tr
>
--
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: (MPLUGIN-148) PluginXdocGenerator generates poorly formed output when default values contain XML
[
http://jira.codehaus.org/browse/MPLUGIN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brent N Atkinson updated MPLUGIN-148:
-
Attachment: MPLUGIN-148.patch
Introduces escaping of default values back into the XDoc generator.
> PluginXdocGenerator generates poorly formed output when default values
> contain XML
> --
>
> Key: MPLUGIN-148
> URL: http://jira.codehaus.org/browse/MPLUGIN-148
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 2.4.3, 2.5
>Reporter: Brent N Atkinson
> Attachments: MPLUGIN-148.patch
>
>
> Due to changes made in revision 684062, PluginXDocGenerator no longer handles
> defalultValues properly. Before, the routines depended on
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter's method writeText (which
> escaped XML). Since the change to using pure ResourceBundle interpolation,
> the values are no longer escaped. The following excerpt shows the offending
> changes:
>
> ---
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:24:21 684061
> +++
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:28:52 684062
> ...
> @@ -532,15 +526,13 @@
> }
> else
> {
> -description = getBundle( locale ).getString(
> "pluginxdoc.nodescription" );
> +description = getString( "pluginxdoc.nodescription" );
> }
> w.writeMarkup( description + "" );
>
> if ( StringUtils.isNotEmpty( parameter.getDefaultValue() ) )
> {
> -w.writeMarkup( "" + getBundle( locale ).getString(
> "pluginxdoc.mojodescriptor.parameter.defaultValue" ) + ": " );
> -w.writeText( parameter.getDefaultValue() );
> -w.writeMarkup( "." );
> +w.writeMarkup( format(
> "pluginxdoc.mojodescriptor.parameter.defaultValue",
> parameter.getDefaultValue() ) );
> }
> w.endElement();//td
> w.endElement(); //tr
>
--
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: (MPLUGIN-148) PluginXdocGenerator generates poorly formed output when default values contain XML
[
http://jira.codehaus.org/browse/MPLUGIN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168078#action_168078
]
Brent N Atkinson commented on MPLUGIN-148:
--
It appears that the maven-jspc-plugin suffers from this when using newer plugin
releases. By using 2.4.2 or earlier it works around the issue. the following
pom.xml section works around this until the fix is released:
{code:xml}
org.apache.maven.plugins
maven-plugin-plugin
2.4.2
{code}
> PluginXdocGenerator generates poorly formed output when default values
> contain XML
> --
>
> Key: MPLUGIN-148
> URL: http://jira.codehaus.org/browse/MPLUGIN-148
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
>Affects Versions: 2.4.3, 2.5
>Reporter: Brent N Atkinson
> Attachments: MPLUGIN-148.patch
>
>
> Due to changes made in revision 684062, PluginXDocGenerator no longer handles
> defalultValues properly. Before, the routines depended on
> org.codehaus.plexus.util.xml.PrettyPrintXMLWriter's method writeText (which
> escaped XML). Since the change to using pure ResourceBundle interpolation,
> the values are no longer escaped. The following excerpt shows the offending
> changes:
>
> ---
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:24:21 684061
> +++
> maven/plugin-tools/trunk/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.java
> 2008/08/08 19:28:52 684062
> ...
> @@ -532,15 +526,13 @@
> }
> else
> {
> -description = getBundle( locale ).getString(
> "pluginxdoc.nodescription" );
> +description = getString( "pluginxdoc.nodescription" );
> }
> w.writeMarkup( description + "" );
>
> if ( StringUtils.isNotEmpty( parameter.getDefaultValue() ) )
> {
> -w.writeMarkup( "" + getBundle( locale ).getString(
> "pluginxdoc.mojodescriptor.parameter.defaultValue" ) + ": " );
> -w.writeText( parameter.getDefaultValue() );
> -w.writeMarkup( "." );
> +w.writeMarkup( format(
> "pluginxdoc.mojodescriptor.parameter.defaultValue",
> parameter.getDefaultValue() ) );
> }
> w.endElement();//td
> w.endElement(); //tr
>
--
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: (MPLUGIN-148) PluginXdocGenerator generates poorly formed output when default values contain XML
[
http://jira.codehaus.org/browse/MPLUGIN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168079#action_168079
]
Brent N Atkinson commented on MPLUGIN-148:
--
It's also worth noting that because the xdoc generated is poorly formed, it
causes the site plugin to choke on it. The original manifestation of the issues
was the following stack trace:
{noformat}
$ mvn clean site:stage -DciProfile
...
INFO] [site:stage]
[INFO] Unable to load parent project from a relative path: Could not find the
model file 'C:\cygwin\home\batkinson\maven-jspdeclare-plugin\..\pom.xml'. for
project unknown
[INFO] Parent project loaded from repository.
[INFO] Unable to load parent project from a relative path: Could not find the
model file 'C:\cygwin\home\batkinson\maven-jspdeclare-plugin\..\pom.xml'. for
project unknown
[INFO] Parent project loaded from repository.
[INFO] snapshot edu.maine.usm.dbas.usmsiteskin:usmsiteskin:1.0-SNAPSHOT:
checking for updates from snapshots
[INFO] Generating "Plugin Documentation" report.
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 1 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[INFO] Generating "Plugin Management" report.
[INFO] Generating "Mailing Lists" report.
[INFO] Generating "Continuous Integration" report.
[INFO] Generating "Project License" report.
[INFO] Generating "Project Team" report.
[INFO] Generating "Source Repository" report.
[INFO] Generating "About" report.
[INFO] Generating "Issue Tracking" report.
[INFO] Generating "Project Summary" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Dependencies" report.
[ERROR] Error parsing
C:\cygwin\home\batkinson\maven-jspdeclare-plugin\target\generated-site\xdoc\declare-jsps-mojo.xml:
line [-1] Error parsing the model: end tag name must match start
tag name from line 65 (position: START_TAG seen ...:
... @65:83)
org.apache.maven.doxia.parser.ParseException: Error parsing the model: end tag
name must match start tag name from line 65 (position:
START_TAG seen ...: ... @65:83)
at
org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:57)
at
org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:99)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:59)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:342)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:46)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:137)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
at
org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:105)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag
name must match start tag name from line 65 (position:
START_TAG seen ...: ... @65:83)
[jira] Moved: (ARCHETYPE-231) Maven webapp archetype does not create correct project
[ http://jira.codehaus.org/browse/ARCHETYPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Kuleshov moved MNGECLIPSE-1233 to ARCHETYPE-231: --- Workflow: Maven New (was: jira) Issue Type: Improvement (was: Bug) Key: ARCHETYPE-231 (was: MNGECLIPSE-1233) Project: Maven Archetype (was: Maven Integration for Eclipse) > Maven webapp archetype does not create correct project > -- > > Key: ARCHETYPE-231 > URL: http://jira.codehaus.org/browse/ARCHETYPE-231 > Project: Maven Archetype > Issue Type: Improvement > Environment: Eclipse 3.3 (Europa), m2eclipse 0.9.4.200806 >Reporter: Brennan Spies > Attachments: m2_webapp_arch.zip > > > Created a Maven project, selected the Maven webapp archetype. Zipped project > created is attached. > * Missing src/test/java, src/test/resources, and src/main/java source folders > (config in Eclipse) > * Actual folders are not created > * No stack traces in workspace log file -- 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: (ARCHETYPE-231) Maven webapp archetype does not create correct project
[ http://jira.codehaus.org/browse/ARCHETYPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168116#action_168116 ] Eugene Kuleshov commented on ARCHETYPE-231: --- I am not sure where this issue belong to, but it require to fix and release an updated version of Maven webapp archetype that would create folders listed in the bug description. Until that the m2eclipse is working as expected. > Maven webapp archetype does not create correct project > -- > > Key: ARCHETYPE-231 > URL: http://jira.codehaus.org/browse/ARCHETYPE-231 > Project: Maven Archetype > Issue Type: Improvement > Environment: Eclipse 3.3 (Europa), m2eclipse 0.9.4.200806 >Reporter: Brennan Spies > Attachments: m2_webapp_arch.zip > > > Created a Maven project, selected the Maven webapp archetype. Zipped project > created is attached. > * Missing src/test/java, src/test/resources, and src/main/java source folders > (config in Eclipse) > * Actual folders are not created > * No stack traces in workspace log file -- 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
