[jira] Closed: (MINVOKER-14) release maven-invoker
[ http://jira.codehaus.org/browse/MINVOKER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINVOKER-14. Resolution: Fixed Release done. pom updated in rev 604574. > release maven-invoker > - > > Key: MINVOKER-14 > URL: http://jira.codehaus.org/browse/MINVOKER-14 > Project: Maven 2.x Invoker Plugin > Issue Type: Task >Affects Versions: 1.1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy >Priority: Blocker > Fix For: 1.1 > > > a new release of maven-invoker is needed to release maven-invoker-plugin 1.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: (MANTTASKS-97) add support for *
[ http://jira.codehaus.org/browse/MANTTASKS-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-97: --- Issue Type: Improvement (was: Bug) > add support for * > -- > > Key: MANTTASKS-97 > URL: http://jira.codehaus.org/browse/MANTTASKS-97 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0.8 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3324) livings
livings --- Key: MNG-3324 URL: http://jira.codehaus.org/browse/MNG-3324 Project: Maven 2 Issue Type: Bug Reporter: Derek Hval Attachments: aa.html livings -- 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-3324) livings
[ http://jira.codehaus.org/browse/MNG-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-3324. - Resolution: Won't Fix spam > livings > --- > > Key: MNG-3324 > URL: http://jira.codehaus.org/browse/MNG-3324 > Project: Maven 2 > Issue Type: Bug >Reporter: Derek Hval > Attachments: aa.html > > > livings -- 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: (NMAVEN-97) remove the alternative deploy plugin and change the lifecycle to use the standard one
[ http://jira.codehaus.org/browse/NMAVEN-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-97. -- Resolution: Fixed Fix Version/s: 0.14 > remove the alternative deploy plugin and change the lifecycle to use the > standard one > - > > Key: NMAVEN-97 > URL: http://jira.codehaus.org/browse/NMAVEN-97 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 >Reporter: Brett Porter > Fix For: 0.14 > > > see http://jira.codehaus.org/browse/NMAVEN-95#action_116451 for details -- 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: (NMAVEN-99) Need a VB .NET quickstart archetype
[ http://jira.codehaus.org/browse/NMAVEN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-99. -- Resolution: Fixed Fix Version/s: 0.14 Applied patch. > Need a VB .NET quickstart archetype > --- > > Key: NMAVEN-99 > URL: http://jira.codehaus.org/browse/NMAVEN-99 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 >Reporter: Teodoro Cue Jr. >Assignee: Teodoro Cue Jr. > Fix For: 0.14 > > Attachments: NMAVEN-99.patch > > > We need an archetype to generate a "Hello World" project for VB .NET similar > to the dotnet-simple archetype for C#. -- 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] Deleted: (MNG-3324) livings
[ http://jira.codehaus.org/browse/MNG-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter deleted MNG-3324: -- > livings > --- > > Key: MNG-3324 > URL: http://jira.codehaus.org/browse/MNG-3324 > Project: Maven 2 > Issue Type: Bug >Reporter: Derek Hval > > livings -- 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-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116980 ] Rob Hasselbaum commented on MECLIPSE-361: - Confirmed here as well. I think this deserves a higher priority than "minor" because it requires a very tedious workaround every time you run the eclipse:eclipse goal. Essentially, WTP 2.0 support isn't practical for day to day use until this is fixed. > eclipse plugin and WTP generating warnings in Europa > - > > Key: MECLIPSE-361 > URL: http://jira.codehaus.org/browse/MECLIPSE-361 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the > last maven-eclipse-plugin 2.5-SNAPSHOT >Reporter: Yann >Priority: Minor > Attachments: wtpTest.zip > > > The issue is regarding warnings in Europa and WTP: > "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be > exported or published. Runtime ClassNotFoundExceptions may result." > 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS) > 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.4 => I get the same behaviour in EUROPA (WARNINGS) > 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse > 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or > 2.5-SNAPSHOT => Everything is perfect, no more warnings > I create a simple test in order to reproduce the issue. > This test is a multi module application composed of 1 Ejb module and 1 Ear > module. > So at the top level Just run "mvn install eclipse:eclipse" > And then in an europa workspace import the projetcs and you should see the > warnings on the EJB module. > It will behave the same way if it exists other modules. > I notice that, in the case you update parameters on the eclipse plugin you > will need to remove projects from workspace and import them again. > otherwise some old parameter will stay in the eclipse cache... > let me know if you need other tests > Yann. -- 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: (MAVENUPLOAD-1857) Upload of release 1.6.2 for Simple XML
Upload of release 1.6.2 for Simple XML -- Key: MAVENUPLOAD-1857 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1857 Project: maven-upload-requests Issue Type: Bug Reporter: Niall Gallagher Attachments: simple-xml-1.6.2-bundle.jar, simple-xml-1.6.2-javadoc.jar, simple-xml-1.6.2.jar http://simple.sourceforge.net/simple-xml-1.6.2-bundle.jar http://simple.sourceforge.net http://www.whois.net/whois_new.cgi?d=simpleframework&tld=org -- 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-193) forced url links where parsed as WikiWords links
[ http://jira.codehaus.org/browse/DOXIA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan F. Codagnone updated DOXIA-193: Attachment: DOXIA-193_r17.diff > forced url links where parsed as WikiWords links > > > Key: DOXIA-193 > URL: http://jira.codehaus.org/browse/DOXIA-193 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone > Attachments: DOXIA-193_r17.diff > > > Links like [[http://twiki.com]] were transformed to wikiwords links. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 17 -- 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: (MSTAGE-2) The version parameter is ignored
The version parameter is ignored Key: MSTAGE-2 URL: http://jira.codehaus.org/browse/MSTAGE-2 Project: Maven 2.x Stage Plugin Issue Type: Bug Reporter: Dennis Lundberg The version parameter is currently ignored and the entire staging repository is synced, not just the given version or the current project. The parameter still needs to be provided, though. -- 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: (MSTAGE-1) RepositoryCopierTest fails on Windows
RepositoryCopierTest fails on Windows
-
Key: MSTAGE-1
URL: http://jira.codehaus.org/browse/MSTAGE-1
Project: Maven 2.x Stage Plugin
Issue Type: Bug
Reporter: Dennis Lundberg
This test has been excluded in the pom, but if the test is included it produces
the following surefire report:
{code}
---
Test set: org.apache.maven.plugins.stage.RepositoryCopierTest
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 27.641 sec <<<
FAILURE!
testCopy(org.apache.maven.plugins.stage.RepositoryCopierTest) Time elapsed:
27.547 sec <<< ERROR!
org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect.
Reason: java.net.ConnectException: Connection refused: connect
at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
at
org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:151)
at
org.apache.maven.plugins.stage.RepositoryCopierTest.testCopy(RepositoryCopierTest.java:41)
Caused by: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection
refused: connect
at com.jcraft.jsch.Util.createSocket(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158)
... 30 more
{code}
--
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-190) text like (=something=) is parsed incorrectly
[ http://jira.codehaus.org/browse/DOXIA-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-190. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied, thanks! > text like (=something=) is parsed incorrectly > - > > Key: DOXIA-190 > URL: http://jira.codehaus.org/browse/DOXIA-190 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: 13.diff > > > Text like: > (=something=) > is parsed incorrectly > Author: Christian Nardi > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 13. -- 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: (MAVENUPLOAD-1858) Dozer 4.2 upload request
Dozer 4.2 upload request Key: MAVENUPLOAD-1858 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1858 Project: maven-upload-requests Issue Type: Task Reporter: Matt Tierney Attachments: dozer-4.2-bundle.jar Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level. Dozer not only supports mapping between attribute names, but also converting between types. Many conversion scenarios are supported out of the box, but Dozer also allows you to specify custom conversions via XML. The mapper is used any time you need to take one type of Java Bean and map it to another type of Java Bean. Most field mapping can be done automatically by Dozer using reflection, but any custom mapping can be predescribed in XML format. Mapping is bi-directional so only one relationship between classes needs defining. If any property names on both objects are the same you do not even need to do any explicit property mapping for these fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-191) Display images given an url
[ http://jira.codehaus.org/browse/DOXIA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-191. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied, thanks! > Display images given an url > --- > > Key: DOXIA-191 > URL: http://jira.codehaus.org/browse/DOXIA-191 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-191_r14.diff > > > In the original release of the twiki parser, images weren't supported. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 14. -- 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-192) checkstyle
[ http://jira.codehaus.org/browse/DOXIA-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-192: Fix Version/s: 1.0-beta-1 Component/s: Module - Twiki > checkstyle > -- > > Key: DOXIA-192 > URL: http://jira.codehaus.org/browse/DOXIA-192 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Priority: Trivial > Fix For: 1.0-beta-1 > > Attachments: DOXIA-192_r15.diff, DOXIA-192_r16.diff > > > some checkstyle fixes in two patches. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 15 and 16. -- 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-192) checkstyle
[ http://jira.codehaus.org/browse/DOXIA-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-192. --- Assignee: Lukas Theussl Resolution: Fixed Applied, thanks! > checkstyle > -- > > Key: DOXIA-192 > URL: http://jira.codehaus.org/browse/DOXIA-192 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl >Priority: Trivial > Fix For: 1.0-beta-1 > > Attachments: DOXIA-192_r15.diff, DOXIA-192_r16.diff > > > some checkstyle fixes in two patches. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 15 and 16. -- 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-193) forced url links where parsed as WikiWords links
[ http://jira.codehaus.org/browse/DOXIA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-193. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied thanks! > forced url links where parsed as WikiWords links > > > Key: DOXIA-193 > URL: http://jira.codehaus.org/browse/DOXIA-193 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-193_r17.diff > > > Links like [[http://twiki.com]] were transformed to wikiwords links. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 17 -- 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-271) Page title reads Introduction to $project.name
[ http://jira.codehaus.org/browse/MSITE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-271. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-7 > Page title reads Introduction to $project.name > -- > > Key: MSITE-271 > URL: http://jira.codehaus.org/browse/MSITE-271 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: site-index.patch > > > Number one for google search maven site plugin gives: > Page title reads Introduction to $project.name > Also still has no version in strap line. > Maven is about versioning. -- 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: (MSITE-271) Page title reads Introduction to $project.name
[ http://jira.codehaus.org/browse/MSITE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116992 ] Dennis Lundberg commented on MSITE-271: --- I didn't apply your patch, because it reordered the goals at the same time as it changed their content. That makes it extremely hard to see what actually changed. But I added some formating like you had in the patch. > Page title reads Introduction to $project.name > -- > > Key: MSITE-271 > URL: http://jira.codehaus.org/browse/MSITE-271 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: site-index.patch > > > Number one for google search maven site plugin gives: > Page title reads Introduction to $project.name > Also still has no version in strap line. > Maven is about versioning. -- 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-194) Generate usefull links for WikiWords
[ http://jira.codehaus.org/browse/DOXIA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-194. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied, thanks! > Generate usefull links for WikiWords > > > Key: DOXIA-194 > URL: http://jira.codehaus.org/browse/DOXIA-194 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Twiki >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-194_r18.diff > > > [[WikiWord][text]] links used to generate links links like > #WikiWord. > This is not useful when the parser is used to generate a mvn-site site. With > this patch there is a new entity called WikiWordLinkResolver that is > responsible for resolving the href for the links. The default implementation > is generates links to WikiWord.html that can be used to build a site. > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 18 -- 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-127) Twiki module cannot parse two forced links in the same paragraph
[ http://jira.codehaus.org/browse/DOXIA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-127. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: (was: 1.0) 1.0-beta-1 Applied, thanks! > Twiki module cannot parse two forced links in the same paragraph > > > Key: DOXIA-127 > URL: http://jira.codehaus.org/browse/DOXIA-127 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-127_r19.diff > > > The regex used is too eager so it sucks up two (or more) links on the same > line, e.g. [[a]] b [[c]] parses as "[[" "a]] b [[c" "]]". THe fix is > relatively easy - just use a more specific regx to match for links (forced > and/or specifc). -- 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-195) Guess a title for the parsed page
[ http://jira.codehaus.org/browse/DOXIA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-195. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied, thanks! > Guess a title for the parsed page > - > > Key: DOXIA-195 > URL: http://jira.codehaus.org/browse/DOXIA-195 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Twiki >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-195-r21.diff, DOXIA-195_r20.diff > > > TWikiParser now tries to guess the title for the page. It tries to use the > first section title it found. This allows maven sites that use twiki pages to > have a title in the pages. > Author: Juan F. Codagnone (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 20 -- 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-196) Support for block
[ http://jira.codehaus.org/browse/DOXIA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-196. --- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.0-beta-1 Applied, thanks! > Support for block > > > Key: DOXIA-196 > URL: http://jira.codehaus.org/browse/DOXIA-196 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-196-r22.diff > > > Verbatim blocks initial support: > > some code... > > Author: Christian Nardi (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 22. -- 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-198) Support for images with links
[ http://jira.codehaus.org/browse/DOXIA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-198. --- Assignee: Lukas Theussl Resolution: Fixed Applied, thanks! > Support for images with links > -- > > Key: DOXIA-198 > URL: http://jira.codehaus.org/browse/DOXIA-198 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: DOXIA-198-r24.diff > > > Support for linked images. For example: >[[http://twiki.org][http://twiki.org/logo.png]] > in xhtml this is the same as >http://twiki.org";>http://twiki.org/logo.png"/> > Author: Juan F. Codagnone (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 24 -- 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-198) Support for images with links
[ http://jira.codehaus.org/browse/DOXIA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-198: Fix Version/s: 1.0-beta-1 Component/s: Module - Twiki > Support for images with links > -- > > Key: DOXIA-198 > URL: http://jira.codehaus.org/browse/DOXIA-198 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone > Fix For: 1.0-beta-1 > > Attachments: DOXIA-198-r24.diff > > > Support for linked images. For example: >[[http://twiki.org][http://twiki.org/logo.png]] > in xhtml this is the same as >http://twiki.org";>http://twiki.org/logo.png"/> > Author: Juan F. Codagnone (for Zauber S.A.) > Original SVN: https://code.zauber.com.ar/repos/doxia/branches/592499/ > revision 24 -- 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-197) more checkstyle issues
[ http://jira.codehaus.org/browse/DOXIA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116997 ] Lukas Theussl commented on DOXIA-197: - Can you either describe the issue or attach a patch? :) > more checkstyle issues > -- > > Key: DOXIA-197 > URL: http://jira.codehaus.org/browse/DOXIA-197 > Project: Maven Doxia > Issue Type: Task > Components: Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Juan F. Codagnone >Priority: Trivial > > more checkstyle issues -- 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-68) Adding twiki plugin as build extension makes goal site:site fail.
[ http://jira.codehaus.org/browse/DOXIA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-68: --- Fix Version/s: (was: 1.0) > Adding twiki plugin as build extension makes goal site:site fail. > - > > Key: DOXIA-68 > URL: http://jira.codehaus.org/browse/DOXIA-68 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-8 > Environment: WinXp, Java5 >Reporter: Martin Zeltner >Assignee: Lukas Theussl > > When I add the twiki module as an extension in my pom.xml the goal site:site > will fail. > Extension config snippet: > -- > > > > > doxia-module-twiki > org.apache.maven.doxia > 1.0-alpha-9-SNAPSHOT > > > > -- > Console output: > -- > mvn site:site -X > + Error stacktraces are turned on. > Maven version: 2.1-SNAPSHOT > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'site'. > [INFO] > > [INFO] Building EL4J module core > [INFO]task-segment: [site:site] > [INFO] > > [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] ** > [INFO] Starting Jakarta Velocity v1.4 > [INFO] RuntimeInstance initializing. > [INFO] Default Properties File: > org\apache\velocity\runtime\defaults\velocity.properties > [INFO] Default ResourceManager initializing. (class > org.apache.velocity.runtime.resource.ResourceManagerImpl) > [INFO] Resource Loader Instantiated: > org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader > [INFO] ClasspathResourceLoader : initialization starting. > [INFO] ClasspathResourceLoader : initialization complete. > [INFO] ResourceCache : initialized. (class > org.apache.velocity.runtime.resource.ResourceCacheImpl) > [INFO] Default ResourceManager initialization complete. > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach > [INFO] Created: 20 parsers. > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > [INFO] Velocimacro : allowInline = true : VMs can be defined inline in > templates > [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may > NOT replace previous VM definitions > [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be > global in scope if allowed. > [INFO] Velocimacro : initialization complete. > [INFO] Velocity successfully started. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.apache.maven.plugins:maven-jxr-plugin': Unable to find the mojo > 'org.apache.maven.plugins:maven-jxr-plugin:2.1-SNAPSHOT:jxr' in the plugin > 'org.apache > .maven.plugins:maven-jxr-plugin' > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports > from the plugin 'org.apache.maven.plugins:maven-jxr-plugin': Unable to find > the mojo 'org.apache.maven.plugins:maven-jxr-p > lugin:2.1-SNAPSHOT:jxr' in the plugin > 'org.apache.maven.plugins:maven-jxr-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:689) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:637) > at > org.apache.maven.l
[jira] Closed: (DOXIA-68) Adding twiki plugin as build extension makes goal site:site fail.
[ http://jira.codehaus.org/browse/DOXIA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-68. -- Assignee: Lukas Theussl Resolution: Won't Fix Closing, based on comments above. > Adding twiki plugin as build extension makes goal site:site fail. > - > > Key: DOXIA-68 > URL: http://jira.codehaus.org/browse/DOXIA-68 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Twiki >Affects Versions: 1.0-alpha-8 > Environment: WinXp, Java5 >Reporter: Martin Zeltner >Assignee: Lukas Theussl > Fix For: 1.0 > > > When I add the twiki module as an extension in my pom.xml the goal site:site > will fail. > Extension config snippet: > -- > > > > > doxia-module-twiki > org.apache.maven.doxia > 1.0-alpha-9-SNAPSHOT > > > > -- > Console output: > -- > mvn site:site -X > + Error stacktraces are turned on. > Maven version: 2.1-SNAPSHOT > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'site'. > [INFO] > > [INFO] Building EL4J module core > [INFO]task-segment: [site:site] > [INFO] > > [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] ** > [INFO] Starting Jakarta Velocity v1.4 > [INFO] RuntimeInstance initializing. > [INFO] Default Properties File: > org\apache\velocity\runtime\defaults\velocity.properties > [INFO] Default ResourceManager initializing. (class > org.apache.velocity.runtime.resource.ResourceManagerImpl) > [INFO] Resource Loader Instantiated: > org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader > [INFO] ClasspathResourceLoader : initialization starting. > [INFO] ClasspathResourceLoader : initialization complete. > [INFO] ResourceCache : initialized. (class > org.apache.velocity.runtime.resource.ResourceCacheImpl) > [INFO] Default ResourceManager initialization complete. > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include > [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach > [INFO] Created: 20 parsers. > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > [INFO] Velocimacro : allowInline = true : VMs can be defined inline in > templates > [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may > NOT replace previous VM definitions > [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be > global in scope if allowed. > [INFO] Velocimacro : initialization complete. > [INFO] Velocity successfully started. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.apache.maven.plugins:maven-jxr-plugin': Unable to find the mojo > 'org.apache.maven.plugins:maven-jxr-plugin:2.1-SNAPSHOT:jxr' in the plugin > 'org.apache > .maven.plugins:maven-jxr-plugin' > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports > from the plugin 'org.apache.maven.plugins:maven-jxr-plugin': Unable to find > the mojo 'org.apache.maven.plugins:maven-jxr-p > lugin:2.1-SNAPSHOT:jxr' in the plugin > 'org.apache.maven.plugins:maven-jxr-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:689) > at > org.apache.maven.lifecycle.DefaultLifecycleExecu
[jira] Updated: (NMAVEN-100) dotnet compiler component is not platform independent
[ http://jira.codehaus.org/browse/NMAVEN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-100: Summary: dotnet compiler component is not platform independent (was: dotnet compiler plugins are not platform independent) > dotnet compiler component is not platform independent > - > > Key: NMAVEN-100 > URL: http://jira.codehaus.org/browse/NMAVEN-100 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.15 >Reporter: Brett Porter > Attachments: > org.apache.maven.dotnet.compiler.impl.DotnetCompilerContextImplTest.txt > > > see attached surefire reports for failures when run without a Microsoft or > Mono install -- 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: (NMAVEN-100) dotnet compiler component tests are not platform independent
[ http://jira.codehaus.org/browse/NMAVEN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-100: Summary: dotnet compiler component tests are not platform independent (was: dotnet compiler component is not platform independent) > dotnet compiler component tests are not platform independent > > > Key: NMAVEN-100 > URL: http://jira.codehaus.org/browse/NMAVEN-100 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.15 >Reporter: Brett Porter > Attachments: > org.apache.maven.dotnet.compiler.impl.DotnetCompilerContextImplTest.txt > > > see attached surefire reports for failures when run without a Microsoft or > Mono install -- 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: (NMAVEN-100) dotnet compiler plugins are not platform independent
dotnet compiler plugins are not platform independent Key: NMAVEN-100 URL: http://jira.codehaus.org/browse/NMAVEN-100 Project: NMaven Issue Type: Bug Affects Versions: 0.15 Reporter: Brett Porter Attachments: org.apache.maven.dotnet.compiler.impl.DotnetCompilerContextImplTest.txt see attached surefire reports for failures when run without a Microsoft or Mono install -- 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: (MSITE-271) Page title reads Introduction to $project.name
[ http://jira.codehaus.org/browse/MSITE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117022 ] Benjamin Bentmann commented on MSITE-271: - bq. That makes it extremely hard to see what actually changed Sorry, maybe I should have provided incremental patches. To my shame I must confess, I never realized the importance of minimizing changes to the code base. You know, I just tried to improve it by applying some of the best practices about web design I have come across so far, e.g. proper hyperlinks. > Page title reads Introduction to $project.name > -- > > Key: MSITE-271 > URL: http://jira.codehaus.org/browse/MSITE-271 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: site-index.patch > > > Number one for google search maven site plugin gives: > Page title reads Introduction to $project.name > Also still has no version in strap line. > Maven is about versioning. -- 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: (MSITE-271) Page title reads Introduction to $project.name
[ http://jira.codehaus.org/browse/MSITE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117023 ] Dennis Lundberg commented on MSITE-271: --- Thanks for your efforts Benjamin. If I missed something from your patch please create another issue and attach a new patch to it. > Page title reads Introduction to $project.name > -- > > Key: MSITE-271 > URL: http://jira.codehaus.org/browse/MSITE-271 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Tim Pizey >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: site-index.patch > > > Number one for google search maven site plugin gives: > Page title reads Introduction to $project.name > Also still has no version in strap line. > Maven is about versioning. -- 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: (NMAVEN-100) dotnet compiler component tests are not platform independent
[ http://jira.codehaus.org/browse/NMAVEN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117024 ] Shane Isbell commented on NMAVEN-100: - The test is failing because the value that it is testing against uses Windows file separators, rather than platform specific ones. > dotnet compiler component tests are not platform independent > > > Key: NMAVEN-100 > URL: http://jira.codehaus.org/browse/NMAVEN-100 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.15 >Reporter: Brett Porter > Attachments: > org.apache.maven.dotnet.compiler.impl.DotnetCompilerContextImplTest.txt > > > see attached surefire reports for failures when run without a Microsoft or > Mono install -- 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-3179) [regression] incorrect handling of build errors in the reactor
[ http://jira.codehaus.org/browse/MNG-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3179. --- Assignee: John Casey (was: Jason van Zyl) Resolution: Fixed > [regression] incorrect handling of build errors in the reactor > -- > > Key: MNG-3179 > URL: http://jira.codehaus.org/browse/MNG-3179 > Project: Maven 2 > Issue Type: Bug > Components: Command Line, Reactor and workspace >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: John Casey >Priority: Minor > Fix For: 2.1-alpha-1 > > > example: introduce an error into the Maven trunk build (I removed the jdom > dependency from maven-model to cause compile failures), and run "mvn clean > install". > You get the error in the project, then the list of reactor projects with > success/fail/not built, then the errors again, then: > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] BUILD ERRORS > [INFO] > > [INFO] Total time: 6 seconds > [INFO] Finished at: Mon Sep 03 10:18:07 EST 2007 > [INFO] Final Memory: 20M/37M > [INFO] > > FATAL ERROR: Unable to configure the Maven application > For more information, run with the -e flag > I expect that: > * the build failures should only be output once in the --fail-fast mode > * it should be BUILD FAILURES, not BUILD ERRORS > * the FATAL ERROR message should not be present at the end -- 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-3186) First iteration of concise, user-centric error reporting
[ http://jira.codehaus.org/browse/MNG-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3186. --- Assignee: John Casey Resolution: Fixed We've got a reporting system in place now, covered by implementations of: org.apache.maven.errors.CoreErrorReporter org.apache.maven.project.error.ProjectErrorReporter These provide a host of very specific methods taking relevant context information from aspect bindings in the build, and rendering one concise, user-oriented message per method. They are meant to be deadly simple, without a lot of decision logic...just to help make the reporting api explicit for anyone who wants to implement it. BTW, The MavenExecutionRequest and Configuration (in the embedder) both have methods for setting a custom reporter, to allow IDE integrators better access to the context information. In CLI mode, all error reports are flushed out at the end of the build, via the CLIReportingUtils utility class. > First iteration of concise, user-centric error reporting > > > Key: MNG-3186 > URL: http://jira.codehaus.org/browse/MNG-3186 > Project: Maven 2 > Issue Type: New Feature > Components: Embedding >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 2.1-alpha-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] Closed: (MNG-3175) Take another pass over the exceptions that can occur during execution and project handling
[ http://jira.codehaus.org/browse/MNG-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3175. --- Assignee: John Casey (was: Jason van Zyl) Resolution: Fixed I've started with the implementations of Exception that are handled in the outermost layers of Maven (The embedder and cli), and encoded the specific error conditions that lead to those exceptions into methods in the CoreErrorReporter and ProjectErrorReporter interfaces, diving in up to two or three exception-wrapping layers sometimes to get at an error that's more useful to report on. Obviously, as new behavior (or behavioral changes) evolve, it may become necessary to modify the error reporter interfaces. However, the api should probably be relatively stable, unless/until we get around to refactoring DefaultMavenProjectBuilder, DefaultLifecycleExecutor, or DefaultPluginManager. At that time, the aspects binding the reporter apis to the main body of code will have to be adjusted to collect the proper context elements (project instances, files, etc.). > Take another pass over the exceptions that can occur during execution and > project handling > -- > > Key: MNG-3175 > URL: http://jira.codehaus.org/browse/MNG-3175 > Project: Maven 2 > Issue Type: Task > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Jason van Zyl >Assignee: John Casey > Fix For: 2.1-alpha-1 > > > The problems that can occur during execution and project handing: > - POM parsing errors > - missing metadata > - error retrieving metadata > - version range violations > - circular dependency violations > - missing artifacts > - error retrieving artifacts > I have most of this handled in the ArtifactResolutionResult, but the > ProjectBuildingResult and the MavenExecutionResult need some work to make > sure that everything is passed through correctly. This is of the utmost > important for embedding because it means from the UI that integrators can > give users exact details as to problems that occur. Milos has really gone a > long way to work around the fact we don't do 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] Commented: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117040 ] Gerhard Langs commented on MINVOKER-18: --- Oliver your fix works fine Thanks, Gerhard > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117039 ] Gerhard Langs commented on MINVOKER-18: --- Oliver your fix works fine Thanks, Gerhard > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117039 ] gerhard6 edited comment on MINVOKER-18 at 12/17/07 1:10 AM: - Olivier your fix works fine Thanks, Gerhard was (Author: gerhard6): Oliver your fix works fine Thanks, Gerhard > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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: (MINVOKER-18) two executions of the same pom causes a prooblem with interpolated-pom.xml
[ http://jira.codehaus.org/browse/MINVOKER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117040 ] gerhard6 edited comment on MINVOKER-18 at 12/17/07 1:41 AM: - ... was (Author: gerhard6): Oliver your fix works fine Thanks, Gerhard > two executions of the same pom causes a prooblem with interpolated-pom.xml > -- > > Key: MINVOKER-18 > URL: http://jira.codehaus.org/browse/MINVOKER-18 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: latest 1.1-SNAPSHOT Version, maven-2.0.7 >Reporter: Gerhard Langs >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: invoker-18.patch, invoker-18.patch, > pom-interpolation2-invoked.xml, pom-interpolation2.xml > > > TestCase: >pom-interpolated2.xml uses invoker to invoke > "pom-interpolated2-invoked.xml in 2 "executions". > invocation: >mvn -f pom-interpolated2.xml test -e > the second execution fails, because it is unable to create the > "interpolated-pom.xml". > Proposed solution: >- dont tag the interpolated-pom.xml as "deleteOnExit", >- delete that file at the end of every execution. > Will try to provide a patch > Greetings, Gerhard > Output: > ... > Caused by: org.apache.maven.plugin.MojoExecutionException: fail to create > file > D:\maven\maven-invoker-plugin\src\test\resources\unit\interpolation2\.\interpolated-pom.xml > at > org.apache.maven.plugin.invoker.InvokerMojo.buildInterpolatedPomFile(InvokerMojo.java:997) > at > org.apache.maven.plugin.invoker.InvokerMojo.runBuild(InvokerMojo.java:458) > at > org.apache.maven.plugin.invoker.InvokerMojo.execute(InvokerMojo.java:341) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) -- 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
