[jira] Updated: (DOXIA-160) Book output in doc-book format is not well formed
[ http://jira.codehaus.org/browse/DOXIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Syer updated DOXIA-160: Attachment: DOXIA-160.1.patch Updated patch DOXIA-160.1.patch after SVN update - there was a conflict which probably explains why the old patch couldn't be applied. > Book output in doc-book format is not well formed > - > > Key: DOXIA-160 > URL: http://jira.codehaus.org/browse/DOXIA-160 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > Fix For: 1.0-beta-1 > > Attachments: DOXIA-160.1.patch, DOXIA-160.patch, mylyn-context.zip, > mylyn-context.zip > > > I tried using the output from a book in doc-book to run it through a > postprocesing step with docbook and found that it barfed on the source > generated by doxia. Not surprising when you consider that it is not well > formed, e.g. it has two <<>> headers in it, and no root element: > +--- > > BarThis is bar > > > > SpamThis is spam > > > > +--- > When I changed it to this it worked better > +--- > "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> > > BarThis is bar > > > SpamThis is spam > > > > +--- -- 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-160) Book output in doc-book format is not well formed
[ http://jira.codehaus.org/browse/DOXIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Syer updated DOXIA-160: Attachment: mylyn-context.zip > Book output in doc-book format is not well formed > - > > Key: DOXIA-160 > URL: http://jira.codehaus.org/browse/DOXIA-160 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > Fix For: 1.0-beta-1 > > Attachments: DOXIA-160.1.patch, DOXIA-160.patch, mylyn-context.zip, > mylyn-context.zip > > > I tried using the output from a book in doc-book to run it through a > postprocesing step with docbook and found that it barfed on the source > generated by doxia. Not surprising when you consider that it is not well > formed, e.g. it has two <<>> headers in it, and no root element: > +--- > > BarThis is bar > > > > SpamThis is spam > > > > +--- > When I changed it to this it worked better > +--- > "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> > > BarThis is bar > > > SpamThis is spam > > > > +--- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-186) Use simplified DTD for DocBook?
Use simplified DTD for DocBook? --- Key: DOXIA-186 URL: http://jira.codehaus.org/browse/DOXIA-186 Project: Maven Doxia Issue Type: Task Components: Book Affects Versions: 1.0-alpha-9 Reporter: Dave Syer Fix For: 1.0-beta-1 >From Lukas: Since it's supposed to be a module for simplified docbook, >shouldn't they be given by http://www.docbook.org/xml/simple/sdocbook/ (I really don't know anything about docbook, sorry if this next to the point). I didn't try it yet - I put in the 4.4 XML DTD because that's the one that works best with the agilejava site plugin. It should be configurable, but I would be happy to hard code the simple DTD for the short term as long as it means I can process the output. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-187) Use AbstractSinkTest in DocBookBookSinkTest
Use AbstractSinkTest in DocBookBookSinkTest --- Key: DOXIA-187 URL: http://jira.codehaus.org/browse/DOXIA-187 Project: Maven Doxia Issue Type: Test Components: Book Affects Versions: 1.0-alpha-9 Reporter: Dave Syer Priority: Minor Fix For: 1.0-beta-1 Lukas: the DocBookBookSinkTest should be written the same way as DocBookSinkTest, ie extends AbstractSinkTest (not AbstractSinkTestCase). Dave: I'm not so sure it's a good idea, but I'll put it in JIRA anyway. The AbstractSinkTest would just test the base class again (which has already been tested in the docbook module). It would be better to have a real unit test for the BookSink which didn't depend on the base class behaviour at all. Could be achieved by adopting a delegate pattern for the BookSink instead of extending the DocBookSink - but is it worth the effort when there is a regression test that covers the book extensions pretty well? -- 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-166) Book output ignores book, chapter and section titles
[ http://jira.codehaus.org/browse/DOXIA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113372 ] Dave Syer commented on DOXIA-166: - I checked the PDF, Xhtml, Rtf, latex and xdoc outputs for the sample in the unit test (plexus-user-guide, ha, ha), and they actually look like they respect the titles. So it was only DocBook that wasn't working as far as I can tell. Once the patch for DOXIA-160 is applied this issue can probably be closed as well. > Book output ignores book, chapter and section titles > > > Key: DOXIA-166 > URL: http://jira.codehaus.org/browse/DOXIA-166 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > Fix For: 1.0-beta-1 > > Attachments: docbook-test-patch.txt > > > Book output ignores book, chapter and section titles (for xhtml and doc-book > at least). For PDF the chapter titles are used but not the book or sections. > Maybe this is intentional (but then what are they there for in the book > model)? At least there should be some configuration to switch on/off titles? -- 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: (CONTINUUM-1557) Appearance is not saved
Appearance is not saved Key: CONTINUUM-1557 URL: http://jira.codehaus.org/browse/CONTINUUM-1557 Project: Continuum Issue Type: Bug Components: Web - Configuration Affects Versions: 1.1-beta-4 Reporter: Olivier Lamy Appearance is not saved an upgrade to commons-configuration 1.4 is needed to fix combinedconfiguration issue. -- 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: (CONTINUUM-1557) Appearance is not saved
[ http://jira.codehaus.org/browse/CONTINUUM-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1557: Assignee: Olivier Lamy Fix Version/s: 1.1 > Appearance is not saved > > > Key: CONTINUUM-1557 > URL: http://jira.codehaus.org/browse/CONTINUUM-1557 > Project: Continuum > Issue Type: Bug > Components: Web - Configuration >Affects Versions: 1.1-beta-4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1 > > > Appearance is not saved an upgrade to commons-configuration 1.4 is needed to > fix combinedconfiguration issue. -- 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: (MEJB-30) Make it possible to put full file name in manifest classpath
Make it possible to put full file name in manifest classpath Key: MEJB-30 URL: http://jira.codehaus.org/browse/MEJB-30 Project: Maven 2.x Ejb Plugin Issue Type: Improvement Affects Versions: 2.1 Environment: Maven 2.0.7 Reporter: Martin von Zweigbergk The ear and war plugins have a parameter called fileNameMapping. When this is set to "full", the groupId of any dependency is prefixed to the filename before packaging it in the ear or war file. To make this feature useful with included EJBs, it must be configurable to prefix the filename in the same way in the classpath entries in the manifest file of ejb jars. -- 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: (CONTINUUM-1558) ability to customise web templates
ability to customise web templates -- Key: CONTINUUM-1558 URL: http://jira.codehaus.org/browse/CONTINUUM-1558 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-beta-2 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 1.1 it'd be good to be able to customise the footer - for the ASF install on vmbuild I'd like to be able to link to the correct place to report issues/get help. -- 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: (CONTINUUM-1558) ability to customise web templates
[ http://jira.codehaus.org/browse/CONTINUUM-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1558: Description: it'd be good to be able to customise web ui (user could choose skins). (was: it'd be good to be able to customise the footer - for the ASF install on vmbuild I'd like to be able to link to the correct place to report issues/get help.) Fix Version/s: (was: 1.1) Future Issue Type: New Feature (was: Improvement) > ability to customise web templates > -- > > Key: CONTINUUM-1558 > URL: http://jira.codehaus.org/browse/CONTINUUM-1558 > Project: Continuum > Issue Type: New Feature > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: Future > > > it'd be good to be able to customise web ui (user could choose skins). -- 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: (CONTINUUM-1558) ability to customise web templates
[ http://jira.codehaus.org/browse/CONTINUUM-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1558: Fix Version/s: (was: Future) To Sort > ability to customise web templates > -- > > Key: CONTINUUM-1558 > URL: http://jira.codehaus.org/browse/CONTINUUM-1558 > Project: Continuum > Issue Type: New Feature > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: To Sort > > > it'd be good to be able to customise web ui (user could choose skins). -- 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: (CONTINUUM-1397) ability to customise html footer
[ http://jira.codehaus.org/browse/CONTINUUM-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1397: Summary: ability to customise html footer (was: ability to customise web templates) update the summary the previous was too generic (an other issue has been created for this CONTINUUM-1558) > ability to customise html footer > > > Key: CONTINUUM-1397 > URL: http://jira.codehaus.org/browse/CONTINUUM-1397 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Brett Porter >Assignee: Olivier Lamy > Fix For: 1.1 > > > it'd be good to be able to customise the footer - for the ASF install on > vmbuild I'd like to be able to link to the correct place to report issues/get > help. -- 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: (CONTINUUM-1397) ability to customise html footer
[
http://jira.codehaus.org/browse/CONTINUUM-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113376
]
Olivier Lamy commented on CONTINUUM-1397:
-
Wendy in : ${appserver.home}/conf/continuum.xml
> ability to customise html footer
>
>
> Key: CONTINUUM-1397
> URL: http://jira.codehaus.org/browse/CONTINUUM-1397
> Project: Continuum
> Issue Type: Improvement
> Components: Web - UI
>Affects Versions: 1.1-beta-2
>Reporter: Brett Porter
>Assignee: Olivier Lamy
> Fix For: 1.1
>
>
> it'd be good to be able to customise the footer - for the ASF install on
> vmbuild I'd like to be able to link to the correct place to report issues/get
> help.
--
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: (CONTINUUM-1397) ability to customise html footer
[ http://jira.codehaus.org/browse/CONTINUUM-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1397. --- Resolution: Fixed comitted rev 593773 > ability to customise html footer > > > Key: CONTINUUM-1397 > URL: http://jira.codehaus.org/browse/CONTINUUM-1397 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Brett Porter >Assignee: Olivier Lamy > Fix For: 1.1 > > > it'd be good to be able to customise the footer - for the ASF install on > vmbuild I'd like to be able to link to the correct place to report issues/get > help. -- 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: (CONTINUUM-1557) Appearance is not saved
[ http://jira.codehaus.org/browse/CONTINUUM-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1557. --- Resolution: Fixed comitted rev 593773. (upgrade plexus-registry version which has now a dependency to commons-configuration 1.4) > Appearance is not saved > > > Key: CONTINUUM-1557 > URL: http://jira.codehaus.org/browse/CONTINUUM-1557 > Project: Continuum > Issue Type: Bug > Components: Web - Configuration >Affects Versions: 1.1-beta-4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1 > > > Appearance is not saved an upgrade to commons-configuration 1.4 is needed to > fix combinedconfiguration issue. -- 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: (CONTINUUM-1559) loading company pom doesn't use repositories declared in settings.xml
loading company pom doesn't use repositories declared in settings.xml - Key: CONTINUUM-1559 URL: http://jira.codehaus.org/browse/CONTINUUM-1559 Project: Continuum Issue Type: Bug Reporter: Olivier Lamy -- 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: (CONTINUUM-1559) loading company pom doesn't use repositories declared in settings.xml
[ http://jira.codehaus.org/browse/CONTINUUM-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1559: Assignee: Olivier Lamy Fix Version/s: 1.1 > loading company pom doesn't use repositories declared in settings.xml > - > > Key: CONTINUUM-1559 > URL: http://jira.codehaus.org/browse/CONTINUUM-1559 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1, 1.1-beta-2, 1.1-beta-3, 1.1-beta-4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 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: (CONTINUUM-1559) loading company pom doesn't use repositories declared in settings.xml
[ http://jira.codehaus.org/browse/CONTINUUM-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1559: Affects Version/s: 1.1-beta-1 1.1-beta-2 1.1-beta-3 1.1-beta-4 > loading company pom doesn't use repositories declared in settings.xml > - > > Key: CONTINUUM-1559 > URL: http://jira.codehaus.org/browse/CONTINUUM-1559 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1, 1.1-beta-2, 1.1-beta-3, 1.1-beta-4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 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] Commented: (MWAR-130) warSourceExcludes not working for war:inplace
[ http://jira.codehaus.org/browse/MWAR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113383 ] Stephane Nicoll commented on MWAR-130: -- How the heck could it be used? The purpose of the war:inplace goal is to build the WAR file directly from the source tree. Do you expect the war plugin to remove your source files according to this parameter? > warSourceExcludes not working for war:inplace > - > > Key: MWAR-130 > URL: http://jira.codehaus.org/browse/MWAR-130 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 >Reporter: Adrian > > warSourceExcludes appears to work only for war:war but not war:inplace or > war:exploded. > This would be usefull so JARs aren't put in src/main/webapp/WEB-INF/lib with > war:inplace. > Related to mails : > http://www.nabble.com/-war--warSourceExcludes-not-working-for-war%3Ainplace-tf4773104s177.html#a13654205 > and > http://www.nabble.com/Is-it-possible-to-customize-maven-war-plugin-so-JARs-aren%27t-put-in-src-main-webapp-WEB-INF-lib-when-using-war%3Ainplace--tf4466701s177.html#a12759424 -- 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: (MANTTASKS-82) Environment variables are not resolved in settings files
[
http://jira.codehaus.org/browse/MANTTASKS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MANTTASKS-82.
--
Assignee: Herve Boutemy
Resolution: Fixed
Fix Version/s: 2.0.8
fixed in r593783
> Environment variables are not resolved in settings files
>
>
> Key: MANTTASKS-82
> URL: http://jira.codehaus.org/browse/MANTTASKS-82
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
>Affects Versions: 2.0.7
>Reporter: Gerhard Langs
>Assignee: Herve Boutemy
> Fix For: 2.0.8
>
>
> (Pulled Item 2 of Issue 80 out to this Issue):
> when i use a settings file in antlib like in
>value="d:/laglap3/HEAD_CI/tools/maven-2.0.7/conf/settings.xml"/>
>
> and, in the settings file, I use a environment variable, like:
>${env.MPA_ROOT}/mavenrepo
> then this environment variable MPA_ROOT is NOT resolved to its value.
> Note that this is inconsistent to the behaviour of mvn.bat
--
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: (MRELEASE-230) release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies
[ http://jira.codehaus.org/browse/MRELEASE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113386 ] John Allen commented on MRELEASE-230: - did you develop a patch for this? > release:prepare cannot update the version of a module in a multi-module build > if you have both normal artifact and attached artifact in dependencies > > > Key: MRELEASE-230 > URL: http://jira.codehaus.org/browse/MRELEASE-230 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Chris Wewerka > Attachments: release-test.zip > > > Following situation: > you have a multimodule build with 2 modules A,B, and B has two dependencies > to A, one for the "normal" jar artifact and one for an attached artifact > (e.g. the test-jar of A). > The release will fail with: > ... > [INFO] Transforming 'O2 Release test Base Module'... > [INFO] Checking out file: > E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\pom.xml > [INFO] Transforming 'release-test-module-one'... > [INFO] Checking out file: > E:\prj\o2\branches\main_latest\sd_pa\tools\release-test\release-test-module-one\pom.xml > [INFO] Transforming 'release-test-module-two'... > [INFO] Updating release-test-module-one to 5.0.2 > [INFO] Updating release-test-module-one to 5.0.2 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] The version could not be updated: 5.0.2 > [INFO] > > [INFO] For more information, run Maven with the -e switch -- 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: (CONTINUUM-1560) Error with group summary auto-refresh after performing a release
Error with group summary auto-refresh after performing a release
Key: CONTINUUM-1560
URL: http://jira.codehaus.org/browse/CONTINUUM-1560
Project: Continuum
Issue Type: Bug
Components: Web - UI
Affects Versions: 1.1-beta-4
Environment: 1.1-beta-4 on Linux. Firefox.
Reporter: Wendy Smoak
After completing the release process, click Done to return to the Group Summary
page.
The URL at this time is http://example.com/continuum/releaseCleanup.action.
Wait for it to automatically refresh. It should display the list of groups and
project counts again, but instead you get:
{noformat}
Error Occurred
org.apache.maven.continuum.ContinuumException: could not find project group
containing 0
Show/hide Stack Trace
org.apache.maven.continuum.ContinuumException: could not find project
group containing 0
at
org.apache.maven.continuum.DefaultContinuum.getProjectGroupByProjectId(DefaultContinuum.java:265)
at
org.apache.maven.continuum.web.action.ReleaseCleanupAction.getProjectGroupName(ReleaseCleanupAction.java:97)
at
org.apache.maven.continuum.web.action.ReleaseCleanupAction.execute(ReleaseCleanupAction.java:45)
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
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358)
at
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
at
org.codehaus.plexus.xwork.interceptor.PlexusReleaseComponentInterceptor.intercept(PlexusReleaseComponentInterceptor.java:69)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:72)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:100)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.D
[jira] Closed: (MANTTASKS-94) Maven ant tasks do not load correctly the settings.xml file (overriding central repository)
[ http://jira.codehaus.org/browse/MANTTASKS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-94. -- Assignee: Herve Boutemy Resolution: Won't Fix Profiles are not supported yet, and in your case they are not necessary. If you want to use Archiva instead of a direct connection to the central repo, just use a mirrorOf section in your settings.xml as explained in the documentation: http://maven.apache.org/ant-tasks.html, "The Settings File" section > Maven ant tasks do not load correctly the settings.xml file (overriding > central repository) > --- > > Key: MANTTASKS-94 > URL: http://jira.codehaus.org/browse/MANTTASKS-94 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.7 > Environment: Linux >Reporter: Dimo Velev >Assignee: Herve Boutemy > Attachments: settings.xml > > > When I run an ant script which uses maven tasks to download dependencies it > fails to do so. After turning the verbose mode in ant and in maven I have > found out the configuration file is correctly found and loaded > ([artifact:pom] Loading Maven settings file: > /home/deployer/.m2/settings.xml). In my settings I basically define a profile > which is always active and overrides the maven central repository with a > local installation of artifactory (I have attached my settings.xml file). > Running mvn in the console works as expected using the same settings 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] Closed: (MANTTASKS-16) Antlib attempts to download version.txt files from legacy repository.
[ http://jira.codehaus.org/browse/MANTTASKS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-16. -- Resolution: Cannot Reproduce if the problem persists, please reopen the issue and provide a test case > Antlib attempts to download version.txt files from legacy repository. > - > > Key: MANTTASKS-16 > URL: http://jira.codehaus.org/browse/MANTTASKS-16 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Environment: Reproduced on Solaris, Linux, and Win32. >Reporter: Tim Clemons > > When attempting to download artifacts from a legacy repository, the build > sometimes fails with the following error: > Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: > Unable to retrieve metadata > On checking the maven-proxy's log, it appears that files of the format > --SNAPSHOT-version.txt are getting queried. These don't > appear to be a part of Maven 1.x builds and so shouldn't trigger a failure > condition if they can't be found. -- 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-13) Ant Tasks use of is inconsistent
[ http://jira.codehaus.org/browse/MANTTASKS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-13: --- Affects Version/s: 2.0.7 > Ant Tasks use of is inconsistent > - > > Key: MANTTASKS-13 > URL: http://jira.codehaus.org/browse/MANTTASKS-13 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.7 > Environment: cygwin/win32 >Reporter: jonathan anderson >Priority: Minor > > In the ant build file, authentication works fine if you do: > >version="1.0-SNAPSHOT"/> >url="https://blah.blah.edu:8081/maven2";> > > > > But, if you do >url="https://blah.blah.edu:8081/maven2";> > > > >version="1.0-SNAPSHOT"/> > > > It fails mysteriously. The remoteRepository is found, but the http client > does not respond to the authentication challenge. The only error which > presents is a vague "Error transferring file" message -- 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-13) Ant Tasks use of is inconsistent
[ http://jira.codehaus.org/browse/MANTTASKS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-13: --- Affects Version/s: 2.0.4 2.0.6 > Ant Tasks use of is inconsistent > - > > Key: MANTTASKS-13 > URL: http://jira.codehaus.org/browse/MANTTASKS-13 > Project: Maven 2.x Ant Tasks > Issue Type: Bug >Affects Versions: 2.0.4, 2.0.6, 2.0.7 > Environment: cygwin/win32 >Reporter: jonathan anderson >Priority: Minor > > In the ant build file, authentication works fine if you do: > >version="1.0-SNAPSHOT"/> >url="https://blah.blah.edu:8081/maven2";> > > > > But, if you do >url="https://blah.blah.edu:8081/maven2";> > > > >version="1.0-SNAPSHOT"/> > > > It fails mysteriously. The remoteRepository is found, but the http client > does not respond to the authentication challenge. The only error which > presents is a vague "Error transferring file" message -- 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: (MANTTASKS-39) Flattened fileset reference
[ http://jira.codehaus.org/browse/MANTTASKS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-39. -- Resolution: Won't Fix this issue can't be solved by Maven: the fileset references files in the local repository, with complete directory structure. It a problem with the Ant's war task if there is no feature to flatten the fileset when referencing it > Flattened fileset reference > --- > > Key: MANTTASKS-39 > URL: http://jira.codehaus.org/browse/MANTTASKS-39 > Project: Maven 2.x Ant Tasks > Issue Type: Sub-task > Components: dependencies task >Reporter: Anders Harrisson >Priority: Minor > > Having the dependency fileset-reference flattened would really simplify some > use of it, ie direct reference of the fileset in the lib-element of the > War-task. -- 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-1810) update ANTLR to version 3.0.1
update ANTLR to version 3.0.1 - Key: MAVENUPLOAD-1810 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1810 Project: maven-upload-requests Issue Type: New Feature Reporter: Erik Putrycz Attachments: antlr-3.0.1-bundle.jar, antlr-runtime-3.0.1-bundle.jar, stringtemplate-3.1-b1-bundle.jar -- 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-1810) update ANTLR to version 3.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Putrycz updated MAVENUPLOAD-1810: -- Attachment: antlr-3.0.1-bundle.jar fixed pom descriptor in the 3.0.1 bundle. Was missing the antlr 2.7.7 dependency. This only affects the compiler not the runtime. > update ANTLR to version 3.0.1 > - > > Key: MAVENUPLOAD-1810 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1810 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Erik Putrycz > Attachments: antlr-3.0.1-bundle.jar, antlr-3.0.1-bundle.jar, > antlr-runtime-3.0.1-bundle.jar, stringtemplate-3.1-b1-bundle.jar > > -- 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-1811) In regards to adding Annsor to the Maven Central Repository.
In regards to adding Annsor to the Maven Central Repository. Key: MAVENUPLOAD-1811 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1811 Project: maven-upload-requests Issue Type: Task Reporter: Richard Burton Attachments: annsor-core-1.0.1-bundle.jar I'm opening a request to have Annsor added to the Maven Central Repository. A brief description of Annsor: Annsor is a lightweight runtime annotation processor. The purpose of Annsor is to simplify processing of Annotations during runtime, without sacrificing performance or affecting your API. Thank you, Richard L. Burton III -- 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: (MRM-586) entire proxy request fails if a queried remote repository throws a proxyexception
entire proxy request fails if a queried remote repository throws a proxyexception - Key: MRM-586 URL: http://jira.codehaus.org/browse/MRM-586 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-4 Reporter: Brett Porter Fix For: 1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-586) entire proxy request fails if a queried remote repository throws a proxyexception
[ http://jira.codehaus.org/browse/MRM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-586. Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0 > entire proxy request fails if a queried remote repository throws a > proxyexception > - > > Key: MRM-586 > URL: http://jira.codehaus.org/browse/MRM-586 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-4 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3280) Keep getting required artifacts are missing when compiling geotool using maven
Keep getting required artifacts are missing when compiling geotool using maven -- Key: MNG-3280 URL: http://jira.codehaus.org/browse/MNG-3280 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.7 Reporter: F. Ahmed Missing: -- 1) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-webdav \ -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-webdav \ -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.geotools:gt2:pom:2.3.3 2) org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2 2) org.codehaus.plexus:plexus-utils:jar:1.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.geotools:gt2:pom:2.3.3 2) org.codehaus.plexus:plexus-utils:jar: 1.1 -- 2 required artifacts are missing. for artifact: org.geotools:gt2:pom:2.3.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), ibiblio (http://www.ibiblio.org/maven2), refractions (http://lists.refractions.net/m2), geotools (http://maven.geotools.fr/repository) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 50 minutes 54 seconds [INFO] Finished at: Sun Oct 28 11:35:51 AST 2007 [INFO] Final Memory: 10M/197M [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
