[jira] Commented: (MPIR-28) improve convergence report
[ http://jira.codehaus.org/browse/MPIR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103968 ] Brett Porter commented on MPIR-28: -- I was probably thinking of conflict resolution strategy (which we don't really have yet) - not sure. I'd ignore it :) > improve convergence report > -- > > Key: MPIR-28 > URL: http://jira.codehaus.org/browse/MPIR-28 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Brett Porter > > things to improve: > * alignment > * icons > * transitive dependencies included > * strategy for ranges > * ignore snapshots in the reactor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-28) improve convergence report
[ http://jira.codehaus.org/browse/MPIR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103965 ] Dennis Lundberg commented on MPIR-28: - Brett, what did you mean by "strategy for ranges"? > improve convergence report > -- > > Key: MPIR-28 > URL: http://jira.codehaus.org/browse/MPIR-28 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Brett Porter > > things to improve: > * alignment > * icons > * transitive dependencies included > * strategy for ranges > * ignore snapshots in the reactor -- 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: (MPIR-71) Include transitive dependencies in convergence report
[ http://jira.codehaus.org/browse/MPIR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-71: Description: (was: things to improve: * alignment * icons * transitive dependencies included * strategy for ranges * ignore snapshots in the reactor) > Include transitive dependencies in convergence report > - > > Key: MPIR-71 > URL: http://jira.codehaus.org/browse/MPIR-71 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Reporter: Dennis Lundberg > -- 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: (MPIR-71) Include transitive dependencies in convergence report
Include transitive dependencies in convergence report - Key: MPIR-71 URL: http://jira.codehaus.org/browse/MPIR-71 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Reporter: Dennis Lundberg things to improve: * alignment * icons * transitive dependencies included * strategy for ranges * ignore snapshots in the reactor -- 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-56) clean up doxia api and code
[ http://jira.codehaus.org/browse/DOXIA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103956 ] Vincent Siveton commented on DOXIA-56: -- Small discussion about this http://www.nabble.com/Doxia-core-clean-up-tf4212325.html > clean up doxia api and code > --- > > Key: DOXIA-56 > URL: http://jira.codehaus.org/browse/DOXIA-56 > Project: Maven Doxia > Issue Type: Task > Components: Core >Reporter: Brett Porter > Fix For: 1.0-beta-1 > > > there is a lot of "throws Exception" and uncertainty in the API. It needs a > clean up before 1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-137) Add comments to sink API
[ http://jira.codehaus.org/browse/DOXIA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103947 ] Dennis Lundberg commented on DOXIA-137: --- This sounds like a good addition to the API. At least some of the generated formats supports comments, the others can just do nothing. > Add comments to sink API > > > Key: DOXIA-137 > URL: http://jira.codehaus.org/browse/DOXIA-137 > Project: Maven Doxia > Issue Type: Improvement > Components: Sink API >Affects Versions: 1.0-alpha-8 >Reporter: Lukas Theussl > Fix For: 1.0-beta-1 > > > Comments are often an important part of source documents, they should be > preserved by doxia transformations. -- 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-106) When using a template from a custom skin, default images and css from doxia-site-renderer are not copied to rendered site
[ http://jira.codehaus.org/browse/DOXIA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIA-106. - Resolution: Won't Fix Fix Version/s: (was: 1.0) > When using a template from a custom skin, default images and css from > doxia-site-renderer are not copied to rendered site > - > > Key: DOXIA-106 > URL: http://jira.codehaus.org/browse/DOXIA-106 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer >Affects Versions: 1.0-alpha-8 > Environment: maven-site-plugin 2.0-beta-5; maven 2.0.5 >Reporter: John Casey > > I've created my own Velocity template for rendering site pages, and included > it in my own site skin. The skin makes no changes to the built-by image, or > the maven-base or print CSS files. However, when I use the new skin, none of > these files are found in the site. This leads to massive formatting problems > and missing icons/images all over the place. > When I copy the images/ and css/ directories out of the > doxia-site-renderer/src/main/resources/... directory structure into my skin, > all is fine. -- 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-112) A single plexus JAR must be used to avoid problems with older versions of Maven
[ http://jira.codehaus.org/browse/DOXIA-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIA-112. - Assignee: Jason van Zyl Resolution: Fixed Fixed in r561197 and r561199. > A single plexus JAR must be used to avoid problems with older versions of > Maven > --- > > Key: DOXIA-112 > URL: http://jira.codehaus.org/browse/DOXIA-112 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 1.0-alpha-9 > > -- 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-71) APT: Allow figure as link
[
http://jira.codehaus.org/browse/DOXIA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed DOXIA-71.
Resolution: Won't Fix
This is not possible to do with the APT syntax.
We follow the spec for aptconvert:
http://www.xmlmind.com/_aptconvert/docs/userguidetoc.html
> APT: Allow figure as link
> -
>
> Key: DOXIA-71
> URL: http://jira.codehaus.org/browse/DOXIA-71
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Apt
>Affects Versions: 1.0-alpha-8
> Environment: WinXp, Java5
>Reporter: Martin Zeltner
>
> APT: Allow figure as link.
> Example:
> More information {{{documentation.html}[images/goto.gif] Documentation}}
--
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-71) APT: Allow figure as link
[
http://jira.codehaus.org/browse/DOXIA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated DOXIA-71:
-
Component/s: (was: Core)
Module - Apt
> APT: Allow figure as link
> -
>
> Key: DOXIA-71
> URL: http://jira.codehaus.org/browse/DOXIA-71
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Apt
>Affects Versions: 1.0-alpha-8
> Environment: WinXp, Java5
>Reporter: Martin Zeltner
>
> APT: Allow figure as link.
> Example:
> More information {{{documentation.html}[images/goto.gif] Documentation}}
--
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: (MASSEMBLY-195) unpackOptions ignored
[ http://jira.codehaus.org/browse/MASSEMBLY-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103943 ] Wesley Hartford commented on MASSEMBLY-195: --- I'm seeing this issue using 2.2-beta-1 > unpackOptions ignored > - > > Key: MASSEMBLY-195 > URL: http://jira.codehaus.org/browse/MASSEMBLY-195 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 >Reporter: Todd Wolff > > excludes/includes defined within unpack options of dependency set are > effectively ignored -- 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-131) HtmlTools.encodeId makes id lower case
[
http://jira.codehaus.org/browse/DOXIA-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103942
]
Dennis Lundberg commented on DOXIA-131:
---
Here are the results of a little test I did with aptconvert
APT
{code}
{Anchor}. Link to {{Anchor}}. Link to {{http://www.pixware.fr}}.
Link to {{{Anchor}showing alternate text}}.
Link to {{{http://www.pixware.fr}Pixware home page}}.
{-.:_myAnchor-_.:}
{code}
HTML
{code:xml}
Anchor. Link to
Anchor. Link to
http://www.pixware.fr";>http://www.pixware.fr. Link to
showing alternate text. Link to
http://www.pixware.fr";>Pixware home page.
-.:_myAnchor-_.:
{code}
As you can see characters are converted to lower case and "-_.:" are being
stripped away.
I think that preserving case, like we do now, is the right thing to do. If we
don't it might lead to duplicate ids which is illegal.
We should probably remove the "-_.:" characters though, as they don't have any
value in an id attribute.
> HtmlTools.encodeId makes id lower case
> --
>
> Key: DOXIA-131
> URL: http://jira.codehaus.org/browse/DOXIA-131
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.0-alpha-8
>Reporter: Lukas Theussl
>Assignee: Dennis Lundberg
> Fix For: 1.0-beta-1
>
>
> HtmlTools.encodeId uses Character.toLowerCase to convert its argument to
> lower case. I don't see the reason for that since upper case characters are
> legal in id's (see http://www.w3.org/TR/html4/types.html#type-name ). In
> particular, it's a problem with anchors/links in the xhtml sink (see DOXIA-47
> ), especially if we want to create anchors from section names, to maintain
> backward compatibility with m1. Is there a special reason for the toLowerCase
> or can we remove it?
--
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-131) HtmlTools.encodeId makes id lower case
[
http://jira.codehaus.org/browse/DOXIA-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103941
]
Dennis Lundberg commented on DOXIA-131:
---
I had a look at the original docs for aptconvert and found this interesting
quote:
{quote}
The name of an anchor/link is its text with all non alphanumeric characters
stripped.
{quote}
That suggests that we should be removing these characters ":_.-" from the ids
as well.
I'll give aptconvert a spin and see if I can shed some light on these issues.
> HtmlTools.encodeId makes id lower case
> --
>
> Key: DOXIA-131
> URL: http://jira.codehaus.org/browse/DOXIA-131
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.0-alpha-8
>Reporter: Lukas Theussl
>Assignee: Dennis Lundberg
> Fix For: 1.0-beta-1
>
>
> HtmlTools.encodeId uses Character.toLowerCase to convert its argument to
> lower case. I don't see the reason for that since upper case characters are
> legal in id's (see http://www.w3.org/TR/html4/types.html#type-name ). In
> particular, it's a problem with anchors/links in the xhtml sink (see DOXIA-47
> ), especially if we want to create anchors from section names, to maintain
> backward compatibility with m1. Is there a special reason for the toLowerCase
> or can we remove it?
--
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: (MRM-451) regression: editing a repository on first creation of ~/.m2/archiva.xml doesn't call change listeners
[
http://jira.codehaus.org/browse/MRM-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-451:
-
Priority: Critical (was: Major)
Assignee: Brett Porter
Fix Version/s: 1.0-beta-1
> regression: editing a repository on first creation of ~/.m2/archiva.xml
> doesn't call change listeners
> -
>
> Key: MRM-451
> URL: http://jira.codehaus.org/browse/MRM-451
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-beta-1
>Reporter: Brett Porter
>Assignee: Brett Porter
>Priority: Critical
> Fix For: 1.0-beta-1
>
>
> steps to reproduce:
> - ensure there is no ${appserver.base}/conf/archiva.xml or ~/.m2/archiva.xml
> - start Archiva
> - edit the internal repository to change the path
> - scan the repository
> Expected: the new path is scanned
> Actual: the original (default) path is scanned.
> I expect this is because the change listener is not called in the new 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] Created: (MRM-451) regression: editing a repository on first creation of ~/.m2/archiva.xml doesn't call change listeners
regression: editing a repository on first creation of ~/.m2/archiva.xml doesn't
call change listeners
-
Key: MRM-451
URL: http://jira.codehaus.org/browse/MRM-451
Project: Archiva
Issue Type: Bug
Affects Versions: 1.0-beta-1
Reporter: Brett Porter
Fix For: 1.0-beta-1
steps to reproduce:
- ensure there is no ${appserver.base}/conf/archiva.xml or ~/.m2/archiva.xml
- start Archiva
- edit the internal repository to change the path
- scan the repository
Expected: the new path is scanned
Actual: the original (default) path is scanned.
I expect this is because the change listener is not called in the new 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] Updated: (MRM-450) change default label for repository ID report search to "All repositories" instead of ""
[ http://jira.codehaus.org/browse/MRM-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-450: - Fix Version/s: 1.0-beta-2 > change default label for repository ID report search to "All repositories" > instead of "" > > > Key: MRM-450 > URL: http://jira.codehaus.org/browse/MRM-450 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > -- 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-450) change default label for repository ID report search to "All repositories" instead of ""
change default label for repository ID report search to "All repositories" instead of "" Key: MRM-450 URL: http://jira.codehaus.org/browse/MRM-450 Project: Archiva Issue Type: Improvement Affects Versions: 1.0-beta-1 Reporter: Brett Porter Fix For: 1.0-beta-2 -- 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-449) improvement to the reports form group search
improvement to the reports form group search Key: MRM-449 URL: http://jira.codehaus.org/browse/MRM-449 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0-beta-1 Reporter: Brett Porter if you search for org.apache, it should find org.apache.* -- 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: (MRM-448) validation for reports form
[ http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-448: - Fix Version/s: 1.0-beta-2 > validation for reports form > --- > > Key: MRM-448 > URL: http://jira.codehaus.org/browse/MRM-448 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > validation is missing - see MRM-329 -- 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-447) resolve jasper licensing issue by separating into a profile
resolve jasper licensing issue by separating into a profile --- Key: MRM-447 URL: http://jira.codehaus.org/browse/MRM-447 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-1 Reporter: Brett Porter Fix For: 1.0-beta-1 - put it in a separate module (and profile) that isn't distributed with archiva, but can be built manually and installed - provide a bland, default implementation of the reporting pages that doesn't use jasper (just a spit out a table of everything). -- 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: (MRM-447) resolve jasper licensing issue by separating into a profile
[ http://jira.codehaus.org/browse/MRM-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-447: - Priority: Blocker (was: Major) Assignee: Brett Porter Fix Version/s: 1.0-beta-1 > resolve jasper licensing issue by separating into a profile > --- > > Key: MRM-447 > URL: http://jira.codehaus.org/browse/MRM-447 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Blocker > Fix For: 1.0-beta-1 > > > - put it in a separate module (and profile) that isn't distributed with > archiva, but can be built manually and installed > - provide a bland, default implementation of the reporting pages that doesn't > use jasper (just a spit out a table of everything). -- 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-448) validation for reports form
validation for reports form --- Key: MRM-448 URL: http://jira.codehaus.org/browse/MRM-448 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-1 Reporter: Brett Porter validation is missing - see MRM-329 -- 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-143) improve error reporting on corrupt jars, poms, etc
[ http://jira.codehaus.org/browse/MRM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-143. Resolution: Fixed > improve error reporting on corrupt jars, poms, etc > -- > > Key: MRM-143 > URL: http://jira.codehaus.org/browse/MRM-143 > Project: Archiva > Issue Type: Improvement > Components: indexing >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0-beta-1 > > > currently, many failures can be detected during indexing but none are > reported anywhere other than the logs. Either these need to be sent through > the regular reporting mechanism, or the regular reporting mechanism needs to > be able to come back later and pick up the same 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] Commented: (MRM-329) The Reports link gives an HTTP 500
[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103932 ] Brett Porter commented on MRM-329: -- applied, thanks! > The Reports link gives an HTTP 500 > -- > > Key: MRM-329 > URL: http://jira.codehaus.org/browse/MRM-329 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0-alpha-1 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Teodoro Cue Jr. >Priority: Blocker > Fix For: 1.0-beta-1 > > Attachments: MRM-329-archiva-database-20070725.patch, > MRM-329-archiva-database-20070801.patch, > MRM-329-archiva-model-20070727.patch, MRM-329-archiva-model-20070801.patch, > MRM-329-archiva-webapp-20070725.patch, MRM-329-archiva-webapp-20070801.patch, > MRM-329.patch > > > Clicking the Reports link in the side navigation menu displays the following > (edited/snipped stacktrace): > HTTP ERROR: 500 > RequestURI=/admin/reports.action > Caused by: javax.el.PropertyNotFoundException: The class > 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have > the property 'groupId'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) > at com.sun.el.parser.AstValue.getValue(AstValue.java:118) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) > at > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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-329) The Reports link gives an HTTP 500
[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-329. Resolution: Fixed > The Reports link gives an HTTP 500 > -- > > Key: MRM-329 > URL: http://jira.codehaus.org/browse/MRM-329 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0-alpha-1 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Teodoro Cue Jr. >Priority: Blocker > Fix For: 1.0-beta-1 > > Attachments: MRM-329-archiva-database-20070725.patch, > MRM-329-archiva-database-20070801.patch, > MRM-329-archiva-model-20070727.patch, MRM-329-archiva-model-20070801.patch, > MRM-329-archiva-webapp-20070725.patch, MRM-329-archiva-webapp-20070801.patch, > MRM-329.patch > > > Clicking the Reports link in the side navigation menu displays the following > (edited/snipped stacktrace): > HTTP ERROR: 500 > RequestURI=/admin/reports.action > Caused by: javax.el.PropertyNotFoundException: The class > 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have > the property 'groupId'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) > at com.sun.el.parser.AstValue.getValue(AstValue.java:118) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) > at > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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: (MRM-329) The Reports link gives an HTTP 500
[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103931 ] Brett Porter commented on MRM-329: -- couple of tweaks I'd make: - if you enter org.apache, look for org.apache* - add "(All Repositories)" as the text on the default repository id. > The Reports link gives an HTTP 500 > -- > > Key: MRM-329 > URL: http://jira.codehaus.org/browse/MRM-329 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0-alpha-1 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Teodoro Cue Jr. >Priority: Blocker > Fix For: 1.0-beta-1 > > Attachments: MRM-329-archiva-database-20070725.patch, > MRM-329-archiva-database-20070801.patch, > MRM-329-archiva-model-20070727.patch, MRM-329-archiva-model-20070801.patch, > MRM-329-archiva-webapp-20070725.patch, MRM-329-archiva-webapp-20070801.patch, > MRM-329.patch > > > Clicking the Reports link in the side navigation menu displays the following > (edited/snipped stacktrace): > HTTP ERROR: 500 > RequestURI=/admin/reports.action > Caused by: javax.el.PropertyNotFoundException: The class > 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have > the property 'groupId'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) > at com.sun.el.parser.AstValue.getValue(AstValue.java:118) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) > at > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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-430) Archiva always writes to ~/.m2/archiva.xml
[ http://jira.codehaus.org/browse/MRM-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-430. Resolution: Fixed > Archiva always writes to ~/.m2/archiva.xml > -- > > Key: MRM-430 > URL: http://jira.codehaus.org/browse/MRM-430 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Wendy Smoak >Assignee: Brett Porter > Fix For: 1.0-beta-1 > > > From http://maven.apache.org/archiva/guides/configuration.html : > "When Archiva saves it's configuration, all configuration is stored to > a single file. The file chosen is by the following rules: > * If ~/.m2/archiva.xml exists, it is saved there > * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml, > regardless of whether it previously existed. " > The latest code (r553963) always writes to ~/.m2/archiva.xml, even if it did > not exist, and completely ignores $ARCHIVA_BASE/conf/archiva.xml. > Related thread: > http://www.nabble.com/Archiva-now-always-writes-to-%7E-.m2-archiva.xml-t4053580.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-262) Release pom dependencies are incorrectly rewritten for internal snapshot ranges
[ http://jira.codehaus.org/browse/MRELEASE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103929 ] Sylvain Mougenot commented on MRELEASE-262: --- Affects 2.0-beta-7 also > Release pom dependencies are incorrectly rewritten for internal snapshot > ranges > --- > > Key: MRELEASE-262 > URL: http://jira.codehaus.org/browse/MRELEASE-262 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Mark Hobson > > GenerateReleasePomsPhaseTest.testRewriteInternalRangeDependency fails. -- 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-138) Review and clarify the APT guide
[ http://jira.codehaus.org/browse/DOXIA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103924 ] Denis Cabasson commented on DOXIA-138: -- the guide states : "Section titles are implicitly defined anchors." however, it doesn't seem to be the case. Still for anchors, they are rewritten in minuscule, with spaces distilled to '_'. That should be somewhere in the documentation > Review and clarify the APT guide > > > Key: DOXIA-138 > URL: http://jira.codehaus.org/browse/DOXIA-138 > Project: Maven Doxia > Issue Type: Task > Components: Documentation, Module - Apt >Affects Versions: 1.0-alpha-8 >Reporter: Lukas Theussl > Fix For: 1.0 > > > Our current apt guide is a copy of > http://www.xmlmind.com/_aptconvert/docs/userguide2.html, but there are > several issues that need clarification, eg > * case sensitivity and white space handling in anchors > * anchors for section titles > * figure handling, esp extensions > * tables: is the first line always a header row? > Some of these depend on how things are going to be implemented. > We also decided to remove the apt guide at > http://maven.apache.org/guides/mini/guide-apt-format.html and only keep the > one on the doxia site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1360) Prepended semicolon in svn password does not work
[ http://jira.codehaus.org/browse/CONTINUUM-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103922 ] Jan Lisse commented on CONTINUUM-1360: -- A little addition: The initial download of the pom.xml of my Maven2 project works fine using the same credentials. But when triggering a build the checkout fails with a faulty commandline. Svn complains about missing argument --password. > Prepended semicolon in svn password does not work > - > > Key: CONTINUUM-1360 > URL: http://jira.codehaus.org/browse/CONTINUUM-1360 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-beta-1 > Environment: Suse Linux 10.2, 64-Bit, Java 1.6 >Reporter: Jan Lisse > > If i have a prepended semicolon in my scm (Subversion) password, for example > ";password" Continuum generates a faulty commandline for svn checkout. > Before i used 1.1-alpha-2 with success. So i guess the handling of form input > data has changed in 1.1-beta-1. > I had no time to do further tests, but i guess there are problems with other > special chars too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1360) Prepended semicolon in svn password does not work
Prepended semicolon in svn password does not work - Key: CONTINUUM-1360 URL: http://jira.codehaus.org/browse/CONTINUUM-1360 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1-beta-1 Environment: Suse Linux 10.2, 64-Bit, Java 1.6 Reporter: Jan Lisse If i have a prepended semicolon in my scm (Subversion) password, for example ";password" Continuum generates a faulty commandline for svn checkout. Before i used 1.1-alpha-2 with success. So i guess the handling of form input data has changed in 1.1-beta-1. I had no time to do further tests, but i guess there are problems with other special chars too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-173) Project should be considered a Java project if it has at least one source folder even if the language of its artifact handler is not java
[
http://jira.codehaus.org/browse/MECLIPSE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103921
]
Graham Leggett commented on MECLIPSE-173:
-
The v2.4 plugin contains a patch that forced the project to be considered a
Java project if the PDE mode was enabled.
This in theory should solve this problem.
> Project should be considered a Java project if it has at least one source
> folder even if the language of its artifact handler is not java
> -
>
> Key: MECLIPSE-173
> URL: http://jira.codehaus.org/browse/MECLIPSE-173
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
>Affects Versions: 2.2
>Reporter: Cédric Vidal
> Fix For: 2.5
>
> Attachments: MECLIPSE-173.patch
>
>
> Use case:
> - I have non java source files in src/main/foo (for example a UML model)
> - the "foo" artifact handler builds a zip containing the "foo" source files
> and its language is not "java" (for example the UML model zipped)
> - I have a "bar" plugin which generates "bar" java source files from the
> "foo" source files in target/generated-sources/bar. (for example an MDA
> plugin)
> - The "bar" plugin also builds a jar containing the
> target/generated-sources/bar java source files and attachs it with a "bar"
> classifier.
> So even if the language of my project's artifact handler is not set to
> "java", since my project contains java source code (generated), my project
> should be considered a java project so that it can be referenced in
> multiproject mode by other projects in their build path.
> The effect is obtained by replacing :
> isJavaProject = "java".equals( artifactHandler.getLanguage() ) &&
> !"ear".equals( packaging );
> by
> isJavaProject = ("java".equals(artifactHandler.getLanguage()) ||
> sourceDirs.length > 0)
> && !"ear".equals(packaging);
> and moving the code which builds the sourceDirs from the
> EclipsePlugin#writeConfiguration( IdeDependency[] deps ) to the
> EclipsePlugin#setup() method.
> Regards,
> Cédric
--
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: (MRM-329) The Reports link gives an HTTP 500
[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated MRM-329: Attachment: MRM-329.patch Hi Guys, I've attached the latest patch with changes in my email yesterday on the dev mailing list. Patch is now formatted with Brett's comments taken into consideration. Thanks for the info Brett! Changes: -Taken out Artifact search -Taken out Version link -Repository list now a drop down -Consolidated all the fields into 1 form -Dropped the last 3 columns from the table -Unit tests for all the constraints Lacking: -Unit tests for the actions and the model (can someone help me out as to how to test the action? how do we inject the dao from the test environment?) -Form validation (especially the rowCount, which needs a positive number) -Profile regarding licensing of JasperReports discussed in the dev mailing list Comments are always welcome! :) > The Reports link gives an HTTP 500 > -- > > Key: MRM-329 > URL: http://jira.codehaus.org/browse/MRM-329 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0-alpha-1 >Reporter: Napoleon Esmundo C. Ramirez >Assignee: Teodoro Cue Jr. >Priority: Blocker > Fix For: 1.0-beta-1 > > Attachments: MRM-329-archiva-database-20070725.patch, > MRM-329-archiva-database-20070801.patch, > MRM-329-archiva-model-20070727.patch, MRM-329-archiva-model-20070801.patch, > MRM-329-archiva-webapp-20070725.patch, MRM-329-archiva-webapp-20070801.patch, > MRM-329.patch > > > Clicking the Reports link in the side navigation menu displays the following > (edited/snipped stacktrace): > HTTP ERROR: 500 > RequestURI=/admin/reports.action > Caused by: javax.el.PropertyNotFoundException: The class > 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have > the property 'groupId'. > at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574) > at javax.el.BeanELResolver.getValue(BeanELResolver.java:280) > at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) > at com.sun.el.parser.AstValue.getValue(AstValue.java:118) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) > at > org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143) > at > org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) -- 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-429) Find Artifact does not work when the applet is disabled
[ http://jira.codehaus.org/browse/MRM-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-429. Resolution: Fixed > Find Artifact does not work when the applet is disabled > --- > > Key: MRM-429 > URL: http://jira.codehaus.org/browse/MRM-429 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-2 > Environment: Archiva 1.0-alpha-2, 1.0-alpha-3-SNAPSHOT trunk at > r553362 >Reporter: Wendy Smoak >Assignee: Brett Porter > Fix For: 1.0-beta-1 > > > When the Find Artifact applet is disabled with the following config in > archiva.xml, the feature does not work. > Providing a md5 checksum and clicking 'Go' does nothing. The page re-displays > (without the checksum) and nothing appears in the logs. > > > true > false > > > See MRM-351 for the ability to disable the applet. -- 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-446) find artifact / search by checksum is not working
[ http://jira.codehaus.org/browse/MRM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-446. Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0-beta-1 the applet was generating a capitalised checksum. Changed constraint to always lowercase to match the database. > find artifact / search by checksum is not working > - > > Key: MRM-446 > URL: http://jira.codehaus.org/browse/MRM-446 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0-alpha-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-1 > > > I always get 0 results, even if the artifact being searched from comes > directly from the repository that is already scanned completely. -- 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-446) find artifact / search by checksum is not working
find artifact / search by checksum is not working - Key: MRM-446 URL: http://jira.codehaus.org/browse/MRM-446 Project: Archiva Issue Type: Improvement Affects Versions: 1.0-alpha-2 Reporter: Brett Porter I always get 0 results, even if the artifact being searched from comes directly from the repository that is already scanned completely. -- 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: (MRM-429) Find Artifact does not work when the applet is disabled
[ http://jira.codehaus.org/browse/MRM-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103911 ] Brett Porter commented on MRM-429: -- I'm finding the feature itself isn't working as well > Find Artifact does not work when the applet is disabled > --- > > Key: MRM-429 > URL: http://jira.codehaus.org/browse/MRM-429 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-2 > Environment: Archiva 1.0-alpha-2, 1.0-alpha-3-SNAPSHOT trunk at > r553362 >Reporter: Wendy Smoak > Fix For: 1.0-beta-1 > > > When the Find Artifact applet is disabled with the following config in > archiva.xml, the feature does not work. > Providing a md5 checksum and clicking 'Go' does nothing. The page re-displays > (without the checksum) and nothing appears in the logs. > > > true > false > > > See MRM-351 for the ability to disable the applet. -- 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-445) search functions should show a notification message if an initial scan is still in progress
search functions should show a notification message if an initial scan is still in progress --- Key: MRM-445 URL: http://jira.codehaus.org/browse/MRM-445 Project: Archiva Issue Type: Improvement Components: web application Reporter: Brett Porter Priority: Minor currently, on first run against a new repo, it might take some time for the relevant index or database to be up to date. Any functions that rely on them should be aware that the data is not yet complete and be able to show an appropriate warning instead of the misleading "no results 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: (MRM-428) managed and remote repositories with same name causes problems
[ http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-428: - Fix Version/s: (was: 1.0-beta-1) 1.0-beta-2 scheduling for beta-2 since this is nether a feature or a blocker. I'd like to do a more general configuration/admin review as there are plenty of other similar problems. > managed and remote repositories with same name causes problems > -- > > Key: MRM-428 > URL: http://jira.codehaus.org/browse/MRM-428 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Eli Miller >Priority: Critical > Fix For: 1.0-beta-2 > > > I created both a managed and remote repository entry with the name central -- > the intent was for one to proxy the other. The administrative interfaces did > not gripe about using duplicate names but the proxy did not seem to work. In > the logs I found the following information (which looked suspect): > 328579 [SocketListener0-1] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - > Attempting connector: ProxyConnector[ > source:ArchivaRepository[central,file:/u01/home/proj/.repos/central/] > target:ArchivaRepository[central,file:/u01/home/proj/.repos/central/] > proxyId:mpare > policy[releases]:once > policy[checksum]:fix > policy[snapshots]:disabled > policy[cache-failures]:ignored > ] > When I requested that the remote central repository be deleted, the managed > repository entry was deleted instead. After I removed all central > repositories I created a managed repository named central and a remote > repository named centralExt and the proxying seemed to work as expected. -- 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: (MRM-435) need to review repository defaults
[
http://jira.codehaus.org/browse/MRM-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-435:
-
Description: we should review the use of the appserver path as the default
location, as it is not particularly friendly to seting up as a standalone web
application. I believe there is insufficient error handling to correct this
situation if the user forgets to first set the variables during installation.
(was: when running the appserver, the default is file:/${appserver.home}/...
which is incorrect (it should be pre-filled with the value of appserver.home).
Moreover, it should really be appserver.base, not appserver.home anyway.
)
> need to review repository defaults
> --
>
> Key: MRM-435
> URL: http://jira.codehaus.org/browse/MRM-435
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-beta-1
>Reporter: Brett Porter
> Fix For: 1.0-beta-2
>
>
> we should review the use of the appserver path as the default location, as it
> is not particularly friendly to seting up as a standalone web application. I
> believe there is insufficient error handling to correct this situation if the
> user forgets to first set the variables during installation.
--
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-347) Undefined ${appserver.home} and ${appserver.base}
[
http://jira.codehaus.org/browse/MRM-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRM-347.
Resolution: Fixed
> Undefined ${appserver.home} and ${appserver.base}
> -
>
> Key: MRM-347
> URL: http://jira.codehaus.org/browse/MRM-347
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Environment: Windows, Maven 2.0.6, JDK 5 or JDK 6
>Reporter: Jan Nielsen
>Assignee: Brett Porter
> Fix For: 1.0-beta-1
>
>
> When I run:
> mvn jetty:run
> from trunk at r538691, the "appserver.base" property is undefined, resulting
> in the creation of this directory:
> Directory of C:\dev\apache-maven\archiva\archiva-web\archiva-webapp
> 05/17/2007 02:24 PM ${appserver.base}
> 05/16/2007 11:40 AM 14,681 pom.xml
> 05/16/2007 11:40 AM src
> 05/17/2007 11:06 AM target
--
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: (MRM-444) intermittent test failures on proxy
[ http://jira.codehaus.org/browse/MRM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-444: - Fix Version/s: 1.0-beta-2 > intermittent test failures on proxy > --- > > Key: MRM-444 > URL: http://jira.codehaus.org/browse/MRM-444 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-1 > Environment: mac os x >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > testGetDefaultLayoutAlreadyPresentPolicyIgnored(org.apache.maven.archiva.proxy.ManagedDefaultTransferTest) > Time elapsed: 0.114 sec <<< FAILURE! > junit.framework.AssertionFailedError: Check file timestamp is that of > original managed file: expected within range lo:<1186125890450> > hi:<1186125891550> but was:<1186125892000> > at junit.framework.Assert.fail(Assert.java:47) > at > org.apache.maven.archiva.proxy.ManagedDefaultTransferTest.testGetDefaultLayoutAlreadyPresentPolicyIgnored(ManagedDefaultTransferTest.java:139) -- 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-444) intermittent test failures on proxy
intermittent test failures on proxy --- Key: MRM-444 URL: http://jira.codehaus.org/browse/MRM-444 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-beta-1 Environment: mac os x Reporter: Brett Porter testGetDefaultLayoutAlreadyPresentPolicyIgnored(org.apache.maven.archiva.proxy.ManagedDefaultTransferTest) Time elapsed: 0.114 sec <<< FAILURE! junit.framework.AssertionFailedError: Check file timestamp is that of original managed file: expected within range lo:<1186125890450> hi:<1186125891550> but was:<1186125892000> at junit.framework.Assert.fail(Assert.java:47) at org.apache.maven.archiva.proxy.ManagedDefaultTransferTest.testGetDefaultLayoutAlreadyPresentPolicyIgnored(ManagedDefaultTransferTest.java:139) -- 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] Work started: (MRM-347) Undefined ${appserver.home} and ${appserver.base}
[
http://jira.codehaus.org/browse/MRM-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MRM-347 started by Brett Porter.
> Undefined ${appserver.home} and ${appserver.base}
> -
>
> Key: MRM-347
> URL: http://jira.codehaus.org/browse/MRM-347
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Environment: Windows, Maven 2.0.6, JDK 5 or JDK 6
>Reporter: Jan Nielsen
>Assignee: Brett Porter
> Fix For: 1.0-beta-1
>
>
> When I run:
> mvn jetty:run
> from trunk at r538691, the "appserver.base" property is undefined, resulting
> in the creation of this directory:
> Directory of C:\dev\apache-maven\archiva\archiva-web\archiva-webapp
> 05/17/2007 02:24 PM ${appserver.base}
> 05/16/2007 11:40 AM 14,681 pom.xml
> 05/16/2007 11:40 AM src
> 05/17/2007 11:06 AM target
--
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: (MRM-347) Undefined ${appserver.home} and ${appserver.base}
[
http://jira.codehaus.org/browse/MRM-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103909
]
Brett Porter commented on MRM-347:
--
all good under jetty:run
> Undefined ${appserver.home} and ${appserver.base}
> -
>
> Key: MRM-347
> URL: http://jira.codehaus.org/browse/MRM-347
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Environment: Windows, Maven 2.0.6, JDK 5 or JDK 6
>Reporter: Jan Nielsen
> Fix For: 1.0-beta-1
>
>
> When I run:
> mvn jetty:run
> from trunk at r538691, the "appserver.base" property is undefined, resulting
> in the creation of this directory:
> Directory of C:\dev\apache-maven\archiva\archiva-web\archiva-webapp
> 05/17/2007 02:24 PM ${appserver.base}
> 05/16/2007 11:40 AM 14,681 pom.xml
> 05/16/2007 11:40 AM src
> 05/17/2007 11:06 AM target
--
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
